Accessibility Checklists

Accessible Input Checklist (WCAG)

Every Input rule that WCAG 2.2, WAI-ARIA or the APG backs, in one checklist, with the success criteria behind each rule and their level.

Here's every rule for the Input that WCAG 2.2, WAI-ARIA or the APG backs, in one list you can work through when you build or review one. Each row names the WCAG 2.2 success criteria behind its rule, with their level, and links to the rule's table on its layer's page, where we explain why it's there. A rule that rests on WAI-ARIA or the APG alone says "None".

We build this list from the Input's checklists, so it always matches them. It leaves out the rules that rest only on HTML and the ones that are our own, so you'll find every rule in the Input's checklist.

UI rules

RuleLevelRequirementWCAG 2.2Basis
input/contrastMustThe value, the placeholder, prefixes and suffixes have a contrast of 4.5:1, and the focus ring has 3:1 against the page1.4.3 Contrast (Minimum) (AA), 1.4.11 Non-text Contrast (AA)WCAG 1.4.3, 1.4.11 (AA)
input/boundary-contrastMustThe border has a contrast of 3:1 against the page, so an empty input stays visible1.4.11 Non-text Contrast (AA)WCAG 1.4.11 (AA)
input/focus-visibleMustFocus shows an outline at least 2px thick around the whole field, outside its border2.4.7 Focus Visible (AA), 2.4.13 Focus Appearance (AAA)WCAG 2.4.7 (AA), 2.4.13 (AAA)
input/target-sizeMustThe field is at least 24px tall, with a hit area at least 44px tall on touch screens2.5.8 Target Size (Minimum) (AA), 2.5.5 Target Size (Enhanced) (AAA)WCAG 2.5.8 (AA), 2.5.5 (AAA)
input/resizableMustThe field is sized with min-height and padding in rem, so it grows with its text instead of clipping it1.4.4 Resize Text (AA), 1.4.12 Text Spacing (AA)Open Components, beyond WCAG 1.4.4, 1.4.12 (AA)
input/fits-valueShouldIts width fits the value it expects, like a short one for a postcode, and never outgrows the screen1.4.10 Reflow (AA)Open Components, beyond WCAG 1.4.10 (AA)

UX rules

RuleLevelRequirementWCAG 2.2Basis
input/native-elementMustIt's a native <input>, and never a contenteditable element2.1.1 Keyboard (A), 4.1.2 Name, Role, Value (A)Open Components, beyond WCAG 2.1.1, 4.1.2 (A)
input/visible-labelMustEvery input has a visible <label>, linked with for, rather than a placeholder alone, unless it's a search next to its Search button, named with aria-label1.3.1 Info and Relationships (A), 3.3.2 Labels or Instructions (A), 4.1.2 Name, Role, Value (A)WCAG 1.3.1, 3.3.2, 4.1.2 (A)
input/label-in-nameMustAn aria-label or aria-labelledby includes the visible label, ideally at the start2.5.3 Label in Name (A)WCAG 2.5.3 (A)
input/describedShouldHints, like the format it expects, are linked with aria-describedby, and a placeholder only ever shows an example1.3.1 Info and Relationships (A)WCAG 1.3.1 (A), Open Components
input/decorative-slotsMustleading and trailing are hidden from assistive technologies with aria-hidden, while actions stay reachable1.1.1 Non-text Content (A)WCAG 1.1.1 (A)
input/units-in-labelMustA prefix or a suffix, like a currency or a unit, is in the label or the hint as well1.3.1 Info and Relationships (A)WCAG 1.3.1 (A)
input/input-purposeMustAn input that asks about the person filling it in has the matching autocomplete, like email or tel1.3.5 Identify Input Purpose (AA)WCAG 1.3.5 (AA)
input/keyboardMustTab reaches the input and then its actions, and the browser's text editing keys work as they do in any text field2.1.1 Keyboard (A)WCAG 2.1.1 (A)
input/allow-pasteMustPasting, autofill and password managers are never blocked3.3.8 Accessible Authentication (Minimum) (AA)WCAG 3.3.8 (AA)
input/error-messageMustAn invalid input has an error message, in text and linked with aria-describedby, that says what's wrong and how to fix it1.4.1 Use of Color (A), 3.3.1 Error Identification (A), 3.3.3 Error Suggestion (AA)WCAG 1.4.1, 3.3.1 (A), 3.3.3 (AA)
input/invalid-stateMustAn input sets aria-invalid="true" while its error message shows, and only looks invalid when it does4.1.2 Name, Role, Value (A)WCAG 4.1.2 (A), Open Components
input/action-buttonsMustButtons in actions are named Buttons that Tab reaches after the input, and one that goes away moves focus back to the input2.1.1 Keyboard (A), 2.4.3 Focus Order (A), 4.1.2 Name, Role, Value (A)WCAG 2.1.1, 2.4.3, 4.1.2 (A)
input/focus-not-obscuredMustSticky headers and footers never cover a focused input, for example thanks to scroll-padding2.4.11 Focus Not Obscured (Minimum) (AA), 2.4.12 Focus Not Obscured (Enhanced) (AAA)WCAG 2.4.11 (AA), 2.4.12 (AAA)

AX rules

RuleLevelRequirementWCAG 2.2Basis
input/role-and-nameMustIt can be found by its role and label alone, with getByRole("textbox", { name }), or with getByLabel for a password4.1.2 Name, Role, Value (A)WCAG 4.1.2 (A)

Sources

Copyright © 2026