Accessibility Statement

1. Our commitment

A11y Shield is a tool for building accessible websites, so an accessible product is not optional for us — it is the whole point. We are committed to making A11y Shield usable by as many people as possible, regardless of disability, assistive technology or device.

This statement is deliberately written to the same structure we generate for our own customers, so you can see exactly the kind of honest, specific accessibility statement A11y Shield produces.

2. Conformance status

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. To be honest about the term: “conformance” is a formal, page-by-page claim. The A11y Shield application is built to substantially conform to WCAG 2.2 AA and is automatically checked against those criteria, but we do not claim flawless conformance on every single view at every moment — where we fall short we treat it as a bug and fix it.

3. Measures we take

Accessibility is built into how we develop the product. Concretely:

• Accessible-by-default components. Our interface is built from components designed for accessibility from the start, rather than retrofitted.
• Automated checks in CI. Every change runs axe-core accessibility tests, and our pipeline requires zero violations across our key surfaces before code can ship.
• Full keyboard operability. Every interactive element can be reached and used with a keyboard alone.
• Visible focus indicators. Focus is always clearly visible as you move through the interface.
• AA (or better) colour contrast. Text and meaningful interface elements meet or exceed WCAG AA contrast ratios.
• Skip links and landmark structure. A skip-to-content link and proper landmark regions let people move around quickly.
• Reduced-motion support. We honour the prefers-reduced-motion setting and tone down or remove animation for people who ask for it.
• Screen-reader-friendly data. Charts are paired with screen-reader-only data tables so the underlying numbers are available to assistive technology, not just the visual.
• Live status regions. We use aria-live regions to announce status changes — such as a scan completing — to screen reader users.

4. Compatibility

A11y Shield is designed to work with recent versions of the major browsers (Chrome, Edge, Firefox and Safari) and common screen readers (such as NVDA, JAWS and VoiceOver). Where a feature is not supported by an older browser or assistive technology, the interface is built to degrade gracefully so the core tasks remain possible.

5. Known limitations

We would rather be candid than pretend the product is perfect. Areas we are aware of and continue to work on include:

• Third-party embedded content (for example a payment form served by our billing provider) is not fully under our control, and its accessibility may vary.
• Downloadable and exported documents, such as PDF reports, may not reach the same standard as the application interface in every respect.

If you hit a barrier that is not listed here, please tell us — it helps us prioritise.

6. Feedback

We welcome your feedback on the accessibility of A11y Shield. If you encounter a barrier, or need information in a different format, email hello@lukeduff.co.uk. Please tell us where you were, what you were trying to do, and the browser or assistive technology you were using, so we can reproduce it. We aim to respond within two working days.

7. Enforcement & escalation

We would always prefer the chance to put a problem right first. If you are not satisfied with how we respond to an accessibility complaint, you may be able to escalate the matter to the relevant national accessibility or equality body for your country. In the UK, guidance on your rights is available from the Equality Advisory and Support Service.

8. Preparation of this statement

This statement reflects a self-evaluation of the A11y Shieldapplication, combined with automated testing carried out using our own scanning engine — the same axe-core-based engine we run for customers. It was last reviewed on the date shown under “Last updated” above, and we revisit it as the product changes.