User interface components and navigation must be operable.
Questions & Answers
I was checking to make sure an element on my page has an accessible name in Chrome's Developer Tools and under the Computed Properties section of the Accessibility panel, it says "Accessibility node note exposed. Element not interesting for accessibility." What does that mean?
- accessibility node
- hidden content
Can you help define what a keyboard trap is for me?
- keyboard trap
I was told that my buttons need to be operable by the spacebar. Is that true? Are there any other keys that need to be supported?
- keyboard support
I come across a long of links that look like buttons. Is this OK from an accessibility standpoint?
Do I need to add aria attributes on native elements (eg. <button role="button>)?
- aria attributes
- native elements
I was wondering if Google Maps is accessible or not. Do you have any info?
- google maps
What are landmark roles and how can they be used?
- aria landmarks
- aria roles
- landmark roles
I've been told to make sure my site has an accessibility tree. What is an accessibility tree? How do I view it?
- accessibility tree
I've been hearing a lot about website accessibility and something called a VPAT. Can you help me understand what a VPAT is and what it's for?
- section 508
- voluntary product accessibility template
I ran my page through the wave scanner in chrome and got 'suspicious link text' as a warning. My question is this... how specific do I need to make the text? If I go over the top and make it super specific it goes away...
- best practices
- building content
- wave scanner