I'm implementing a web application with high accessibility requirements. In come cases, the screen reader (VO) behaves in unexpected ways (for example, skips some elements).

To find out whether the bug is inside the screen reader, or my application code, or the browser, or somewhere else, I need to first know what the expected behavior is.

Given some HTML with some aria- attributes, what are all the specs that decide how exactly a screen reader should interact with it?

Is it even fully specified, and how much is left up to the implementor of the screen reader?


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Browse other questions tagged or ask your own question.