Accessibility
A11Y (an acronym that stands for Accessibility - especially useful if you forget how to spell it). I still remember when Section 508 Guidelines were federally mandated way back in 1998[1] On my bookshelf, I have a copy of Robert Yonaitis' book Understanding Accessibility from 2002 ISBN:1-930616-03-1
See the A11Y checklist for a generic reference providing a quick implementation of WCAG
Accessibility in MediaWiki[edit | edit source]
- Accessibility as a design principle
- mw:Accessibility guide for developers and
- mw:Wikimedia Quality and Test Engineering Team/Playbooks/Accessibility,
- the Accessibility workboard in Phabricator or the
- full list of Open bugs and feature requests related to the accessibility in MediaWiki and other Wikimedia software
In the Codex Design system, the README states "Web accessibility compliant (Web Content Accessibility Guidelines 2.1 level AA)"
The project sources (docs) at packages/codex-docs/docs/style-guide/accessibility.md gives greater detail on the goals, and accessibility focus of the project.
There is a long-standing tradition of accessibility in WikiMedia projects, expressed in the wikipedia:Wikipedia:Manual_of_Style/Accessibility Wikipedia's Manual of Style (emphasis on Content Accessibility)
mw:Accessibility guide for developers describes techniques, guidelines and some tools for developers.
Tools[edit | edit source]
- https://addons.mozilla.org/en-US/firefox/addon/wave-accessibility-tool/
- https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/
- https://firefox-source-docs.mozilla.org/devtools-user/accessibility_inspector/
Guidance boils down to "Open the WAVE extension or your Firefox Accessibility Inspector to confirm WCAG 2.1 level AA compliance".
- ↑ In 1998, Congress amended the Rehabilitation Act of 1973 to require federal agencies to make their electronic and information technology (EIT) accessible to people with disabilities.
