Skip to content
https://spain.info

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
51
GRADE
F
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
F
404 Error Page
Action
HTTP 403, custom page
FIX
HTTP 403, custom page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 403 ✗Page Title Voight-Kampff Browser Test ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
4 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 4 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
9 landmarks
REVIEW
9 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
4 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

B
Alt Text Quality
3 of 161 images have issues
REVIEW
3 of 161 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Warning::
2 image(s) with generic alt text
Info::
3 image(s) with alt text over 125 characters
Info::
3 decorative image(s) correctly marked
Info::
152 image(s) with good alt text
161 images 152 good alt text 3 decorative 2 generic 1 missing
IssueCount
missing1 image(s)
generic2 image(s)
too long3 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

C
Form Accessibility
Action
5 of 13 controls have issues
REVIEW
5 of 13 controls have issues
Critical::
5 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">; <input type="submit">; <input type="submit">; <input type="submit">; <input type="button" id="verRuta">
Info::
8 control(s) properly labeled
13 controls
8 labeled
0 placeholder only
5 unlabeled
ControlTypeLabelMethod
qsearchBuscararia-label
qsearchBUSCAR OTROS DESTINOSaria-label
#buscadorRelMapaSimpletext(buscar otros destinos)for/id
qsearchBUSCAR OTROS DESTINOSaria-label
#origentextOrigenfor/id
#destinotextDestinofor/id
#eventosFechaselect¿Cuándo viajas?for/id
#selectMunicipioinput(buscar otros destinos)for/id
inputsubmit(none)none
inputsubmit(none)none
inputsubmit(none)none
#verRutabutton(none)none
inputsubmit(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="submit">; <input type="submit">; <input type="submit">; <input type="submit">; <input type="button" id="verRuta">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

A+
Heading Hierarchy
40 headings
PASS
40 headings
Info::
Single H1 present
  • H1 Portal oficial de turismo de España
  • H2 No te lo puedes perder
  • H3 Alguno de los jardines botánicos más alucinantes que vas a ver
  • H3 2026: el año en el que "empiezan" los eclipses
  • H3 Buen momento para dejarse sorprender por la vida salvaje
  • H3 Microescapadas en tren hacia la España menos conocida
  • H3 ¿Qué tipo de viajero eres? Encuentra las vacaciones que encajan más contigo
  • H2 Otras ideas para tu viaje
  • H2 Joyas del interior de España que aún no has descubierto
  • H3 Rutas para los amantes de la fotografía
  • H3 Arte en libertad: land art en los paisajes más bellos
  • H3 Día Internacional de los Museos
  • H2 Más formas de conocer España
  • H2 Inspírate en nuestras redes sociales
  • H2 Netflix & Turespaña
  • H2 Sumérgete en nuestra cultura
  • H2 Planificador de rutas
  • H2 Disfruta de los mejores eventos
  • H2 Transvulcania - Ultramaratón de montaña y senderismo
  • H2 Exposición: Yoko Ono. Insound and Instructure
  • H2 Salón Internacional del Cómic
  • H2 Feria del Caballo
  • H2 Festival WOMAD Cáceres
  • H2 Festival de los patios cordobeses
  • H2 Transvulcania - Ultramaratón de montaña y senderismo
  • H2 Exposición: Yoko Ono. Insound and Instructure
  • H2 Salón Internacional del Cómic
  • H2 Feria del Caballo
  • H2 Festival WOMAD Cáceres
  • H2 Festival de los patios cordobeses
  • H2 Transvulcania - Ultramaratón de montaña y senderismo
  • H2 Exposición: Yoko Ono. Insound and Instructure
  • H2 Salón Internacional del Cómic
  • H2 Feria del Caballo
  • H2 Toda la información útil que necesitas
  • H3 Cómo llegar
  • H3 Folletos
  • H3 Cómo moverse
  • H3 Información práctica
  • H2 Las mejores ideas para viajar por España
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Portal oficial de tu…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 No te lo puedes perd…8.91:13.0:1
#000000
#A6AB9A
Pass
h2 Otras ideas para tu …8.91:13.0:1
#000000
#A6AB9A
Pass
h2 Joyas del interior d…8.91:13.0:1
#000000
#A6AB9A
Pass
h2 Más formas de conoc…8.91:13.0:1
#000000
#A6AB9A
Pass
h2 Inspírate en nuestr…8.91:13.0:1
#000000
#A6AB9A
Pass
h2 Netflix & Turespaña8.91:13.0:1
#000000
#A6AB9A
Pass
h2 Sumérgete en nuestr…8.91:13.0:1
#000000
#A6AB9A
Pass
h2 Planificador de ruta…8.91:13.0:1
#000000
#A6AB9A
Pass
h2 Disfruta de los mejo…8.91:13.0:1
#000000
#A6AB9A
Pass
h2 Transvulcania - Ultr…8.91:13.0:1
#000000
#A6AB9A
Pass
h2 Exposición: Yoko On…8.91:13.0:1
#000000
#A6AB9A
Pass
h2 Salón Internacional…8.91:13.0:1
#000000
#A6AB9A
Pass
h2 Feria del Caballo8.91:13.0:1
#000000
#A6AB9A
Pass
h2 Festival WOMAD Cáce…8.91:13.0:1
#000000
#A6AB9A
Pass
h2 Festival de los pati…8.91:13.0:1
#000000
#A6AB9A
Pass
h2 Transvulcania - Ultr…8.91:13.0:1
#000000
#A6AB9A
Pass
h2 Exposición: Yoko On…8.91:13.0:1
#000000
#A6AB9A
Pass
h2 Salón Internacional…8.91:13.0:1
#000000
#A6AB9A
Pass
h2 Feria del Caballo8.91:13.0:1
#000000
#A6AB9A
Pass

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

A+
Lighthouse Accessibility Audits
Score 97/100 — 1 failing, 30 passed
PASS
97

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
MADRID div#slider-mobile-home > div.slick-list > div.slick-track > a#slick-slide10

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[role]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Input buttons have discernible text.
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
○`[accesskey]` values are unique
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○`<input type="image">` elements have `[alt]` text
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○Elements with visible text labels have matching accessible names.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback