Accessibility Engineering
Keyboard, screen reader and focus behaviour, tested against real assistive technology.
- Courses
- 14
- Hours
- 21
- Modules
- 4
An automated checker finds perhaps a third of what matters. This path is mostly about the other two thirds, which is why every course ends with you listening to your own page.
Assessed on one component, submitted with a transcript of what a screen reader says as you operate it.
The sequence
Modules unlock in order. You finish one before the next opens, which is the point of a path rather than a playlist.
-
01
The keyboard first
Tab order, focus visibility and the traps that break a page.
-
02
Names, roles and values
What a screen reader actually announces, and why yours says nothing.
-
03
Components that behave
Menus, dialogs and tabs built to the patterns rather than to a guess.
-
04
Testing with the real thing
Running your work through NVDA and VoiceOver instead of a linter.
What you can do afterwards
The assessment checks these directly, against a rubric published before you start.
Before you start Comfortable with HTML, CSS and enough JavaScript to wire a component.
- Navigate and operate your own build with the keyboard alone.
- Fix an announcement instead of adding another aria attribute.
- Test against assistive technology rather than against a score.