Accessibility statement

SharpHaw is committed to making sharphaw.com usable by as many people as possible, including people who browse with a keyboard, a screen reader, magnification, or reduced motion enabled. This statement describes where the site stands today.

The standard we target

We aim to meet Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. The site is partially conformant with that standard: most of it meets Level AA, and the exceptions we know about are listed below.

What the site does

• Every page is reachable and operable with a keyboard alone, and interactive elements show a visible focus ring rather than relying on the browser default.
• Text contrast meets the Level AA ratio against the site’s dark ground. Dimmed states are drawn with a readable colour step, never with reduced opacity on live text.
• Every animation on the site respects the operating system’s reduced-motion setting. Where a section is animated — the work stream on the homepage, the process loop, the scroll reveals — a static composition ships as the complete design, not as a degraded fallback.
• Images that carry meaning have descriptive alternative text; decorative images and looping preview clips are hidden from assistive technology so they are not announced twice.
• The site is built as server-rendered HTML, so content is present and readable before any JavaScript runs.

Known limitations

These are the items open at the last review. They come from our own audit of the site, and each is scheduled rather than accepted.

• Card links on the plans and service pages. Some cards are wrapped in a single link whose accessible name summarises the card rather than repeating all of its visible text. Voice-control users may not be able to activate one of these by speaking every word they can see (WCAG 2.2 success criterion 2.5.3, Label in Name).
• The thirteen concept builds under /cases. These are illustrative demonstration sites, each designed in a different visual language. They are not held to the same accessibility standard as sharphaw.com itself, and some do not meet Level AA.
• The support chat widget. The in-page assistant is a third-party embed (SharpOS). We do not control its markup, and we have not independently verified it against WCAG 2.2 AA. Every function it offers is also available by email.

Reporting a barrier

If you hit something on this site you cannot use, tell us and we will fix it. Email contact@sharphaw.com with the page address and what happened. We aim to reply within five working days, and we will tell you when the fix will ship rather than close the report without one.

If you need something on this site in a different format — a document, a page’s content, a proposal — ask at the same address and we will provide it.

How this statement was prepared

This statement was prepared following a self-assessment of sharphaw.com carried out with automated testing (Lighthouse and axe rule sets) alongside manual keyboard and screen-reader checks. It is reviewed whenever the site’s structure changes, and at least once a year.

Last reviewed: 4 August 2026