obsidian/wiki/tech-patterns/payload-cms-admin-accessibility.md
2026-05-15 15:13:56 +01:00

44 lines
1.9 KiB
Markdown

---
title: "Payload CMS — Admin Panel Accessibility"
aliases: [payload-accessibility, payload-a11y]
tags: [payload-cms, accessibility, a11y, wcag, admin-panel]
sources: [raw/admin__accessibility.md]
created: 2026-05-15
updated: 2026-05-15
---
# Payload CMS — Admin Panel Accessibility
Payload's admin panel has an active accessibility program targeting WCAG 2.2 AA compliance.
## Compliance Status
| Standard | Status | Notes |
|----------|--------|-------|
| WCAG 2.2 AA | **In Progress** | Actively working toward full compliance |
Current status report: [GitHub Discussion #14489](https://github.com/payloadcms/payload/discussions/14489)
## Testing Approach
- **Axe** integrated into e2e test suites — automated long-term compliance checking
- Custom utilities for keyboard navigation, window overflow, and focus indicator testing
- Manual screen reader testing with assistive technologies
## Key Takeaways
- Payload is **not yet fully WCAG 2.2 AA compliant** — "in progress" as of 2026-05
- Accessibility issues should be reported via the [GitHub Discussion](https://github.com/payloadcms/payload/discussions/14489)
- Axe in e2e = regressions caught automatically; don't rely solely on manual testing
- If building custom Payload UI components, test with keyboard nav and screen readers to match the panel's own approach
- Focus indicators and keyboard navigation are explicitly tested — custom fields should follow the same standard
## Related Articles
- [[wiki/tech-patterns/payload-cms-installation|Payload CMS — Installation & Setup]]
- [[wiki/tech-patterns/payload-cms-access-control-overview|Payload CMS — Access Control Overview]]
- [[wiki/tech-patterns/payload-cms-field-access-control|Payload CMS — Field-Level Access Control]]
## Sources
- `raw/admin__accessibility.md` — from [payloadcms.com/docs/admin/accessibility](https://payloadcms.com/docs/admin/accessibility)