Accessibility Statement

Conformance status

Canoa // edu — all pages under canoanumis.org/edu/, including student assignments, teacher tools, and these public pages — conforms to the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. Conformance to WCAG 2.2 AA also satisfies the WCAG 2.1 AA requirements referenced by the ADA Title II web accessibility rule, by Section 508 (2017 Refresh), and by EN 301 549 V3.2.1.

Our detailed, criterion-by-criterion Accessibility Conformance Report (ACR), based on the ITI VPAT structure, is published at Accessibility Conformance Report — as an accessible HTML document, not a PDF.

Assessment method: self-assessment by our development team using automated testing (axe-core 4.10.2, tags wcag2a, wcag2aa, wcag22a, wcag22aa) across all key pages, with 0 violations recorded in the audit of 6 August 2026, plus manual keyboard testing. Screen-reader testing with NVDA and VoiceOver is ongoing. An independent third-party audit is planned as we scale to district-wide deployments; we would rather state the intention without a date than publish a date we might miss. This page and the ACR will be updated with the results.

What this means in practice

• Every coin image has a scholarly text alternative. Screen-reader users receive the catalog's descriptions of the obverse and reverse — the same scholarly data sighted students see, not a generic "image of a coin." For a numismatic product we consider this the single most important accessibility feature, and it is built into the data model rather than added per page.
• Everything works with a keyboard. Answer forms, the assignment builder, review screens, and navigation are fully operable without a mouse, with a visible focus indicator throughout.
• No time traps. Assignments have no time limits by default. If a teacher enables a timer, students can request an extension — supporting IEP and 504 accommodations is a pedagogical requirement, not just a technical one.
• No CAPTCHAs, no passwords. Students launch from their LMS; there is nothing to type, remember, or solve to get in. This satisfies WCAG 2.2's Accessible Authentication criterion by design.
• Works without JavaScript. Reading assignments, submitting answers, and browsing these pages all degrade gracefully; content is never locked behind scripts.
• Readable structure. Semantic headings, labelled form fields, contrast of at least 4.5:1 for text, and correct language markup — including lang="la" on Latin coin legends so screen readers do not mangle IMP CAES NERVA TRAIAN AVG.
• Resizable and reflowable. Content stays usable at 200% zoom and in a 320-pixel-wide viewport without horizontal scrolling of text.

Known limitations

We list these openly; each has a workaround.

• Third-party LMS interfaces (Canvas, Schoology, Moodle) are outside our control. Our tool launches inside them; accessibility issues in the LMS itself should go to the LMS vendor — but write to us first if you are unsure where a problem lies, and we will help you diagnose it.
• Museum image quality varies. Some specimen photographs from partner institutions are low-resolution or poorly lit; magnification will not always help. Where a coin's description is available, the text alternative carries the scholarly detail the image cannot.
• Screen-reader testing is not yet exhaustive. NVDA and VoiceOver testing is in progress across all screens; TalkBack on Android has not been systematically tested and we do not claim it. No other conformance gaps are known at the time of this assessment.

Compatibility

Canoa // edu is tested with current versions of Chrome, Firefox, Safari, and Edge, in combination with NVDA on Windows and VoiceOver on macOS. We require no specific browser, plugin, or app: the service is standard HTML delivered over the web.

Feedback and complaints

If you or your students encounter an accessibility barrier anywhere in Canoa // edu, tell us: accessibility@canoanumis.org.

This address is monitored by a human. We acknowledge reports within 2 business days, and a barrier that blocks a student from completing an assignment is treated as a priority defect with a target fix or workaround within 10 business days. When a fix will take longer we will say so, propose an interim workaround, and follow up when it ships.

This is also the correct contact for formal accessibility complaints, including those raised under Section 504 of the Rehabilitation Act or the Americans with Disabilities Act. Districts may route complaints through their own 504 coordinator; we will cooperate fully with any resulting review.

For districts: procurement documents

Everything your accessibility review needs is one click away: the Accessibility Conformance Report, this statement, and — on request — our remediation roadmap for the limitations above. If your district requires a specific format, such as a signed ACR or a state-specific form, email accessibility@canoanumis.org and we will provide it within two business days. The whole vendor packet is collected at for districts.

Our commitment going forward

• Automated accessibility checks run against every change; releases introducing critical violations do not ship.
• The ACR is reviewed and re-dated with every major release, and at least annually.
• We do not use accessibility overlay widgets. We fix problems in the code, not on top of it.
• We follow the development of WCAG 3.0 and will adopt new success criteria as they stabilize.