Accessibility Statement

1. How We Tested

• Automated scanning. Every one of the 220 URLs router.php dispatches to was scanned with axe-core against WCAG 2.1 A and AA rules: all public pages, the full authenticated app, every staff and admin page, and every tool/guide/quiz page. The final scan found zero violations.
• Keyboard navigation. A scripted pass drove real Tab, Enter, and Escape key input across the app and read the browser's accessibility tree, a reliable stand-in for what screen-reading software consumes. This covered every modal and popover (each one traps focus while open and returns it to the triggering control on close), the tabbed admin-panel widget (arrow-key navigation, correct ARIA roles), and the drag-and-drop milestone-review scheduler, which has a fully keyboard-operable non-drag alternative for every action.
• Color contrast. Text and interface colors were checked against WCAG's contrast thresholds as part of the automated scan above, including a second pass specifically for combinations (an icon badge's text against its own tinted background, for example) that a page-by-page sample missed the first time around.

2. What This Doesn't Cover

Here's what this testing didn't cover:

• No live screen-reader session. Reading the accessibility tree that NVDA, JAWS, and VoiceOver consume is a reliable proxy for what those tools expose, but nobody has run this site through one of those tools with speech output turned on, end to end. Behavior that depends on a specific screen reader's own quirks isn't something automated testing catches.
• No usability testing with people who use assistive technology. Everything above tests conformance to a written standard. It doesn't tell us whether the experience is actually good for someone navigating the app that way day to day.
• No other languages. Forzara is English-only today, with no localization. WCAG's language requirements are met for the one language the site has.

3. Ongoing Monitoring

New pages and features go through the same automated scanning and keyboard-navigation checks before they ship. If a future change introduces a regression, we want to hear about it (see Section 5), and we'll fix it and correct this page.

4. Known Limitations

None open as of the "Last Updated" date above. If that changes, this section will say exactly which pages or features are affected and when we expect to fix them.

5. Tell Us About a Barrier

If something on Forzara doesn't work with your assistive technology, is hard to operate without a mouse, or is otherwise difficult to use because of a disability, we want to know. A passing automated scan doesn't mean we've found everything a real person will. Visit our Support page and describe what happened, or email us directly at the address below. Tell us the page, what you were trying to do, and what assistive technology (if any) you were using. That's the fastest way for us to reproduce and fix it.

6. Changes to This Statement

We'll update this page and its "Last Updated" date whenever our testing, conformance status, or known limitations change.

7. Contact Us

Questions about this statement, or to report an accessibility barrier, contact us at: