You face the South, Huitztlampa, land of thorns and flowers. Huitzilopochtli watches over what grows. The scene takes on turquoise tones of Xiuhtecuhtli mosaic.
Nuada · RGAA accessibility audit
The auditor who codes the fix.
The market reality
The French RGAA accessibility audit market is mature but paradoxical. Large firms deliver 80-page PDF reports, structured against the 106 criteria of the standard, listing each non-compliance with a screenshot and a generic recommendation. The engineering teams receiving those reports are often left helpless: how do you translate "improve link focus contrast" into a concrete pull request? Nuada starts from that observation to propose something else.
The technical stance
Each non-compliance identified by Nuada is delivered with directly implementable fix code, tested on a client project fork when possible. No vague "recommendation," no "to investigate on the team side": a Git diff, an explanation of why, a non-regression test. The auditor becomes a temporary contributor, not a consultant leaving behind a knot of problems.
Site architecture
Astro for static generation, native i18n for fr/en/es with no overhead, MDX for long-form articles, Netlify hosting with preview branches for each new piece of content. The site itself is RGAA 4.1 compliant by construction · no post-audit patching, every component is designed accessible from the start. A test-driven a11y approach that serves as its own example.
What Nuada teaches me
Building Nuada forced me to formalize what was implicit: what I did intuitively on client missions (deliver code rather than text) becomes a reproducible method. The real deliverable of an accessibility audit isn't a document, it's a codebase more accessible than before.
Next steps
Once the RGAA certification is validated (access42 exam October 23, 2026), Nuada can move from showcase site to real tool: partial audit automation via axe-core in CI, before/after comparator on pull request, public library of reusable accessible patterns.