Accessibility

Mastery Board is for every teacher, including those who use a keyboard, a screen reader, magnification or voice control. Below is each success criterion of WCAG 2.1 at Levels A and AA — the standard the ADA’s Title II rule sets for a school district’s websites and apps — and how Mastery Board meets it. Mastery Board is provided by Above Soulutions, LLC.

Last reviewed September 29, 2026

Meets WCAG 2.1 Level AAEvery Level A and AA success criterion that applies to Mastery Board, by our own evaluation.
41 met, 9 not applicableThe ones that don't apply are about audio, video and device motion, which Mastery Board doesn't have.
Keyboard, screen reader, voice controlEvery screen works from the keyboard, controls are named by the words on them, and saving is announced.
Our own evaluationChecked by us, with automated tests and by hand, not by an outside auditor. Testing with screen readers is still to do.

Level A · 30 criteria

1.1.1 Non-text ContentMeets
Icon buttons have names a screen reader reads, and decorative icons are hidden from it. The growth chart has a text alternative, and its values are on the page as text too.
1.2.1 Audio-only and Video-only (Prerecorded)Not applicable
No audio or video.
1.2.2 Captions (Prerecorded)Not applicable
No video.
1.2.3 Audio Description or Media Alternative (Prerecorded)Not applicable
No video.
1.3.1 Info and RelationshipsMeets
Headings, landmarks, lists, and tables with header cells. Every field is labelled. Tabs, radio groups, menus and dialogs use native elements or the matching roles.
1.3.2 Meaningful SequenceMeets
Reading order follows the order on screen.
1.3.3 Sensory CharacteristicsMeets
No instruction depends on shape, color, position or sound alone.
1.4.1 Use of ColorMeets
Mastery levels are also shown as words and percentages. A missed letter or word is struck through as well as colored.
1.4.2 Audio ControlNot applicable
No audio.
2.1.1 KeyboardMeets
The score grid works with arrow keys and Enter; tabs and radio lists with arrow keys. Menus open with Enter or Space and close with Escape. Favorites and the builder's divider move with arrow keys.
2.1.2 No Keyboard TrapMeets
Dialogs are native and close with Escape, and focus goes back to what opened them.
2.1.4 Character Key ShortcutsMeets
No single-letter shortcuts.
2.2.1 Timing AdjustableMeets
No task has a time limit. A district can sign an unused browser out after 1, 4 or 8 hours; two minutes before, the page asks “Still there?” with Stay signed in, as often as needed. Longer settings fall under WCAG's 20-hour exception.
2.2.2 Pause, Stop, HideNot applicable
Nothing moves, blinks, scrolls or updates by itself.
2.3.1 Three Flashes or Below ThresholdMeets
Nothing flashes. The template builder lights up what an edit touched, once, and fades it.
2.4.1 Bypass BlocksMeets
A “Skip to main content” link comes first, and navigation and main content are landmarks.
2.4.2 Page TitledMeets
Every page's title names it and, where it matters, the class, board or template.
2.4.3 Focus OrderMeets
Focus follows the order on screen, and a dialog hands it back when it closes.
2.4.4 Link Purpose (In Context)Meets
Each link's words, or the words around it, say where it goes.
2.5.1 Pointer GesturesMeets
Nothing needs two fingers or a traced path. Dragging to reorder favorites or resize a panel depends only on where it is let go.
2.5.2 Pointer CancellationMeets
Buttons act when released, not when pressed, and a drag finishes where it is let go.
2.5.3 Label in NameMeets
A control with words on it is named with those words, so voice control finds it by what it says — the grid's all, clr and abs included.
2.5.4 Motion ActuationNot applicable
Nothing is worked by shaking or tilting the device.
3.1.1 Language of PageMeets
Every page is marked as English.
3.2.1 On FocusMeets
Moving focus to a control never changes the page.
3.2.2 On InputMeets
Choosing in a field never changes the page by itself. The school picker is a menu that acts on the school chosen, and the term picker waits for Done.
3.3.1 Error IdentificationMeets
Errors are described in words beside the field or form, and announced.
3.3.2 Labels or InstructionsMeets
Every field has a label, and a field that needs a format says what it is.
4.1.1 ParsingMeets
Pages are generated by React and are well-formed.
4.1.2 Name, Role, ValueMeets
Native controls throughout. Toggle tiles say whether they are pressed, and radio lists, tabs and menus say what is chosen.

