Information and user interface components must be presentable to users in ways they can perceive.
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 working on some new blog posts and I want to include videos. Do all videos need a transcript to be accessible?
I want to make sure that my site uses proper contrast ratios. Are there different contrast ratio requirements for text and for UI elements?
- contrast ratios
I'm building some new pages and was wondering about navigation landmarks. Is it OK to have multiple navigation landmarks?
- landmark roles
I'm going to add some videos to my website and I've heard that videos need audio descriptions. Is that true? Do all videos need audio descriptions?
- audio descriptions
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've read recently that there are situations where a null or empty alt tag is appropriate. In what situations should I use an empty alt attribute?
- alt tags
- empty alt
- null alt attribute
I am curious about how to make an image act as a button and ensure it's accessible. Any guidance?