Accessibility
Our commitment, conformance level, known limitations, and how to report a barrier. Last reviewed: 2026-05-18.
Our commitment
PostingPal aims to be usable by everyone, regardless of ability, device, or assistive technology. We align with the Accessible Canada Act and target WCAG 2.1 Level AA conformance for our web interface.
Standard applied
WCAG 2.1 Level AA (target).
EN/FR bilingual parity is maintained across the interface and communications per the Official Languages Act.
What we've done
- Semantic HTML, heading structure, and a single <main> per page.
- Radix UI (shadcn) components for ARIA-correct dialogs, menus, and form controls.
- Accessible names on icon-only buttons; labels and id/htmlFor associations on form fields.
- Design tokens meeting AA contrast, visible focus rings, mobile tap targets ≥ 44×44 pixels.
- lang attribute on the document and on exported PDFs (EN or FR).
- Automated audit (axe-core) run on public pages with no violations.
- “Skip to main content” link as the first focusable element on every page.
- Honours the prefers-reduced-motion user preference for animations and transitions.
- Authenticated-route sweep: labels added to hidden file inputs (camera, gallery, import) and filter selects.
Known limitations
- PDF exports are not tagged. Our current PDF generator does not emit a PDF/UA-1 structure tree. Screen readers can read the content but semantic reading order is not guaranteed. For a fully accessible format, use the CSV export — it contains the same data and works perfectly with assistive technology.
- Manual verification pending. A full manual screen-reader audit (VoiceOver, NVDA) and WCAG 2.2 conformance are not yet completed. Scheduled before any institutional pilot.
- Session-timeout warning. Users are not yet warned before the authentication session expires automatically (WCAG 2.2.1).
Roadmap
- Tagged PDF (PDF/UA-1) generation for inventories and insurance claims.
- Manual testing with VoiceOver, NVDA, and JAWS on primary flows.
- WCAG 2.2 Level AA conformance.
Report a barrier
If you hit an accessibility barrier, please tell us. We commit to acknowledging within 7 days and proposing a fix or timeline.