Skip to content

Latest commit

 

History

History
96 lines (61 loc) · 4.05 KB

accessibility.md

File metadata and controls

96 lines (61 loc) · 4.05 KB

Accessibility

Compliance

We use a subset of the WCAG 2.1 AA standards as our benchmark for accessible products.

Aim to build user interfaces that:

For web-based products, ensure your interfaces:

Assistive technology

Web

For web-based products, test each change using one of the most commonly used screen reader / browser combinations:

  • JAWS with Chrome or Internet Explorer
  • NVDA with Chrome or Firefox
  • VoiceOver with Safari

WebAIM provides a useful guide to testing accessibility with VoiceOver.

Also test your changes using only a keyboard.

Test each change using speech recognition software:

Native

For native apps, test changes using the most commonly used screen reader on the platform:

  • VoiceOver on iOS
  • Talkback on Android

All products

For all products, test changes using a screen magnifier:

Design system

In web products, use the standard UI components and typography snippets provided by the Source Design System. These are optimised for accessibility.

For all products, try to use:

  • colour tokens to ensure text and iconography have suitable colour contrast
  • size tokens to ensure interactive elements have adequate target size

Tools

Incorporate automated accessibility testing tools into the CI process, where appropriate.

The following tools have proven useful for web-based products:

Audits

Perform regular accessibility self-audits against your products. Tools such as WAVE can help facilitate audits.

Prioritise and fix any issues in a health week.

Arrange external audits for your product using a recognised accessibility auditing company (e.g. the RNIB).