What they are
Rule-based checkers read a page’s code. Some WCAG requirements are about what happens when a person changes the page or moves through it, and code alone does not show that. Supervisor’s own checks do the thing a person would do, in the same real browser, and compare the page after with the page before.
There are six rules. In the issue list their ids start with sv:.
Text spacing
WCAG 1.4.12 says a page must stay readable when a reader sets wider text spacing. The check sets the spacing WCAG names (line height 1.5, letter spacing 0.12 em, word spacing 0.16 em, paragraph spacing 2 em) and reports text that is now cut off or runs out of its box.
- Rule:
sv:text-spacing
Zoom to 200%
WCAG 1.4.4 says text must be resizable to 200% without losing content. The check zooms the page to 200% and reports two things:
sv:zoom-clip: text that is cut off or runs out of its box at 200%.sv:zoom-text-size: text sized in viewport units, which does not grow when the page is zoomed.
Reflow at 320 px
WCAG 1.4.10 says content must fit a 320 px wide window without scrolling sideways. That is the same as a 1280 px window zoomed to 400%. The check narrows the page to 320 px and reports elements that stick out sideways.
- Rule:
sv:reflow
The Tab walk
The check presses the Tab key for real, from the top of the page, up to 60 times, so the page’s own key handling takes part. It reports two things:
sv:focus-hidden(WCAG 2.4.7): the keyboard focus lands on an element that cannot be seen.sv:keyboard-trap(WCAG 2.1.2): the focus goes round the same one or two elements, and 25 more Tab presses, Shift+Tab and Escape do not get it out, on a page that has more to reach.
Whether a focused element shows a visible focus indicator is checked separately, with Alfa and screenshot comparison.
Fewer false alarms
- Each check compares after with before. A box that is already cut off at the normal size, such as a carousel or a text shortened with an ellipsis, is not counted.
- A few pixels of overflow at 320 px are ignored.
- An embedded frame is not called a keyboard trap, because moving through its links looks like one element from outside.
Limits
- The checks run at the desktop size, on each page of a crawl. They do not run when a check follows a journey, because resizing the page and pressing keys would disturb the journey.
- They look at the page as it loads. A dialog or a menu that opens later is not covered.
- For each rule, up to 10 elements per page are kept.
- They cannot tell whether the focus order makes sense, or whether a whole task can be finished with a keyboard. That takes a person.
Where the findings go
Every finding from these checks waits for a person as “needs review” before it counts in the accessibility statement. Your agent can show you the element and its screenshot, and you confirm it or mark it as a false positive with update_accessibility_issue.