A practical accessibility article built around useful findings from the WebAIM Screen Reader User Survey 2024, including JavaScript usage, Windows and Chrome usage, JAWS and NVDA adoption, mobile behaviour, navigation patterns, and why accessible websites matter more than waiting for assistive technology to solve everything.
Read article →
ARIA helps browsers and assistive technology communicate the role, state, name, and relationships of interface elements, but it does not automatically make custom controls accessible. This article explains why native HTML should come first, how roles and attributes work, why accessible names matter, and why keyboard behaviour and screen reader testing are part of the contract.
Read article →
Accessibility is still first and foremost about people. But the same practices that make websites more usable for blind and visually impaired users can also help search engines and generative AI systems understand structure, controls, meaning, and context. This article looks at accessibility as a practical way to express non-visual meaning on the web.
Read article →