Timeline

Apr 24, 2026Milestone

The discomfort that became a project

At the “Who's left out when AI works?” roundtable in the TDC Summit São Paulo Community Lounge, accessibility keeps being framed as compliance and punishment. The discomfort leaves the room as a question: what if the rules entered the AI's context before its first answer?

Frontend Dogma, Jens Oliver Meiert's accessibility archive, lists the project on the day it is born.

On day two, someone takes a copy to build on (@Hiltonjunior). A standard only exists once it leaves its author's hands.

Maria Eduarda Iwashita runs a blind-baseline A/B test against a pre-1.0 version — without asking permission, which is how science works. Her findings return to this timeline in August.

The three compliance profiles (Shield, Standard, Launchpad), the AI behavior contract and the technical guide library form the first stable version.

Every requirement now cites its WCAG criterion by number, separated from House Rules†. And the translation layer for iOS, Android, React Native and Flutter — the only one in the field — joins the library.

Jul 2026Milestone

The standard reaches a real building

The São Paulo CEUs portal (Faculdade Phorte × City Hall, design by Marcelo Vignola) is born with A11Y.md in the AI's working rules — and the conversation spills off the screen: the team starts studying physical accessibility improvements in the educational centers themselves.

The evidence artifacts stop depending on someone remembering to ask: report, decisions and exceptions now have a trigger in the contract, and the repository gets its first executable checker.

Video and audio get a contract of their own, and the cognitive criteria of WCAG 2.2 enter the standard's floor.

Independent Verification joins the contract: the agent that wrote the code cannot be the sole witness that it conforms. Five new guides — including generative interfaces — and voice-control validation in the checklist.

Discussions opened, contribution forms (field reports, errata, proposals, gallery) and a complete security policy. That day, the repository stood at 363 stars and 15 forks — with 18 contract rules and 29 guides in the library.

Aug 26, 2026Milestone

The conversation reaches Natura

An accessibility and inclusion panel inside Natura, alongside Simone Freire, founder of the Web para Todos movement, and Vitor David, of ABNT’s CB-040 committee and author of the sentence that opens this site. The subject stepping out of the specialists' circle and into organizational decisions and culture — precisely this project's bet.

Study 3's hardest criterion failed, and the consequence table written before collection collected on the promise: Section 6 now names the exact mold that survived both versions — the carousel announced as tabs without the tab roles — with its two honest exits. Nothing else changed.

No obligation changed. What changed is the address of everything an agent fetches: the invocation phrase, the lazily loaded guides and the scripts now point at the plain file on GitHub, not at the page. The phrase also stops naming "A11Y.md" before the link, because .md is an internet domain and an IDE chat could turn the name into a link to the wrong site.

Since v1.7.0 someone who did not write the code has to witness that the interface works, but nothing told that person what to look for. Now every component guide ends with verification scenarios: what must happen by keyboard and what the screen reader must announce, on desktop and on a phone. The shape came from Magoo, Marcelo Sales' behavior library. Also in: a guide for checkbox, radio, switch, slider and select, and the field that says which version of the standard a report was verified against.