Crear un flujo de auditoría manual

Automated scanners catch maybe 30% of issues. A manual audit is how you find the broken experiences a robot can never feel. 🔍

A solid manual audit leans on three pillars: the keyboard, a screen reader, and browser zoom. Together they reveal what real users hit.

Unplug your mouse and press Tab through the page. Every link, button, and field should be reachable in a sensible order.

As you Tab, you must always see where you are. A missing focus indicator leaves keyboard users completely lost on the page.

Turn on NVDA, VoiceOver, or TalkBack and navigate by heading and landmark. Does what you hear match what you see?

Press Ctrl or Cmd plus to reach 200% zoom. WCAG requires no loss of content or function, with no horizontal scrolling on a normal page.

Sample real text against its background. Body text needs a contrast ratio of at least 4.5 to 1 to pass WCAG AA.

Open DevTools and read the accessibility tree. It shows the name, role, and state that assistive tech actually receives for each element.

Work from a fixed checklist every time. A consistent list means you cover the same ground and never skip a critical check by accident.

Pick the trio that anchors a thorough manual audit.

Capture each issue as you go with a screenshot or note. A clear record turns a messy audit into a fixable, trackable list.

Scope each pass to a single user flow, like sign-up or checkout. Small, focused passes find more than skimming the whole site at once.

You now run a manual audit with keyboard, screen reader, and zoom, read the a11y tree, and log findings flow by flow. 🎯