Build an accessibility repair workspace that accepts website screenshots, HTML snippets, CSS, and optional browser-generated accessibility reports to help developers identify and resolve interface barriers.
Analyze visible elements for potential contrast problems, unclear visual hierarchy, small interactive targets, confusing focus indicators, and controls whose purpose may be ambiguous. When source code is available, inspect semantic HTML, accessible names, keyboard interactions, heading structure, and form labeling.
For each finding, provide a severity rationale, supporting evidence, a proposed correction, and a test that can verify the fix. Generate revised HTML or CSS patches in an isolated preview so developers can compare before-and-after results.
Include keyboard-only navigation walkthroughs, screen-reader-oriented checks, and regression checklists. Distinguish screenshot-based suspicions from findings verified through code or automated testing.
Do not claim full WCAG compliance based on screenshots or automated scans alone. Keep original files unchanged until the developer explicitly accepts a patch.
0 Comments