.png)
Table of Contents
- Our Commitment
- Conformance Status
- Accessibility Features
- Known Limitations
- Legal Framework
- Feedback and Accessibility Requests
- Updates to This Statement
Our Commitment
At abcAssess, we believe every teacher deserves access to high-quality classroom assessment tools — regardless of ability. We are committed to ensuring that our web-based platform, fully accessible on desktop, tablet, and mobile browsers, is usable by educators and administrators with diverse abilities. We deliberately built abcAssess web-first so it works across the widest possible range of devices without requiring a specific app install. Dedicated native iOS and Android applications are the next major step on our roadmap, planned once the web platform’s mobile and tablet experience is fully refined; this statement will be updated to reflect their accessibility features once they are available.
We continually audit, test, and improve our interfaces to provide a seamless and supportive experience for all users. Accessibility is not an afterthought — it is built into our design and development process from the start.
abcAssess is committed to compliance with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, Section 508 of the Rehabilitation Act of 1973, and the Americans with Disabilities Act (ADA) Title III as applied to web-based services, as well as equivalent accessibility standards in the United Kingdom, Australia, New Zealand, Canada, and Ireland. Where our platform falls short of full conformance, we are actively working to close those gaps and welcome feedback from any user who encounters a barrier.
Conformance Status
The Web Content Accessibility Guidelines (WCAG) define technical requirements for making digital content accessible to people with disabilities. abcAssess is designed to meet WCAG 2.1 Level AA on our web-based platform, including on mobile and tablet browsers.
Current Status: Partially Conformant with WCAG 2.1 Level AA. This means that some parts of our platform do not yet fully meet all guidelines. We are actively working toward full conformance and provide the known limitations and our remediation roadmap below. Users who encounter a specific barrier may request an accessible alternative by contacting us at danielle@abcassess.app.
Accessibility Features
abcAssess implements the following accessibility features across our web and mobile platforms:
-
Screen Reader Support
Our web platform uses semantic HTML landmarks and structured heading elements (H1, H2, etc.) to support screen reader navigation, including VoiceOver on iOS/macOS and TalkBack on Android when accessing abcAssess through a mobile browser. -
Keyboard and Switch Access
Our web platform is fully navigable using a standard keyboard, with visible focus indicators on all interactive elements. On mobile and tablet browsers, abcAssess is designed to work with standard assistive gesture navigation and platform-level switch access tools. -
Color Contrast
Our core color palette enforces a minimum contrast ratio of 4.5:1 between text and background elements, meeting WCAG 2.1 Level AA requirements. This supports readability in a range of lighting conditions, including brightly lit classroom environments. -
Colorblind-Accessible Assessment Tracking
abcAssess uses a combined color and symbol system throughout the platform to communicate student proficiency levels, ensuring that information is never conveyed by color alone. Each proficiency level is represented by both a color and a distinct symbol:- ✓ Proficient (sage green)
- ~ Developing (amber)
- ! Emerging (terracotta)
- ⛔ Skipped (grey)
This system appears in the in-app tracking chart, individual student profiles (Current Mastery and Assessment History), and throughout all printed and PDF reports. In reports, proficiency zones are additionally represented by pattern fills (diagonal lines, horizontal lines, and dots) alongside colors, ensuring full accessibility in black-and-white print output. This system was designed specifically to support educators with color vision deficiencies and meets WCAG 2.1 Success Criterion 1.4.1 (Use of Color).
-
Accessibility Settings
abcAssess provides a dedicated Accessibility section in Settings, organized into the following groups:- Visual Accessibility
Show proficiency symbols — teachers can show or hide the ✓ ~ ! — symbol system alongside colors throughout the app. Default on. Recommended for colorblind users. - Motion & Sensitivity
Reduced motion — teachers can disable confetti animations and dialog slide-up animations for users sensitive to motion or flashing content. Default off. - Sensory Feedback
Assessment sounds — teachers can enable or disable audio feedback including the timed assessment alert sound and assessment completion chime. Default on. Haptics — teachers can enable or disable vibration feedback when an assessment is completed. Available on mobile devices only. Default on.
- Visual Accessibility
-
Audio Assessment Support
abcAssess supports optional audio prompts during assessments, including teacher-recorded audio for custom assessment items. This feature supports educators working with diverse learners and allows teachers to provide consistent, accessible verbal prompts without relying solely on visual content. Teachers can enable or disable audio prompts per assessment type in their assessment settings. -
Touch Target Sizing
Interactive elements on our web platform — including buttons, toggles, and list items — are designed to meet a minimum tap target size of 48x48 pixels on mobile and tablet devices, consistent with WCAG 2.1 Success Criterion 2.5.5. We are actively testing and refining touch target sizing across a range of mobile and tablet devices as part of our ongoing mobile optimization work — see Known Limitations below. -
Text Alternatives for Images
Non-decorative system images include descriptive text alternatives. For teacher-uploaded instructional content — such as custom assessment images or audio prompts — our assessment builder provides fields for educators to assign their own descriptive labels within their content library. abcAssess cannot guarantee the accessibility of user-generated content, but we provide the tools to support it.
Known Limitations
We are transparent about the areas of our platform that do not yet meet full WCAG 2.1 Level AA conformance. We are actively working to address each of the following:
- Mobile & Tablet Optimization: We are in the process of testing and refining the mobile and tablet browser experience — including layout, touch target sizing, and screen sizing across devices. Some visual and interaction issues specific to smaller screens may still be present while this work is ongoing. Dedicated native iOS and Android applications are the next major step on our roadmap, planned once this mobile web refinement is complete.
- Complex Data Visualizations: Class-wide analytics dashboards, historical progress charts, and report snapshots do not yet include comprehensive text or audio equivalents for all visual data. We are working to add accessible data table alternatives and descriptive summaries for these views.
- Accessible Data Exports: We are developing accessible, high-contrast CSV data exports for all roster summaries and student progress records. This feature is currently in development. Users who need immediate access to data in an alternative format may contact us at danielle@abcassess.app and we will work to accommodate the request manually.
- User-Generated Content: abcAssess cannot guarantee the accessibility of assessment content, images, or templates created or shared by other teachers using the platform. We encourage all educators to use the descriptive labeling tools available in the assessment builder when creating or sharing content.
Legal Framework
abcAssess is committed to compliance with the following legal frameworks as they apply to our platform and user base:
- United States
- WCAG 2.1 Level AA — Our primary technical accessibility standard for web and mobile interfaces.
- Section 508 — Applicable to federally funded programs and institutions using our platform. We design to Section 508 technical standards, which align closely with WCAG 2.1 AA.
- ADA Title III — Increasingly applied to web-based services and applications. We design our platform to meet ADA Title III standards for accessibility of public-facing digital services.
- IDEA — We recognize that many of our users serve students with disabilities under the Individuals with Disabilities Education Act, and we design our tools to support educators working in those environments.
- United Kingdom
- Equality Act 2010 — We design our platform to meet the accessibility requirements of the Equality Act 2010 as applied to digital services.
- Public Sector Bodies Accessibility Regulations 2018 — Where applicable to institutions using abcAssess, we design to these standards which align with WCAG 2.1 AA.
- Australia
- Disability Discrimination Act 1992 (Cth) — We design our platform to avoid discrimination on the basis of disability consistent with the DDA and the Web Accessibility National Transition Strategy.
- Disability Discrimination Act 1992 (Cth) — We design our platform to avoid discrimination on the basis of disability consistent with the DDA and the Web Accessibility National Transition Strategy.
- New Zealand
- Human Rights Act 1993 — We design our platform to meet accessibility obligations consistent with New Zealand’s human rights framework for digital services.
- Human Rights Act 1993 — We design our platform to meet accessibility obligations consistent with New Zealand’s human rights framework for digital services.
- Canada
- Accessible Canada Act (ACA) — We design our platform consistent with the principles of the Accessible Canada Act and applicable provincial accessibility legislation.
- Accessible Canada Act (ACA) — We design our platform consistent with the principles of the Accessible Canada Act and applicable provincial accessibility legislation.
- Ireland
- Equal Status Acts 2000–2018 — We design our platform to meet the accessibility requirements of Irish equality legislation as applied to digital services.
Feedback and Accessibility Requests
We welcome feedback from teachers, administrators, specialists, and assistive technology users. If you encounter an accessibility barrier — a missing label, an inaccessible feature, or any element that prevents you from using abcAssess effectively — please let us know.
When you contact us with an accessibility concern, we commit to the following:
- Acknowledge your report within 2 business days.
- Provide an initial response with a resolution plan or workaround within 10 business days.
- Where an immediate fix is not possible, offer a reasonable alternative means of accessing the relevant feature or content upon request.
We treat accessibility reports as high-priority feedback and use them to inform our ongoing development roadmap.
| danielle@abcassess.app | |
| Subject Line | Please include “Accessibility” in your subject line |
| Response Time | It’s just me here, but I aim to respond within 2 business days |
Updates to This Statement
We review and update this Accessibility Statement as our platform evolves and as we make progress toward full WCAG 2.1 Level AA conformance. The Effective Date and Version number at the top of this document reflect the most recent revision. Material updates will be communicated to active account holders in accordance with our standard notification policy.
Data Processing Agreement - Privacy Policy - Sub-Processor Registry - Technical FAQs - Terms of Service - User Guide