Accessibility at Facultory

Last reviewed 2026-08-16.

Facultory aims to conform to WCAG 2.2 Level AA. We target 2.2 even where procurement asks for 2.1 AA, because 2.2 is the current W3C recommendation and the extra criteria are the ones that matter most on a dense, form-heavy application.

Where we are

Every merge is blocked by an automated accessibility gate: each major surface is scanned with axe-core at 1280, 390, and 320 CSS pixels, and a new serious or critical finding fails the build. Existing findings are recorded in a checked-in register that may only shrink. That is a real floor, and it is not the same as conformance.

What we know is not yet right

• Two elements in the signed-in scheduling view fall below the contrast minimum at narrow widths. This is recorded, owned, and not yet fixed.
• One public letter-request page can require horizontal scrolling at 320 CSS pixels.
• Some map imagery has no text alternative that conveys the same information; the same information is available as text elsewhere on the page.
• We have not completed a full manual assistive-technology pass (NVDA, JAWS, VoiceOver) against the signed-in application. Until we have, treat our screen-reader support as unverified rather than assured.

Assessment approach

Our conformance report (VPAT® 2.5 Rev, WCAG edition) is published in the source repository as docs/compliance/VPAT-WCAG2.1-AA.md. It is based on source review plus the automated gate above, and it says so — criteria that genuinely require assistive-technology testing are marked as such rather than claimed.

Telling us about a barrier

If any part of Facultory blocks you, write to borowczak@gmail.com. Tell us the page, what you were trying to do, and your browser and assistive technology if you know them. We aim to acknowledge within 3 business days and to agree a fix or a workaround with you.

If you need something in an alternative format to complete a task, ask — we would rather do that by hand for you now than have you wait for a release.