llms.txt Content
# wcagc.com
> wcagc is a web accessibility workflow for automated WCAG 2.1 AA checks, EN 301 549 mapping, PDF checks, accessibility statements, scheduled monitoring, and developer-friendly remediation evidence. Automated checks are partial coverage and do not replace manual review.
## Tools
- [Color Contrast Calculator](https://wcagc.com/tools/contrast-checker): Free WCAG color contrast checker. Enter foreground and background colors to see the ratio and whether it passes WCAG 2.1 AA and AAA.
- [Accessibility Statement Generator](https://wcagc.com/tools/accessibility-statement-generator): Generate a basic accessibility statement draft for your organization in seconds.
- [WCAG 2.1 AA Interactive Checklist](https://wcagc.com/tools/wcag-checklist): A free WCAG 2.1 checklist: all 50 Level A and AA success criteria in plain language, flagged by what an automated scanner can and can't check.
- [EN 301 549 Conformance Checklist](https://wcagc.com/tools/en-301-549-checklist): Verify conformance with the European standard for digital accessibility. Maps directly to WCAG 2.1 AA.
- [PDF Accessibility Checker](https://wcagc.com/tools/pdf-accessibility-checker): Check PDF accessibility online for free. Upload a PDF to validate it against PDF/UA and WCAG: tags, reading order, and structure.
## Axe Rule Guides
- [color-contrast](https://wcagc.com/rules/color-contrast): Text does not have enough contrast against its background for many low-vision users to read it comfortably.
- [image-alt](https://wcagc.com/rules/image-alt): An image is missing an alternative text decision, so screen reader users may lose information or hear a raw filename.
- [label](https://wcagc.com/rules/label): A form control has no programmatic label, so assistive technology cannot announce what input is expected.
- [button-name](https://wcagc.com/rules/button-name): A button has no accessible name, so assistive technology users cannot tell what action it performs.
- [link-name](https://wcagc.com/rules/link