Accessibility Statement

Where wapiti.digital stands against WCAG 2.1 Level AA — the measures in place, the gaps we know about, how we test, and how to reach us if something gets in your way.

Wapiti Digital is committed to making our website usable by as many people as possible, regardless of ability or technology. Accessibility isn’t a checkbox we tick at the end of a project — it’s part of how we build, both for ourselves and for our clients.

This statement explains where https://wapiti.digital currently stands, what we’ve done, what we know still needs work, and how to reach us if you hit a barrier.

Conformance status

The Web Content Accessibility Guidelines (WCAG) (opens in a new tab) define requirements for designers and developers to improve accessibility for people with disabilities. They have three levels of conformance: Level A, Level AA, and Level AAA.

This website is partially conformant with WCAG 2.1 Level AA. “Partially conformant” means that some parts of the content do not yet fully meet the standard. We are actively working through the remaining items, and we’ve listed them honestly below rather than claiming a level we haven’t reached.

We target Level AA because it is the benchmark referenced by the Americans with Disabilities Act (ADA) in practice, by Section 508 of the Rehabilitation Act, and by the European Accessibility Act.

What we’ve done

Measures currently in place across this site:

• Keyboard navigation. Every interactive element — navigation, menus, forms, buttons — can be reached and operated with a keyboard alone, with a visible focus indicator showing where you are.
• Skip to main content. A skip link is the first item you reach when tabbing, so keyboard and screen reader users can bypass the navigation on every page.
• Landmark structure. Pages use proper HTML landmarks (header, navigation, main, footer) so assistive technology can jump between regions.
• Text alternatives. Images carry descriptive alternative text. Purely decorative graphics are hidden from screen readers so they don’t add noise.
• Labelled forms. Every form field has a visible, programmatically associated label. Errors are announced to screen readers, not just shown in colour.
• Captioned media. Embedded videos carry descriptive titles, and video players are keyboard operable.
• Reduced motion. If your operating system is set to reduce motion, animations and auto-scrolling content are disabled.
• Responsive and zoomable. Content reflows to a single column and remains readable at 320px width and up to 400% zoom, with no loss of information.
• Clear link text. Links describe their destination rather than saying “click here,” and links that open a new tab say so.

Known limitations

We’d rather tell you what’s imperfect than pretend otherwise. We’re aware of the following, and each is scheduled for remediation:

• Colour contrast in some interface text. Certain small labels, accent headings and footer text do not yet meet the 4.5:1 contrast ratio required at Level AA. We are revising our colour palette to correct this while keeping our brand identity intact.
• Heading order in some older articles. A small number of blog posts skip a heading level (for example, jumping from a level 2 heading to a level 4). This does not prevent access but makes navigating by headings less predictable.
• Third-party embedded content. Some pages embed content we don’t control, including YouTube video players and our client billing portal. We choose accessible providers where we can, but we cannot guarantee the accessibility of content hosted elsewhere.
• Older uploaded documents. Some historic PDFs and downloads may not be fully tagged for screen readers. If you need one of these in an accessible format, contact us and we will provide it.

How we assess this site

We evaluate accessibility using a combination of methods, because no single one is sufficient on its own:

• Automated testing with Lighthouse and axe-core, run against representative page templates
• Manual keyboard-only walkthroughs of navigation, forms and interactive components
• Programmatic contrast measurement of rendered pages, rather than eyeballing colour swatches
• Self-evaluation against the WCAG 2.1 Level AA success criteria

Automated tools typically catch only around a third of accessibility issues, so manual testing carries the weight here.

Compatibility

This site is designed to work with current versions of Chrome, Edge, Firefox and Safari on desktop and mobile, used together with assistive technologies including screen readers (NVDA, JAWS, VoiceOver and TalkBack), screen magnification, speech recognition and browser zoom.

The site may not display as intended in browsers more than two major versions out of date, or with JavaScript disabled.

Technical specifications

Accessibility of this site relies on HTML, WAI-ARIA, CSS and JavaScript, and on the combination of a modern web browser with any assistive technology installed on your device.

Tell us if something isn’t working

If you encounter a barrier on this site, or need information from it in a different format, please get in touch. Feedback from people who actually use assistive technology is the most valuable input we get.

Email: [email protected]
Contact form: wapiti.digital/contact

Please tell us the page address, what you were trying to do, and what went wrong — including the browser and assistive technology you were using, if you know. We aim to respond within five business days. If we can’t fix something quickly, we will tell you when we expect to, and offer an alternative way to get what you need in the meantime.

If you’re not satisfied with our response

If you contact us about an accessibility problem and are not happy with how we handle it, please let us know by replying directly so we can escalate it internally. In the United States, you may also contact the U.S. Department of Justice Civil Rights Division regarding accessibility under the Americans with Disabilities Act.

A note on accessibility overlays

We deliberately do not use accessibility overlay widgets — the third-party toolbars that promise instant compliance. Independent testing and the disability community have repeatedly found that overlays fail to fix underlying problems and can actively interfere with the screen readers and browser settings people already rely on. We fix accessibility in the underlying code instead. We give our clients the same advice.

Statement details

This statement was prepared in August 2026 following a self-evaluation of wapiti.digital against WCAG 2.1 Level AA. We review it whenever we make significant changes to the site, and at least once a year.