Accessibility
Accessibility statement
The standard this site is built and checked to, what that checking does and does not cover, and how to tell us when something blocks you.
- Effective date
- Last reviewed
1The standard this site is built to
CertaSafe builds this site to WCAG 2.2 Level AA. It is the floor the design system sets for every page, component, and interaction, not a target for later, and it applies to the public site, the ordering flow, and the customer portal alike.
Accessibility is treated here the way a measurement is treated: as something with a stated basis that a person can check, rather than an assurance. What follows is that basis.
2How that is checked
Contrast is computed, not judged by eye. Every color pair the site uses carries its measured ratio and its result in the design system, for text and for graphical objects and control boundaries separately. A pair that only passes at large sizes is recorded as large text only and used that way.
Focus is defined once and applies everywhere. A single visible focus treatment is set in the design tokens for every link, button, input, select, textarea, summary, and anything else that can hold focus, so a keyboard user sees the same clear indicator on every control on every page rather than one that varies by component.
Motion never gates content, and reduced motion is honored. Navigation, headings, actions, and page content are usable before, during, and after any animation. When your system asks for reduced motion, animation durations collapse and the home page's opening film is replaced by its own end frame, so you get the resolved picture rather than an empty space where a video would have been.
Every page starts with a skip link. The first thing in the tab order on every page is a link to the main content, so a keyboard or screen reader user is never required to walk the navigation to reach the page.
Facts are text, never pictures of text. Prices, timing, sample requirements, scope, and limitations are selectable, resizable text. Nothing that carries a fact is baked into an image, so it survives zoom, reflow, a screen reader, and a copy and paste.
Real flows are exercised in a real browser. Ordering, sign in and routing, package pricing, price consistency, and COA administration are each driven end to end through a browser against a running copy of the site, rather than tested only as functions.
3What that checking does not cover
There is no automated accessibility test in this site's continuous integration, and no independent audit or accessibility conformance report has been carried out.
So this statement names the standard the site is built and checked to, and stops there. It does not claim conformance with WCAG 2.2 Level AA, because claiming conformance without having tested for it would tell you the work is finished when nobody has verified that it is.
The practical consequence is that a barrier can exist here without CertaSafe knowing about it. If you hit one, telling us is the fastest way it gets fixed, and the section below is how.
4Reporting a barrier
A barrier report reaches support@certasafelabs.com and is answered there.
If it is easy to include, the address of the page and what you were trying to do when you hit the barrier will usually let us reproduce it on the first try. Neither is required, and a report without them is still worth sending.
Support contact. support@certasafelabs.com, telephone 707-731-9296, 8 to 5 daily.
5Changes to this statement
The dates at the top of this page are its record. When the site's accessibility practice changes, or when it is checked in a way it has not been checked before, a new version publishes here with its own effective date, and the version it replaced stays identifiable.
This version took effect on 1 September 2026. When a policy changes, the new version publishes here with its own effective date, and the version it replaced stays identifiable.