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).
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.
I'm using Appium (Mobile App Automation for Testing) to test an iOS app.
My question is similar to Should inline validation check emp
I was working on a mobile project and I faced a problem.
How do i show if there are two different action on a single object in mobile.
When I trigger a blur event on an input, button or select element chrome and firefox keep the current tabindex.
I'm trying to make use of Accesibility API in Swift, to register for notifications of window properties of the current frontmost app.
I have a simple GUI with a single QTextEdit. I want to change the text of textEdit object whenever some keys pressed by user.
In TableViewCell, I have custom imageview which act as a radio button. This imageview has two states
I have a navigation with dropdown menus on larger screens, and in order to create the proper responsive behavior for smaller screens, I've set preventDefault on the parent-link that has a dropdown
At certain point I used Accessibility Inspector (from Xcode -> Open developer tool -> Accessibility Inspector) while running my app in simulator, and ever since the Xcode console is cluttered
I have a table with multiple rows and columns. This table as a whole is reloaded by AJAX once in a while.
I'm currently on Firefox 56 and have seen the warning that many add-ons are going to break in 57, which is coming soon.
What WAI-ARIA roles should be used for carousels, like the one below?
In my app we enable the user to go into full screen mode by executing the following code when the user clicks the "Full Screen" actionBar button.
I've read around on the internet and I've heard people say
Access specifiers ::
Recently when I was using Gmail i ought to notice that Gmail runs an algorithm by which if user types " I have attached " in a mail and does not actually attach mail it shows a dialog confirmation
I'm looking to define what makes more sense in a page visual hierarchy for both visual design / consistency & accessibility.
I have an iOS application and I'm adding accessibility to it.
If you see an error or omission or if you have any other comments, please let us know