WCAG tells you to provide alt text. ADA tells you to build a ramp. Both are correct. Neither one asks the question that actually matters: who is the person on the other end, and what do they need from this system to use it?

Accessibility standards are governance without attunement. They prescribe what to build. They say nothing about how to think about the person you’re building for. A checklist of ARIA roles and contrast ratios can produce a technically compliant interface that still fails the user, because the standard doesn’t require you to understand who’s using it. It requires you to meet a specification.

I taught self-contained special education in Sunset Park, Brooklyn. Twelve students, twelve IEPs. The IEP starts with what’s called Present Levels of Performance: where the student actually is right now. Processing speed, working memory, sensory profile, attention, reading level, behavioral patterns. The accommodation comes after the assessment. You read the person first. Then you design the intervention.

That order changes everything. Most accessibility practice starts with the standard and works backward toward the person. WCAG 2.1 says contrast must be 4.5:1. Build to the ratio. The ratio is correct. But two users who both need the ratio might need entirely different things from the same interface. One has low vision and needs large type. The other has a processing delay and needs reduced cognitive load. The contrast ratio helps both. The ratio alone is sufficient for neither.

The pedagogical approach starts with the person and works forward toward the design. What is the processing reality of the person receiving this? How do they take in information? Where do they lose the thread? What accommodation lets them succeed at this task?

In the classroom, that meant one student got instructions broken into single steps because compound instructions overwhelmed his working memory. Another student got the same content delivered verbally because written instructions didn’t process. Same classroom, same lesson, different accommodations, because the accommodations followed from the profiles, not from a standard.

The same structure applies to anything you build for someone else to use. A product page, an onboarding flow, a dashboard. The accessibility checklist tells you what to include. It doesn’t tell you what the person on the other end actually needs in order to understand what they’re looking at.

Attunement is the missing layer. Before you select the accommodation, you read the room. Who is receiving this? What’s their context? What do they already know? Where will they get stuck? A form that passes every WCAG audit can still lose a user if the cognitive load is too high for the moment they encounter it. The standard doesn’t measure that. The standard measures the surface.

I’ve been running this same operation across every domain I’ve worked in. In the kitchen, attunement means reading which kid is having a good day and which one is already past their threshold before I decide what to put on the table. On an enterprise platform, it means understanding the recruiter’s workflow before restructuring the interface. In AI governance, it means assessing the model’s processing profile before designing the prompt.

The difference between compliance and accommodation is the difference between meeting a standard and meeting a person. Both matter. The standard protects the floor. Without WCAG, you get interfaces that exclude entire populations. Without ADA, you get buildings people can’t enter.

But the standard is the floor, not the practice. Accommodation design starts where the standard ends. It asks what this specific system, this specific person, this specific moment actually requires. The IEP is the document. Attunement is the skill that makes the document worth writing.