Skip to content

Project Gallery

fecarrico edited this page Jul 27, 2026 · 1 revision

Project Gallery

Why this page exists: context files are easy to praise and hard to prove. This gallery collects real projects that shipped with A11Y.md in the loop — what was built, who built it, and how the protocol showed up in the work. Every entry needs a public link; that's the entry ticket.


🏛️ CEU São Paulo — Phorte × City of São Paulo (July 2026)

What shipped: ceu.phorte.org.br — the public portal for four CEUs (Unified Educational Centers) in São Paulo, Brazil: Silvio Santos, Rei Pelé, Padre Ticão and Papa Francisco. A partnership between Faculdade Phorte / Instituto Phorte de Educação, the City of São Paulo and Integra S/A, the site organizes the discovery of free education, sports, leisure and culture activities — agenda, filters, unit pages, maps and enrollment paths.

Design lead: Marcelo Vignola Coelho (UI/UX & Product Designer, Design Engineer) — branding, visual identity, information architecture, UX/UI, components, accessibility, and follow-through to the published site. Three sprints in four weeks, in collaboration with Dorys Dantas Ribeiro (Marketing Manager) and Emerson Rocha (Educational Project Lead).

How A11Y.md was used — in the team's own words, from the published design case (translated from Portuguese):

"An important reference at this stage was A11yMD, by Felipe A. Carriço. The proposal of putting accessibility into the AI's working rules, before starting to build the interface, helped bring that conversation to the beginning of the process."

What accessibility shipped: keyboard navigation, visible focus, skip link, font-size adjustment, high contrast, reduced motion, voice reading, VLibras (Brazilian Sign Language) integration, alt text, and states that don't rely on color alone. The team is explicit that no formal specialized audit has been run — accessibility shipped as a structural criterion of the build, not as a certification claim. That is Principle Zero working as intended.

The part we didn't expect: the accessibility conversation spilled beyond the screen. From the announcement post:

"As that discussion grew, we also began studying structural and physical improvements in the CEUs for people with mobility difficulties and other groups who face barriers in the space. That front remains under study, but the biggest gain is bringing accessibility to the table."

A context file for code generation ended up on the agenda of a building. We'll take it.

Links: Live site · Design case · LinkedIn announcement


📬 Submit your project

Built something with A11Y.md in the loop — a product, a prototype, an internal tool? Open an issue with:

  1. A public link to the shipped project (or a case study about it).
  2. How A11Y.md showed up in the work — the rule file in your agent, a profile choice (Shield / Standard / Launchpad), an A11Y-DECISIONS.md, a REPORT.md… in your own words.
  3. Who to credit — person or team, with a link.

Entries are curated for one thing only: that the connection to the protocol is real and publicly verifiable. Imperfect, in-progress, honest projects are welcome — that's what EXCEPTIONS.md is for.

Clone this wiki locally