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.
71
87%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
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
48405aa
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.