Search Results

Some ARIA roles must contain specific children to be valid. Learn how to fix this accessibility issue to comply with WCAG 2.0.

Deprecated ARIA roles are a sign of an outdated and inaccessible website. Learn why you should not use them and what to use instead.

The marquee element is a relic of the past and a major accessibility issue. Learn why you should not use the deprecated marquee element and what to use instead.

For a definition list to be accessible, it must contain only ordered groups of ‘dt’ and ‘dd’ elements. Learn how to fix this issue to comply with WCAG 2.0.

For a definition list to be accessible, all

Elements with role=img must have an accessible name. Learn how to add alternate text to your ARIA images to comply with WCAG 2.0.

Using the wrong ARIA attribute for a role can create a confusing experience for screen reader users. Learn how to use the correct ARIA attributes to comply with WCAG 2.0.

Form fields should have only one label element to avoid confusion for screen reader users. Learn how to fix this accessibility issue to comply with WCAG 2.0.

Form input elements without labels are a major accessibility issue. Learn how to add labels to your form inputs to comply with WCAG 2.0.

Frames without a title attribute are a major accessibility issue. Learn how to add a title to your frames to comply with WCAG 2.0.