Button without an accessible name
The interactive element exists in the DOM, but a screen reader does not receive a clear action name.
button.product-card__favoriteWCAG AA website accessibility check
Find barriers that make a site hard to use: unclear buttons, unlabeled fields and unreadable text. Get an automated accessibility check with explanations.
Check result
A report that turns directly into team tasks
The report identifies an affected element in the DOM, the browser’s element tree, with a selector and HTML fragment. Find the component, fix the issue and retest its keyboard and screen-reader behavior.
violationspassneeds reviewWCAG tags
accessibility-report3 issues · 42 rules passed
Form field is not connected to its label
The user can see the label, but the technical relationship between the label and input is missing.
#checkout-emailText contrast is below WCAG AA
The button state is visually weak and can disappear against the dark interface background.
.promo-banner .btn-secondaryReview impact
Start with critical and serious issues to remove the most visible access barriers quickly.
Share selector
Send the developer the exact target, HTML fragment, and short reason for the violation.
Recheck release
Run the check again after fixes and see which violations disappeared from the report.
What we check
Semantics, ARIA, forms, and contrast in one accessibility check
The automated website accessibility check examines the rendered interface for detectable issues. Findings relate to WCAG rules; a passing report does not certify full WCAG AA compliance.
Page structure
We check document title, page language, heading hierarchy, landmark regions, lists, and alternative text for images.
Details for developers
- h1-h6 and landmarks
- alt text and hidden SVGs
- lang, title, and base semantics
ARIA and accessible names
ARIA attributes describe a control’s role, state and relationships to assistive tools. We check incorrect relationships and controls without clear names; adding ARIA alone does not make an interaction accessible.
Details for developers
- button, link, input name
- role/state/property issues
- combobox, dialog, and menu patterns
Forms, errors, and contrast
We check labels, required and invalid states, helper text relationships, text contrast, and the readability of important elements.
Details for developers
- label and helper text
- WCAG AA contrast ratio
- errors and live messages
FAQ
Frequently asked questions about accessibility checks
Short answers about WCAG, automated rules, DOM nodes, ARIA, forms, contrast, and fix order.
What does the automated check catch?
It finds issues that can be detected from rendered HTML and styles: missing labels, ARIA errors, invalid roles, contrast problems, empty links and buttons, alt text, landmark structure, and part of the WCAG rule set.
What does WCAG AA mean for a website?
WCAG AA is a practical target level of accessibility for most commercial and public interfaces. Report rules are marked with WCAG tags, so you can see which requirement each violation relates to.
Does this replace a manual audit?
No. The check covers technical violations in DOM and CSS well, but complex scenarios, actual keyboard traversal order, and screen reader behavior should be confirmed in a separate manual stage.
Can I start with one page?
Yes. The first pass usually checks the homepage, lead form, product card, checkout, or account area. For templated sites, it is useful to check one page of each type and compare repeated violations.
What should be fixed first if there are many errors?
Start with critical and serious issues: elements without accessible names, fields without labels, ARIA errors, insufficient contrast, and interactive elements represented incorrectly in the DOM. Moderate and minor issues can be grouped with nearby design or layout changes.
Related services
What to check next to this service
HTML check
Find HTML errors and an overly complex page structure. The report identifies the affected elements.
OpenCSS audit
Find large stylesheets, duplicates, and styles unused during loading. Unused styles may still be needed on other pages or after user actions.
OpenSEO audit
Audit up to 5 pages for SEO, metadata and content availability before and after JavaScript.
OpenLoad speed
Check page loading with your chosen device and network settings. Get speed measurements, findings, and recommendations.
Open