Accessibility

Accessibility

This site is built to WCAG 2.1 Level AA as its target. That is a design target, not a conformance claim — the testing needed to make a conformance claim has not been completed, and it is listed below rather than glossed over.

What this build does

  • Semantic HTML with real landmarks, one h1 per page, and heading levels that are never skipped for visual sizing.
  • A skip link to the main content as the first focusable element on every page.
  • Full keyboard operation: the primary navigation, the products mega-menu (Enter opens, Escape closes and returns focus to the trigger), the mobile navigation, and every accordion, which is a native details element.
  • Horizontally scrollable tables — the dilution guide in particular — are focusable, named scroll regions, so a keyboard user can reach and scroll them.
  • A visible focus indicator on every interactive element, never removed.
  • Body text at 16px minimum, and layouts that reflow rather than break when text is enlarged.
  • Colour is never the only carrier of meaning: form errors carry an icon and a text message as well as a colour.
  • prefers-reduced-motion: reduce is honoured — every reveal animation is disabled and all content sits at full opacity.
  • Arabic and English are separate documents with lang and dir set on the document element itself, so screen readers announce the correct language and the bidirectional algorithm resolves correctly.
  • The site works with JavaScript disabled: content renders, navigation works, and forms fall back to the browser’s own validation.

What has been tested

  • Automated testing with axe-core against WCAG 2.0 and 2.1, Level A and AA, plus the best-practice rule set, on every page in both languages. Zero violations at the time of writing.
  • Keyboard traversal and focus order, in both reading directions.
  • Rendering at 320, 375, 768 and 1440 pixels, with no horizontal page overflow in either language.

What has not been tested

  • Testing with people who use assistive technology. Automated tools catch a minority of accessibility problems; they are a floor, not a verdict.
  • Screen reader testing on real devices — VoiceOver on iOS and macOS, TalkBack on Android, NVDA and JAWS on Windows — in both Arabic and English.
  • Real-device testing on iOS Safari, mid-tier Android, and the Instagram and Snapchat in-app browsers.
  • Any third-party embed, since none is present yet. Anything added later must be assessed on its own.

What HAZ MED must decide

  • A named contact and channel for accessibility feedback, so a visitor who hits a barrier can report it and get an answer.
  • Whether an independent accessibility audit is commissioned, and whether a formal conformance statement is to be published afterwards.
  • The target date by which reported barriers will be addressed.

Anything you need is one message away

If you need the current position on any of this before it is published, ask us directly and we will answer in writing.