Lesson 2 of 9
Follow the information chain
The experience depends on a chain between the product, the platform accessibility layer, and the screen reader. A breakdown at any point changes what the user receives.
Understand where screen reader information comes from and where defects can enter the chain.
1. The product exposes meaning
Interface code provides objects with properties such as name, role, state, value, hierarchy, and relationships. On the web this often begins with semantic HTML; native and embedded platforms use their own accessibility APIs.
2. The platform creates an accessibility model
The operating system or browser represents those objects in a form assistive technologies can query and navigate.
3. The screen reader presents and operates it
The screen reader decides what to announce, how navigation commands work, and how user input is passed back to the product.
What to remember
A visual label is not enough if its meaning never reaches the platform accessibility model.
Try this with your team
Inspect one custom control. Can your team identify its name, role, current state, value, and place in the focus order?