Accessibility

Our target

Studio Builder aims to meet WCAG 2.2 Level AA. That is the standard referenced by the EU Accessibility Act and EN 301 549, by the ADA in the United States, and by AODA in Ontario.

What we do

• Color contrast is checked by a test that fails the build if body text, links or the focus ring fall below AA ratios. It reads the design-token source file. The values actually sent to browsers are a hand-kept copy, so a change made only to that copy would not be caught.
• Every page has a skip link, landmark regions, and a unique descriptive title.
• The search palette (Ctrl/Cmd+K) implements the full combobox pattern: keyboard navigation, a focus trap, focus restored to where you were, and live result announcements.
• All animation is disabled when your system requests reduced motion.
• Data tables built into the site's own pages carry a caption and row and column header associations. Tables written inside article text by an editor are not covered and may have neither.
• An automated accessibility audit runs in continuous integration and fails below a score of 95. It samples five representative pages, and it is triggered by pull requests, so it covers neither every page nor changes committed directly.

Known gaps

We publish these rather than wait until they are fixed, so you know what to expect:

• Touch target sizeshave not been measured against WCAG 2.2's 24×24 CSS pixel minimum (SC 2.5.8). Some controls may be smaller than that.
• Focus appearance(SC 2.4.11) has not been measured. We check the focus ring's contrast, which is necessary but not sufficient for it.
• The staff admin area does not meet this target. Its tables cannot be sorted by keyboard. It sits behind a login and is not part of the public site, but we are not claiming otherwise.
• Screen-reader testing has been done against the accessibility tree rather than with real assistive technology. Announcement quality in NVDA, JAWS and VoiceOver is unverified.
• Automated coverage catches roughly a third of issues. The checks above are necessary, not sufficient.

Tell us about a barrier

If something on this site is hard or impossible to use, we want to hear about it, including the small things. Email accessibility@studiobuilder.co. Tell us the page and what happened; if you can, mention the browser and any assistive technology you were using.

We aim to acknowledge within five working days. If a fix will take longer, we will say so and offer another way to get at the information.

How this was assessed

Self-assessment, by code review against WCAG 2.2 AA plus automated auditing in continuous integration. No third-party accessibility audit has been carried out, and no formal VPAT or accessibility conformance report exists for this site.