juist.nl
Scanned 28 September 2026 against WCAG 2.2 AA with axe-core. 19 issues found.
juist.nl fails 1 automated WCAG 2.2 AA check (1 serious), scoring 90/100 (grade A).
What is failing on juist.nl
One row per failing rule, worst first. Each links to a guide with the corrected markup.
Elements must meet minimum color contrast ratio thresholds
Ensure the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds
Best-practice suggestions
One row per rule. These are not WCAG failures and do not affect the score.
Heading levels should only increase by one
Ensure the order of headings is semantically correct
heading-order
How to fix it
All page content should be contained by landmarks
Ensure all page content is contained by landmarks
region
How to fix it
How this report was produced
We load juist.nl 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, which EN 301 549 V4.1.1 adopts. Automated testing covers about a third of the WCAG success criteria, the machine-checkable ones: colour contrast, missing alternative text, unlabelled form fields, a missing page title. 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. For websites the reference is EN 301 549. EN 301 549 V3.2.1 (2021) uses WCAG 2.1 AA and is cited in the Official Journal only under the public-sector Web Accessibility Directive. EN 301 549 V4.1.1, published on 2 September 2026, adopts WCAG 2.2 AA and adds a mapping to the European Accessibility Act, but it is not cited yet, so no standard currently gives a presumption of conformity under the EAA. The Act also asks a provider to publish how its service meets the accessibility requirements. 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 90 mean for juist.nl?
It means juist.nl fails 1 automated WCAG 2.2 AA check (1 serious). 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 covers about a third of the 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, which EN 301 549 V4.1.1 adopts. The version cited in the Official Journal, V3.2.1, uses WCAG 2.1 AA.
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 juist.nl, or track it over time
This is one page, scanned once. New accounts get 14 days of Agency features with no card, including automatic re-scans and regression alerts. After that they move to Free, where you start each scan yourself: 1 site, 25 pages a scan.