Un 6,1% de los empleados de Microsoft presenta algún tipo de discapacidad

 Este dato se puede leer en el artículo  Microsoft Reveals 6.1% Disability Representation For The First Time : A newly released report from Microsoft reveals that 6.1 % of the company’s U.S. employees self-identify as disabled, meaning they have a physical, mental or cognitive disability. If you’re not quite sure how to put that number in context, that’s because few companies ever disclose similar numbers. This is the first time Microsoft has included disability in their annual diversity and inclusion report—and although the number may be modest, its significance will be understood worldwide. [...] Microsoft already employs people with all types of disabilities and is actively looking for new ways to be inclusive. The company has slowly and persistently chipped away at the issue since Satya Nadella became CEO in 2014. It takes patience and persistence to move the needle. Even the basics can’t be taken for granted. Many Americans don’t know that most disabilities are not visible, likely

Accesibilidad de los reproductores multimedia

En  How accessible is the HTML video player? han analizado la accesibilidad de los reproductores multimedia. La conclusión es: In case you don’t make it all the way to the bottom, I feel, based on the results of testing each player (and comparing to my own Accessible Video Player project), that relying on native video players should be used with caution. This is my opinion stemming from experience, but I found most to have poor keyboard and screen reader support, which may lead to frustrated users.  There were a lot of inconsistencies across the board as far as keyboard and screen reader support. Some lose focus when the video controls receive focus then fade away, forcing the user to re-position themselves to adjust playback. Others did not trap keyboard focus in full-screen mode, leading to a similar situation as an inaccessible modal window allowing content to be accessed "behind" the window. One player in particular featured very awkward keyboard support where controls w

Curso gratuito "¿Cómo diseñar y programar sitios web accesibles?"

 El curso gratuito  ¿Cómo diseñar y programar sitios web accesibles? tiene el siguiente contenido: Introducción a la accesibilidad web Estándar WCAG 2.1. Organización del estándar Tecnologías de asistencia Destinatarios del WCAG Principios, pautas y criterios Niveles de conformidad. Accesibilidad en elementos gráficos. Accesibilidad en hipervínculos. Accesibilidad en controles de formulario. Accesibilidad en tablas Accesibilidad en la estructura de una página. Accesibilidad en el contenido. El curso tiene estos prerrequisitos: Estar matriculado en alguna institución educativa de educación superior. Tener conocimientos de HTML, CSS y JavaScript. Disponer de 6 horas por semana durante tres semanas, para el estudio de los contenidos y la realización de las prácticas y tareas.

Cómo diseñar para lectores de pantalla

En  Designing Layouts for Screen Readers se explica: It’s easy to think about a layout as being a primarily visual concern. The header goes up top, the sidebar is over here, the call to action is in an overlay on top of the content (just kidding). Grids, borders, spacing and color all portray valuable visual data, but if these hints to the structure of a page are only visible, some users may find your content unintelligible. You can experience this first hand if you try using a screen reader on the web. When I fired up VoiceOver on my Mac and took it out for a test drive, I realized that to a screen reader user, a lot pages are just a big heap of ‘content’, missing helpful organizational cues.  The experience can be kind of like listening to a long rambling story without any indication to what details are important or related to the main thread of the story. Halfway through the story, you aren’t sure whether it’s worth it to keep listening because you don’t know if you’ll even find wh

Las novedades de WCAG 2.2

En  Web Content Accessibility Guidelines (WCAG) 2.2 Draft for Review , el W3C explica las novedades de WCAG 2.2: 2.5.7 Dragging 2.5.8 Pointer Target Spacing 2.4.11 Focus Appearance (Minimum) 2.4.12 Focus Appearance (Enhanced) 2.4.13 Fixed Reference Points 3.2.6 Findable Help 3.2.7 Hidden Controls 3.3.7 Accessible Authentication 3.3.8 Redundant Entry En  What’s New in WCAG 2.2 y  WCAG 2.2 Overview and Feedback se analizan las novedades que tiene WCAG 2.2 hasta el momento actual, ya que todavía es un borrador, no es la recomendación final.

Una introducción a WCAG 2.x

 Interesante el vídeo  A WCAG Overview — Web Content Accessibility Guidelines (WCAG) 2.1 and 2.0 Explained : Y la transcripción del vídeo en  A WCAG Overview — Web Content Accessibility Guidelines (WCAG) 2.1 and 2.0 Explained .

Accessibility Maze, un juego accesible sobre accesibilidad

Accessibility Maze es un juego serio accesible sobre accesibilidad: For people who do not experience barriers, it can be difficult to empathize with the challenges that people with disabilities often face when navigating the Web. The Accessibility Maze was created to help those new to web accessibility experience firsthand what it is like to encounter those barriers. The game introduces a number of common barriers players must work around, mirroring the experience of those who encounter these obstacles daily, and provides quick lessons on how to avoid or correct them.  In creating the game we wanted to ensure it would be accessible. Gaming being one of the more challenging areas in which to address accessibility, the Accessibility Maze has been created to be playable with a current screen reader, using only a keyboard, and to demonstrate strategies for making games accessible.