How we build for accessibility
We work toward WCAG 2.1 AA on this site and on the sites we build for clients. This page explains what that means and where things stand. Last updated July 22, 2026.
The standard we build toward
WCAG 2.1 AA is the widely used benchmark for web accessibility: guidelines that make sites workable for people using screen readers, keyboard navigation, magnification and other assistive tools. We treat it as a working standard for this site and for client projects.
It’s a working standard because the web keeps changing, from browsers to assistive technology. We audit the site and fix what we find, and we keep doing it after launch.
What that looks like on this site
Keyboard access
Every interactive element, from the navigation to the forms, is meant to be reachable and usable with a keyboard alone, in a logical order, with a visible focus indicator.
Color and contrast
Text and interface colors are chosen to meet AA contrast ratios, so content stays readable in bright rooms and for readers with low vision or color blindness.
Reduced motion
With reduced motion turned on in your system settings, the site’s transitions are switched off and the video at the top of a page shows a still image instead. Where video plays, a button pauses it.
Structure and labels
Pages use headings in a sensible order, descriptive link text, labeled form fields and alternative text on meaningful images, so screen readers get the same information sighted visitors do.
We hold the sites we build for clients to the same bar
New client builds are developed against the same guidelines: semantic structure, keyboard operation, contrast-checked palettes and forms that assistive technology can navigate. When we redesign or take over an existing site, we flag accessibility gaps during scoping, so fixing them becomes part of the plan. For organizations with formal obligations, we can make accessibility review an explicit part of the engagement.
Where things stand, and how to reach us
This is an ongoing effort rather than a certification. Some third-party embeds and older documents may fall short of the standard, and we work through issues as we find them.
If any part of this site is hard for you to use, we want to know. Email hello@framematic.ai with the page and the problem, and we’ll reply and fix what we can.
Tell us what you need built
A person reads every request and replies within one business day.
Start a project