Top 10 Accessibility Issues

To express their purpose and meaning to screen reader users, all images must include alternative text.

For screen reader users, buttons must include recognizable text that specifies the destination, purpose, function, or action.

Certain ARIA roles must be enclosed by specific parent roles in order to carry out their intended accessibility functions.

Each form element must have a label element attached with it.

ARIA attributes must only be used on elements whose roles support them. Every ARIA role — whether explicitly set via the role attribute or implicitly derived from the HTML element — defines a specific set of required, supported, and inherited attributes. Any ARIA attribute outside those categories should be removed, relocated to an appropriate element, or the element’s role should be changed to one that supports the intended attribute.

Some ARIA role values in parent elements must contain specific child elements and role values in order to execute the intended accessibility function.

A label element with a programmatic association must be included for each select element.

The document must not use <meta http-equiv="refresh"> with a refresh time of less than 20 hours, as this could prohibit users with disabilities from controlling when the page is refreshed.

Valid values must be present for ARIA properties that begin with aria-.

To fulfill the intended accessibility purpose, these values must be written correctly and relate to values that make sense for a certain property.

Markup for data tables can be tedious and perplexing. Tables must be semantically marked up and have the proper header structure. Table navigation is made easier by features in screen readers, but for these capabilities to function properly, the tables must be precisely marked up.