Aria-hidden elements should never contain focusable elements. Learn how to fix this critical accessibility issue to comply with WCAG 2.0.
Using aria-hidden=true on the body element can make your entire site inaccessible. Learn why this is a critical accessibility issue and how to fix it.
ARIA input fields without an accessible name are a major accessibility issue. Learn how to add a name to your ARIA input fields to comply with WCAG 2.0.
ARIA meter nodes without an accessible name are a major accessibility issue. Learn how to add a name to your ARIA meter nodes to comply with WCAG 2.0.
ARIA progressbars without an accessible name are a major accessibility issue. Learn how to add a name to your ARIA progressbars to comply with WCAG 2.0.
Some ARIA roles must be contained within a specific parent role to be valid. Learn how to fix this accessibility issue to comply with WCAG 2.0.
ARIA toggle fields without an accessible name are a major accessibility issue. Learn how to add a name to your ARIA toggle fields to comply with WCAG 2.0.
ARIA tooltips without an accessible name are a major accessibility issue. Learn how to add a name to your ARIA tooltips to comply with WCAG 2.0.
The blink element is a relic of the past and a major accessibility issue. Learn why you should not use the deprecated blink element and what to use instead.
Buttons without discernible text are a major accessibility issue. Learn how to add text to your buttons to comply with WCAG 2.0.
Have questions about our services? Contact us today for a free consultation and performance audit.
By filling out this form, you agree to our Privacy Policy.