Ir al contenido

State of HTML 2025

Accesibilidad

Sitios y aplicaciones accesibles para todos.

We're highlighting up-and-coming features or libraries we think you should know about.

Feature Highlight: <search>

The <search> element is one of those easy wins that take very little effort to add to your list of best practices. Step 1: use it to denote any search field in your apps. Step 2: well that's it really!

And now that it's supported in all four major browsers, there's really no reason not to be using it.

Baseline: Newly Available

Learn more

Useful Resources

Funciones de accesibilidad

Landmark elements (<main>, <nav>, etc.) aren't very new or exciting but they remain a foundation of web accessibility.

Group by:

Sort by:

1
Accesibilidad
96.7%
4,383
2
Accesibilidad
88.2%
8%
4,381
3
Accesibilidad
29.3%
29.1%
41.2%
4,377
4
Accesibilidad
13%
22.5%
64.3%
4,378

Experience

  • 👍 Lo he usado: Respondents who have used an item.
  • ✅ Lo conozco: Respondents who have heard about an item, but haven't used it.
  • 🤷 Nunca he oído hablar de ello: Respondents who have never heard about an item.

Sentiment

  • Positive: Respondents who are interested in learning more about a technology; or are willing to use it again.
  • Neutral: Responents who did not indicate any sentiment about a technology.
  • Negative: Respondents who are not interested in learning more about a technology; or have used it and had a negative experience.
“Used” average:57%
“Positive” average:37%
“Negative” average:2%

Otras técnicas de accesibilidad

While things like alt text or proper heading hierarchy have become second nature to most front-end developers, newer tools like the prefers- set of media queries have yet to truly become mainstream.

¿Qué otras técnicas forman parte de su estrategia habitual de accesibilidad?
Multiple
0%
20%
40%
60%
80%
100%
1
Texto descriptivo `alt
3,647
2
Jerarquía de la información
3,452
3
Etiquetas de control de formularios
3,331
4
Texto de enlace significativo
+1
2,827
5
Contraste suficiente
+1
2,778
6
Anillo de enfoque visible
+1
2,725
7
Navegación intuitiva con el teclado
-3
2,454
8
<fieldset> y <legend>
+2
2,250
9
No depender sólo del puntero
2,194
10
No depender sólo del color
-2
2,192
0%
20%
40%
60%
80%
100%
% de respuestas respondidas
4,124
66%
10

Discapacidades de los usuarios

It's nice to see that beyond accounting for users with vision impairments, more developers are also taking atypical color vision and mobility impairments into account compared to last year.

¿Qué tipo de discapacidades tienen en cuenta los usuarios al crear sitios web?
Multiple
0%
20%
40%
60%
80%
100%
1
Baja visión
2,724
2
Visión atípica de los colores
2,163
3
Problemas de movilidad
1,387
4
Trastornos vestibulares
920
5
Deficiencias auditivas
687
6
Problemas de aprendizaje
677
7
🚫 None
665
8
Otras deficiencias cognitivas
600
9
Other Answers
52
0%
20%
40%
60%
80%
100%
% de respuestas respondidas
3,727
60%
10

Lectores de pantalla

Once again, easily accessible tools like VoiceOver or the Chrome DevTools win over more specialized options. Although many developers still don't use screen readers of any kind (also note that 39% of survey respondents skipped the question altogether).

¿Qué lectores de pantalla utiliza para las pruebas de accesibilidad?
Multiple
0%
20%
40%
60%
80%
100%
1
VoiceOver
+1
1,376
2
🚫 None
1,358
3
Chrome DevTools
-1
1,306
4
NVDA
742
5
JAWS
414
6
WAVE
366
7
TalkBack
216
8
Narrator
199
9
Orca
137
10
Chromevox
88
11
Firefox Accessibility Inspector
12
Other Answers
51
0%
20%
40%
60%
80%
100%
% de respuestas respondidas
3,784
61%
10

Herramientas de accesibilidad

Browser devtools have seen a huge jump in usage compared to last year's results, seeing them overtake Lighthouse to become the lead accessibility testing tool.

¿Qué herramientas utiliza para las pruebas de accesibilidad?
Multiple
0%
20%
40%
60%
80%
100%
1
Browser Devtools
+1
2,259
2
Lighthouse
-1
1,983
3
Axe
1,145
4
Firefox Accessibility Inspector
1,033
5
🚫 None
-1
717
6
WAVE
+1
648
7
-1
544
8
Accessibility Insights
523
9
Pa11y
+1
188
10
Arc
-1
167
0%
20%
40%
60%
80%
100%
% de respuestas respondidas
3,860
62%
10

Puntos débiles de la accesibilidad

While there are technical gaps when it comes to accessibility (e.g. cross-root ARIA), a recurring theme whenever we ask about it is that the main pain points are around the humans involved with issues around workplace priorities, education, and cognitive overhead topping the list.

¿Cuáles son sus mayores dificultades en materia de accesibilidad web?
Multiple
Top pain point topics overall.

View:

Items that are not one of “limitations”
0%
20%
40%
60%
80%
100%
1
Education
3
2
workplace
1
3
Cognitive overload
2
4
Debugging
1
5
Environments & Consumers
6
Screen reader issues
2
7
ARIA
1
8
Browser support
1
9
Low priority
-7
10
Tooling
2
11
Excessive complexity
-2
12
Keyboard navigation
13
Standards & Specs
1
14
Focus management
-3
15
16
Missing elements
17
Ecosystem issues
18
Content
1
19
Accessible visual design
20
Reliance on JavaScript
21
Access to screen readers
+3
22
Component-Based Architecture
23
Invalid/Spam
24
CSS Integration
25
26
Other Answers
0%
20%
40%
60%
80%
100%
% de respuestas respondidas
606
10%
25
5

Recursos recomendados

Website Accessibility, v3
Jon Kuperman
Bloomberg

Website Accessibility, v3

Build content for everyone and become your company's accessibility expert! Learn the importance of semantic HTML and alt text for ensuring screen readers can navigate your site.
¡Gracias a nuestros socios por apoyarnos! Aprende más.