Bluehost EN 301 549 Checker

EN 301 549 for Bluehost Sites

EN 301 549 is the European standard for accessible information and communication technology. For websites, its clause 9 reuses WCAG: version 3.2.1 uses WCAG 2.1 Level AA, and version 4.1.1, published in September 2026 for the European Accessibility Act, uses WCAG 2.2 Level AA.

The European Accessibility Act has applied to e-commerce and other consumer services since June 28, 2025, wherever the business is based. This checker runs the scan with the EN 301 549 preset, which tests the WCAG 2.1 AA web requirements. Run the Bluehost WCAG 2.2 checker as well to cover version 4.1.1.

Hosting does not affect EN 301 549 conformance. For a site on Bluehost that serves EU customers, test the site itself, in every language you publish.

Who Should Run the Bluehost EN 301 549 Checker

• Bluehost businesses that sell products or services to consumers in the EU.
• Public sector bodies in the EU running a site on Bluehost.
• Vendors selling software or services to EU public bodies.
• Non-EU companies with EU customers, since the EAA follows the customer.

EN 301 549 Requirements to Check on Bluehost

• 1.4.10 Reflow

  Pages must reflow on a narrow screen without scrolling in two directions.

• 1.4.11 Non-text Contrast

  Controls, icons and focus indicators need 3:1 contrast.

• 3.1.1 Language of Page

  Each page must declare its language, which matters on multilingual EU sites.

• 3.3.2 Labels or Instructions

  Form fields, including checkout and consent forms, need visible labels or instructions.

• 4.1.2 Name, Role, Value

  Custom controls such as cookie consent switches need a name, role and state.

• 4.1.3 Status Messages

  Status messages, such as cart updates and form errors, must be announced.

Where Bluehost Sites Usually Fail EN 301 549

These problems come up again and again on Bluehost sites, and each one fails EN 301 549. The Bluehost accessibility checker explains how to fix them in Bluehost.

• Starter themes and demo content. Placeholder images without alt text, sample pages and demo sections can stay live long after launch.
• Low-contrast colors. Theme color settings often produce light text or buttons that fail WCAG contrast minimums.
• Unlabeled form fields. Contact and signup forms that use placeholder text instead of labels are hard to use with a screen reader.
• Empty links and buttons. Social icons, cart icons and search buttons without text alternatives are announced as just "link" or "button".
• Sliders and pop-ups. Auto-rotating sliders without a pause button and pop-ups that trap keyboard focus are common in WordPress themes.

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

What to Test by Hand on Bluehost

Automated testing finds many, but not all, EN 301 549 failures. Check these yourself after the scan:

1. Check every language version, including the page language setting (3.1.1).
2. Test the cookie consent banner with a keyboard and screen reader.
3. Publish accessibility information for your service, as the EAA requires.
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

• EN 301 549 CheckerThe EN 301 549 standard in full, for any website.
• WCAG 1.1.1 Non-text Content Explained in Plain EnglishWCAG 1.1.1 Non-text Content explained simply: how to write alt text for every kind of image, icon, chart and CAPTCHA, with code examples and a test routine.
• 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 Success Criteria LibraryLook up any criterion the scan flags, in plain language.

Bluehost EN 301 549 Checker: Frequently Asked Questions