Elementor Section 508 Checker

Section 508 for Elementor 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.

If a federal program or contractor runs a site on Elementor, the builder’s templates and widgets must meet WCAG 2.0 AA. Check that you can edit the parts that fail; if you cannot, document them in your ACR.

Who Should Run the Elementor Section 508 Checker

• Federal agencies running a site or microsite on Elementor.
• Contractors and vendors whose Elementor 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 Elementor 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 Elementor Sites Usually Fail Section 508

These problems come up again and again on Elementor sites, and each one fails Section 508. The Elementor accessibility checker explains how to fix them in Elementor.

• Heading tags chosen for size. The Heading widget lets you pick the HTML tag, but many pages choose it for how big the text looks. The result is several h1s, skipped levels or headings used as decoration.
• Forms with hidden labels. Form widgets can hide field labels and rely on placeholder text, which disappears once someone starts typing and is not a reliable name for assistive technology.
• Icon-only buttons and links. Icon widgets, icon boxes and social buttons often link somewhere without any text, so a screen reader announces only "link".
• Popups, carousels and entrance animations. Popups can open without moving focus, sliders autoplay with no pause control, and entrance and motion effects ignore the visitor’s reduced-motion setting.
• Global colors and sticky headers. A global color palette that fails contrast fails everywhere at once, and sticky or transparent headers can cover the element that has keyboard focus.

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

What to Test by Hand on Elementor

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.3.2 Meaningful Sequence Explained in Plain EnglishWCAG 1.3.2 Meaningful Sequence explained simply: why reading order matters, how CSS and layout tables break it, how to fix it and how to test your pages.
• 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.
• WCAG 2.2.2 Pause, Stop, Hide Explained in Plain EnglishWCAG 2.2.2 Pause, Stop, Hide explained simply: what moving and auto-updating content needs, the 5-second rule, carousel fixes and how to test your pages.
• WCAG Success Criteria LibraryLook up any criterion the scan flags, in plain language.

Elementor Section 508 Checker: Frequently Asked Questions