This website, jortech.co.uk, is built to WCAG 2.2 AA as standard, and applies AAA success criteria where the content allows. We want anyone in Leeds who needs a computer or laptop fixed to be able to reach us easily, whatever device or assistive technology they use.

1. Our commitment

This site is designed and tested to conform to WCAG 2.2 AA from the first commit, not bolted on after launch, and we meet selected AAA success criteria where the content allows. The AAA criteria reach a wider audience: people with motor impairments need larger tap targets (SC 2.5.5 Enhanced), people with cognitive impairments benefit from clearer language (SC 3.1.5), people with low vision need 7:1 contrast (SC 1.4.6), and so on, so we target them where they fit the content rather than claiming blanket AAA conformance.

2. What we do, technically

Semantic HTML, landmark elements (<main>, <nav>, <article>, <aside>), one <h1> per page, properly-nested heading hierarchy.
Skip links, bypass-blocks links in the header, jumping to main content and navigation (targeting SC 2.4.1).
Target size, interactive controls meet at least 24×24 CSS pixels (SC 2.5.8 AA). The primary call and booking buttons are comfortably larger; a few small controls, such as the notification-bar and sticky-bar close buttons, sit between 24 and 44 pixels, so we do not claim the 44×44 of SC 2.5.5.
Contrast ratios, text meets at least 4.5:1, and large text at least 3:1 (SC 1.4.3 AA). Most body text is well above that, and white on --accent-dark #0A6A34 measures 6.72:1, so some combinations reach AAA; we do not claim AAA across the site.
Keyboard-only navigation, every page navigable without a mouse; visible focus indicator on every focusable element.
Screen reader semantics, ARIA labels on icon-only controls (for example the sticky call button), aria-current="page" on breadcrumbs, and aria-label on landmark <nav> regions.
Form labels, every input on the enquiry form has an explicit <label for=> association; error messages are programmatically connected.
Images, meaningful images have descriptive alt text; decorative images use alt="" or role="presentation".
Motion preferences, animations respect prefers-reduced-motion; no auto-playing video.
Language, <html lang="en-GB"> is set on every page so screen readers select the right voice.
Works without JavaScript, the pages render, read and let you reach us without JavaScript; the enquiry form is a progressive enhancement and falls back to emailing us directly.

3. Tools we test with

The site goes through a manual and automated accessibility pass before launch and on every significant change:

Lighthouse / axe-core, automated rule coverage for contrast, landmarks and ARIA correctness.
Keyboard-only walkthrough, Tab through every interactive element on every page.
Screen reader spot-check, VoiceOver (macOS / iOS) for the main flows.
Real device testing, iOS Safari (iPhone), Chrome Android, plus desktop Firefox / Safari / Chrome.
Browser zoom, every page tested at 200% zoom without loss of content or function (SC 1.4.4).

4. Known limitations

We are honest about the gaps, which means naming them rather than saying there are none. A full audit of the site in September 2026 found issues we have since fixed, including two contrast failures that affected every page: an emphasised phrase in page headings that rendered as a gradient fading to 2.6:1, and a line above the closing call-to-action at 2.9:1. Both now pass.

These are open at the last-updated date above:

Tables in guides and legal pages change layout below 760 pixels in a way that drops their column headings for screen readers (SC 1.3.1).
Some lists inside long-form guides lose their list semantics in Safari with VoiceOver, because a styling reset is not paired with an explicit list role (SC 1.3.1).
Two controls in the mobile menu signal keyboard focus with a border change that is weaker than the 3:1 the standard asks for (SC 1.4.11).
The main menu buttons announce themselves as menus to screen readers when they open a panel of ordinary links, so keyboard behaviour may not match what is announced (SC 4.1.2).

If a future version embeds third-party content, for example an online map, that content follows the provider's own accessibility posture, which we do not fully control, and we will note it here.

5. Feedback & reporting an issue

If you find a barrier on this site, or if you would find it easier to reach us another way, email hello@jortech.co.uk. Include the page and what specifically did not work, if you can. We aim to acknowledge within 1 working day and fix within 5.

6. Enforcement

If you are not satisfied with our response, in England, Wales and Scotland you can contact the Equality Advisory and Support Service (equalityadvisoryservice.com).

7. Statement preparation

This statement was prepared on the date above by Jordan Gilbert (founder, JorTech). It is based on a self-assessment against WCAG 2.2 AA, with named AAA criteria targeted (SC 2.4.1, 2.5.5, 1.4.6, 3.1.5), carried out with the tools listed in section 3. It is reviewed at least annually and on any significant site change.

8. Who we are

JorTech is a trading name of TicketWave HQ Ltd, a company registered in England and Wales, company no. 17143167. Contact us at hello@jortech.co.uk.

9. Related documents

10. Changelog

v1.1, August 2026, renamed throughout from Leeds Tech Repair to JorTech. The trading entity, TicketWave HQ Ltd, is unchanged.
v1.0, July 2026, initial publication, as Leeds Tech Repair.

← Back to home

Accessibility Statement