Your daily frequent11y newsletter, brought to you by @ChrisBAshton:
Our development approach for accessible front-end code
- This guide by the BBC walks through their approach for implementing front-end changes, e.g. implementing a component.
- Look at the screen reader UX; ask the UX designer for the required documentation if it is missing. It should cover the focus order, the announced content for screen readers, etc.
- Read accessibility acceptance criteria
- Write the HTML
- Check with supported assistive technology (AT). You should do this before adding CSS, and then again before and after adding JavaScript. They advise against doing all your testing at the end, as this “may be more time consuming to debug”, since you won’t necessarily know which layer caused the bug.
- Write automated tests for accessibility
- Get it reviewed (code review by engineers, design review by designers)
- Hold an accessibility swarm, resolve any bugs, then the component is ready for Test.
Prefer longer newsletters? You can subscribe to week11y, fortnight11y or even month11y updates! Every newsletter gets the same content; it is your choice to have short, regular emails or longer, less frequent ones. Curated with ♥ by developer @ChrisBAshton.
