Software more people can use.
WHY IT MATTERS COMMERCIALLY
Public bodies and large organisations increasingly require it, and its absence loses deals.
WHAT TO BUILD IN
Keyboard operation of everything Visible focus Sufficient colour contrast Labels on every input Errors identified in text, not colour alone Structure that screen readers can navigate
WHY KEYBOARD OPERATION FIRST
It underpins most assistive technology, and it is the commonest failure.
WHAT TO TEST
Completing the core task without a pointer.
WHAT CUSTOM COMPONENTS REQUIRE
Correct roles and states, announced properly.
WHY THEY FAIL
A custom control built from generic elements conveys nothing to assistive software.
WHAT TO PREFER
Standard elements, wherever possible.
WHAT DIALOGS REQUIRE
Focus moved into them Focus trapped while open Focus returned on closing
WHAT TABLES REQUIRE
Proper headers, associated with cells.
WHAT AUTOMATED CHECKING FINDS
A minority of real problems.
WHAT IT CANNOT FIND
Whether the product is actually usable.
WHAT TO DO
Navigate it with a screen reader yourself.
WHAT TO DOCUMENT
Which standards you meet, honestly.
WHY HONESTLY
Overstating it in a procurement response is discovered.
