IONOS Section 508 Checker

Section 508 for IONOS Sites

Section 508 of the Rehabilitation Act requires federal agencies to make the information and communication technology they develop, buy, maintain or use accessible. The Revised 508 Standards, in effect since January 2018, incorporate WCAG 2.0 Level A and AA for web content, electronic documents and software.

Private businesses are not directly covered, but agencies must buy accessible technology, so vendors are often asked for an Accessibility Conformance Report (ACR) based on the VPAT. This checker runs the scan with the WCAG 2.0 AA preset that Section 508 uses.

Hosting does not affect Section 508 conformance. For an agency or vendor site on IONOS, test the site you run there and keep dated results for your ACR.

Who Should Run the IONOS Section 508 Checker

• Federal agencies running a site or microsite on IONOS.
• Contractors and vendors whose IONOS site or portal is part of a federal contract.
• Agencies and vendors preparing a VPAT or Accessibility Conformance Report.
• State bodies and universities whose policies adopt Section 508.

Section 508 Checks That Matter for IONOS Sites

• 1.1.1 Non-text Content

  Every image, icon and chart needs a text alternative, or must be marked as decorative.

• 1.3.1 Info and Relationships

  Headings, lists, tables and form labels must be marked up so assistive technology can read the structure.

• 1.4.3 Contrast (Minimum)

  Text needs a contrast ratio of at least 4.5:1, or 3:1 for large text.

• 2.1.1 Keyboard

  Every function must work with a keyboard alone.

• 2.4.1 Bypass Blocks

  Provide a way to skip repeated navigation, such as a skip link.

• 4.1.2 Name, Role, Value

  Custom controls need a name, role and state that assistive technology can read.

Where IONOS Sites Usually Fail Section 508

These problems come up again and again on IONOS sites, and each one fails Section 508. 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, Section 508 failures. Check these yourself after the scan:

1. Test every page with a keyboard only, including menus and dialogs (2.1.1).
2. Check documents and PDFs separately, since Section 508 covers them too.
3. Record results per criterion if you need to complete a VPAT or ACR.
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

• Section 508 CheckerThe Section 508 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 Section 508 Checker: Frequently Asked Questions