mphaxise Accessibility Review
Use this skill when the user asks whether a UI, workflow, document, or product experience is accessible.
This is a Praneet-specific hand-port enhancement. It expands the existing design and QA layer so accessibility is a first-class quality bar, not a footnote.
Workflow
- Identify the experience and supported platforms.
- Check evidence:
- source code
- screenshots
- running UI
- design docs
- existing accessibility tests
- Review core areas:
- keyboard and focus order
- screen reader labels and semantics
- color contrast and non-color affordances
- text scaling and responsive layout
- motion sensitivity
- form labels, errors, and recovery
- cognitive load and plain language
- localization and reading direction when relevant
- mobile Dynamic Type or platform equivalents
- Report findings with severity, evidence, and recommended fix.
- Route follow-up:
design-reviewfor visual polishqafor flow verificationresponsible-design-reviewfor harm or exclusion risks
Guardrails
- Do not claim WCAG compliance from a superficial scan.
- Do not rely only on color contrast when interaction semantics are unknown.
- If assistive technology testing was not run, say so.