Web Accessibility and WCAG 2.1 is a relatively new area of expertise for many web developers and webmasters. We’re working to build a comprehensive knowledge base of questions and answers to help solve the unique challenges around building websites with web accessibility in mind. Browse or search our knowledge base, or submit questions to our team of developers.
Browse by Topic
Browse Recent 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?
Are there any guidelines or best practices about using a video loop as the background images for banner areas? Should there be a control for the user to stop the video?
When to use the aria-label attribute vs. the aria-labelledby attribute?
- accessibility tree
- accessible name
Under the regulations for public sector bodies, can I link to an external website that isn't accessible itself? What are the WCAG 2.1 AA rules on this?
- external links
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 would like to add focus states for interactive elements on my website, however I don't want the styling I add to apply when clicking on elements. If I just use :focus in my css I see the styles come through when clicking elements, or...
How many total WCAG success criteria are there?
- success criteria
I have a button on my page which I'd like to make disabled. If I use disabled as an attribute I can no longer tab navigate to it, or handle click events on the button. How can I maintain its disabled meaning, while being able...
- screen readers
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