Weak focus visibility
Keyboard users cannot clearly see which element they control.
Automated audits find only part of the problem. Keyboard use, focus, semantics, screen readers and component behavior need to be checked by actually using the interface.
Scanners are useful, but they do not replace using the page.
Keyboard users cannot clearly see which element they control.
Keyboard navigation does not follow the logical structure of the page.
Labels, errors and instructions are not correctly connected to inputs.
Visually correct components can be announced poorly by assistive technology.
Text, controls or interactive states can be difficult to distinguish.
Small targets, blocked zoom or gesture-only actions can create barriers.
I use automated tools for repeatable issues and manual checks to understand how real flows behave.
Homepage, forms, menus, modals, checkout or other important paths.
Headings, landmarks, labels, roles, accessible names and element relationships.
Check order, focus, interactive components and whether flows can be completed without a mouse.
Check announcements, reading order, errors and state changes in critical areas.
Each issue is documented with context, impact and a technical fix that can be retested.
The exact scope depends on the site and its components.
Accessibility improves when every issue is reproducible and the fix can be tested with the same flow that previously failed.
We can start from the most-used pages and build a prioritized list of reproducible issues.