Accessibility.

1. What we are aiming for

We build this site to the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. That is the standard courts and settlements use, and it is the one we hold ourselves to.

We are not claiming full conformance. No independent audit has been done. What follows is what we have actually implemented and what we know is still outstanding — stated plainly, because a vague claim of compliance helps nobody.

2. What is in place

Text and interface colours meet the 4.5:1 contrast minimum for body text and 3:1 for interface elements. Every page has a skip-to-content link as its first focusable element, and a visible keyboard focus ring that is never suppressed.

Every form control has a programmatically associated label. Every embedded video player carries a descriptive title. The autoplaying video on profile pages is muted, is disabled entirely for anyone whose system asks for reduced motion, and has a visible pause control.

The site works at 320px width and at 400% zoom, and every page has a unique title and a single top-level heading.

3. What we know is not fixed

Captions on member videos are outside our control. Videos are hosted on YouTube, Vimeo, and similar platforms, and captions are the uploader’s responsibility. We ask members to caption their work, but we cannot guarantee it, and automatically generated captions are often not accurate enough to be genuinely usable. If a specific video is uncaptioned and you need it, tell us and we will contact the member.

Audio description for member videos is likewise not something we can supply on their behalf.

We have not yet completed a full screen-reader pass on every page. If something is unusable, we would rather hear it from you than not know.

4. Tell us

If any part of this site is difficult or impossible for you to use, email accessibility@aifilmmakerindex.com. Describe the page and what went wrong. A person reads that address and we aim to reply within two business days.

If you need information from a listing that you cannot access, we will get it to you in another format — we would rather do that than leave you stuck while we fix the underlying problem.