Accessibility

What we aim for

We build this site to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. That is the target we design and review against.

We have not commissioned an independent audit, so we do not claim conformance to that level — only that it is what we are working towards. Everything listed below is claimed because it is implemented in the code, not because it is a good intention.

What the site does today

• Every page starts with a skip link that jumps past the header straight to the main content, and every page marks that content as a single main region for the link to land on.
• Headings are ordered and meaningful — one top-level heading per page, with sections nested beneath it — and navigation, footer and content sit in real landmark regions rather than anonymous containers.
• Every interactive element takes keyboard focus and shows a visible focus ring. Nothing is reachable by mouse alone.
• Anything that opens over the page keeps your keyboard inside it: the mobile menu holds focus until you close it, and closing the language list or the menu puts focus back on the control you opened it with rather than dropping you at the top of the page.
• A collapsed answer in a list of questions is closed to a screen reader too, not merely made short — so what is announced matches what the button next to it says about being open or closed.
• Every form field on the contact page has a real label, and the message field has a description tied to it, so a screen reader announces both.
• The interface is available in 9 languages, and each one sets the page's language and text direction — including right-to-left for Arabic — so assistive technology reads it correctly.
• If your system asks for reduced motion, the site honours it: animations and smooth scrolling are switched off rather than merely shortened.
• There is no autoplaying audio or video anywhere on the site, and nothing moves or flashes on its own.
• Text resizes with your browser's zoom and text-size settings, and layouts reflow rather than clipping.
• Every meaningful image carries alternative text; decorative marks are hidden from assistive technology instead of being announced.

What we know is not covered

• No independent or automated audit has been run against the whole site, so there will be issues we have not found.
• We have tested with keyboard navigation and browser zoom, but not systematically with every screen reader and browser combination.
• Colour contrast has been designed for, not measured page by page. If any text is hard to read, that is a bug and we want to know.
• The mobile apps we publish are not covered by this statement. They follow the platform's own accessibility settings — Orbyx additionally offers a colour-safe palette, motion and text-size options in its settings.

Telling us about a barrier

If any part of this site stops you doing what you came to do, email support@angyal.in. Tell us the page, what you were trying to do, and what happened — and, if you can, what you were using: browser, device, and any assistive technology.

We acknowledge within 1–2 business days. We will tell you what we can fix and when, and if something cannot be fixed quickly we will offer another way to get what you needed — including simply answering by email.

You do not need to identify the guideline it breaches or use any particular wording. A description of what went wrong is enough.

Reviewing this statement

We review this page whenever the site changes in a way that affects it, and at least once a year. The revision date at the top of the page shows when it last changed.