About this tool
Separate deterministic contrast calculations, automated violations, uncertain findings, passes, and manual review without claiming WCAG conformance.
- Calculates normal, large, enhanced, and non-text contrast thresholds from opaque sRGB colors, text size, and weight.
- Removes executable elements, event handlers, embedded documents, and resource URLs before running axe-core in a unique-origin iframe with network-denying CSP.
- Reports violations, incomplete checks, passes, CSS targets, sanitized-input evidence, and a manual checklist while explicitly excluding conformance claims.
How to use Accessibility QA
Enter foreground and background colors or paste inert HTML, run the relevant check, then review each finding as bounded evidence rather than a conformance verdict.
When this tool is useful
- Before shipping a color token change.
- When reviewing headings, labels, image alternatives, and document language in static HTML.
Practical tips
- Test focus behavior and announcements in a real browser separately.
- Recheck contrast in every actual state and background.
Examples you can test
Load an example, compare the result with the expected output, then replace it with your own input.
Check body text contrast
Example input
Foreground #626c67 on background #f6f7f5
Expected output
Calculated ratio with WCAG AA comparison
A passing pair does not prove the full component is accessible.
Validation checklist
- Confirm colors match the rendered state.
- Review keyboard and screen-reader behavior manually.
- Do not describe the result as WCAG conformance.