IONOS WCAG 2.1 Checker

WCAG 2.1 for IONOS Sites

WCAG 2.1 became a W3C Recommendation in June 2018. It added criteria for mobile, low vision and cognitive accessibility to WCAG 2.0, and it is the standard named in the US Department of Justice rule for state and local government websites, in EN 301 549 V3.2.1 and in most accessibility settlements.

This checker runs the free scan with the WCAG 2.1 AA preset, so the results match the standard your contract, policy or regulator is most likely to name for a IONOS site.

For a site on IONOS, WCAG 2.1 compliance depends on the theme, builder or code you run, not the hosting. Scan the live pages and fix issues in that software.

Who Should Run the IONOS WCAG 2.1 Checker

• IONOS site owners whose contracts or policies name WCAG 2.1 AA.
• State and local government bodies, under the ADA Title II rule.
• Businesses responding to an ADA demand letter, which usually cites WCAG 2.1 AA.
• Public sector bodies in the EU, under the Web Accessibility Directive.

WCAG 2.1 Criteria That Often Fail on IONOS

• 1.3.5 Identify Input Purpose

  Form fields that collect personal data, such as name, email and address, need the right autocomplete attribute.

• 1.4.10 Reflow

  Content must reflow at 320 CSS pixels wide, the same as 400% zoom, without scrolling in two directions.

• 1.4.11 Non-text Contrast

  Buttons, form borders, icons and focus indicators need a contrast ratio of at least 3:1.

• 1.4.12 Text Spacing

  Text must stay readable when users increase line, paragraph, letter and word spacing.

• 1.4.13 Content on Hover or Focus

  Tooltips and menus that appear on hover or focus must be dismissible, hoverable and stay visible.

• 4.1.3 Status Messages

  Messages such as “added to cart” or form errors must be announced to screen readers without moving focus.

Where IONOS Sites Usually Fail WCAG 2.1

These problems come up again and again on IONOS sites, and each one fails WCAG 2.1. The IONOS accessibility checker explains how to fix them in IONOS.

• Template color contrast. Builder templates and themes often use light gray text or pale buttons that fall below the 4.5:1 contrast WCAG requires for normal text.
• Images without alt text. Photos added through a builder or media library are easy to publish without alternative text, so screen reader users miss what they show.
• Contact and booking forms. Form widgets and plugins sometimes rely on placeholder text instead of visible labels, and do not announce errors to screen readers.
• Cookie consent banners. Consent banners, common on EU sites, can trap keyboard focus or hide the rest of the page from screen readers until dismissed.
• Headings used for styling. Text styled to look like a heading, or headings chosen for their size, leaves the page without a structure screen reader users can navigate.

Worried about ADA claims as well? The IONOS ADA compliance checker covers the IONOS risks behind most complaints.

What to Test by Hand on IONOS

Automated testing finds many, but not all, WCAG 2.1 failures. Check these yourself after the scan:

1. Zoom to 400% and check nothing is cut off or needs scrolling in two directions (1.4.10).
2. Apply increased text spacing with a bookmarklet and check text is still readable (1.4.12).
3. Open hover menus and tooltips and check you can dismiss them with Escape (1.4.13).
4. Rescan after each fix. Continuous monitoring rescans up to 500 URLs per domain daily and keeps a dated record in the Compliance Vault.

Start 3-day free trial

Related Guides

• WCAG 2.1 AA CheckerThe WCAG 2.1 standard in full, for any website.
• WCAG 1.4.3 Contrast (Minimum) Explained in Plain EnglishWCAG 1.4.3 Contrast (Minimum) explained simply: the 4.5:1 and 3:1 ratios, what counts as large text, the exceptions, fixes and how to test your colors.
• WCAG 3.3.2 Labels or Instructions Explained in Plain EnglishWCAG 3.3.2 Labels or Instructions explained simply: visible labels, format hints, grouped fields and required markers, with code examples and a test routine.
• Automated vs Manual Accessibility Testing: Where Each FitsWhat automated accessibility testing catches, what needs a human, and how to combine both into a repeatable process for finding and fixing WCAG issues.
• WCAG Success Criteria LibraryLook up any criterion the scan flags, in plain language.

IONOS WCAG 2.1 Checker: Frequently Asked Questions