Level AA · 20 criteria

1.2.4 Captions (Live)Not applicable
No live audio or video.
1.2.5 Audio Description (Prerecorded)Not applicable
No video.
1.3.4 OrientationMeets
Works upright and sideways on phones and tablets.
1.3.5 Identify Input PurposeMeets
Sign-in, password, invitation, account and free-trial fields say what they are for, so a browser can fill them in.
1.4.3 Contrast (Minimum)Meets
All text is 4.5:1 or better against its background.
1.4.4 Resize TextMeets
Text grows with the browser's zoom to 200% without losing anything. Wide tables scroll within their own box.
1.4.5 Images of TextMeets
No pictures of text, apart from the logo.
1.4.10 ReflowMeets
Pages fit a phone's width. Score grids and summary tables scroll within their own box, as tables are allowed to.
1.4.11 Non-text ContrastMeets
Fields, focus rings, mastery colors and the lines of the score grid are 3:1 or better against whatever sits beside them.
1.4.12 Text SpacingMeets
With WCAG's wider letter, word and line spacing, nothing is lost: names wrap rather than being cut off, and text still shortened with “…” is a link or button that opens it in full.
1.4.13 Content on Hover or FocusMeets
Extra detail uses the browser's own tooltips. Menus open on a click or a key, and close with Escape.
2.4.5 Multiple WaysMeets
The sidebar, favorites, breadcrumbs, and links between classes, boards and children.
2.4.6 Headings and LabelsMeets
Headings and labels say what they are for.
2.4.7 Focus VisibleMeets
Keyboard focus is shown on every control, including grid cells, tabs, radio lists, menus and selects.
3.1.2 Language of PartsNot applicable
Everything is in English.
3.2.3 Consistent NavigationMeets
The sidebar and header are the same on every page.
3.2.4 Consistent IdentificationMeets
The same action has the same name everywhere.
3.3.3 Error SuggestionMeets
An error message says how to put it right.
3.3.4 Error Prevention (Legal, Financial, Data)Meets
Deleting a child, class, template, school or district asks first, and a school's or district's name must be typed.
4.1.3 Status MessagesMeets
Saving on the Assessments tab and in the template builder, and the result of a form, are announced without moving focus.

How we checked

Automated testing. axe-core 4.10 ran every WCAG 2.0, 2.1 and 2.2 Level A and AA rule against 20 page states, signed in as a school administrator: Classes; a board’s Assessments grid, one-child view, Summary, Reports and Small groups; a child’s progress and What to reteach; Board Templates and the template builder; Teams, Your profile and the change log; the printed class record and student summary; and the Privacy and Security pages. Once the fixes it found were in, every one reported no violations. On September 29, 2026 it ran again on every public page — the front page, Sign in, Privacy, Security, Help and this page — with none.
By hand. Reaching everything with the keyboard, and seeing where focus is; WCAG’s text-spacing values applied, to the board and to every public page at a computer’s width and a phone’s; status messages; what sign-in and account fields say they are for; what a press does before it is released; and the names voice control would use.
Fixed on September 29, 2026. The school picker became a menu and the term picker waits for Done, so choosing never changes the page by itself. The score grid’s lines and the last of the fields’ borders reached 3:1. Names wrap instead of being cut off. Absent and unenrolled children’s rows are muted in a gray that still reads, rather than faded. An idle sign-out now warns two minutes before, with Stay signed in. The grid’s all, clr and abs, Start over, and Export CSV are named by the words on them. And the front page’s pictures of the app can be scrolled from the keyboard.

Not done yet

Testing with screen readers — VoiceOver on iPad and Mac, NVDA on Windows — and with teachers who use assistive technology.
The automated run on screens added since it: the school and district consoles, Import Scores, the standards picker and the free-trial form. They are built from the same parts as the rest, and that run is next.

Tell us about a barrier

If something in Mastery Board gets in your way, write to info@abovesoulutions.com and tell us which page and what happened. A district can ask there for the full conformance report, too: the VPAT® 2.5, WCAG edition.