Accessibility
Last updated: 7 August 2026
We want this website to be usable by as many people as reasonably possible, including people using keyboards, screen readers, magnification, voice input, or changed text and colour settings.
1. Our target
Our design and development target is the Web Content Accessibility Guidelines WCAG 2.2 Level AA. It is also the standard we build client websites to, as one of the eleven things included in every site we build.
For a private business the legal position is not identical to the public-sector accessibility regulations. The Equality Act 2010 can still require reasonable adjustments in the provision of services. This statement uses WCAG as a practical technical target, not as a claim that one standard covers every legal duty.
2. What should be possible
These are the things the site is built to allow. Each one is a claim that has to survive the audit before it stays on this page.
- Navigate the website using a keyboard
- See a visible focus indicator
- Zoom and reflow the content without losing the main information
- Use headings and landmarks to move around
- Understand form labels, instructions and errors
- Avoid non-essential motion
- Use text alternatives for meaningful images
- Use every control without relying on colour alone
- Complete the enquiry and scoping journeys with supported assistive technology
Still to confirm. Keep only the statements the test confirms, and delete any it does not support.
3. Current conformance status
Not ready to publish
Not yet assessed against WCAG 2.2 Level AA.The status is the point of an accessibility statement and it is the one thing that cannot be written before the site is tested. Nothing is claimed here until an audit has happened.
Partial conformance is not a safer thing to write in the meantime. It is still a claim, about criteria nobody has checked, on the one page whose whole purpose is to be a truthful account of what works.
An automated tool's score is not the audit either, and must not be recorded here as full conformance.
The parts of this website that need particular attention during testing are the colour selection tool, file uploads, wide tables, the outline that updates as you answer, and the controls for returning to a request you have already sent.
WCAG 2.2 adds nine success criteria over 2.1. These are the ones that commonly fail on a site of this shape, and the ones to test before the status above is filled in.
| Criterion | What it means here |
|---|---|
| 2.4.11 Focus not obscured | A sticky header hiding the element that has focus. |
| 2.4.13 Focus appearance | The size and contrast of the focus indicator. |
| 2.5.7 Dragging movements | Any slider or drag interaction needs a single-pointer alternative. The colour ordering tool is the one to check. |
| 2.5.8 Target size, minimum | 24 by 24 CSS pixels. Footer links and small icons are the usual failures. |
| 3.2.6 Consistent help | Help mechanisms in the same relative order across pages. |
| 3.3.7 Redundant entry | Not asking for the same information twice within one process. The scoping journey already satisfies this: the send step shows the contact details back rather than asking a second time. |
| 3.3.8 Accessible authentication | No cognitive function test. Not applicable unless a login is added. |
4. Known limitations
Still to confirm. One entry per real issue the audit finds, each saying what is affected, why it is not yet fixed, what somebody can do instead, and the planned action with a date. If the audit finds nothing, this section says so rather than staying empty.
5. Third-party content
Some embedded booking, payment, map, video or commerce interfaces are controlled by another supplier.
We remain responsible for selecting and integrating services carefully, and for providing a reasonable alternative where appropriate, but we cannot directly change every part of an independent platform.
Still to confirm. The specific third-party limitations found by the audit, named. This paragraph is not a general exemption and must not be left to read as one.
6. Report a problem
Email info@twincoretech.com.
It helps if you can tell us:
- The page or feature
- What you were trying to do
- What happened
- Your browser and device
- Any assistive technology you were using
- How you would prefer us to reply
We acknowledge within two working days, and provide a substantive response or a plan within five working days.
Still to confirm. A telephone number, if a route other than email is to be offered. If not, nothing is added rather than a number nobody answers.
7. How this statement was prepared
Still to confirm. The date this statement was prepared, the date the website was last tested, who tested it, a summary of the methods and assistive technologies used, and the next review date or trigger. All five follow from the audit and none can be written before it.