Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
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
I'm building some new pages and was wondering about navigation landmarks. Is it OK to have multiple navigation landmarks?
- landmark roles
I come across a long of links that look like buttons. Is this OK from an accessibility standpoint?
While reading up on WCAG, I noticed the terms "native widgets" and "custom widgets". What's the difference?
- custom widgets
- native widgets
Do I need to add aria attributes on native elements (eg. <button role="button>)?
- aria attributes
- native elements
I am curious about how to make an image act as a button and ensure it's accessible. Any guidance?
I was wondering if Google Maps is accessible or not. Do you have any info?
- google maps
I'm working on updating my site and have become a little confused about the differences between legend and label elements. Can you explain?
I've been told to be aware of CSS pseudo content because of the way it is treated by screen readers. Do you have any guidance?
- css psuedo content
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