Does WCAG require keyboard focus to follow visual order?
What 2.4.3 requires for sequential navigation, and when tabindex or CSS order fails it.
Read MoreResources
Each guide answers a specific question, cites the WCAG criterion or the DOJ source, and links to the related pages.
What 2.4.3 requires for sequential navigation, and when tabindex or CSS order fails it.
Read MoreWhat 1.3.5 requires when a field collects information about the user, and which inputs are out of scope.
Read MoreWhat 1.4.13 requires for custom tooltips and hover menus: dismissible, hoverable, and persistent.
Read MoreWhat 1.4.11 requires for UI components and graphics, and how it differs from text contrast.
Read MoreWhat 1.3.4 requires, and when a single orientation is essential.
Read MoreWhat 1.4.12 requires when a reader increases spacing, and why the default styles can stay tighter.
Read MoreWhat 1.4.10 requires at 320 CSS pixels, and how it differs from 200% text resize.
Read MoreWhat 3.3.1 requires, and why a red border or “Invalid” alone does not meet it.
Read MoreWhat 3.3.3 requires when the correction is known, and when security limits the hint.
Read MoreWhat 3.3.2 requires, and why a placeholder alone does not meet it.
Read MoreWhat 4.1.3 requires, and why Title II (2.1 AA) includes status messages.
Read MoreWhat 2.4.6 requires when headings are used, and how that differs from the page title.
Read MoreWhat 2.4.11 requires at WCAG 2.2 AA, and why Title II (2.1 AA) does not include it.
Read MoreWhat 3.3.8 requires, and why Title II (2.1 AA) does not include accessible authentication.
Read MoreWhat 2.5.7 requires at WCAG 2.2 AA, and why Title II (2.1 AA) does not include it.
Read MoreWhat 2.3.1 requires, and why a pause control does not make seizure-risk flashing allowed.
Read MoreWhy a red border or a red asterisk fails 1.4.1 unless another cue is present.
Read MoreWhat 1.4.2 requires after three seconds, and why the system volume does not count.
Read MoreWhat 2.4.2 requires, and why “Untitled Document” fails.
Read MoreWhat 2.2.2 requires when motion starts by itself and lasts more than five seconds.
Read MoreWhen 2.4.4 allows context, and when a nearby heading is not enough.
Read MoreWhat 3.1.1 requires on the html element, and when a passage needs its own lang.
Read MoreWhat 1.4.4 requires, and how reflow at 320 CSS pixels is a separate check.
Read MoreWhy Level AA is 24 by 24 CSS pixels, and why 44 pixels is Level AAA.
Read MoreWhat 2.4.7 requires, and when removing the outline still fails.
Read MoreWhat bypass blocks requires, and when a hidden skip link still fails.
Read MoreWhy keyboard access is Level A, and what to check on menus, dialogs, and forms.
Read MoreWhat automated checks find, and which success criteria still need a person.
Read MoreWhy a toolbar added after the page loads does not satisfy the success criteria.
Read MoreHow the ADA applies to websites and what a practical program includes.
Read MoreHow WCAG 2.1 and 2.2 map to fixes on a real site.
Read MoreWhat 2.2 adds, and which version a contract should name.
Read MoreDeadlines for state and local government websites and apps.
Read MoreWhat an audit checks, and which templates to start with.
Read MoreWhen an image needs a text alternative, and when it should be empty.
Read MoreLabels, errors, keyboard access, and authentication.
Read MoreThe 4.5:1 and 3:1 ratios in WCAG 2.1 Level AA.
Read MoreWhen an accessible name helps, and when it hides the visible label.
Read MoreTags, reading order, and when HTML is the better format.
Read MoreCaptions, transcripts, and audio description.
Read MoreFilters, cart, and checkout without a mouse.
Read MoreShort answers on the ADA, WCAG, overlays, and audits.
Read More