Accessibility statement

Nooryva wants nooryva.com to be usable by everybody, including people who browse with a keyboard, a screen reader, a magnifier, or with animation and colour turned down. This page says what we aim at, what we have actually checked, what we know is imperfect, and how to tell us when we have got it wrong.

What we aim at

We aim to meet WCAG 2.2 at level AA. That is the standard most laws and most buyers point at, and we treat it as a floor rather than a target.

What we check, and how

Accessibility here is tested automatically on every change, not reviewed once and forgotten. Each check runs across every page template on the site:

• at a narrow phone width and a wide desktop width, because a layout can pass at one and fail at the other;
• in both the light and the dark theme;
• against the WCAG 2.0, 2.1 and 2.2 rule sets at level A and AA.

Colour contrast is measured separately, on the colours the browser actually painted rather than the ones written in the stylesheet, against 4.5 to 1 for body text and 3 to 1 for large text. A change that would drop any text below that does not ship.

What we have built in deliberately

• Every page can be operated entirely by keyboard, in a visible and sensible order, and the focus outline is never removed.
• Nothing is signalled by colour alone. Errors, successes and warnings each carry an icon and words as well as a colour.
• Form labels are always visible above their field rather than disappearing into it, every error names its field, and the error summary links to the field it is about.
• Touch targets are at least 44 pixels, including the consent tick boxes and the language switcher.
• Wide tables scroll inside a frame a keyboard can reach and a screen reader announces, rather than forcing the page sideways.
• Headings run in order and never skip a level, so a screen reader’s outline matches the page.
• Where the page animates, it respects a request for reduced motion and stops.
• The site is published in right-to-left as well as left-to-right languages, and the layout is built from logical properties so it mirrors properly rather than being flipped by hand.
• Text can be enlarged to 200 per cent without losing content, because nothing is laid out at a fixed width.

What we have not done

We would rather be straight about this than imply more than we have:

• No independent third-party audit has been carried out, and no certification has been issued to us. Anybody who tells you a certificate proves accessibility is selling something.
• Automated checks find perhaps a third of real barriers. They cannot judge whether alternative text is meaningful, whether a reading order makes sense, or whether a form is genuinely understandable.
• We have not carried out formal testing with users of assistive technology. If you use one and something here fights you, your report is worth more to us than any tool’s output.
• Documents we publish for download, and content from third parties, may not meet the same standard as the pages themselves.

Known limitations

Machine translation is used for some languages, and a translated page may read less naturally than the English one. Where a commodity or a technical term has no settled translation, the original term is kept.

Tell us about a barrier

If any part of this site is difficult or impossible for you to use, write to and say what you were trying to do, which page you were on, and what got in the way. You do not need to know why it failed or what to call it.

We will acknowledge within three working days, and tell you what we can do and by when. If something cannot be fixed quickly, we will offer you another way to get what you needed, including simply dealing with you by email or telephone.

Keeping this page honest

The date at the top of this page is the date it was last reviewed. We review it whenever the site changes materially, and we update the section above about what we have not done as things move, in both directions.