Who audits your site

I've used a screen reader for 13 years. It isn't a tool I open to work: it's how I use a computer. All of it, every day, at work and away from it. When I test your product with NVDA, I'm using it the same way I use everything else, at the same speed.

I work with NVDA, JAWS, Windows Narrator, and TalkBack on Android, and with keyboard-only navigation. That's the part of the job where the barriers no automated tool flags actually show up.

What I audit, and since when

I've audited accessibility professionally since 2021, across websites, mobile apps, documents, and desktop software, against WCAG 2.2, EN 301 549, and the European Accessibility Act.

I came to accessibility from software QA, and that's the part that shows in the deliverable. A finding doesn't reach your team as an observation. It reaches them with the WCAG criterion it fails and its level, the environment it was found in, the steps to reproduce it, and an acceptance criterion your team can close the ticket against. I also write accessibility statements and cognitive accessibility recommendations.

I also teach

I teach digital accessibility at the DALAT Foundation, and I taught the accessibility module at XAcademy. Teaching forced me to explain technical barriers to people who don't write code, and that changed how I write reports: if a content owner can't understand the finding, the finding doesn't get fixed.

Certifications

• A11Y Development Knowledge Badge — IAAP, the International Association of Accessibility Professionals, January 2026. Earned by scoring above 85% on their accessibility knowledge test for developers. Verify on Credly.
• Digital Accessibility Specialist, WCAG 2.2 Level AA — Instituto de Accesibilidad and DALAT, certified by Universidad Nacional de Tres de Febrero. October 2025.
• ARIA from Scratch for Developers and Designers — WeAAAre, July 2025.
• Digital Accessibility — Universidad Tecnológica Nacional, 2020.

Your report goes through two readings

I do the auditing. I don't get the last word on the report. Before it goes out, another person at tuaccesible reads it, checks the prioritization and pushes back on the criteria I applied. The pushback is real: sometimes I drop a finding from critical to high because I can't defend it. That's the point. What reaches your team has already survived an argument.

Let's talk

If you have a product to audit, tell me where it stands and on what timeline. I'll tell you where to start.

Email me, or write straight to contacto@tuaccesible.com.