Accessibility Statement
- Last updated 12 August 2026
- About 4 minutes to read
- Applies worldwide
Our commitment
Accessibility is not a checkbox at the end of a project. Everyone should be able to read what we publish, fill in our forms, and hire us — with a screen reader, a keyboard, a magnifier, voice control, or no assistive technology at all.
Standard we follow
This site aims to meet WCAG 2.2 Level AA, published by the W3C. That standard also underpins the European Accessibility Act, EN 301 549 in the EU, Section 508 in the United States, and the UK Public Sector Bodies Accessibility Regulations. We consider this site partially conformant: most of it meets Level AA, with the exceptions listed under Known gaps.
What we have done
- Every interactive element is reachable and operable by keyboard, with a visible focus ring that meets contrast requirements.
- Text contrast meets or exceeds 4.5:1 for body copy and 3:1 for large text and interface components.
- Headings follow a logical order, landmarks are marked up, and the page has a skip-to-content link.
- Images carry meaningful alt text; decorative illustrations are hidden from assistive technology.
- Forms use real labels, group related fields, and announce errors in text — never by colour alone.
- Animation and parallax respect
prefers-reduced-motion; nothing autoplays with sound. - The layout reflows to 320px wide and survives 200% zoom without loss of content or function.
- Multi-step flows such as the project brief expose the current step to screen readers and never trap focus.
Known gaps
Being honest is more useful than claiming perfection. Current exceptions:
| Area | Issue | Target fix |
|---|---|---|
| Older blog posts | A few posts published before this site was rebuilt have images without descriptive alt text | Q4 2026 |
| Embedded booking widget | The third-party scheduler does not fully meet AA for focus visibility; we are pressing the vendor | Under review |
| Portfolio previews | Some project screenshots carry detail that is not described in text | Q4 2026 |
| Downloadable PDFs | Legal documents saved as PDF are not yet tagged for screen readers; the HTML version always is | Q1 2027 |
How we test
Automated checks run in the build — axe-core in CI, plus Lighthouse budgets. Automated tools catch roughly a third of issues, so we also test manually: keyboard-only passes on every template, screen reader checks with NVDA on Windows and VoiceOver on macOS and iOS, 200% zoom, and a forced-colours pass.
Accessibility in client work
Every site we build ships with semantic HTML, keyboard support, and contrast-tested colour by default — it is not an upsell. Where a client needs formal conformance for procurement or the European Accessibility Act, we run a full audit and issue an accessibility conformance report.
European Accessibility Act
From 28 June 2025 the European Accessibility Act requires many consumer-facing digital services sold in the EU — e-commerce, banking, travel, e-books — to be accessible. If you sell to EU consumers online, this likely applies to you. Ask us and we will tell you plainly whether it does and what closing the gap involves.
Tell us about a barrier
If something on this site blocked you, we want to know. Email accessibility@webtechnosys.dev with the page address, what you were trying to do, and the browser or assistive technology you were using. We acknowledge within two working days and aim to fix or offer an alternative route within ten.
Enforcement
If our response does not satisfy you, EU and UK users can escalate to the accessibility enforcement body in their country. We will cooperate fully with any such body.
Contact
accessibility@webtechnosys.dev — a human reads it, not a ticket queue.
Hit a barrier?
Tell us the page and what you were trying to do. We reply within two working days.