Preceptby SquidSkull
Accessibility

Accessibility

Students, preceptors and faculty all need to use Precept, including people who use a keyboard, a screen reader, zoom or high contrast. I build it to the Web Content Accessibility Guidelines (WCAG) 2.1, level AA.

How it is checked

Every page of the site and every screen of the app is tested with axe-core, an automated checker, against the WCAG 2.1 A and AA rules. The test covers the front page, sign-up and sign-in, the package builder, the account page, the developer page, and all 23 screens of the app for the director, student and preceptor, at desktop and phone widths.

Last full check: November 9, 2026. No failures were found. I run it again whenever a page changes.

Automated checks find many problems, but not all of them. Precept has not yet had a formal audit by an outside firm.

What is built in

  • Every form field has a label, and errors are written out in words next to the field.
  • Text and buttons meet the AA contrast ratio.
  • Buttons, links and controls have names a screen reader can announce.
  • Pages are tested at phone width as well as on a computer.
  • Animations stop if your device is set to reduce motion.
  • Preceptors can type their name to sign a shift instead of drawing a signature.
  • Every table can be downloaded as a CSV file to open in a spreadsheet or another tool.

What is still open

  • A hand check of every screen with a screen reader (NVDA and VoiceOver) and with the keyboard alone.
  • A formal outside audit and a VPAT (Accessibility Conformance Report). If your college needs one, tell me.

Report a problem

If something in Precept is hard to use with your setup, email me at aaron@hedgeslabs.com and tell me the page and what happened, and I'll fix it.