Information and user interface components must be presentable to users in ways they can perceive.
Questions & Answers
Our director wants to have an eagle (our logo) fly across the page on our web site. This is a terrible idea but I'd like to know what WCAG 2.0, section 508, and/or usability principles this violates. Any other arguments against this will also be...
- alt tags
Placeholder text for form inputs are often times very light. Does placeholder text need to meet contrast requirements?
I'm working on updating my focus, mouseover (hover) & select (active) states and want to make sure that my new design meets contrast requirements. What are the contrast requirements for these different states?
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