Scan any Weebly site against 16 WCAG 2.1 AA rules in seconds — nothing to install, no signup. Built for EU compliance.
Weebly (now part of Square) hosts millions of small-business sites and stores. EU accessibility law does not care how easy the builder was: a Weebly storefront selling to European consumers must meet WCAG 2.1 AA under the European Accessibility Act, same as any bespoke site.
Drag-and-drop builders create a false sense of safety — the layout looks clean, but alt text fields go unfilled, decorative colour pairings fail contrast, and pasted embed widgets ship without titles. Our scanner reads the published page exactly the way a user with a screen reader would encounter it.
16 automated rules covering images, links, forms, headings, language, viewport, contrast, ARIA misuse, and more — mapped to real WCAG success criteria.
Paste your URL, get a letter grade with every issue listed by severity. No account, no email, no waiting for an audit report.
The rule set targets what EU enforcement and enterprise procurement actually look at: WCAG 2.1 AA basics you can document today.
When your scan flags a failing rule, here is where to fix it:
| Issue | Where to fix in Weebly |
|---|---|
| Missing alt text on images | Edit the page → click the image element → Advanced → Alt Text field. For gallery images, open the gallery editor and set alt text per photo. |
| Low contrast text | Theme → Change Theme / Edit Theme → adjust font and background colours. Weebly's colour pickers show hex values — aim for at least 4.5:1 between body text and background. |
| Missing heading structure | Weebly's Title element defaults to H2. Use one H1 (page title via theme settings) then Titles for sections. Avoid using bold paragraph text instead of real headings — screen readers cannot navigate it. |
| Missing form labels | Weebly's Form element generates labels automatically for standard fields. For placeholder-only custom fields, edit the form element and give each field a visible label. |
| Generic link text ("read more", "click here") | Edit text elements and rewrite link anchors descriptively — blog post excerpts commonly repeat "Read More"; change the excerpt link text where the theme allows, or lead with descriptive sentence text. |
| Missing page language | Settings → General → Site Language sets the site language, which feeds the html lang attribute. Verify after changing it by viewing your page source. |
| Buttons without discernible text | Icon-only buttons in headers or footers need accessible names — check social icons render with aria-labels or add visible text next to them. |
Weebly ships with useful foundations — these approaches take you further:
Weebly themes ship responsive layouts, skip-navigation behaviour and labelled standard forms. The platform handles much of the technical layer automatically — which means most remaining issues come from content and theme colour choices.
Changing themes re-renders every page. After any theme change, run a fresh scan — heading structures and colour palettes differ between themes and can silently break compliance.
Weebly gives free rein over fonts and colours with no contrast warnings. Pick text/background pairs that pass 4.5:1 and stick to them site-wide; the scanner flags violations page by page.
Embed code bypasses all platform safeguards. If you paste third-party widgets (calendars, chats, maps), scan the published page — embedded iframes need titles and their inner content may be inaccessible.
Weebly is now part of Square. Accounts are migrating to Square Online, whose editor differs — if you migrate, re-verify accessibility from scratch rather than assuming parity.
Accessibility is not a one-time fix — sites change through content edits, theme updates and new pages. Keep compliance sustainable:
Automated scanning catches roughly a third of accessibility issues — but it catches the ones that are cheapest to fix first. For the full picture, our e-book covers the complete checklist plus a 14-day fix plan.