Skip to content
https://aepd.es

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ 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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
9 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link
Labeled Navigation 9 <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
61 landmarks
REVIEW
61 landmarks
Info::
<main> landmark present
Info::
9 <nav> landmark(s) found
Warning::
2 of 9 <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.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV SEARCH 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
6 of 45 images have issues
REVIEW
6 of 45 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Warning::
5 image(s) with filename as alt text
Info::
14 decorative image(s) correctly marked
Info::
25 image(s) with good alt text
45 images 25 good alt text 14 decorative 5 generic 1 missing
IssueCount
missing1 image(s)
filename5 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
3 of 5 controls have issues
REVIEW
3 of 5 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" id="edit-submit-solr-general-contents">; <input type="submit" id="edit-submit-agenda-eventos-solr">; <input type="submit" name="op" id="edit-reset">
Info::
2 control(s) properly labeled
5 controls
2 labeled
0 placeholder only
3 unlabeled
ControlTypeLabelMethod
#edit-searchsearchBuscador generalfor/id
#edit-date-recurtextFecha recurrentefor/id
#edit-submit-solr-general-contentssubmit(none)none
#edit-submit-agenda-eventos-solrsubmit(none)none
#edit-resetsubmit(none)none

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

<input type="submit" id="edit-submit-solr-general-contents">; <input type="submit" id="edit-submit-agenda-eventos-solr">; <input type="submit" name="op" id="edit-reset">

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

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h2 Recomendaciones para proteger la privaci…
1.08:1
#000000
on
#180909
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Plan de actuación 2026 e Informe de cum…
1.08:1
#000000
on
#180909
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Principios básicos para la contratació…
1.08:1
#000000
on
#180909
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Recomendaciones para proteger la privaci…
1.08:1
#000000
on
#180909
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Plan de actuación 2026 e Informe de cum…
1.08:1
#000000
on
#180909
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Principios básicos para la contratació…
1.08:1
#000000
on
#180909
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Recomendaciones para proteger la privaci…
1.08:1
#000000
on
#180909
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Destacados
1.08:1
#000000
on
#180909
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Agenda
1.08:1
#000000
on
#180909
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Laboratorio de Privacidad AEPD
1.08:1
#000000
on
#180909
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Información práctica
1.08:1
#000000
on
#180909
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Enlaces de interés
1.08:1
#000000
on
#180909
needs 3.0:1 (large text)
24px · bottom of viewport
h3 El Comité Europeo de Protección de Dat…
1.08:1
#000000
on
#180909
needs 3.0:1 (large text)
19px · bottom of viewport
h3 La Agencia incorpora nuevos contenidos a…
1.08:1
#000000
on
#180909
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Jornada ‘10º aniversario del RGPD …
1.08:1
#000000
on
#180909
needs 3.0:1 (large text)
19px · bottom of viewport
h3 El presidente de la AEPD, Lorenzo Cotino…
1.08:1
#000000
on
#180909
needs 3.0:1 (large text)
19px · bottom of viewport
h3 La AEPD participa en una acción europea…
1.08:1
#000000
on
#180909
needs 3.0:1 (large text)
19px · bottom of viewport
h3 La AEPD promueve el uso responsable de l…
1.08:1
#000000
on
#180909
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Resultados del European Blockchain Sandb…
1.08:1
#000000
on
#180909
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Nuevo episodio de ‘Diálogos de privac…
1.08:1
#000000
on
#180909
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Recomendaciones para…1.08:13.0:1
#000000
#180909
Fail
h2 Plan de actuación 2…1.08:13.0:1
#000000
#180909
Fail
h2 Principios básicos …1.08:13.0:1
#000000
#180909
Fail
h2 Recomendaciones para…1.08:13.0:1
#000000
#180909
Fail
h2 Plan de actuación 2…1.08:13.0:1
#000000
#180909
Fail
h2 Principios básicos …1.08:13.0:1
#000000
#180909
Fail
h2 Recomendaciones para…1.08:13.0:1
#000000
#180909
Fail
h2 Destacados1.08:13.0:1
#000000
#180909
Fail
h2 Agenda1.08:13.0:1
#000000
#180909
Fail
h2 Laboratorio de Priva…1.08:13.0:1
#000000
#180909
Fail
h2 Información prácti…1.08:13.0:1
#000000
#180909
Fail
h2 Enlaces de interés1.08:13.0:1
#000000
#180909
Fail
h3 El Comité Europeo d…1.08:13.0:1
#000000
#180909
Fail
h3 La Agencia incorpora…1.08:13.0:1
#000000
#180909
Fail
h3 Jornada ‘10º aniv…1.08:13.0:1
#000000
#180909
Fail
h3 El presidente de la …1.08:13.0:1
#000000
#180909
Fail
h3 La AEPD participa en…1.08:13.0:1
#000000
#180909
Fail
h3 La AEPD promueve el …1.08:13.0:1
#000000
#180909
Fail
h3 Resultados del Europ…1.08:13.0:1
#000000
#180909
Fail
h3 Nuevo episodio de …1.08:13.0:1
#000000
#180909
Fail

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.

