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).
Instead of adding/removing my different sections to/from the DOM, I'm only hiding them with aria-hidden="true", and unhiding them if certain <a> toggles are clicked.
What WAI-ARIA roles should be used for carousels, like the one below?
I have an issue where drilling down into a text field with Control+Option+Shift+Down ends up reading more than what's currently inside of the text field.
I'm running an automated accessibility test on my site and getting an error for a tooltip element which uses
I'm trying to grasp how to code with screen readers in mind, and I'm having a number of issues. The first example is a single HTML element that I tried to display:
Building a nice accessible web page is hard. Currently, Im trying to make a tooltip web accessible and I need help. Do you guys have any piece of advice for it?
Basically, I'm trying to clone an element and change its aria-label within React.cloneElement.
If you see an error or omission or if you have any other comments, please let us know