Rules

Every check, explained.

The 99 rules the pour engine runs, grouped by the WCAG 2.2 principle they serve. Each page says what the rule looks for, shows markup that fails and markup that passes, and says how to fix it. A rule only fails what it can show; when it cannot tell, it asks a person to look.

For the criteria no rule can decide, see WCAG 2.2 coverage.

Perceivable

Perceivable rules
RuleWhat it checksCriterionSeverity
Image map alt text Image map areas must have alternative text. 1.1.1 A, 2.4.4 A Critical
Canvas accessible name Meaningful <canvas> graphics need an accessible name or fallback. 1.1.1 A Moderate
Embed accessible name <embed> needs an accessible name. 1.1.1 A Serious
Image alt text Every <img> needs a text alternative. 1.1.1 A Critical
Image button alt text Image inputs need alt text describing their action. 1.1.1 A, 4.1.2 A Critical
Object alt text <object> embeds must have a text alternative. 1.1.1 A Serious
SVG accessible name Inline SVG and role="img" graphics need an accessible name. 1.1.1 A Serious
Audio transcript Prerecorded audio-only content needs a transcript. 1.2.1 A Serious
Video captions Video content must have captions. 1.2.2 A Critical
Video audio description Video content needs audio description or a text alternative. 1.2.3 A, 1.2.5 AA Serious
Required ARIA children Composite ARIA roles must contain their required children. 1.3.1 A Critical
Required ARIA parent ARIA child roles must be inside their required container role. 1.3.1 A Critical
Definition list structure <dl> must be structured as term/description pairs. 1.3.1 A Serious
Definition item placement <dt> and <dd> must be inside a <dl>. 1.3.1 A Serious
Form field labels Every form field needs a label. 1.3.1 A, 3.3.2 A, 4.1.2 A Critical
List structure Lists must only contain list items. 1.3.1 A Serious
List item placement <li> must be inside a list. 1.3.1 A Serious
Styled text as heading Bold paragraphs should not stand in for headings. 1.3.1 A Serious
Table header associations Data tables must have properly associated header cells. 1.3.1 A Serious
Reading order vs visual order CSS reordering should not make reading order diverge from the visual order. 1.3.2 A Moderate
Orientation lock Content must work in both portrait and landscape. 1.3.4 AA Serious
Autocomplete tokens autocomplete attributes must use valid tokens. 1.3.5 AA Serious
Regions with a purpose The purpose of page regions should be programmatically determinable (AAA) 1.3.6 AAA Moderate
Link distinction in text Links inside text must be distinguishable by more than colour. 1.4.1 A Serious
Auto-playing audio control Auto-playing audio must be stoppable or muted. 1.4.2 A Critical
Text contrast Text must have sufficient contrast against its background. 1.4.3 AA Serious
Form control contrast Text inside form controls must have sufficient contrast. 1.4.3 AA Serious
Viewport zoom lock The viewport must let users zoom to at least 200%. 1.4.4 AA Critical
Enhanced text contrast Text must have enhanced contrast against its background (AAA) 1.4.6 AAA Serious
Justified text Blocks of text should not be justified to both margins (AAA) 1.4.8 AAA Moderate
Content reflow Content should reflow to one-dimensional scrolling. 1.4.10 AA Moderate
Form field boundary contrast Form field fills and borders below 3:1 need checking against the field's other identifiers. 1.4.11 AA Serious
Text spacing overrides Text must survive user spacing overrides without being cut off. 1.4.12 AA Serious

Operable

Operable rules
RuleWhat it checksCriterionSeverity
Keyboard-reachable scroll areas Scrollable regions must be reachable by keyboard. 2.1.1 A, 2.1.3 AAA Serious
Timed page refresh The page must not use a timed refresh. 2.2.1 A Critical
Pausable moving content Moving content must be pausable. 2.2.2 A Serious
Looping video control Looping autoplay video must be pausable. 2.2.2 A Serious
Timed refresh (AAA) The page must not refresh or redirect itself on any timer (AAA) 2.2.4 AAA, 3.2.5 AAA Serious
Motion honours reduced-motion Motion set off by scrolling, hovering or focusing should be switchable off. 2.3.3 AAA Moderate
Skip to content The page must offer a way to skip repeated blocks. 2.4.1 A Serious
Page title The page must have a title that describes its topic or purpose. 2.4.2 A Serious
Focus order vs visual order CSS reordering should not make Tab jump against the visual order. 2.4.3 A Moderate
Link names Links must have an accessible name. 2.4.4 A, 4.1.2 A Serious
Generic link text Link text should describe where the link goes. 2.4.4 A Moderate
Placeholder headings and labels Headings and labels must describe their topic or purpose, not be template text. 2.4.6 AA Moderate
Visible focus Keyboard focus must remain visible. 2.4.7 AA Serious
Self-sufficient link text Link text alone must identify where the link goes (AAA) 2.4.9 AAA Moderate
Section headings Sections of written content should begin with a heading (AAA) 2.4.10 AAA Moderate
Unobscured focus Focused elements must not be fully hidden behind overlays. 2.4.11 AA Serious
Fully unobscured focus No part of a focused element may be hidden behind overlays (AAA) 2.4.12 AAA Serious
Pointer gesture alternative Swipe, pan and pinch gestures need a single-pointer alternative. 2.5.1 A Serious
Enhanced target size Interactive targets must be at least 44×44 pixels (AAA) 2.5.5 AAA Serious
Dragging alternative Dragging must have a single-pointer alternative. 2.5.7 AA Moderate
Target size Interactive targets must be at least 24×24 pixels. 2.5.8 AA Serious

