Accessibility Inspector for WCAG Evaluation

Rule Categories

Rule categories are an alternative to WCAG Guidelines for grouping related rules. The Rule Categories are based on HTML element types to make it easier for web designers and developers to understand WCAG accessibility requirements.

Landmarks
Use ARIA landmark roles to structure the content of each page and identify major sections of content, thus making them more findable and navigable.
The use of landmarks will, in many cases, reflect the visual styling and page layouts that web designers utilize to set apart various sections of content.
Headings
Use heading elements (H1-H6) to identify sections and subsections of content in a web page.
Headings can also be used to provide accessible names for landmarks using the aria-labelledby attribute.
Color/Content
Use proper HTML markup to identify the semantics and language of text content. Ensure that text is readable by adhering to color contrast requirements, and that information is not conveyed solely by the use of color, shape, location or sound.
Images
Provide appropriate text alternatives for static images and graphics.
Links
Use link text that properly describes the target of each link. Ensure consistency and uniqueness for links that are usable, predictable and understandable.
Tables/Layout
Provide table captions or other meta-information as needed. Provide row and column header references for data cells of data tables. Ensure that tables used for layout properly linearize text content.
Forms
Provide meaningful labels for form elements and usable and understandable error feedback as needed.
Widgets/Scripts
Use appropriate event handlers on elements to support native interactivity using JavaScript.
Ensure that custom widgets created using JavaScript support keyboard interaction and include ARIA markup to describe their roles, properties and states.
Audio/Video
Provide appropriate text transcripts, captions or audio descriptions for elements used in rendering audio and video content.
Keyboard Support
Provide logical and sequential keyboard navigation among interactive elements such as links and form controls. Use standard models of keyboard interaction for custom widgets, guidance and examples can be found in the ARIA Authoring Practices.
Timing/Live Regions
Identify accessibility problems caused by time limits on input and by content that moves, scrolls, flashes or auto-updates.
Site Navigation
Ensure the consistent labeling and ordering of recurrent page sections across all pages within a website. Provide a meaningful title for each page within a website.