It is a legal and moral obligation to make web content and functionality available to people with disabilities. This includes but is not limited to:
- Vision impairment
- Hearing impairment
- Cognitive impairment
- Fine motor control impairment
- Physical impairment
- Injury
- Siezure susceptibility
- Neurodiversity
- Motion sickness
- Reading level
Primarily, write semantic HTML. Without this rock solid base for your content, any later efforts to bolt on accessibility will fall short. Developers must familiarise themselves with the HTML living standard so that they use the best element for each piece of structure, content, and interaction.
All Barnardo's web pages must achieve WCAG (web content accessibility guidelines) AA conformance throughout, and level AAA conformance where possible. Restated: AA conformance is a minimum, not a goal.
All text content must have a Flesch-Kincaid Grade Level of 4.2 or lower. To see the Flesch-Kincaid Grade Level in Word follow these steps.
Automated accessibility tools can pick up some problems, but manual testing is required to meet many success criteria. For example an automated tool cannot check if alternative text is descriptive and relevant.
Product owners must never allow the use of accessibility overlays. The people who use Barnardo's products deserve better, and any product that carries the Barnardo's name must provide better.
We recommend TetraLogical for accessibility testing and reporting if the relevant expertise is not present in the team building your product.
Tota11y
Drag this bookmarklet into your bookmark bar. Instructions.
Reading list
- https://www.w3.org/TR/html-aria/
- https://www.w3.org/TR/using-aria/
- https://stevefaulkner.github.io/HTML5accessibility/