Legal
Accessibility
We would rather publish an honest account of where this site stands than a badge. Here is what works, what does not yet, and how to tell us when something blocks you.
Status
Version 1, posted July 25, 2026. Written in‑house from a pass over the live pages. It has not yet been reviewed by an attorney. Pro bono review is being arranged, and the reviewed version will be posted here with a new date. Until then this is what we actually do, written by the people who do it.
The standard we build to
We aim at WCAG 2.1 level AA. No outside firm has audited this site, so we make no conformance claim and we publish no badge. What follows is our own account, and it is meant to be checkable.
What is built in today
A skip link ahead of the navigation, so a keyboard user can reach the content in one press. Semantic landmarks and a heading order that a screen reader can move through. Every interactive control reachable by keyboard, with a visible focus ring that we style deliberately rather than remove. Decorative images carry empty alternative text so they are passed over, and meaningful ones are described. Animation and scroll effects stand down when your system asks for reduced motion. The pledge form announces its result in a live region, so the confirmation is spoken and not only shown. Type scales with browser zoom and text settings. Each language in the translation menu is marked with its own language attribute, and Arabic is marked right‑to‑left.
Known gaps, named plainly
The director cards on the About page are images. Their alternative text names the person and the role, so the bio text inside the image is unavailable to a screen reader and invisible to search. Replacing them with real HTML is queued.
The globe and the maps are visual. The Overview and the resource atlas convey a good deal through position and color, and there is no text‑equivalent summary yet.
The Horizon readings update while you are on the page. They are dense, and we have not yet tuned how they announce themselves to assistive technology.
Translation is machine‑made. Google Translate handles the language menu. Nobody has reviewed those translations for accuracy, and the source pages are written in English.
Downloadable PDFs may not be fully tagged for reading order and structure. If a document you need is unusable, ask and we will send you the content in another form.
How we test
Keyboard‑only passes through each page, browser zoom to 200 percent, contrast checks on the palette, and reading pages with the stylesheet turned off. There has been no paid audit and no session in an assistive‑technology lab. When either happens, this page will say so.
Telling us about a barrier
Email kazumizi@enfiare.com or call (833) 363-4273. Say what page you were on, what you were trying to do, and what got in the way. We aim to reply within five business days with what we are going to do and when.
If the barrier is standing between you and help you need right now, say that first. We will get you the information by phone or email while the fix is being made.