clasohlson.com
Scanned 2 September 2026 against WCAG 2.2 AA with axe-core. 30 issues found.
clasohlson.com fails most automated WCAG 2.2 AA checks, scoring 20/100 (grade F).
What is failing on clasohlson.com
One row per failing rule, worst first. Each links to a guide with the corrected markup.
Certain ARIA roles must contain particular children
Ensure elements with an ARIA role that require child roles contain them
aria-required-children
WCAG 1.3.1 Info and Relationships
Images must have alternative text
Ensure <img> elements have alternative text or a role of none or presentation
Frames must have an accessible name
Ensure <iframe> and <frame> elements have an accessible name
Links must have discernible text
Ensure links have discernible text
<li> elements must be contained in a <ul> or <ol>
Ensure <li> elements are used semantically
Interactive controls must not be nested
Ensure interactive controls are not nested as they are not always announced by screen readers or can cause focus problems for assistive technologies
nested-interactive
WCAG 4.1.2 Name, Role, Value
All touch targets must be 24px large, or leave sufficient space
Ensure touch targets have sufficient size and space
All page content should be contained by landmarks
Ensure all page content is contained by landmarks
region
How to fix it
Headings should not be empty
Ensure headings have discernible text
empty-heading
How this report was produced
We load clasohlson.com in a real Chromium browser and run axe-core against it once it has rendered. That matters: a modal that traps focus or a menu built by JavaScript doesn't exist in the source HTML, only on the rendered page.
The rules map to WCAG 2.2 level AA, the conformance level referenced by EN 301 549 and by the European Accessibility Act. Automated testing catches roughly one third of WCAG success criteria, the machine-checkable ones: colour contrast, missing alternative text, unlabelled form fields, broken heading order. The remaining two thirds need a person, including whether alt text is accurate and whether a flow can be completed with a screen reader.
What the European Accessibility Act requires
Since 28 June 2025 the European Accessibility Act applies to most consumer-facing digital services sold in the EU: e-commerce, banking, transport, e-books and telecoms. It expects conformance with EN 301 549, which points at WCAG 2.2 AA, plus an accessibility statement describing the current state. Anyone can reproduce the issues above in a browser, a regulator included. Read what the Act requires, sector by sector.
Questions about this report
What does a score of 20 mean for clasohlson.com?
It means clasohlson.com fails most automated WCAG 2.2 AA checks. The score starts at 100 and loses points for each distinct failing rule, weighted by severity. Ten missing alt attributes cost the same as one, because they share a single fix.
Does this prove the site is or is not legally compliant?
No. Automated testing reliably catches roughly a third of WCAG success criteria: the machine-checkable ones such as contrast, missing alt text and unlabelled form fields. A clean automated report is a good sign. It is not a conformance statement: full conformance under the European Accessibility Act needs a manual audit alongside it.
How was this report produced?
We load the page in a real browser and run axe-core against it once it has rendered. The rules map to WCAG 2.2 level AA, the standard EN 301 549 and the European Accessibility Act point to.
This is my website. Can I have this page removed?
Yes. Use the removal link at the bottom of this page and the report comes down immediately, no account needed.
Re-scan clasohlson.com, or track it over time
This is one page, scanned once. A free account crawls the whole site, re-scans it on a schedule and emails you when a deploy breaks something.