The admin holds itself to WCAG 2.1 AA, and verifies it rather than claiming it: the end-to-end suite runs axe over the pages in both themes and walks the interface by keyboard.
Keyboard
Everything is reachable and operable by keyboard. Dialogs trap focus and restore it to whatever opened them; menus close on Esc and hand focus back to their trigger.
A few details that are easy to get wrong and are handled deliberately:
- Deleting the tile your focus was on hands focus to the surrounding section rather than dropping it on the document body.
- The collapse toggle for the properties panel exists in two places — inside the panel and in the top bar — and passes focus between the two halves as it moves.
- Tables and grids announce their selection state, and the
{n} selectedbar is announced rather than merely appearing.
Content is checked too
Accessibility here is not only the interface. The rich-text editor checks the content you are writing — heading order, table headers, link text, language markers — and shows every finding while you can still act on it, not after a save fails.
The server enforces the errors; the editor additionally shows the advisory ones. An authoring tool that only refuses at the end does not help anybody produce accessible content. See the rich-text editor.
Alt text is writable at upload and in the asset drawer, and the Insights dashboard counts images that have none.
Language
Every locale slug is a BCP-47 language tag, so a translated field can be
rendered with a correct lang attribute without a mapping table, and text
direction is resolved by the server so the admin never guesses whether a
language is right-to-left.
A field written in a different language from the entry can declare it, and a passage inside a rich-text body can too.
Theme
Light, dark or system, in Preferences on your own user page. The choice is stored server-side against your account, so it follows you to another browser, and it is applied before first paint — there is no flash of the wrong theme.
The palette is measured rather than assumed: the design system’s colour pairings are checked against 4.5:1 for text and 3:1 for control boundaries.
Where the gaps are
Two honest caveats
Content is not checked for colour contrast. The editor lets an author set a text colour and a highlight, and nothing measures the pair. A body can be made unreadable and the system will store it.
The checks cover the shipped admin. A plugin you write is your own
responsibility — the same test harnesses are available to you, and the
accessibility skill in the repository documents the conventions, but nothing
automatically holds a third-party plugin to them.