Understandable

Understandable rules
RuleWhat it checksCriterionSeverity
Page language The <html> element must declare a valid language. 3.1.1 A Serious
Part language tags lang attributes on page parts must be valid. 3.1.2 AA Serious
Unexpected context change Changing or focusing a control must not unexpectedly change context. 3.2.2 A, 3.2.1 A Serious
Error message linkage Fields marked invalid need their error described in text. 3.3.1 A Serious
Payment form safeguards A form that takes a payment must be reversible, checked or confirmed before submission. 3.3.4 AA Serious
Redundant entry A form should not ask for the same information twice. 3.3.7 A Moderate
Accessible login fields Login fields must not block paste or password managers. 3.3.8 AA, 3.3.9 AAA Serious
CAPTCHA in a login step A picture-puzzle CAPTCHA in an authentication step needs an alternative (AAA) 3.3.9 AAA Serious

Robust

Robust rules
RuleWhat it checksCriterionSeverity
Allowed ARIA attributes ARIA attributes must be supported by the element’s role. 4.1.2 A Minor
Valid ARIA values aria attributes must exist and have valid values. 4.1.2 A Critical
ARIA field names ARIA fields and value widgets must have an accessible name. 4.1.2 A Serious
Focusable hidden content Nothing focusable may sit inside aria-hidden="true". 4.1.2 A Serious
aria-label placement aria-label or aria-labelledby on a plain container is prohibited by ARIA, so its announcement is not guaranteed. 4.1.2 A Moderate
ARIA state the element really has cannot be reached A state the element has must be exposed through a role that supports it. 4.1.2 A Moderate
ARIA id references ARIA id references must point to elements that exist. 4.1.2 A Moderate
Button names Buttons must have an accessible name. 4.1.2 A Critical
Widget item names Tabs, menu items, options and tree items need an accessible name. 4.1.2 A Serious
Frame titles Frames must have a title describing their content. 4.1.2 A Serious
Popover and command targets popovertarget and commandfor must point at an element they can act on. 4.1.2 A Serious
Label target references label[for] must reference a form control that exists. 4.1.2 A Serious
Nested controls A control must not contain another control. 4.1.2 A Serious
Required role states Some roles require a state attribute to work. 4.1.2 A Serious
Disclosure names Disclosure controls (<summary>) need an accessible name. 4.1.2 A Serious
Valid roles role attributes must use valid ARIA roles. 4.1.2 A Critical

Best practice

These 21 rules go beyond what WCAG requires. They run when Best practices is switched on.

Best practice rules
RuleWhat it checksCriterionSeverity
Duplicate access keys The same accesskey must not be assigned twice. Best practice Serious
Button types in forms Buttons inside forms should declare their type. Best practice Minor
Dialog names Dialogs should have an accessible name. Best practice Serious
Empty headings Headings must contain text. Best practice Minor
Grouped field labels Radio and checkbox groups should be grouped with a label. Best practice Moderate
Heading order Headings should step down one level at a time. Best practice Moderate
One main landmark The page should have exactly one main landmark. Best practice Moderate
Top-level landmarks banner, main, contentinfo and complementary landmarks must be top level. Best practice Moderate
Distinguishable landmarks Landmarks of the same type need distinguishing labels. Best practice Moderate
Multiple labels Form fields should not have multiple labels. Best practice Minor
New-window warnings Links opening a new window should say so. Best practice Minor
Autofocus on load autofocus disorients assistive-technology users. Best practice Minor
Leading page heading Every page should start its outline with an <h1>. Best practice Moderate
Positive tabindex Positive tabindex values disrupt the natural focus order. Best practice Serious
Redundant alt phrasing alt text should not start with "image of" or similar. Best practice Minor
Redundant ARIA attributes aria attributes should not duplicate native HTML attributes. Best practice Minor
Redundant aria-label aria-label should not repeat the visible text. Best practice Minor
Redundant image alt Image alt should not repeat adjacent link or button text. Best practice Minor
Redundant roles role attributes should not repeat the element’s built-in role. Best practice Minor
Redundant tabindex tabindex="0" is unnecessary on natively focusable elements. Best practice Minor
Content outside landmarks All readable content belongs inside a landmark region. Best practice Moderate