Accessible by construction, verified by test.
Forma builds on native HTML semantics so that keyboard, focus, form and assistive-technology behavior come from the browser. This page states what Forma guarantees, what applications must supply, how the catalog is tested, and the limitations we know about.
What Forma provides
- Native elements (
button,input,select,dialog,details, Popover API) carry role, name, state and keyboard behavior. - Visible two-tone focus indicators that work on light and dark surfaces.
- State is never communicated by color alone: text, shape, position or pattern repeats it.
- Forced-colors mode projects every semantic color token to system colors.
- Reduced motion removes spatial travel; state still changes immediately.
- Components reflow at 320 CSS pixels and at 200% zoom without page-level horizontal scrolling, with approximately 44px touch targets.
What your application supplies
- Meaningful labels, headings, instructions and error text in the user's language.
- Page structure and landmarks, and focus management for behavior beyond native HTML.
- Live-region timing, announcements and any behavior Limen adds (roving focus, typeahead, drag alternatives).
Each component page has an Accessibility section that splits these responsibilities for that component.
How the catalog is tested
- Every canonical pattern is checked with axe-core in Chromium, Firefox and WebKit, in light and dark themes (
tests/browser/accessibility.spec.mjs). - Every generated documentation page is loaded at 320, 390 and 430 CSS pixels, a tablet width and desktop, and at 200% text size, and checked for page-level overflow and undersized site targets (
tests/site-browser/). - Generated pages are checked for duplicate ids, heading order, broken internal links and axe-core violations.
- Catalog coverage (every component has purpose, examples, a mobile example, API, states, accessibility, responsive, motion, guidance and related entries) is enforced in CI (
npm run catalog:check).
Known limitations
- The documentation site runs no JavaScript by policy. Code is copied by selecting it (one click or tap selects a whole block) or by opening the Raw HTML link, not with a clipboard button.
- There is no full-text search box; the A–Z index filters by family with CSS and works with the browser's find command.
- Mobile demonstration frames have a fixed height and may need internal scrolling for tall examples.
- The documentation chrome is light-only. Component dark themes are demonstrated in the Brand Laboratory.
- Automated checks do not replace testing with assistive-technology users. Visual Engineering stress screens are engineering screens, not human-subject validation.
- Category previews are inert static renderings; interactive behavior is on each component page.