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
When to use aria-label vs. aria-labelledby?
When to use the aria-label attribute vs. the aria-labelledby attribute?
- accessibility tree
- accessible name
- aria
- html
- label
Is it ok to link out to a non-accessible website?
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
- links
What are the contrast requirements for an element’s focus, mouseover & select states?
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?
- focus
- mouseover
- select
- states
How can I add keyboard only focus styling?
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...
- CSS
- focus
- keyboard
How many WCAG success criteria are there?
How many total WCAG success criteria are there?
- success criteria
- wcag
How can I make a disabled button focusable, clickable, in general “interact-able”?
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...
- aria
- html
- screen readers
What does “accessibility node not exposed” mean?
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
Do forms need to have visible labels?
Do my form elements need to have visible labels or is placeholder text good enough?
- form input labels
- form labels
- forms
- labels
- visible labels
What is the difference between native and custom widgets?
While reading up on WCAG, I noticed the terms "native widgets" and "custom widgets". What's the difference?
- custom widgets
- native widgets