Accessibility Statement

Last updated: July 22, 2026

What we have done

Specific, checkable claims about this site as it stands today.

Colour and contrast

• Body text on the page background measures approximately 7.2:1, against a 4.5:1 requirement.
• Solid orange call-to-action buttons use a darkened brand orange (#B83B08) rather than the brighter #E8500F, because white text on the brighter shade measures 3.76:1 and fails at body size. The brighter orange is retained for underlines, icons and focus rings, where the 3:1 non-text threshold applies and it passes.
• Text on the dark footer and dark call-to-action panels was raised in opacity until every level cleared 4.5:1.
• Colour is never the only way information is conveyed.

Keyboard and focus

• Every interactive element is reachable and operable by keyboard.
• A visible focus ring appears on every link, button, input and summary, with an offset so it is not swallowed by the element’s own border.
• A “Skip to content” link is the first thing in the tab order on every page.
• The FAQ accordions are built from native <details> elements, so they work without JavaScript.
• The mobile navigation menu reports its state with aria-expanded and closes on Escape.

Screen readers

• Every icon on the site is decorative and is hidden from assistive technology, because the adjacent text already carries the meaning. Icons are generated by one component that makes an unlabelled, unhidden icon impossible to produce.
• Phone links carry a spoken-digit label, so the number is read as “4 0 8, 3 2 0, 6 0 0 9” rather than as hundreds and thousands.
• One <h1> per page, with headings in order beneath it.
• The profile grader announces its score, band and remaining question count through a live region as you answer, rather than silently updating a number.
• Form fields have real <label> elements. Placeholder text is never used as a label.
• Validation errors are associated with their field and announced, not shown only in red.

Motion and layout

• prefers-reduced-motion is respected: all transitions drop to 1ms and smooth scrolling is disabled, while hover and focus states remain fully functional.
• There is no autoplay, no parallax, no scroll-jacking and no content that moves on its own.
• Layout reflows to 320px without horizontal scrolling; wide tables scroll inside their own container.
• Text can be resized to 200% without loss of content or function.

What we know is imperfect

Listing these is more useful than claiming full conformance.

• The profile grader requires JavaScript.It scores entirely in your browser, which is why nothing is transmitted anywhere — but it means the tool does not function with scripting disabled. A message explains this and offers the same twelve questions by phone.
• The embedded map on the contact page is Google’s. Its internal accessibility is outside our control. It does not load unless you press a button, and the address information it shows is also written out as plain text on the page.
• We have not commissioned a third-party audit. Testing to date is our own: keyboard traversal, contrast measurement and screen reader checks. An independent audit is planned and this page will say when it has happened.
• The card fan on the home page uses overlapping rotated cards on wide screens. Each is individually focusable and straightens on focus, and the layout collapses to a plain vertical stack below 820px, but the wide-screen arrangement is visually dense.

Standard we measure against

Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. We aim for full conformance and describe our current state as substantially conformant with the known exceptions listed above.

Tell us if something does not work

If any part of this site is difficult or impossible for you to use, we want to hear about it and we will fix it — not add a widget over it.

Call (408) 320-6009 and a person will answer. Tell us the page, what you were trying to do, and what assistive technology you use if that is relevant. We aim to respond within two working days and to fix confirmed barriers within thirty days, or to tell you honestly why something will take longer.

If you need information from this site in another format — read to you over the phone, sent as plain text — ask and we will provide it at no charge.

Why we do not use an accessibility overlay

Overlay products promise compliance from a single script. They do not deliver it: they cannot fix underlying markup, they frequently interfere with the screen readers people already use well, and their presence has not prevented litigation. Accessibility is a property of how a page is built, so we build it in.

What we do for clients

Every site we build applies the same standard as this one: real labels, keyboard operability, contrast checked rather than assumed, reduced-motion respected. It is part of the build, not an upsell, and we would rather ship it correctly than sell it back to you later.

This statement describes how this website was actually built as of July 22, 2026. It is not legal advice and has not been reviewed by an attorney. An accessibility statement documents good-faith effort; it is not on its own a defence, and neither is any overlay product. If you are adapting this for your own business, have counsel review it and have the site itself audited.