Description
Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
Questions & Answers
What’s the difference between aria-controls and aria-owns?
What's the difference between aria-controls and aria-owns?
- aria
- aria-controls
- aria-owns
What’s the difference between a fieldset and a radio group?
What is the main difference between a fieldset and a radio group?
- aria
- forms
- html
When should I use required vs. aria-required?
In a form field, when should I use required vs. aria-required?
- aria
- aria attributes
- form
- html
What Are the Code Differences between Links vs Buttons?
Where can I find code (html, css, and javascript) examples of links vs buttons.
- buttons
- html
- links
When to use aria-label vs. aria-labelledby?
When to use the aria-label attribute vs. the aria-labelledby attribute?
- accessibility tree
- accessible name
- aria
- html
- label
How can I make a disabled button focusable, clickable, in general “interact-able”?
I have a button on my page which I'd like to make disabled. If I use disabled as an attribute I can no longer tab navigate to it, or handle click events on the button. How can I maintain its disabled meaning, while being able...
- aria
- html
- screen readers
What does “accessibility node not exposed” mean?
I was checking to make sure an element on my page has an accessible name in Chrome's Developer Tools and under the Computed Properties section of the Accessibility panel, it says "Accessibility node note exposed. Element not interesting for accessibility." What does that mean?
- accessibility node
- hidden content