B
Lighthouse Accessibility Audits
Score 82/100 — 7 failing, 30 passed
REVIEW
82

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.

ARIA

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
30 table.table-condensed > tbody > tr > td.old
31 table.table-condensed > tbody > tr > td.old
1 table.table-condensed > tbody > tr > td.disabled
2 table.table-condensed > tbody > tr > td.disabled
3 table.table-condensed > tbody > tr > td.disabled
4 table.table-condensed > tbody > tr > td.disabled
5 table.table-condensed > tbody > tr > td.disabled
6 table.table-condensed > tbody > tr > td.day
7 table.table-condensed > tbody > tr > td.day
8 table.table-condensed > tbody > tr > td.disabled
9 table.table-condensed > tbody > tr > td.day
10 table.table-condensed > tbody > tr > td.disabled
11 table.table-condensed > tbody > tr > td.disabled
12 table.table-condensed > tbody > tr > td.disabled
13 table.table-condensed > tbody > tr > td.day
14 table.table-condensed > tbody > tr > td.disabled
15 table.table-condensed > tbody > tr > td.disabled
16 table.table-condensed > tbody > tr > td.day
17 table.table-condensed > tbody > tr > td.day
18 table.table-condensed > tbody > tr > td.disabled
19 table.table-condensed > tbody > tr > td.disabled
20 table.table-condensed > tbody > tr > td.day
21 table.table-condensed > tbody > tr > td.day
22 table.table-condensed > tbody > tr > td.disabled
23 table.table-condensed > tbody > tr > td.disabled
24 table.table-condensed > tbody > tr > td.disabled
25 table.table-condensed > tbody > tr > td.disabled
26 table.table-condensed > tbody > tr > td.disabled
27 table.table-condensed > tbody > tr > td.disabled
28 table.table-condensed > tbody > tr > td.disabled
29 table.table-condensed > tbody > tr > td.disabled
30 table.table-condensed > tbody > tr > td.disabled
1 table.table-condensed > tbody > tr > td.new
2 table.table-condensed > tbody > tr > td.new
3 table.table-condensed > tbody > tr > td.new
4 table.table-condensed > tbody > tr > td.new
5 table.table-condensed > tbody > tr > td.new
6 table.table-condensed > tbody > tr > td.new
7 table.table-condensed > tbody > tr > td.new
8 table.table-condensed > tbody > tr > td.new
9 table.table-condensed > tbody > tr > td.new
10 table.table-condensed > tbody > tr > td.new

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
30 table.table-condensed > tbody > tr > td.old
31 table.table-condensed > tbody > tr > td.old
10 table.table-condensed > tbody > tr > td.disabled
11 table.table-condensed > tbody > tr > td.disabled
12 table.table-condensed > tbody > tr > td.disabled
14 table.table-condensed > tbody > tr > td.disabled
15 table.table-condensed > tbody > tr > td.disabled
18 table.table-condensed > tbody > tr > td.disabled
19 table.table-condensed > tbody > tr > td.disabled
22 table.table-condensed > tbody > tr > td.disabled
23 table.table-condensed > tbody > tr > td.disabled
24 table.table-condensed > tbody > tr > td.disabled
25 table.table-condensed > tbody > tr > td.disabled
26 table.table-condensed > tbody > tr > td.disabled
27 table.table-condensed > tbody > tr > td.disabled
28 table.table-condensed > tbody > tr > td.disabled
29 table.table-condensed > tbody > tr > td.disabled
30 table.table-condensed > tbody > tr > td.disabled
10 table.table-condensed > tbody > tr > td.new

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.content > div.field > div.field__item > img#img-88395 div.content > div.field > div.field__item > img#img-88395

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.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
body.is-mobile > meta body.is-mobile > meta

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1 div#slick-block-content-highlighted-content-lista-contenidos-full-45-2-slider > ul.slick-dots > li.slick-active > button#slick-slide-control10

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Ver más información div > div.view > div.more-link > a

