Description
Provide ways to help users navigate, find content, and determine where they are.
Questions & Answers
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
Where should keyboard focus go in modals?
When a user opens a modal, where should focus go?
- focus
- keyboard
- manual auditing
- modal
Can a link/anchor element still be accessible without an href?
Can a link built with an anchor element still be accessible without an href?
- href
- html
- links
Is it compliant to have the same link present twice, as both an image and as text?
Is it considered accessible to have an image that acts as a link, followed by text that links to the same location?
- accessibility tree
- best practices
- links
- wcag
Are semantic heading levels important?
Why are semantic/programmatic heading levels important?
- headings
- text
Why do mobile apps need to be keyboard accessible?
Accessibility requirements for mobile apps say that all interactive elements need to be navigable with the keyboard. Why would someone use an external keyboard with a tablet or mobile phone?
- external keyboard
- keyboard navigation
- mobile
- tablet