Accessibility Statement for WiseBoard

The Web Content Accessibility Guidelines (WCAG) defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA.

WiseBoard is partially conformant with WCAG 2.2 level AA. Partially conformant means that some parts of the content do not fully conform to the accessibility standard. The non-conforming items are documented in the "Limitations and alternatives" section below and are tracked to closure in the published VPATs.

We additionally conform to Section 508 of the US Rehabilitation Act, as updated by the 2018 ICT Refresh, and to the relevant clauses of EN 301 549 v3.2.1.

Our published conformance documents:

• VPAT 2.4 ; Main product (PDF) : Dashboard, Lessons, Performance Tracker, public surfaces.
• VPAT 2.4 ; Pip's Arcade companion (Markdown) : student game suite.
• Arcade Keyboard Controls Reference : per-game keyboard map for AT trainers.
• Accessibility Commitments one-pager (PDF) : sales-friendly procurement summary.

Accessibility of WiseBoard relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer:

• HTML
• WAI-ARIA
• CSS
• JavaScript
• WebGL (for the optional 3D arcade scenes; an accessible DOM mirror is always provided alongside)

These technologies are relied upon for conformance with the accessibility standards used.

WiseBoard is designed to be compatible with the following browsers and assistive technologies:

• Current and immediately previous major versions of Chrome, Edge, Firefox, and Safari on Windows, macOS, ChromeOS, and iPadOS.
• Screen readers: NVDA + Firefox / Chrome on Windows; VoiceOver + Safari on macOS and iPadOS; TalkBack + Chrome on Android; JAWS + Chrome on Windows.
• Voice control: Voice Control on macOS / iPadOS; Voice Access on Android.
• Switch control: Apple Switch Control with single- and two-switch scanning.

WiseBoard is not compatible with Internet Explorer or with browsers older than two major releases.

Despite our best efforts to ensure accessibility of WiseBoard, there may be some limitations. Below is a description of known limitations, and potential solutions. Please contact us if you observe an issue not listed below.

Known limitations for WiseBoard:

1. Some classroom games and "arcade" mini-games rely on rapid visual or audio cues that may not be fully usable by every player. Alternative: equivalent non-game versions of the underlying activities (quiz, flashcards, exit ticket) are always available, and the published Arcade Keyboard Reference documents the keyboard input each game accepts.
2. The seating chart drag-and-drop editor currently requires pointer input. Alternative: teachers can edit seat assignments through the standard class roster page using only the keyboard. A keyboard-only fallback for the visual editor is on our roadmap.
3. Embedded YouTube playback uses the third-party YouTube player. Alternative: YouTube's own accessibility features (captions, playback speed, full-screen) apply; teachers can also link to a video instead of embedding it. WiseBoard cannot modify the embedded player itself.
4. Some PDF exports (report cards, sub plans, certificates) are generated as visual layouts rather than tagged PDFs. Alternative: the same content is also available as accessible HTML inside the app, and tagged-PDF generation is in progress.

WiseBoard assessed the accessibility of the Service by the following approaches:

• Self-evaluation: the Service was last self-evaluated for the main product on April 26, 2026 and for the companion Pip's Arcade VPAT on April 30, 2026.
• Automated tooling: eslint-plugin-jsx-a11y in CI; axe-core via jest-axe rendering all 3 auth-free public pages and all 15 audited authenticated teacher pages in jsdom; manual axe DevTools spot-checks on the live auth-free surfaces.
• Manual evaluation: keyboard-only walkthrough of the authenticated teacher workflows (dashboard, classes, Performance Tracker, lessons, attendance, behavior, parent contacts); reduced-motion verification with the OS preference toggled on macOS Safari and Chrome.
• Screen-reader spot checks: VoiceOver on macOS Safari for the teacher control surfaces a non-sighted educator is most likely to operate live (Boss Battle, Horse Racing, Escape Room).

All critical and serious findings from the April 2026 sweep (51 total) were remediated in the same pass. The full methodology, per-page findings table, fixes applied, known limitations, and next-pass plan are published as the April 2026 Accessibility Audit Report.

Continuous regression guard. Two CI checks run on every change: classroom-a11y-lint (jsx-a11y rules promoted from warn to error for image alt text and anchor validity) and classroom-a11y-axe (jest-axe assertion of zero serious / critical violations on the rendered DOM of all 3 public pages and all 15 audited teacher pages).

We welcome your feedback on the accessibility of WiseBoard. Please let us know if you encounter accessibility barriers on WiseBoard:

• Email: info@mywiseboardclassroom.com with the subject line Accessibility.
• What to include: the page URL, a description of the barrier, the assistive technology and browser you are using, and (if comfortable) a screenshot or screen recording.

We try to respond to feedback within 2 business days and provide a remediation plan within 10 business days. Critical barriers (a teacher cannot complete a core workflow) are addressed under our P1 SLA.

District procurement reviewers can request the following from info@mywiseboardclassroom.com:

• The current VPAT 2.4 (Section 508 / WCAG 2.2 AA);
• The companion VPAT 2.4 ; Pip's Arcade covering the student game suite;
• The Accessibility Commitments one-pager (PDF) for the district vendor file;
• A signed letter of accessibility commitment for inclusion in the district's vendor file;
• A demonstration call with assistive-technology testing on request.

This statement is published in alignment with the requirements of the Americans with Disabilities Act (ADA), Section 504 and Section 508 of the Rehabilitation Act of 1973, the 21st Century Communications and Video Accessibility Act (CVAA) where applicable, the European Accessibility Act for any users in covered jurisdictions, and analogous state laws including California Government Code § 11135, the New York State Information Technology Services policy NYS-P08-005, and the Pennsylvania Department of Education's student-information-system accessibility expectations.

This statement was created on April 26, 2026 and last reviewed and updated on April 30, 2026.