Screen readers have features to make navigating tables easier. Ensuring that tables use the actual caption element instead of cells with the `[colspan]` attribute may improve the experience for screen reader users. Learn more about captions.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
<< Retroceder en el calendario Abril 2026 >> Avanzar en el calendario Lu M… div#datepicker-always-visible-home > div.datepicker > div.datepicker-days > table.table-condensed
○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-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
●Input buttons have discernible text.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Links have a discernible name
●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
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
●`<td>` elements in a large `<table>` have one or more table headers.
○`[accesskey]` values are unique
○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
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
A+
Heading Hierarchy
52 headings
PASS
52 headings
Info::
Single H1 present
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 (empty)
  • H2 Recomendaciones para proteger la privacidad al usar herramientas de IA
  • H2 Plan de actuación 2026 e Informe de cumplimiento 2025
  • H2 Principios básicos para la contratación y el uso de plataformas educativas digitales
  • H2 Recomendaciones para proteger la privacidad al usar herramientas de IA
  • H2 Plan de actuación 2026 e Informe de cumplimiento 2025
  • H2 Principios básicos para la contratación y el uso de plataformas educativas digitales
  • H2 Recomendaciones para proteger la privacidad al usar herramientas de IA
  • H2 Destacados
  • H3 El Comité Europeo de Protección de Datos somete a consulta pública sus Directrices sobre el tratamiento de datos personales con fines de investigación científica
  • H3 La Agencia incorpora nuevos contenidos a su asistente virtual
  • H3 Jornada ‘10º aniversario del RGPD (2016-2026): Una década de retos y desafíos’
  • H3 El presidente de la AEPD, Lorenzo Cotino, premiado en la categoría de Investigación en Derecho digital de los Premios ENATIC
  • H3 La AEPD participa en una acción europea para analizar el cumplimiento de las obligaciones de transparencia e información por parte de las organizaciones
  • H3 La AEPD promueve el uso responsable de la IA con una iniciativa sobre deepfakes
  • H3 Resultados del European Blockchain Sandbox
  • H3 Nuevo episodio de ‘Diálogos de privacidad'
  • H3 Resultados de la acción europea que ha analizado la atención del ejercicio del derecho de supresión por parte de los responsables
  • H3 La Agencia publica unas orientaciones sobre Inteligencia Artificial agéntica desde la perspectiva de protección de datos
  • H3 Herramienta para el uso responsable de IA en las Administraciones Públicas
  • H3 El uso de imágenes de terceros en sistemas de inteligencia artificial y sus riesgos visibles e invisibles
  • H3 Lorenzo Cotino charla con Nuria Oliver
  • H3 Desarrollo práctico de la Política general interna para el uso de la IA generativa en la AEPD
  • H3 La Agencia publica su Política interna de uso de IA, la primera de este tipo en el sector público
  • H2 Agenda
  • H3 Privacy Symposium 2026
  • H3 VI Congreso Internacional de Derecho Bancario
  • H3 Reunión con la directora del DSN
  • H3 The Wave 2026
  • H3 The DMA Meets the Cloud: Gatekeepers and Beyond
  • H3 Presentación del Laboratorio de Ideas de AESIA
  • H3 El blog de la Agencia
  • H3 Transcripción de voz con IA (II): responsabilidad, derechos y transparencia
  • H2 Laboratorio de Privacidad AEPD
  • H2 Información práctica
  • H3 Conoce tus derechos
  • H3 Criterios jurídicos AEPD
  • H3 Facilita RGPD
  • H3 Preguntas Frecuentes
  • H3 Registro DPD
  • H3 Notificación de brechas de datos personales
  • H3 Asesora Brecha
  • H3 Comunica-Brecha RGPD
  • H3 Certificación DPD
  • H3 Consultas previas
  • H3 Transparencia
  • H3 Canal del DPD
  • H3 Gestiona RGPD
  • H3 Facilita EMPRENDE
  • H3 ValidaCripto RGPD
  • H2 Enlaces de interés
  • H2 Recomendaciones para un uso seguro del cifrado

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

A
404 Error Page
HTTP 404, custom page
PASS
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Página no encontrada | AEPD ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback