Questions & Answers
If only 3rd party tools have accessibility issues, does my website conform to WCAG?
My website has 3rd party tools that have accessibility issues I can't control. Can my website still conform to WCAG?
- 3rd party
- partial conformance
- wcag
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
What are description lists?
What are description lists and when should I use them?
- description lists
- html
- lists
Where should keyboard focus go in modals?
When a user opens a modal, where should focus go?
- focus
- keyboard
- manual auditing
- modal
What are the differences between label, aria-label, aria-labelledby and aria-describedby?
There appear to be several ways to put a label on items in order for them to be accessible for users of screen readers or other assistive technologies. Which method of labeling should I use?
- accessible name
- aria
- aria attributes
- aria-label
- form
- form input labels
- form labels
- forms
- html
- label