Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Use when reviewing support UI across multi-page flows such as checkout, onboarding, account recovery, or support journeys. Compare multiple pages in the same variation instead of reviewing a single page alone.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-01 | ✗→✓ | ▲ Improved | 524% | 0% |
| case-02 | ✗→✓ | ▲ Improved | 53% | 0% |
| case-06 | ✗→✓ | ▲ Improved | -16% | 0% |
| case-21 | ✗→✓ | ▲ Improved | -1% | 0% |
| case-03 | ✓→✓ | = Same ✓ | -7% | 0% |
Users who need help during a task should not have to hunt for it on every screen. Predictable placement reduces stress and makes support easier to find when a user is already struggling.
Audit repeated help mechanisms across this set of pages. Check whether contact links, chat triggers, help-center links, or support phone numbers appear in the same relative order on each page.
Move repeated help mechanisms into a consistent location and keep their relative order stable across the flow at the same breakpoint.
Explain WCAG Consistent Help, what counts as a repeated help mechanism, and why consistent serial order matters more than pixel-perfect placement.
Review page chrome, support UI, and responsive layouts related to Keep repeated help mechanisms in a consistent location. Flag exact pages or breakpoints where repeated help moves to a different relative position.
For full implementation details, code examples, and framework-specific guidance, see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/accessibility/consistent-help
Other measured skills in the registry, with their headline benchmark lift.