Cómo comprobar y garantizar la accesibilidad de una página web

 

Visual crowding

El término Visual crowding lo he descubierto recientemente. El artículo de la Wikipedia que lo explica solo está en inglés. En una página web sobre un proyecto financiado por la Unión Europea se denomina como "aglomeración visual".

"Visual crowding" es un fenómeno que afecta al reconocimiento de estímulos en situaciones desordenadas, como una letra en una palabra o una palabra en un texto.

Parece que existe cierta relación entre la "aglomeración visual" y la dislexia:

• Abnormal visual crowding and developmental dyslexia: Cause or effect?
• Is excessive visual crowding causally linked to developmental dyslexia?

Y Microsoft proporciona dos tipos de letra que tienen el propósito de ayudar a las personas con "aglomeración visual": Microsoft Fluent Calibri and Sitka. 

Las capas de accesibilidad deberían ser para los usuarios finales, no para los sitios web

Una reflexión muy interesante sobre las capas de accesibilidad en Overlays Misunderstand Accessibility:

To talk about this subject, let’s start with a hypothetical. We’ll hypothesize that accessibility overlays perfectly solve all accessibility problems on a site. Let’s imagine a future world where the technology used by an accessibility overlay is able to magically transform a user’s experience on a website from a completely blocking experience to something absolutely delightful.

Yeah, it’s a long-shot hypothesis. But work with me, here.

Even in that situation, I would continue to oppose accessibility overlays, for one simple reason:

If it’s so amazing, why isn’t it sold to people with disabilities as assistive technology?

Características de accesibilidad de los captcha actuales

En How to Make CAPTCHA Accessible: A Hands-On GuideHow to Make CAPTCHA Accessible: A Hands-On Guide se comentan las principales características de accesibilidad de los captcha actuales:

CAPTCHA systems are tests that protect websites from automated threats by checking whether the visitor is a human or a bot. However, these systems can create barriers for people with visual, auditory, or cognitive impairments, making some CAPTCHAs challenging to navigate.

Despite the possible accessibility issues, the Web Content Accessibility Guidelines (WCAG) permit the use of CAPTCHAs, but only if they add certain accessible features. This ensures that security measures do not exclude users with disabilities.

In this article, you’ll learn all about implementing CAPTCHA systems that are as accessible as possible. However, it’s important to remember that no matter how accessible or transparent your CAPTCHA is, it will never be perfect – valid interactions will still be marked as unwanted and bots will still be able to pierce your site’s defences.

For that reason, we’ll also introduce alternative solutions that offer greater security and inclusivity, adhering to the highest standards of web accessibility to improve the experience for all users.

¿Se aplica WCAG 2.2 a las aplicaciones nativas?

En Does WCAG 2.2 apply to native apps se analizan los criterios de WCAG 2.2 que se deben aplicar a las aplicaciones nativas desarrolladas con:

• Android
• Jetpack Compose
• iOS
• SwiftUI
• Flutter
• React Native
• .NET MAUI
• Xamarin

Congreso Latinoamericano de Accesibilidad y Usabilidad

Me ha llegado el aviso de la próxima celebración del Segundo Congreso Latinoamericano de Accesibilidad y Usabilidad. En el formulario de inscripción pone:

Nos encontraremos el viernes 8 y sábado 9 de noviembre para compartir un espacio de talleres, charlas y debates, 100% online. Se transmitirá a través de Zoom y contará con intérpretes de lengua de señas y transcripciones.

Los diferentes tipos de zoom en una página web

En Zoom, zoom, and zoom - The three types of browser (and CSS!) magnification se explica:

In brief: there is wide support for three different types of ‘zoom’ – available both to site visitors and (to some extent) CSS authors:

• Page zoom is the default with a handy keyboard shortcut, and roughly matches behavior of the CSS zoom property.
• Scale factor (or ‘pinch zoom’) was introduced by early versions of mobile Safari, and may only be available through trackpad or touch interfaces – roughly matching the behavior of the CSS scale transform.
• Text-only zoom is also provided by Firefox and Safari. While not directly available in CSS, the behavior is similar to changing default font size on a site that uses entirely relative text sizing with rem units.

Aplicación del árbol de decisión de la norma EN 301 549 sobre app eBiblio

