Using this site your way

Accessibility statement · October 29, 2026

We aim for the Web Content Accessibility Guidelines (WCAG) 2.2, level AA, on every page. If something here doesn’t work for you, tell us and we’ll fix it or find another way.

What we’ve done

Keyboard
Every link, button and form field can be reached and used without a mouse, with a visible focus outline and a skip link at the top of each page.
Screen readers
Pages use headings, landmarks and labelled fields. Form errors are announced and tied to the field they belong to.
Reading
Text and controls are designed to meet AA contrast. Pages reflow down to a 320 px width without sideways scrolling.
Arabic
Every Arabic word on the site comes with its transliteration and its English meaning, so nobody needs to read Arabic already. Arabic text is marked as Arabic, so screen readers can switch language, and it is set right to left.
The home page’s 3D
The moving letter tiles at the top of the home page are decoration. They spell the Arabic word إِحْيَاء (iḥyāʾ, “revival”) on its pattern. Screen readers get one short text description of the picture instead of the tiles. When your device asks for reduced motion, or where WebGL isn’t available, a still picture of the finished word is shown and nothing moves.
No JavaScript
The pages read and work without JavaScript, apart from the form’s spam check. With JavaScript off, the form says so and gives our email address instead.

A known problem we can’t fix ourselves

The inquiry form uses Cloudflare Turnstile, a third-party spam check. When its box appears, the small “Privacy” and “Help” links inside it are smaller than the 24 by 24 pixel minimum target size in WCAG 2.2 (success criterion 2.5.8). It is a separate widget and we can’t change how it looks. If it’s hard for you to use, email us at info@rvvl.us instead. We’ll deal with your message exactly as we would if you’d sent the form.

Tell us about a problem

Email info@rvvl.us. Say which page and what happened, and tell us how you’d like us to reply. We read every message.

How we check

We test new pages with automated checks and by hand, with a keyboard, and at phone and desktop widths, before they go live. We’ll update this statement when something changes. It was last reviewed on October 29, 2026.