Skip to main content
The HTML Tags Checker provides full bilingual support, allowing you to use the tool in either Spanish or English with seamless language switching.

Available Languages

The validator supports two languages:

Spanish (ES)

Default language with complete Spanish translations for all interface elements, messages, and documentation.

English (EN)

Full English translations matching the Spanish interface with culturally appropriate examples.

Switching Languages

1

Locate the language selector

The language toggle buttons appear in the top-right corner of the page:
[ES] [EN]
The active language is highlighted.
2

Click your preferred language

Click ES for Spanish or EN for English. The interface updates immediately.
3

Language persists in URL

Your language choice is saved in the URL parameter lang=es or lang=en, so bookmarks and shared links preserve the language.

What Gets Translated

When you switch languages, the following elements update automatically:

Interface Elements

  • Título: HTML Tag Validator
  • Subtítulo: Verifica si una etiqueta HTML puede contener a otra según los estándares W3C
  • Etiqueta Padre: Input label for parent tag
  • Etiqueta Hija: Input label for child tag
  • Validar: Submit button text
  • Ver reglas de anidamiento: Button to open rules guide

Validation Results

Result titles and statuses adapt to your language:
EnglishSpanish
AllowedPermitido
Not allowedNo permitido
Allowed with warningPermitido con advertencia

Validation Messages

All validation messages are fully translated with context-appropriate explanations:
La etiqueta <div> es un elemento de bloque y puede contener 
elementos de bloque o en línea como <p>.
The <div> tag is a block element and can contain block or 
inline elements like <p>.

Code Examples

Even code comments are translated:
<!-- Esto no es válido según los estándares HTML5 -->
<p>
  <div>Contenido de ejemplo</div>
</p>

Nesting Rules Guide Translation

The comprehensive nesting rules modal is fully translated, including:

Section Headings

  • Element categories
  • Specific nesting rules by element
  • Best practices for valid HTML
  • Common patterns to avoid
  • Validation tools

Category Descriptions

Spanish: Los elementos de bloque establecen la estructura del documento.English: Block elements establish the document structure.

Element-Specific Rules

Each element’s rules include translated descriptions:
  • Pueden contener: Solo contenido en línea (texto y elementos en línea)
  • No pueden contener: Elementos de bloque

Accessibility Features

Language switching includes proper accessibility support:

ARIA Attributes

<button class="language-option active" 
        data-lang="es" 
        type="button" 
        aria-pressed="true">ES</button>
  • aria-pressed="true" indicates the active language
  • Language buttons update screen reader announcements
  • lang attribute on <html> updates to match selection

HTML Lang Attribute

When you switch languages:
<!-- Spanish -->
<html lang="es">

<!-- English -->
<html lang="en">
This ensures:
  • Screen readers use the correct pronunciation
  • Browser translation features work properly
  • Search engines index the correct language

Default Language Behavior

The validator determines your initial language using this priority:
1

URL parameter

If ?lang=en or ?lang=es is in the URL, that language is used.
2

Default to Spanish

If no URL parameter exists, Spanish (ES) is the default language.
3

Invalid values

If the URL contains an invalid language code, it defaults to Spanish.
The default language is Spanish because this tool was created for the Spanish-speaking web development community at aprendoeasy.com.

Language Persistence

Your language choice is maintained throughout your session:
  • URL updates: Every validation updates the URL with your current language
  • Page navigation: Bookmarked URLs preserve the language setting
  • Shared links: When you share a validation link, the language is included
https://example.com/index.html?parent=div&child=p&lang=en
Language preference is stored in the URL, not in cookies or localStorage, ensuring privacy and making links fully shareable.

Build docs developers (and LLMs) love