Accessibility Statement

We build websites for a living, so we hold our own site to the standard we recommend to clients. We treat accessibility as ongoing maintenance rather than a one-time project: when we ship a change to this site, accessibility is part of the review.

Our target is the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA.

Concretely, three things are true at the same time, and all three matter:

• Our most recent automated accessibility pass, run with axe-core, reported no violations on the pages we tested — the home page, Our Work, Contact, and these policy pages.
• Automated tooling only catches a portion of real accessibility problems. A clean axe-core run is a floor, not a finish line. Automated checks cannot judge whether alternative text is meaningful, whether reading and focus order make sense, whether an interactive component announces its state usefully, whether an error message is actually understandable, or whether a keyboard user can get back out of something they got into. Those require a person.
• Manual screen-reader testing is not yet complete. We have not finished end-to-end testing of this site with screen readers such as VoiceOver, NVDA, and JAWS. Until that work is done, we cannot honestly tell you the site is free of barriers, and we are not going to imply otherwise.

No outside firm has audited this site, we have not commissioned a third-party conformance review, and we have not published a VPAT or Accessibility Conformance Report. If that changes, this page will say so and will name the reviewer and the date.

• Semantic HTML with landmark regions, and a “Skip to main content” link as the first focusable element on every page.
• A text and background contrast pass across the marketing pages against the WCAG AA thresholds — 4.5:1 for normal text and 3:1 for large text and user-interface boundaries — with ratios computed rather than eyeballed.
• Accessible names on icon-only links and buttons, and decorative icons hidden from assistive technology.
• Labels on every contact-form field, and form errors reported in text rather than by color alone.
• Visible keyboard focus styling on form fields and primary controls.
• Automated axe-core scanning of the public pages as part of our development process.
• Several animated components honor your operating system’s “reduce motion” setting.

These are the limitations we are aware of today. We would rather list them than let you discover them.

• Manual assistive-technology testing is pending. A full screen-reader and keyboard-only walkthrough of every page and flow has not been completed. There are almost certainly barriers we have not found yet.
• Embedded third-party site previews. Our home and Our Work pages show live previews of websites we have built for clients, loaded inside frames. Those are other companies’ websites; their accessibility is outside our control and we cannot fix it here. The previews are presentational, and every one of them sits next to a text description and a plain link to the real site, so no information is available only inside a preview.
• The interactive map. The map on the home and contact pages is drawn on a canvas by a third-party mapping library, and its support for screen readers is limited. Everything it communicates — that we are based in Albuquerque, New Mexico and work with clients across the state and nationwide — is also written in text on the same pages.
• Motion. Not every animation on the site respects the “reduce motion” system setting yet. If motion is a problem for you, tell us and we will prioritize it.
• Documents we generate. The PDF invoices, proposals, and contracts we email are not yet fully tagged for screen readers. Ask us and we will send the same information in an accessible format — plain-text email, HTML, or read to you over the phone.
• Areas not yet reviewed. Our client portal and the private invoice, proposal, and contract pages have not been through the same accessibility review as the public marketing pages.

This site relies on HTML, CSS, and JavaScript. Some features will not work with JavaScript disabled. We have not verified this site against specific browser and assistive-technology combinations, so we make no compatibility claims for any particular pairing.

If any part of this site, or any document we have sent you, is a barrier — or if you simply could not do what you came here to do — tell us. It helps to include the page address, what you were trying to do, and the browser or assistive technology you were using, but do not let missing details stop you from contacting us.

Completing manual screen-reader testing of the public pages, extending reduce-motion support across the remaining animations, and reviewing the client portal and generated documents are the next items on our list. We will update this statement, and its effective date, as that work lands or as our understanding of the site changes.