Accessibility Statement

1. Conformance status

This website is designed to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. That standard is referenced by the European Accessibility Act, by EN 301 549, and by public-sector accessibility rules in many jurisdictions.

We assess ourselves as substantially conformant. Where we know of a shortfall, it is listed in section 4 rather than left unstated.

2. What we have done

Accessibility was a design constraint here, not a later audit:

• ›Semantic HTML throughout, with one main landmark per page and a heading order that does not skip levels.
• ›A skip-to-content link as the first focusable element on every page.
• ›Every interactive element reachable and operable by keyboard alone, with a visible focus indicator that meets the contrast requirement.
• ›Text and interface colours tested to meet or exceed a 4.5:1 contrast ratio for body text and 3:1 for large text and interface boundaries, in both the light and dark colour schemes.
• ›Form fields with real associated labels, errors announced in text rather than by colour alone, and each error linked to the field it concerns.
• ›Correct lang and dir attributes, so screen readers pronounce Arabic and English pages correctly and lay them out in the right direction.
• ›Layout that reflows to 320 pixels without horizontal scrolling and remains usable at 200% zoom.
• ›No animation, no auto-playing media, no time limits, and no content that moves or updates without your action.
• ›The site works entirely without JavaScript, which removes a large class of assistive-technology failures by construction.

3. Compatibility

The site is built to current web standards and should work with recent versions of screen readers including NVDA, JAWS, VoiceOver and TalkBack, in combination with current versions of Chrome, Edge, Firefox and Safari.

It does not depend on any particular browser feature beyond HTML and CSS.

4. Known limitations

We would rather name these than claim perfection:

• ›Some technical terms and standard names (WCAG, SaaS, PCI DSS) appear in Latin script within Arabic pages. This is normal industry practice and aids comprehension, but a screen reader set to Arabic may pronounce them awkwardly.
• ›Long policy pages are text-dense. We have kept headings frequent and descriptive so they can be navigated by heading rather than read linearly.

5. Assessment approach

This site was evaluated by self-assessment during development, combining manual keyboard and screen-reader testing with automated checking. It has not been audited by an independent third party. If a formal audit is carried out, this statement will be updated to say so and to record the result.

6. Feedback

If you encounter a barrier on this site, please tell us using the details on the contact page, describing the page and what happened. We aim to acknowledge accessibility reports within 2 working days and to fix confirmed barriers within 30 days.

If you need any information on this site in an alternative format, ask and we will provide it.

7. Enforcement

If you are not satisfied with our response, you may raise the matter with the accessibility enforcement body in your jurisdiction. Contacting us first is usually faster, and we would prefer the chance to fix it.