Description
User interface components and navigation must be operable.
Questions & Answers
How are accessible names calculated?
What happens when a web component has accessible names provided by multiple techniques?
- accessible name
- aria
In web accessibility, what are concurrent input mechanisms?
What are concurrent input mechanisms, and how do they affect web accessibility?
- keyboard
- mouse
- pointer
- touchscreen
Do tooltips need to be keyboard operable?
I have an interactive button with a tooltip that opens on mouse hover to give more information. All the tooltip information is in the button’s ARIA label, so why does the tooltip need to be openable on keyboard?
- keyboard
- tooltip
After closing exposed content, should focus return to the UI component that exposed it?
After exposed content is closed, does focus need to move back to the UI component that exposed it?
- focus order
- modals
- returning focus
Do small navigation bars need skip links?
If there are only a few navigation links in my header, do I still need a link to skip to the main content?
- keyboard navigation
- skip links
Are there multiple ways to build an accessible widget?
I'm trying to build a widget that follows an example in the W3C ARIA Authoring Practices Guide, but I can't quite match it because of the way my site is built. Can my widget still be accessible?
- aria
- custom widgets
What are multiple ways to navigate web pages?
How do I ensure that users have multiple ways to find web pages on my site?
- Multiple Ways
- Navigate Web Pages
What is considered a good page title?
How do I know if my page title is a good page title?
- Page Title
What is a DOM, and how does it affect accessibility?
What is a DOM, and how does it affect accessibility?
- html
- page structure