Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
Questions & Answers
When to use the aria-label attribute vs. the aria-labelledby attribute?
- accessibility tree
- accessible name
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...
- screen readers
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
I come across a long of links that look like buttons. Is this OK from an accessibility standpoint?
While reading up on WCAG, I noticed the terms "native widgets" and "custom widgets". What's the difference?
- custom widgets
- native widgets
If there are multiple elements with empty IDs, are they considered duplicate?
- duplicate ids
- id attributes
Do I need to add aria attributes on native elements (eg. <button role="button>)?
- aria attributes
- native elements
I am curious about how to make an image act as a button and ensure it's accessible. Any guidance?
I'm working on updating my site and have become a little confused about the differences between legend and label elements. Can you explain?
What are landmark roles and how can they be used?
- aria landmarks
- aria roles
- landmark roles