Description
For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.
*This success criterion is primarily for Web authors who develop or script their own user interface components. For example, standard HTML controls already meet this success criterion when used according to specification.
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
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
How should list items be nested?
I am getting an automated scanner error that “<li> elements must be contained in a <ul> or <ol>”, but in my code the <li> elements are contained in <ul>. What’s going on?
- accessibility tree
- lists
- scanner errors
Why are nested interactive controls an accessibility issue?
My automated accessibility scanner is flagging an error for nested interactive controls. Why is that a problem?
- focus
- interactive
- scanner errors