Accessibility

MyEligible is built to be accessible to as many Canadians as possible, including those using screen readers, keyboard navigation, and other assistive technologies. I design toward WCAG 2.1 Level AA and improve continuously based on testing and your 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. Each setting group uses native radio buttons with a visible legend; arrow keys move between options in the same group.
• Action plan: expandable controls for linked programs expose aria-expanded and an associated region for screen readers.
• Benefit cards: headings for titles; confidence labels include visible text (not colour alone); document lists toggle with aria-expanded.
• Motion: animations and transitions are reduced when your device or browser uses “reduce motion” (prefers-reduced-motion).

Use the accessibility icon in the header for high contrast, light or dark colour mode, larger text, and an optional dyslexia-friendly font (Atkinson Hyperlegible, including headings and the wordmark). Choices are saved in your browser only, not on my server. Quiz answers are processed in your browser and are not stored on my server. Accessibility preferences are stored only in this browser's local storage, which may matter on shared or library devices.

• I have not run automated contrast checks on every text style and edge case; primary surfaces are reviewed manually. Tell me if something is hard to read.
• I do not yet run scheduled testing with every screen reader and browser combination.
• Results PDF export (from the action plan) is built from rendered images, not structured accessible PDF text. It has not had a dedicated accessibility review.
• Some benefit copy still mirrors dense government wording; I am simplifying it over time.

If something isn't working for you, email me with “Accessibility” in the subject line (or describe the barrier in the subject). I take these reports seriously and aim to reply within a few business days.

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