It is nine at night and your daughter cannot submit her homework. The district moved assignments to a new portal over the summer, and the portal does not respond to her keyboard. Her screen reader reaches the upload area and announces "button," nothing more. The help desk tested it on their machine and said it works fine.

Both things are true. The site loads, renders, and functions for someone using a mouse and a pair of working eyes. It also fails a published technical standard that most schools in the country are legally required to meet. That standard has a name, a version number, and a list of specific, testable rules. Once you know how to point at the exact rule being broken, the conversation with the help desk changes shape.

What WCAG Is

WCAG stands for the Web Content Accessibility Guidelines, published by the World Wide Web Consortium, the same international body that maintains the technical specifications for HTML itself. Version 2.0 arrived in 2008, version 2.1 in 2018, and version 2.2 in 2023. Each version adds rules without discarding the old ones, so a site meeting 2.2 also meets 2.1.

WCAG is not a law. It is a specification, written by engineers and disability advocates, that defines what an accessible web page does. Laws borrow it. The Department of Justice rule for state and local government websites names WCAG 2.1 Level AA by number. Section 508, which governs federal agencies and the vendors selling to them, points at WCAG as well. Courts hearing accessibility cases against private companies routinely order WCAG conformance as the remedy, even though no federal regulation sets a standard for private business websites.

The useful part for a family is the structure. WCAG is not a philosophy statement. It is a numbered list of success criteria, each one written so that a person can look at a page and say pass or fail. Criterion 1.4.3 says body text needs a contrast ratio of at least 4.5 to 1 against its background, which is a number anyone can measure with a free color picker and get the same answer the district's contractor would get.

The Four Ideas Underneath Every Rule

Every success criterion traces back to one of four questions about a web page.

Can you perceive the content? A photo with no text description, a video with no captions, and a form field labeled only by color all fail here. If information reaches the user through exactly one sense, anyone without that sense loses it.

Can you operate the page? This is the keyboard question. Every menu, button, form, slider, and pop-up has to work without a mouse, because switch users, screen reader users, and people with tremor or limited hand mobility navigate by keyboard or by devices that emulate one. Time limits that cannot be extended fail here too.

Can you understand what is happening? Error messages that say "invalid entry" without saying which entry or why, navigation that reorders itself between pages, and form fields that change the page the instant you touch them all fail this question.

Does the code hold up in assistive technology? The page has to be built so a screen reader, a braille display, or a voice control tool can interpret it correctly. A button coded as a plain image is the classic failure, and it is what your daughter's screen reader ran into at nine at night.

Why Level AA Is the Number That Matters

WCAG sorts its criteria into three conformance levels. Level A covers the failures that make a page flatly unusable for someone. Level AA covers the ones that make it unreasonably difficult. Level AAA covers enhancements that the specification itself says no site is expected to meet across all content.

In WCAG 2.1, Level A holds 30 success criteria and Level AA adds 20 more, so "WCAG 2.1 Level AA" means roughly 50 testable requirements. That phrase is the one to memorize. It is the bar written into the ADA Title II regulation, the bar in most state procurement rules, and the bar named in settlement agreements. A vendor telling a school district that its product is "accessible" or "508 friendly" has said nothing measurable. A vendor certifying WCAG 2.1 Level AA conformance, with a completed accessibility conformance report behind it, has made a claim you can check.

Five Checks You Can Run Yourself

None of these require software, training, or a developer.

Unplug the mouse. Put the mouse aside and move through the page with the Tab key, Enter, and the arrow keys. You should be able to reach every link, button, and form field, and a visible outline should show you where you are at all times. If the outline disappears, or if Tab skips the thing you need, or if a pop-up traps you with no way out, that is criterion 2.1.1 or 2.4.7 failing.

Zoom to 200 percent. Hold Ctrl and press plus five times, or Command and plus on a Mac. Text should grow and reflow. If content vanishes off the right edge, overlaps, or forces you to scroll sideways to read a sentence, the page fails 1.4.4 and 1.4.10.

Turn on the captions. Any prerecorded video with speech needs synchronized captions under 1.2.2. Auto-generated captions with garbled names and no punctuation do not meet the criterion, though they are usually a sign nobody reviewed the content rather than a deliberate choice.

Look hard at the light gray text. Small gray-on-white text, faint placeholder text in form fields, and low-contrast buttons are the most common failure on the entire web. Free contrast checkers let you paste in two colors and get the ratio. Under 4.5 to 1 for normal text fails 1.4.3.

Turn on the screen reader for two minutes. VoiceOver is built into every Mac and iPhone, Narrator into every Windows PC, TalkBack into Android. Turn it on and listen to how the page announces itself. Images that read as "image" or as a filename, buttons that read as "button" with no name, and headings that are not marked as headings become obvious within a minute. Families already using screen reader software as a formal accommodation usually spot these failures faster than the vendor's own testing does.

What Compliance Means in Practice

For public schools, universities, libraries, city and county governments, and any other state or local public entity, the Department of Justice has issued a rule setting WCAG 2.1 Level AA as the requirement for websites and mobile apps. Compliance dates have moved more than once, so check the current status of the web accessibility deadline before quoting a date to anyone. The requirement itself has not changed, only the calendar.

For a family dealing with a specific school, there is often a faster path than the ADA rule. Section 504 and the IDEA both require that a student with a disability get equal access to the education program. An inaccessible homework portal is a denial of access under those laws today, without waiting for any deadline. The same reasoning covers a district's online learning platforms and parent portals, and it extends to the patient portals and scheduling systems that healthcare providers increasingly require families to use.

For private companies, the picture is looser. The Department of Justice has long held that the ADA covers the websites of businesses open to the public, but no regulation sets a technical standard for them. Companies still get sued, and the settlements still cite WCAG 2.1 Level AA, because it is the only measurable standard anyone has.

How to Report a Site That Locks You Out

Write down what happened while it is fresh. The page URL, the date and time, the browser, the assistive technology and its version, what you were trying to do, and what the computer did instead. A thirty-second screen recording with the audio of the screen reader running is worth more than three paragraphs of description.

Then name the failure in the standard's own vocabulary. "The site is hard to use" invites a debate about opinion. "The homework upload control at this URL cannot be reached with the keyboard, which fails WCAG 2.1 success criterion 2.1.1, Level A" gives the district's IT contractor a defect to fix and a ticket number to fix it under.

Send it to the right place. Every public entity with 50 or more employees is required to designate an ADA coordinator and publish a grievance procedure, and most websites carry an accessibility statement with a contact address. Send it to both, in writing, and keep the copy.

If nothing moves, the Office for Civil Rights at the Department of Education takes complaints about schools, generally within 180 days of the incident, and its online complaint form does not require a lawyer. The Department of Justice takes ADA complaints about state and local government. Many state attorneys general accept them as well.

Your daughter's portal will get fixed faster because someone wrote down a criterion number than because someone said the site was frustrating. A published standard converts an experience that a help desk can wave off into a defect that a contract obligates someone to close, on a timeline, with a name attached to it.