Our standard, what we have done, and what is not finished.
A statement of where this website stands against WCAG 2.2 level AA. It says what was measured and how, and names the known gaps – a statement without a section on gaps tells you nothing.
Last updated: 7 October 2026- 01 The standard and our commitment
- 02 Colour and contrast
- 03 Keyboard and focus
- 04 Touch and target size
- 05 Motion and transparency
- 06 Arabic in particular
- 07 Structure and screen readers
- 08 What is not finished yet
- 09 Report a barrier
- 10 Review and updates
The standard and our commitment
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA – the internationally recognised reference, and the level UK government bodies ask of their suppliers.
In the UK, the Equality Act 2010 requires service providers to make reasonable adjustments so that disabled people are not put at a substantial disadvantage. That is the legal basis we build on, and we also follow EN 301 549 for what our work in Europe may require.
Colour and contrast
Every text colour on the website is calculated with the contrast formula, not judged by eye, and documented with its value. Not even the logo blue was given an exception:
- Body text on white, #44506B – 8.06:1
- Secondary text on dark, #7E8CA8 – 5.76:1
- Secondary text on white, #5C6B87 – 5.37:1
- Borders of interactive elements, #7C8BA6 – 3.44:1 (3:1 required under 1.4.11)
The logo blue, #0575F9, gives 4.27:1 on white – below the AA threshold for text. So white surfaces automatically switch it to #0559C7, at 6.44:1: one token that every component on them inherits.
Colour alone is never the signal: the choice chips in the contact form show a tick when selected as well as changing colour, and error messages are written text, not a red border.
Keyboard and focus
The whole website can be used with a keyboard alone:
- A ‘Skip to content’ link is the first thing Tab reaches on every page
- A visible focus ring on every interactive element, and a tab order that follows the reading order
- Escape closes the mobile menu and every pop-up
- Focus moves into a pop-up when it opens, and returns to the button that opened it when it closes
- Every icon-only link carries alternative text for screen readers
Touch and target size
Success criterion 2.5.5 asks for 44 × 44 pixels for every touch target. We measured the touch targets on the pages on an emulated 393-pixel-wide device and found five elements below that – the menu and close buttons at 40, the main submit button at 42, and the footer column links at 36. All were enlarged, and the measurement afterwards: no element below 44 pixels.
On touch screens, hover effects are switched off and replaced by a response on press – so you see an immediate reaction before the page changes.
Motion and transparency
The website reads your system preferences as each page is shown, and follows them without storing anything about you:
| Preference | What changes |
|---|---|
| prefers-reduced-motion | Animations, sequences and rotation stop; transitions become a short fade, and scrolling jumps straight to its target. |
| prefers-reduced-transparency | The frosted-glass blur in the menu, footer and mobile menu is replaced by solid surfaces. |
| prefers-contrast | Borders and secondary text move to higher-contrast shades. |
| Browser text size | Text grows with it, because the base size is a percentage, not a fixed pixel value. |
The moving background is purely decorative: it is hidden from screen readers, calms down when reduced motion is preferred, and no meaning on the page depends on it.
Arabic in particular
Most automated audit tools are written for Latin scripts, and miss errors that spoil the reading of Arabic. These are three we dealt with by hand:
- No letter spacing: letter-spacing breaks the joins between Arabic letters, so words read as fragments. It was removed from all Arabic text and kept for Latin text and numbers only.
- Wider line spacing: values tuned for Latin text make the descenders of one line touch the ascenders of the next. Arabic headings have their own scale, tied to the page language.
- Logical direction: the layout is written with logical properties, so one stylesheet serves Arabic and English, with no mirrored copy left to fall behind the original.
Each page declares its language and direction – lang="ar" dir="rtl" in Arabic, lang="en" in English – so a screen reader uses the right voice. English passages inside Arabic text are marked with their direction, so their numbers and symbols are not reversed.
Structure and screen readers
- Headings in order, with no skipped levels, and a single first-level heading on each page
- Clear landmarks: header, labelled navigation, main content and footer
- Every element’s state is announced: the menu says whether it is open, and a pop-up says it is a dialog
- Form errors are announced as they happen, and focus moves to the field concerned
- On narrow screens, tables become stacked blocks, and the column headings stay readable to screen readers
What is not finished yet
These gaps are known to us, and they are why we say ‘aim to meet’ rather than ‘conform’:
- No independent audit yet. The measurements above are internal, by calculation and in the browser. An external audit is planned before launch.
- Not yet tested with a real screen reader. The structure is written to the standard, but a test session with an NVDA or VoiceOver user has not taken place.
- Temporary images have empty alternative text. The current showcase images are decorative, and will be replaced with images of our work, with their own alternative text, at launch.
- The moving background follows your system setting only. If you want to stop it without changing your device’s setting, there is no button for that yet.
Report a barrier
If you come across a page you cannot use, tell us. The most useful report gives the page, what you were trying to do, and what you were using (browser, device, and screen reader if any).
- Email: access@epictech38.com
- Response time: within five working days
- If a fix will take a while: we send you the information in another format straight away, rather than waiting for the fix
If you are not satisfied with our response, you can contact the Equality Advisory and Support Service, the independent advice service on equality law for England, Scotland and Wales (in Northern Ireland, the Equality Commission for Northern Ireland).
Review and updates
This statement is reviewed with every significant change to the website, and at least once a year. Each review updates the date at the top of the page and the list of gaps in section 08.
Accessibility runs through all six of our services rather than being an internal matter: what is on this page is what we apply to what we build for our clients.
Want this standard in your product?
Measuring by formula, testing with a keyboard, and a written statement of gaps – we do it in our clients’ projects just as we do it here.