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
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).
We're currently updating our site for ADA compliance and want to implement a skip navigation menu on the main landing pages.
I must be missing something simple:
What is causing this accordion nav to lose browser default focus?
I'm working on an ADA level AAA compliant site.
I'm working on a app that has a Settings screen and in that activity user has option to go to native settings accessibility options and switch on the large text feature.
When a UITableViewCell is selected, voice over announces "selected", I don't want voice over to say "selected". How can i achieve this ?
Accessibility question: Can a <label>...</label> have children besides an <input ... />?
<input ... />
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.
I'm trying to make use of Accesibility API in Swift, to register for notifications of window properties of the current frontmost app.
Normally, VoiceOver correctly reads web contents loaded with WKWebView and it is possible to read buttons and links.
Is There any way to force VoiceOver to not read view controller title "heading" word after reading title/accessibilityLabel?
Recently I've been put in charge of testing and implementing WCAG 2.0 AA compliance into our websites (php CMS based). However, my experience with this is pretty limited. My questions are:
Is there some way that I can avoid the section titles of the UITableView from saying "heading" in the voiceover mode after the text on the section is read?
As per the title, what is the difference when I have tabIndex="false" versus having empty tabIndex?
I am using ABCpdf to generate a collection of PDFs from HTML markup, and am struggling with making it fully accessible.
I'm working on a project that it has to be accessible to everyone and I have some problems when the PC is in High Contrast mode.
Above you se a typical breadcrumb.
As the title says, Android Talkback is not registering the onFocus event.
Sorry for the question but I cannot figure it out after searching for a day. I have an iPad, using safari and VoiceOver off, with a wireless keyboard.
Any hints how to control d3 brush/zoom with keyboard:
1. Ability to focus on brush control
2. Ability to change brush area using keyboard
Is it supported out of the box?
If you see an error or omission or if you have any other comments, please let us know