WCAG 2.1 AA for school websites: a plain-English guide

A school website needs to help someone do something: register a child, find a bus route, read a notice, or contact a teacher. Accessibility barriers can interrupt any of those tasks.

WCAG 2.1 AA gives school website teams a technical framework for identifying and removing those barriers. This guide explains the main ideas through common school publishing tasks. It is an introduction, not a complete conformance evaluation.

What does WCAG 2.1 AA mean?

WCAG stands for Web Content Accessibility Guidelines. Version 2.1 is one version of the standard; AA is a conformance level. Meeting Level AA includes meeting the Level A and Level AA requirements. The requirements address four principles: content should be perceivable, operable, understandable, and robust. W3C's WCAG overview.

Those words become easier to use when you connect them to a family task.

Make information available beyond its visual appearance

Imagine a school publishing a concert poster as a single image. A visitor might enlarge it and still struggle to read the small print. A screen reader needs another way to access the information.

Our recommended publishing pattern is a short event page with the date, time, location, cost, accessibility contact, and registration link in text. The poster can accompany the page. Give meaningful images an appropriate text alternative, and mark purely decorative images as decorative in the publishing tool.

Review color combinations too. WCAG 2.1 AA generally requires text contrast of at least 4.5:1, with a 3:1 threshold for qualifying large text. Exceptions apply, including certain logo and incidental text. Check the actual foreground and background combination rather than judging by eye. W3C's contrast guidance.

For school videos, plan accessibility before recording. Review captions for names, dates, and meaningful sounds. Where important visual information is not conveyed by the audio, assess the applicable audio-description requirements. A transcript can also help families find information quickly, but it does not replace every required media alternative. WCAG 2.1 time-based media requirements.

Test the whole task with a keyboard

Start on the homepage and try to find an enrollment form without using a mouse. Move through the menu, open the form, select options, and reach the submit button.

Note where you lose your place. Does the current control have a visible focus indicator? Does a popup let you leave it? Can you close a calendar or language selector and continue?

Record a specific task when something fails. “Cannot reach the campus selector with the keyboard” gives the website team a clearer starting point than “the page is inaccessible.” W3C's preliminary checks include keyboard access and visible focus, while stressing that a first review does not establish full accessibility. W3C Easy Checks.

Repeat the task on pages with different templates and on external tools involved in the process. Testing only the homepage can miss the form a family actually needs.

Make instructions and errors easy to act on

Enrollment forms often include unfamiliar terms, required documents, and several steps. Explain the process before asking a family to begin.

A field should have a meaningful label that remains available while someone types. Required formats need clear instructions. A placeholder inside an empty field is a poor substitute for a persistent label. W3C's form-label guidance.

Write errors that describe the next action. “Enter a phone number including the area code” is more useful than “Invalid input.” Check that assistive technology can identify the affected field and the error message. W3C's form-notification guidance.

For a school review, include a deliberately incomplete test submission. Confirm that the family can correct the problem and finish without re-entering unrelated information.

Keep structure meaningful

A page's appearance and its underlying structure both matter. Ask publishers to use heading styles for sections, descriptive link text for destinations, and real lists for grouped items.

For example, “Read the enrollment document checklist” gives more context than several unrelated links all labeled “Click here.” A page with clear sections also makes future updates easier: staff can find the deadline, requirements, and contact details separately.

Include your current PDFs in the review. The accessible PDF checklist for school staff explains what to check before uploading a document.

Combine automated checks with human review

Automated checks can flag some problems across many pages. Human review is still necessary; tools cannot determine every aspect of accessibility. W3C's evaluation-tool guidance.

Use a shared issue record with the page address, blocked task, evidence, responsible person, and retest result. Ask an accessibility specialist to assess the relevant WCAG criteria and involve people who use assistive technology when evaluating real tasks.

Give staff a way to report a problem after launch. Menus, new documents, and embedded forms can change even when the underlying website template stays the same.

How does this relate to ADA Title II?

DOJ's Title II web rule adopts WCAG 2.1 Level AA for covered public entities. Its scope, exceptions, and compliance dates require a separate review. Use the ADA Title II school website checklist for the current deadline context and a practical starting list. DOJ's compliance guide.

Choose one task to improve this week

Start with something families need now, such as completing enrollment or finding transportation information. Test it, record the barriers, and assign the fixes. Then retest the same task after the changes.

Explore EdPilotHub's school website accessibility offering, or talk with our team about the pages and publishing workflows your school needs to improve.