Cuatro vídeos muy interesantes en los que se aplica el árbol de decisión para comprobar el cumplimiento de la norma EN 301 549 (v3.1.1) por parte de eBiblio, una aplicación para solicitar en préstamo recursos digitales de bibliotecas públicas:

Nuevos criterios de accesibilidad para dispositivos móviles en WCAG 2.2

 

Cómo escribir enlaces que sean accesibles para todos

En How to Build on Basic Principles of Link Accessibility: In-depth StrategiesHow to Build on Basic Principles of Link Accessibility: In-depth Strategies se proporciona una buena explicación sobre cómo escribir enlaces que sean accesibles para todos:

Hypertext links, also known as hyperlinks, are the connective strands that form the web. They take us from one webpage to another, giving us access to a wide range of information, services, and experiences. However, we often forget to think about link accessibility.

Links are important for individuals of all abilities, including those who depend on screen readers or keyboard navigation. When used effectively, links can improve the browsing experience for everyone. However, if overlooked, they can create obstacles that reduce accessibility and usability.

Nuevos criterios de accesibilidad para dispositivos móviles en WCAG 2.1

 

Barreras que se crean cuando se usa mal ARIA para mejorar la accesibilidad

En Best intention barriers (ARIA edition) se indican varias barreras que se crean cuando se usa mal ARIA para mejorar la accesibilidad:

• Adding aria-label as some form of accessible description
• Adding an ARIA Role is enough, or: Adding ARIA implements functionality
• Roles that are not what you think they are

Canadá adopta EN 301 549:2021

Desde el 31 de mayo de 2024, Canadá ha adoptado la Norma EN 301 549 V3.2.1 (2021) como estándar: CAN/ASC - EN 301 549:2024 Accessibility requirements for ICT products and services (EN 301 549:2021, IDT).

Más información:

• Our standard on Accessibility requirements for ICT products and services
• Accessibility Standards Canada adopts the globally recognized accessibility standard for ICT products and services

Muy poco contraste

Mis ojos no pueden creen lo que no ven. Ahí se supone que pone SERVICIOS:

Otra opinión (negativa) sobre las capas de accesibilidad

En Accessibility overlays are not for disabled people:

An accessibility overlay (or accessibility widget) is one of those wee icon-only buttons you sometimes see floating over a web page; usually in the bottom-right corner. When you press them, they give you a bunch of options to make the website ‘more accessible’.

Why did I use inverted commas? Well, they profess to make a website more accessible, but do little-to-nothing of any real use; in fact, they can actually hinder a disabled user’s experience of a website!

[...]

Accessibility overlays are for non-disabled people by non-disabled people. The only way to properly address accessibility issues is at the product development level: carefully considered designs and well written code. Adding a single line of JavaScript to your website or app is not the answer.

Principales aspectos a tener en cuenta en la accesibilidad web

 

Cuatro razones contra las capas de accesibilidad

En 4 Reasons An Overlay Widget Will Not Solve Your Accessibility Woes se explican cuatro razones muy convincentes.

Can Everyone Use

Can Everyone Use es un intento de listado de componentes web en el que se detalle su nivel de accesibilidad. La idea está muy bien, pero por ahora le faltan muchos componentes para ser realmente una herramienta útil.

¿Las capas de accesibilidad sirven para algo?

Según la tesis de maestría  The Impact of Web Accessibility Overlays on the Usability and User Experience for People with Permanent Visual Impairments, realizada en el marco del Master's Programme in Digital Service Innovation de la Salzburg University of Applied Sciences, parece que las capas de accesibilidad no ayudan, sino todo lo contrario:

The research shows that accessibility overlays, in their current form, do not effectively improve the usability or UX for individuals with permanent visual impairments. Although there is a slight improvement when users are unaware of the overlay’s presence, overall, UX and usability are considered marginal at best and deteriorate upon recognition and interaction with an accessibility overlay. Furthermore, the research displays that accessibility overlays in their current form cannot meet WCAG 2.1 AA standards. The study also finds that users with permanent visual impairments are generally hesitant to engage with accessibility overlays and prefer to rely on their existing access technologies. However, they are willing to use accessibility overlays under improved conditions, which are discussed in the thesis. The empirical knowledge gained guides future technology, designs, policies, and research to create a more inclusive digital world. 

¿Qué es un CAPTCHA? Problemas de accesibilidad (1/2)