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 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?
A more complex version of: Word-wrap in an HTML table.
I am working on a reactjs application and I have elements that get added to the DOM:
I cannot seem to access my iron-data-table via tabbing, considering that I am trying to create an accessible web interface.
Does anybody have any knowledge of such things?
I have this Css Toggle which works as expected, I want to add the focus outline to all the toggles for accessiiblity
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
So I have the following function. What it does is listens for the focus event on all elements.
How would one place focus on a paper-input contained within a paper-dialog at the point of it being opened?
My company is exploring some scenarios that we use commonly in our design that we are realizing may not be 100% compliant with WCAG 2.0 standards.
Does the label tag work with radio buttons? If so, how do you use it? I have a form that displays like this:
I am using JAWS version 15 to test my page on Google Chrome that contains a set of related radio buttons, none of which are checked initially.
I am delving into the confusing world of web accessibility and trying to retrofit my HTML code to have better accessibility with things such as aria-labels etc.
What are the differences in properties while using HTML or Accessibility mode in blue prism.
I'm new to aria and this one partially works. I can tab to the field but can't see the individual items in the dropdown. Any suggestions appreciated.
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:
I started reading upon html5 and I am trying to work on a project so that I can see how things work. I know that the tag can be use like this:
I am currently working on a web page with a silent video banner.
In my code I have a list of buttons stored in an unordered list.
Im doing a html page which has to be accessible.
I have the following bootstrap popover:
While making a html page, I notice that NVDA reads "clickable" for every <p> or <span> tag. Is there a way to stop this?
If you see an error or omission or if you have any other comments, please let us know