Practice — Hot · The Accessibility Advocate

Skills focus. Making the accessibility case under pressure — with evidence, a costed plan, and a demonstration.

Ungraded, open-ended. The deliverable is an argument, backed by work.

Scenario

Sprint planning. The report ships Friday. A senior stakeholder says:

"Cut the accessibility tasks — alt text, tab order, the contrast audit. It's polish for a tiny audience, and we don't have the hours. We'll do it in a fast-follow."

You have ten minutes on the agenda and one demonstration slot. The stakeholder is not a villain; they are triaging honestly with wrong information.

Requirements

Cost the work honestly. Time yourself doing the full accessibility kit on ONE real page of your report (alt text, tab order, contrast check, simulation). Report the actual minutes — your argument's credibility depends on a real number, not an estimate.
Build the demonstration. Prepare the before/after that lands hardest in ten minutes. Candidates: the page under CVD simulation with a claim that vanishes; a screen-reader pass over species-label alt text versus finding alt text; the keyboard traversal in creation order versus reading order. Pick ONE and be able to run it live.
Write the two-minute case (the words you would actually say): the one-in-twelve number, the curb-cut argument (each discipline improves the page for every reader), your measured cost from task 1, and the fast-follow's real fate — grounded in this course's own "design later" evidence.
Concede what should be conceded. If any accessibility task on the list genuinely can wait, name it and say why — your credibility as an advocate rests on not defending everything equally.

Reflection

What did the kit actually cost on one page, and how does that number change the argument's character?
Which demonstration did you choose and why — what makes one land harder than the others for THIS stakeholder?