Accessibility in School Software: Why WCAG Matters

A school is one of the most diverse user bases any software will ever meet. In a single building you have a teacher with low vision enlarging everything on screen, a student who navigates entirely by keyboard, a parent reading a portal through a translation layer on a cheap phone, an office administrator with a repetitive strain injury who cannot use a trackpad all day, and a child with dyslexia for whom a cramped, low-contrast screen is genuinely hard work.

Software that only works for the people who designed it has not failed gracefully. It has simply excluded everyone else — and in a school, "everyone else" is a lot of people with a legal and moral claim to be included.

Two words behind the requirement

Two reference points come up whenever this subject does.

The ADA — the Americans with Disabilities Act — has been read by courts to cover digital services, not just ramps and doorways. A public body, and a school is one, is expected to make its digital tools usable by people with disabilities. "We bought it from a vendor" is not a defence; the obligation follows the service.

WCAG — the Web Content Accessibility Guidelines — is the practical standard that turns that obligation into something you can actually check. It is the yardstick most procurement rules, including many school and government ones, now point to. Level AA is the common target. You do not need to memorise it, but you should know it exists and ask whether a tool meets it.

What it means for an attendance tool, concretely

Abstract principles are easy to nod along to and easy to ignore. Here is what accessibility looks like at the point where a real person touches the software.

• Everything works from the keyboard. A teacher should be able to open a class, mark it and move on without ever needing a mouse. If a core action can only be reached by precise pointing, anyone with a motor impairment is locked out of it.
• A screen reader can narrate it. Buttons that are labelled, headings that are real headings, status messages that are announced. A blind administrator pulling an attendance report should hear what is happening, not silence followed by a mystery.
• Contrast is high enough to read. That large green check-in confirmation is only reassuring if a student with low vision, on a sun-glared tablet at the door, can actually see it. Pale grey on white fails the people who most need the feedback.
• Targets are big enough to hit. A check-in button meant to be tapped at speed, by a queue of children, cannot be a tiny target that demands a steady, precise finger.
• Motion and timing are forgiving. A rotating code that refreshes for security must still give someone who reads slowly, or moves slowly, a fair chance to use it. Security and accessibility have to be designed together, not traded off.

The gradebook raises the stakes

Attendance is time-critical; a gradebook is meaning-critical. A grade displayed only as a colour — red for failing, green for passing — is invisible to a colour-blind teacher and to a parent reading in bright light. Information carried by colour alone has to be carried by text or shape as well. A table of marks that a screen reader announces as an undifferentiated wall of numbers, with no row or column context, is technically present and practically useless.

These are not exotic edge cases. Colour-blindness alone affects roughly one in twelve men. In a staffroom of thirty, the odds are that someone cannot rely on your red-and-green.

Myth and reality

A few beliefs keep accessibility stuck at the bottom of the backlog. They are worth retiring.

• "It's for a tiny minority." Permanent disabilities are only part of it. Add the temporary — a broken wrist, an eye infection — and the situational — bright sunlight, a cracked screen, holding a toddler one-handed — and accessible design is better for very nearly everyone, some of the time.
• "It makes the product uglier." Good accessibility and good design are the same discipline: clear hierarchy, legible type, honest contrast, obvious actions. The tools that treat accessibility as an afterthought tend to be the cluttered ones.
• "We'll add it later." Retrofitting accessibility is painful and expensive precisely because it touches structure, not surface. Built in from the start, it is mostly a matter of discipline.

The standard to hold

The right bar is not "accessible to most users." It is "usable by everyone who needs it, without a special version." A separate, stripped-down "accessible mode" is usually a sign the main product left people out. The aim is one product that bends to the person using it.

Classable is built to be used by the whole school community — keyboard and screen-reader friendly, with contrast and targets that hold up at a busy gate — because an attendance and grading tool that some of your staff, students or families cannot use is not actually done.