Framer Section 508 Checker

Section 508 for Framer 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 Framer, 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 Framer Section 508 Checker

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

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

• Text that looks like a heading. Large styled text layers become headings only when you choose a heading tag, so pages can end up with no h1 or with levels in the wrong order.
• Icon-only buttons and links. Social icons, menu toggles and arrow buttons made from a vector frame have no name until you add an ARIA label.
• Tickers, marquees and autoplay. Scrolling logo tickers, looping carousels and background video move constantly, with no way for a visitor to pause them.
• Hover-only interactions. Menus and cards that reveal content only on hover are out of reach for keyboard and touch users unless the same state is available on focus and tap.
• Contrast and focus over imagery. Text over photos and gradients can fail contrast, and custom components often hide or replace the default focus indicator.

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

What to Test by Hand on Framer

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 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 2.4.12 Focus Not Obscured (Enhanced) Explained in Plain EnglishWCAG 2.4.12 Focus Not Obscured (Enhanced) explained simply: how it differs from 2.4.11, who it helps, CSS scroll-padding fixes and how to test for it.
• WCAG 4.1.2 Name, Role, Value Explained in Plain EnglishWCAG 4.1.2 Name, Role, Value explained simply: give every control a name, role and state with native HTML and ARIA, with code examples and how to test.
• WCAG Success Criteria LibraryLook up any criterion the scan flags, in plain language.

Framer Section 508 Checker: Frequently Asked Questions