Accessibility

This is a plain-language account of how accessible this site is and is not, written to be read rather than survived. It is not legal advice, and it is not a claim of formal conformance — it is a description of what we have done and what we have not.

The commitment

This site should work for anyone who arrives at it — with a keyboard, a screen reader, a magnifier, a touchscreen, reduced motion turned on, or JavaScript turned off. We treat an accessibility defect the same as a functional one: it gets written down, it gets fixed, and the fix gets checked.

We target the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. Targeting a standard is not the same as certifying against it, and this page does not claim conformance — section 03 is the honest part.

What is built in

These are properties of the design system every page here is built from, not per-page afterthoughts.

Semantic HTML — real header, nav, main and footer landmarks, one h1 per page, and headings that descend in order rather than by size.
A skip link — the first thing you reach with the Tab key on every page jumps straight past the running head to the content.
Keyboard operation — every interactive element is reachable with Tab and operable with Enter or Space. The mobile index sheet traps focus while open, closes on Escape, and returns focus to the button that opened it.
Visible focus — focus draws a solid two-pixel outline with clear offset, and it inverts on dark sections so it never disappears against the navy.
Contrast — body text is set to meet at least 4.5:1 against its paper, and large text and interface parts at least 3:1. The palette is deliberately narrow so combinations can be checked rather than assumed.
Never colour alone — a form error is text with a mark beside it, not a red border. There is no red in the palette at all.
Reduced motion — every animation the system defines is declared in one place and switched off under prefers-reduced-motion. Nothing moves that you did not ask to move.
Touch targets — interactive elements are at least 44 pixels tall, list rows at least 64, and primary actions at least 56.
Readable text — body copy is 17px on a 1.65 line height, capped at a 66-character measure, and it scales with browser zoom rather than being pinned to fixed pixels.
It works without JavaScript — every scripted enhancement is gated so that with scripting off you get the plain version: full navigation, no hidden steps, the enquiry form present and submittable.
No traps — no autoplaying audio, no hijacked scrolling, no dialogue you cannot escape from, and no horizontal page scroll between 375 and 1440 pixels wide.

Where we fall short

The useful part of a statement like this is the part that admits things. Known, current, and honest:

No independent audit. Everything above comes from our own testing and our own design rules. No third party has assessed this site, and we do not hold an accessibility certification of any kind.
Assistive-technology coverage. This site has not been tested with a screen reader. It is built to semantic HTML with labelled controls, visible focus, and keyboard operation checked by hand — but that is not the same thing as testing with NVDA, JAWS, VoiceOver or Orca, and we will not claim coverage we have not done. If you use one and something blocks you, tell us and we will fix it and say so here.
The enquiry builder. The scope builder on the contact page moves through steps without a page load. It degrades to a single labelled checklist without JavaScript, but its focus handling between steps has not been verified end to end with a screen reader. Its focus handling has been checked programmatically — moving focus to the heading of each step and announcing the change — but not yet confirmed with a real screen reader.
Photography. Images are labelled, but a few carry meaning that a short alt text describes only roughly. Where a picture matters, the surrounding text should say the same thing — that is not yet true everywhere.
The horizontal product rail. On the home page the product line sits in a rail that scrolls sideways on small screens. Every card in it is an ordinary link and reaches by Tab, but sideways scrolling is awkward with some input devices.
Typefaces come from Google Fonts. Their delivery is outside our control. If the request is blocked or fails, the page falls back to a system face and stays readable.

If you hit something that is not on this list, it is not that we decided it was acceptable — we did not know. Please tell us.

Standards we work to

WCAG 2.1 Level AA is the target for everything on this site. Where material is federal-facing, we also work to Section 508 of the US Rehabilitation Act as revised in 2017, which adopts WCAG 2.0 Level AA by reference.

Work we build for clients is held to the same standard by default, and to a stricter one where a contract requires it. If accessibility conformance is a delivery requirement for your project, say so at scoping and it becomes part of the written agreement rather than a hope.

Reporting a barrier

If something here does not work for you, tell us — it is the fastest way for it to get fixed, and you will be talking to the person who wrote the code.

What helps us reproduce it

The address of the page.
What you were trying to do when it stopped working.
Your browser and operating system, and the assistive technology you use, if any.
Whether you want a workaround in the meantime, or just want it fixed.

Send it to [email protected]. If email is itself the barrier, call (801) 917-4617 — the number reaches a person, not a menu.

What happens next

Within 24 hours, Mountain Time, we reply and tell you whether we can reproduce it.
Then you get either a fix, or a written description of the workaround and the date the permanent fix is planned for. We will not leave you guessing which.
Anything that blocks access outright for a group of people is treated as urgent and triaged the same day.

If we do not resolve it, you are free to escalate — in the United States, accessibility complaints can be raised under the Americans with Disabilities Act, or under Section 508 for federal-facing material. We would much rather you gave us the chance to fix it first.

Keeping this current

This statement is reviewed after any significant redesign of the site, whenever a reported barrier changes what is true here, and at least once a year regardless. The date at the top is the last time it was reviewed, not the last time the site changed.