Description
User interface components and navigation must be operable.
Questions & Answers
What are the keyboard navigation requirements for my web app?
What are the keyboard navigation requirements for my web app?
- keyboard
- keyboard navigation
- wcag
Is having a sitemap required?
Is it a WCAG requirement for my website to have a sitemap?
- Multiple Ways
- sitemap
- wcag
How should I hide the slides of a carousel that aren’t displayed visually?
How should I hide the slides of a carousel that aren't displayed visually?
- accessibility tree
- carousel
- focus
For bypass blocks, what types of content should users be able to skip?
For bypass blocks, what types of content should users be able to skip?
- bypass blocks
- keyboard
When should I use aria-label?
How do I properly use an aria-label?
- accessible name
- aria
- aria attributes
- aria-label
Are “ghost tab stops” considered accessibility violations under WCAG?
There's an element on my site that makes the keyboard tab to it even though there isn't a visible item to focus on. Will this "ghost tab stop" fail under the WCAG?
- best practices
- cognitive
- keyboard
- keyboard navigation
- usability
- wcag
How can I test for character key shortcuts?
How can I test for character key shortcuts?
- character key
- keyboard
- manual auditing
- shortcuts
Does the level one heading tag on a page need to be visible to the eye and to screen readers?
I'm working on using headings to help make my website easier for screen reader users to navigate a page. Do I need to have both a visible <h1> heading and an <h1> tag that a screen reader can recognize?
- headings
- html
- page structure
Where should keyboard focus go in modals?
When a user opens a modal, where should focus go?
- focus
- keyboard
- manual auditing
- modal