Find answers to all your questions in the most relevant forums
Discussion lists dealing with users, technologies, and all things between.
Discover groups and organizations for all user needs
Relevant events in the fields of accessibility and inclusive design
Connect developers and testers to build better applications
This listing is a compilation of both questions asked in-site and questions related to accessibility themes gathered from different sources (stackoverflow, UX Stack Exchange).
I'm encountering something bizarre in which a page with a form and fairly minimal layout is read correctly by JAWS 16 and 18 in IE11 on initial load.
When using NVDA on Firefox it fails to read the first child when focusing from a container, but it is able to read the second child.
I have a time picker component, composed by two separate input fields that work together to create the illusion of being one.
This is how the skeleton looks like
Is it possible to determine the order of HTML elements read by a screen reader (like TalkBack or VoiceOver) regardless of their position in the DOM?
I have the following code for a select:
We have an input slider that has a title attribute set to slider value. Since it doesn't have a label, we add aria-label to the input attribute.
This question already has an answer here:
I have been using the Mac OSX's built in screen-reader for testing my site, I know it's not the best but it's all I have for now. But I'm finding it isn't pausing at the end of elements...
Please correct me if I am wrong, but usually screen reader navigation works by pressing the tab key, and usually you do not have (or need) tab-able images.
I am currently working on a highly accessible website. How can I make the screen reader not read the (1) associated labels, (2) not indicate if it is checked or not, to a focused checkbox?
I learned that the <abbr> tag is supposed to be interpreted by screen readers in a way that its title attribute would replace its content when read by a screen reade
I want to detect whether a screen reader is running on a user's machine to avoid sound clashing with audio tag in html. If so, please provide details on how this could be done.
If you see an error or omission or if you have any other comments, please let us know