Accessibility basics for themes
This page is for designers who want every visitor to be able to use their design, including people who use a keyboard, a screen reader, high zoom or high contrast. It lists what a design is responsible for, and links a page for each topic.
Contents
What the design owns
Content, templates and CSS share the work. The design decides the page structure, the navigation, the focus styles, the colors, the forms' markup and the behavior of scripts. A design that gets these right makes every page accessible by default; one that gets them wrong cannot be fixed by editors.
The ten basics
- Language and direction.
<html lang="{$site.http_equiv.Content-language|wash}">anddir="rtl"for right-to-left languages (The pagelayout). - Landmarks and one
<h1>.<header>,<nav>,<main id="main">,<footer>; one<h1>per page, headings in order (Landmarks and headings). - A skip link as the first focusable element (Skip links).
- Visible focus on every interactive element, never
outline: nonewithout a replacement (Keyboard and focus). - Contrast of at least 4.5:1 for text, 3:1 for large text, icons and focus rings, in light and dark mode (Color contrast).
- Alt text printed from the image field (
|wash),alt=""for decoration (Images in a design). - Forms with labels and error messages tied to their fields (Accessible forms).
- Motion only when wanted: respect
prefers-reduced-motion(Reduced motion). - Zoom and reflow: works at 200% and on a 320 px viewport (Testing at zoom levels).
- Scripts that keep state in ARIA: a menu button says
aria-expanded, a dialog traps and returns focus.
What editors own
Alternative texts of images, meaningful link texts, heading order inside rich text, captions of videos. The design helps by printing what editors enter (alt text, captions) and by giving rich text headings sensible styles.
How the project tests
The administration's pages are checked with these targets, which suit public designs too:
- axe (an automated accessibility checker, run in the browser or by a script) finds no serious or critical issues;
- keyboard only: every control reachable with Tab, usable with Enter and Space, Escape closes overlays;
- light and dark mode, at 1440 px, at 960 px scale 2 and at 375 px;
- forced colors (Windows high contrast): admin4's stylesheets have dozens of
@media (forced-colors: active)rules so borders and focus stay visible.
Run the accessibility checklist before every release of a design.
Related pages
- Checklist: accessibility
- Color contrast
- Keyboard and focus
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.
Become an Exponential Partner
Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.