Accessibility checklist for exams, gradebooks, and report cards

1. Define accessible tasks

List the tasks relevant users may need: find an assessment, understand criteria, submit work, enter a mark, read feedback, review moderation, approve a result, read a report, request a correction, and obtain support.

Include teachers, assessment staff, leaders, records, learners, families, administrators, substitute staff, and support users. Note device, connection, language, assistive technology, sensory, cognitive, motor, and temporary needs.

2. Check structure and language

Review headings, focus order, keyboard operation, labels, instructions, error messages, status meaning, scale and grade labels, contrast, text resizing, tables, forms, timeouts, confirmation, and completed-action feedback.

Use plain language for assessment, component, attempt, submission, mark, grade, percentage, weighting, missing, absent, late, exempt, pending, moderated, approved, published, and corrected. Do not rely on colour, sound, position, or an icon alone.

3. Check timing and notification

Test whether a user can find an assessment deadline, recover after a timeout, understand an out-of-date report, read a changed grading period, and request help when a notification arrives late or not at all.

Rehearse missing submission, late work, absent learner, amended mark, moderation adjustment, resit, special consideration, withdrawal, transfer, duplicate, report correction, closure, and outage.

4. Test the complete journey

Accessibility is not only an interface attribute. Test identity, invitation, sign-in, recovery, permissions, marking, moderation, report, correction, export, support, training, backup, restoration, retention, privacy, safeguarding, and incident routes.

The U.S. Department of Education data-quality guidance connects quality with definitions, rules, validation, infrastructure, and professional learning. Include accessibility in definitions, validation, training, and monitoring.

5. Use people and evidence

Test with representative users and assistive technology where appropriate, then combine observed task completion with standards review, support records, error rates, time, workarounds, and unresolved barriers.

Do not claim conformance from an automated scan or vendor statement alone. Record environment, version, task, user need, result, limitation, severity, owner, remedy, and retest date.

6. Keep privacy and safety visible

The U.S. Department of Education data governance checklist covers quality, access, security, lifecycle, sharing, disposal, and monitoring. GOV.UK school guidance emphasises accountable and secure handling of personal data.

Apply qualified local accessibility, privacy, safeguarding, security, records, assessment, and legal review. Avoid collecting sensitive information in a support ticket when a less intrusive description identifies the issue.

7. Operate the checklist

Before release, block tasks with an unsafe or unusable path, publish support, document temporary alternatives, and assign a remedy owner. After release, review accessibility questions, abandoned tasks, corrections, notification failures, and training gaps.

At 30, 60, and 90 days, decide whether to expand, repair, narrow, consolidate, or hold. Keep findings attached to the assessment decision and retest after material change.

Turn the guidance into an accountable decision

Apply this guidance to one bounded part of accessibility checklist for school exam and gradebook software. Define the assessment or reporting decision, authoritative record, accountable owner, permitted users, correction route, evidence, and review date.

Test an ordinary assessment and meaningful exceptions such as a missing submission, late work, absent learner, moderation change, amended result, withdrawn learner, duplicate mark, grading-period change, report correction, access failure, or outage.

Keep supplier capability, school responsibility, professional judgement, local policy, legal advice, and measured outcome separate. If evidence is incomplete, narrow the claim and pilot the smallest safe change.

Review at 30, 60, and 90 days. Check completeness, timeliness, consistency, moderation, calculations, corrections, access exceptions, staff effort, support demand, reporting confidence, and the original outcome. Decide whether to expand, repair, consolidate, narrow, or hold.

Before approval, ask a reviewer who was not involved in the design to challenge the strongest assumption. Replace broad language with the exact evidence, population, date, and limitation the school can verify.

Document what was tested and what was not. A successful demonstration with a simple gradebook does not establish readiness for moderation, resits, special consideration, changed grading periods, multiple campuses, or a changed assessment policy.

Keep evidence beside the decision record so a later reviewer can distinguish observed behaviour from an assumption, estimate, or supplier statement. Name the next test where evidence remains incomplete.

Revisit the boundary when the school adds a subject, year group, campus, grading scale, role, integration, reporting period, or policy. A small change can alter permissions, definitions, calculation, timing, retention, or support demand.

Set the next review date and owner. A dependable exams and gradebook operation is maintained through clear definitions, controlled change, professional judgement, and visible accountability rather than a one-time setup.

Make the handoff readable to a teacher, administrator, leader, learner, and reviewer. State what passed, what remains manual, which records are authoritative, who owns unresolved conflicts, and how a correction is communicated without creating an uncontrolled copy.

Keep approved definitions beside calculation rules, moderation notes, training, support routes, and change history. New subjects, scales, integrations, or reporting windows can change the risk even when field names stay the same.