Description
Provide ways to help users navigate, find content, and determine where they are.
Questions & Answers
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
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
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
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