Skills CX operations
Support accessibility review
Accessibility reviews often stop at the marketing site. Support is where problems become urgent — and where teams hide behind "call us", CAPTCHA gates, and PDF-only policy documents. This is a practical operations audit, not legal advice. It answers: can someone with common access needs complete a support journey?
npx rulebase-skills install cx-accessibility-reviewWhen to use it
Reach for this when someone says any of these — they are the phrases the skill itself triggers on:
- “support accessibility audit”
- “can customers with disabilities reach us”
How it works
The method, in the order the skill runs it. The full procedure — tables, worked examples and the edge cases — is in the skill itself.
Scope the journeys
Test end-to-end paths, not individual pages.
Authentication and barriers
Document alternate paths agents can invoke — not "we'll figure it out."
Alternate formats
Customers may request: Large print, plain language summary, Structured email instead of PDF attachment, Transcript of phone call.
Agent tooling accessibility
Agents with disabilities also need accessible workspaces. Inaccessible internal tools produce inaccessible replies — template pickers, knowledge search, after-call work forms. Include internal UI in scope when agent population includes AT users.
Scoring and severity
Do not average severities into one score. List blockers first with journey and reproduction steps.
Traps
Overlay widgets. Third-party "accessibility" buttons do not fix support forms.
Related skills
Free and open source, and vendor-neutral — it reads the conversations from whichever helpdesk you already run. Browse all 149 skills · connect your helpdesk over MCP · source on GitHub
