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).
While making a html page, I notice that NVDA reads "clickable" for every <p> or <span> tag. Is there a way to stop this?
I was running lynx to test some HTML I had to do, because having accessibility in mind.
I have a form with 3 input fields and then a button that is shaped like a next symbol.
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.
<input type="search" placeholder="search" />
We're building a website, that people will be sent to from an email. There's multiple home pages, because there are different groups in the email list that the home pages correspond to.
Our clients gave us a video that is mostly B-roll so they are saying they do not need to add captions to make is ADA compliant, but I'm not sure that is true.
I have a component which presents an x/y axis plane and a nub that users can move around within the plane.
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?
Desired behavior : When a Tabkey press happens on a particular dom element in a webPage I want my cursor focus to go to address bar.
I am running a slideshow on a client site. The slideshow animates each slide, and relies SOLELY on the scrollwheel of the mouse although it also 'swipes' when in touchscreen devices.
If you see an error or omission or if you have any other comments, please let us know