WCAG 2.2 for Hostinger Sites
WCAG 2.2 became a W3C Recommendation in October 2023. It keeps every WCAG 2.1 requirement except 4.1.1 Parsing and adds six success criteria at Level A and AA, mostly about people with low vision, motor disabilities and cognitive disabilities. A Hostinger site that meets WCAG 2.2 AA also meets 2.1 AA and 2.0 AA.
This checker runs the same free scan as the Hostinger accessibility checker with the WCAG 2.2 AA preset, so the results include the 2.2 rules that automated testing can check.
The host does not decide WCAG 2.2 compliance. For a site hosted on Hostinger, the theme, builder or code you run there does, so scan the live pages and fix issues in that software.
| Published | October 5, 2023 |
|---|---|
| Success criteria at Level A and AA | 55 |
| New at Level A and AA | 6 |
| Removed | 4.1.1 Parsing |
| Automated rules in this scan | 63 |
Who Should Run the Hostinger WCAG 2.2 Checker
- Hostinger site owners who want the most current, future-proof target.
- Teams redesigning a Hostinger site, where adopting the latest version costs little extra.
- Organizations selling into the EU, where EN 301 549 V4.1.1 now uses WCAG 2.2.
- Anyone preparing for new rules, which tend to adopt the latest WCAG version.
The New WCAG 2.2 Criteria to Check on Hostinger
-
2.4.11 Focus Not Obscured (Minimum)
Sticky headers, cookie banners and chat widgets must not completely hide the element that has keyboard focus.
-
2.5.7 Dragging Movements
Anything that works by dragging, such as sliders, carousels and sortable lists, needs a single-pointer alternative.
-
2.5.8 Target Size (Minimum)
Buttons and links need a target of at least 24 by 24 CSS pixels, or enough space around them. Icon buttons and pagination links often fail.
-
3.2.6 Consistent Help
Help such as a contact link or chat must appear in the same place on every page that has it.
-
3.3.7 Redundant Entry
Do not ask for the same information twice in one process, such as shipping and billing addresses, without offering to fill it in.
-
3.3.8 Accessible Authentication (Minimum)
Sign-in must not depend on a cognitive test, such as remembering a password without paste support or solving a puzzle.
Where Hostinger Sites Usually Fail WCAG 2.2
These problems come up again and again on Hostinger sites, and each one fails WCAG 2.2. The Hostinger accessibility checker explains how to fix them in Hostinger.
- Template images and banners. Hero images with text baked into them, stock photos without descriptions and decorative graphics read aloud as content.
- Contrast on template colors. Light text over photos, pale buttons and gray captions that look elegant in a template but fall below the contrast minimum.
- Contact and booking forms. Forms from the builder or a plugin that show only placeholders, with errors that screen readers never hear.
- Sliders and animated sections. Auto-advancing banners and scroll animations with no pause control or reduced-motion support.
- Plugin and cookie banner overlays. On WordPress sites, cookie notices and pop-up plugins can trap or cover keyboard focus.
Worried about ADA claims as well? The Hostinger ADA compliance checker covers the Hostinger risks behind most complaints.
What to Test by Hand on Hostinger
Automated testing finds many, but not all, WCAG 2.2 failures. Check these yourself after the scan:
- Tab through each page and check the focused element is never fully covered by sticky content (2.4.11).
- Try every drag interaction with a single click or tap instead (2.5.7).
- Sign in with a password manager and check paste works (3.3.8).
- Rescan after each fix. Continuous monitoring rescans up to 500 URLs per domain daily and keeps a dated record in the Compliance Vault.
Related Guides
Hostinger WCAG 2.2 Checker: Frequently Asked Questions
Does my Hostinger site need to meet WCAG 2.2?
Few laws require WCAG 2.2 yet, but it is the current standard and meeting it also meets 2.1 and 2.0. EN 301 549 V4.1.1, written for the European Accessibility Act, now uses WCAG 2.2 AA.
What is new in WCAG 2.2 for Hostinger sites?
Six Level A and AA criteria: focus not obscured, dragging movements, target size, consistent help, redundant entry and accessible authentication. Target size and focus visibility are the ones scans most often flag.
Can the scan check every WCAG 2.2 criterion on Hostinger?
No automated tool can. The scan checks the criteria that can be tested automatically, such as target size, and lists the ones that need a person, such as accessible authentication.
Sources
- W3C: Web Content Accessibility Guidelines (WCAG) 2.2 (opens in a new tab)
- W3C WAI: What is new in WCAG 2.2 (opens in a new tab)
- GOV.UK: Accessibility requirements for public sector websites and apps (opens in a new tab)
This page explains general accessibility patterns for Hostinger sites and is not legal advice. AccessBell is not affiliated with Hostinger. Hostinger and its logo are trademarks of their owners and are used only to identify the platform. See our disclaimer.
