Ballanqaadka gelitaanka

MyEligible is built to be accessible to as many Canadians as possible, including those using screen readers, keyboard navigation, and other assistive technologies. We aim to meet WCAG 2.1 AA standards, and we continuously improve based on real user feedback.

The following reflects checks performed in this release (code review, keyboard-only navigation on core flows, and ARIA inspection (not a third-party WCAG certification):

• Skip link: keyboard users can jump straight to the main content landmark (#main).
• Landmarks: pages expose header, main, and footer regions for navigation aids.
• Language of the page updates when you change languages (HTML lang synced client-side).
• Quiz: answer choices use native buttons with keyboard activation and visible focus styles on primary controls.
• Accessibility settings panel: Escape closes it; while open, keyboard focus stays inside the panel and returns to the trigger when it closes.
• Action plan: expandable “gateway” controls expose aria-expanded and an associated region for linked benefits.
• Benefit cards: headings for titles; confidence labels include visible text (not colour alone); document lists toggle with aria-expanded.
• Motion: users can reduce animations from the accessibility panel; CSS honours prefers-reduced-motion on supporting patterns.

Use the accessibility icon in the header for contrast, colour mode, text size, and animation preferences.

• We have not run automated contrast checks on every text style and edge case; primary surfaces are reviewed manually. Tell us if something is hard to read.
• We do not yet run scheduled testing with every screen reader and browser combination.
• PDF report download is disabled; future export will need its own accessibility review.
• Some benefit copy still mirrors dense government wording; we are simplifying it over time.

Email mcxl55@gmail.com with “Accessibility” in the subject line (or describe the barrier in the subject). We take these reports seriously and aim to reply within a few business days.

We treat WCAG 2.1 Level AA as our design target. Meeting it fully on a living product requires ongoing audits; this page states what we verified in development rather than claiming blanket certification.