Accessibility statement

The target

This site is built to meet the Web Content Accessibility Guidelines, version 2.2, at level AA.

That is a target we work to, not a certificate we hold. No independent audit has been done. Everything below is our own assessment of our own work.

What is in place

• Every control can be reached and operated from the keyboard. The order makes sense. The focus ring is one you can actually see.
• A skip link jumps past the navigation to the main content.
• One first-level heading per page, and real landmarks. Headings describe a section. They do not decorate it.
• Form fields have visible labels. An error is written out in words, not signaled by color alone.
• Images carry alt text. Decoration is marked as decoration, and a screen reader passes over it.
• Color contrast is measured at body size. Not at headline size, where it flatters.
• Motion is dropped for anyone whose system asks for less of it. The smooth scrolling included. It is not even downloaded in that case.
• The site works with JavaScript switched off. The emergency form is an ordinary form post. It still submits. It still tells you when something is wrong.
• Both languages are marked up properly. The Arabic pages are laid out right to left. Not translated in place.

Known issues

None open today. The last one, browser zoom not enlarging text on a desktop, was closed when the page's base text size went back to the browser's own.

A short list is easy to write. On its own it is worth nothing. The rule here is the boring one. Anything we find and cannot fix that week is added here. With what it affects, until it is fixed.

How this was assessed

By hand, and by checks that run on every build. Keyboard passes over each page, in both languages. Contrast measured at body size. Markup read, not assumed. Automated content and layout checks that fail the build. Not a warning filed somewhere.

There has been no independent audit. No formal screen reader testing program. When either happens, this page will say who did it and when.

Tell us what we got wrong

If a page here gets in your way, write to contact@fulklabs.com. Say what you were trying to do and what stopped you. A rough note is fine. Far better than nothing.

Need something from this site in another format? Ask, and we will send it.

Under attack right now, and the site is in your way? Go straight to the emergencies page. Do not fight the website during an incident.