Description
Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
Questions & Answers
Should “Download” components be buttons or links?
My website has a component used for downloading files. Should I code it as a button or a link?
- aria roles
- buttons
- download
- Link
How do I make my unique custom widget accessible?
I’ve built a unique custom widget that doesn’t match any of the existing ARIA design patterns. How should I code it to be accessible?
- aria
- aria roles
- custom widgets
When should I use the ARIA “application” role?
When should I use the ARIA "application" role? How does it affect web accessibility?
- aria
- aria roles
- custom widgets
When should I use the ARIA “section” role?
When should I use the ARIA "section" role?
- aria
- aria roles
How do I make my podcast accessible?
How do I make my podcast accessible to people with disabilities?
- audio
- audio controls
How are menu buttons and disclosure buttons different?
I have a button that shows and hides content, should it be coded as a menu button or a disclosure button?
- disclosure button
- menu button
Can I have links within a video?
Is it accessible to provide links within a video, which take you to a new page and pause the video when activated?
- Link
- video
What is ARIA?
What is ARIA? I know it's related to web accessibility, but what does it do?
- aria
- aria attributes
How are accessible names calculated?
What happens when a web component has accessible names provided by multiple techniques?
- accessible name
- aria