Webador Accessibility Checklist 2026 | WCAG 2.1 AA & EAA
Last updated: 2026-07-05
Webador is a straightforward, low-cost website builder popular with small businesses, clubs, and sole traders -- especially across Europe -- who want a simple site or small webshop without hiring anyone. You pick a theme, edit pages in a visual editor, and optionally sell a handful of products. That audience is exactly why accessibility matters here: many Webador sites belong to shops and service businesses that, under the European Accessibility Act now in force, are increasingly expected to be usable by disabled customers, and a small business is the least equipped to absorb a complaint. The good news is that Webador's editor keeps things simple enough that the common problems are few and fixable without code: images published without alt text, theme color combinations that put pale text on pale backgrounds, headings chosen for size instead of order, links labeled 'read more', and webshop product pages where the only description of an item is the photo. This checklist walks through each of those, with fixes you can make directly in the Webador editor so your site works for keyboard users, screen reader users, and the growing number of older customers who simply need readable text and clear structure.
Common Accessibility Issues
Webador's image blocks and webshop product photos publish without alternative text unless you add it, and nothing in the editor forces the step. Screen reader users hear silence or a file name where sighted visitors see your storefront, your team, or the product they are about to buy -- and on a webshop, a product with no described image is a product a blind customer cannot evaluate or purchase.
In the Webador editor, select each image and fill in the alt text field with a short description of what the image shows and, for products, what matters about it ('Blue enamel camping mug, 350ml'). Leave alt text empty only for purely decorative images. After publishing, run the page through WAVE to catch any images -- especially webshop photos -- that slipped through without a description.
Several Webador themes ship with light gray body text, pale headings, or brand-tinted buttons whose label color falls below the 4.5:1 contrast ratio. It looks clean on a designer's monitor but becomes unreadable for the older and low-vision customers many small businesses actually serve, and text placed over hero photos is worse still.
In the design/style settings, darken body text and heading colors until they clearly pass 4.5:1 against their background, and check button label colors too. For any text sitting on a photo, add a dark overlay or move the text onto a solid band. Verify the exact color values with the WebAIM Contrast Checker rather than trusting how it looks on your screen.
The Webador text editor lets you mark any line as a heading, and it is tempting to pick H1 or H3 because of how big it looks. That produces pages with several H1s or levels that skip from H1 to H4. Screen reader users navigate by moving between headings, so a scrambled outline turns an otherwise simple page into a confusing pile of sections with no clear order.
Give each page one H1 -- its main title -- then use H2 for major sections and H3 for sub-points, in order, without skipping levels. When a correctly leveled heading looks too big or small, change its font size in the style settings instead of switching to a different heading level. Confirm the outline reads sensibly using the free HeadingsMap browser extension.
Webador pages and blog posts frequently use 'read more', 'click here', or 'this page' as link text. Screen reader users often bring up a list of every link to navigate the page; a column of identical 'read more' links gives them no way to tell your contact page from your product page or your opening hours.
Rewrite link text to describe its destination -- 'Read our summer opening hours' or 'View the blue camping mug' -- so each link makes sense on its own. This is a pure editing habit with no downside: it helps every visitor scan the page and improves how search engines understand your links, on top of fixing the accessibility problem.
On Webador webshops and contact forms, fields sometimes rely on faint placeholder text or an unclear label, and required fields or errors may be signaled by color alone. Customers using screen readers or magnification can lose track of which field is which, and a colorblind customer may not see which field an error refers to -- directly costing you sales at checkout.
Ensure every form and checkout field has a visible, persistent label (not just placeholder text), mark required fields with the word 'required' rather than only an asterisk or color, and make sure any error message names the field and appears as text next to it. Test the whole checkout with the keyboard alone (Tab and Enter) to confirm a customer can complete a purchase without a mouse.
Webador-Specific Tips
- If you run a Webador webshop and sell to customers in the EU, treat accessibility as an European Accessibility Act obligation, not an optional extra -- product images, descriptions, and checkout are the highest-risk areas.
- Make fixes in the Webador editor and then re-check the live URL with WAVE; the editor preview does not reveal alt-text gaps or true contrast on the published page.
- Prefer describing information in real text over baking it into images -- prices, opening hours, and product details trapped inside a graphic are invisible to screen readers and to search engines.
- Publish a short accessibility statement page (Webador makes adding a page easy) with a contact email so customers who hit a barrier can reach you; it shows good faith and gives you early warning of real problems.
Recommended Tools
WAVE
Free scanner that flags missing alt text, contrast failures, and empty links on your published Webador pages and product listings.
WebAIM Contrast Checker
Check your Webador theme's text, heading, and button colors against the 4.5:1 ratio before rolling a palette out across the site.
HeadingsMap
Browser extension that shows your page's heading outline so you can spot multiple-H1 and skipped-level problems the visual editor creates.
Further Reading
Other CMS Checklists
Get our free accessibility toolkit
We're building a simple accessibility checker for non-developers. Join the waitlist for early access and a free EAA compliance checklist.
No spam. Unsubscribe anytime.