Making a website built on a page builder accessible

Many Manitoba organizations run their websites on a hosted website builder or a content management system with a theme, such as WordPress, Wix, Squarespace or Shopify. These platforms make it possible to publish and update a site without writing code. They can also be used to build accessible websites. Whether a particular site meets WCAG 2.1 Level AA depends far more on the theme, the add-ons and the content than on the platform itself.

This article separates what an owner can usually fix in the editor from what usually needs a developer.

What the platform provides, and what it does not

It helps to think of a builder site in three layers:

• The platform, which provides the editor and the underlying system.
• The theme or template, which controls the layout, menus, header, footer, colours, fonts and many interactive elements.
• The content: your text, images, headings, links, documents and videos.

Accessibility problems can occur in any layer. Content problems are the most common, and they are also the ones an owner can fix. Theme and widget problems usually require changes to code or settings that the editor does not expose.

What owners can usually fix themselves

Alternative text for images

Every platform provides a field for image alternative text. Images that convey information need a short description of that information (1.1.1 Non-text Content). A photo of your storefront might be "Front entrance of our store, with a ramp to the door". Purely decorative images, such as background textures, should be marked as decorative or left with empty alternative text, depending on what the platform offers. Avoid file names such as "IMG_4021".

Headings

Choose heading levels to reflect the outline of the page, not for their size. Use one main heading per page, then section headings in order without skipping levels. Our article on headings and page structure explains common mistakes.

Link text

Replace "Click here" and "Read more" with text that says where the link goes, such as "View our fall class schedule". Edit button labels the same way.

Colours

Most builders let you set text, link and button colours site-wide. Check them against the 4.5:1 ratio for normal text and 3:1 for large text and interface components. Our article on colour contrast shows how to adjust a brand colour slightly so it passes.

Captions and transcripts

If you upload video, add a reviewed caption file, and place a transcript on the page. See our article on video and captions.

Page titles and language

Page title fields are usually under the page's settings or search settings. Give each page a unique, descriptive title. The site language is usually a site-wide setting; make sure it matches the language of your content.

Documents and forms

Many builders include a form tool. Make sure every field has a visible label, not just placeholder text, and that required fields are identified in words. Check whether linked PDFs are accessible, or provide the same information as a web page.

What usually needs code

Some problems sit in parts of the site that the editor does not let you change directly. These typically need a developer who can edit the theme's templates, add custom CSS or JavaScript, or replace a component.

• Theme templates. Missing landmarks, headings built into the header or footer at the wrong level, or a missing "skip to main content" link.
• Navigation menus. Drop-down menus that open only on hover, and mobile menu buttons that cannot be reached or operated with a keyboard.
• Focus styles. Themes that remove the visible focus outline for appearance, so keyboard users cannot see where they are (2.4.7 Focus Visible). A replacement focus style can usually be added with a few lines of CSS.
• Custom widgets. Sliders, tabs, accordions, pop-ups and galleries that are not keyboard operable, do not announce their state, or move without a pause control.
• Reflow and zoom. Layouts that overlap or cut off content at 200% zoom or at a width of 320 CSS pixels.
• Form behaviour. Error messages that are not connected to their fields, or success messages that screen readers do not announce.
• Add-ons and embedded tools. Booking, chat and payment tools supplied by other companies. Our article on third-party tools covers these.

Hosted builders differ in how much code access they allow. Some permit custom code throughout; others restrict it to certain areas or plans. Where a problem cannot be fixed directly, it may be possible to choose a different template section, replace a widget with a simpler one, or change the theme. These are decisions best made with a clear list of what is actually failing.

Avoid overlay plugins

Overlay plugins and widgets are add-ons that place an accessibility icon or toolbar on a site, often with claims of automatic compliance. They are widely available for website builders and are easy to install.

We do not recommend them. An overlay does not change the underlying code of your theme and content, so problems such as unlabelled form fields, keyboard-inaccessible menus and missing captions generally remain. Many people who use assistive technology already have their own settings and tools, and an overlay can interfere with them. Installing one can also give an organization the false impression that the work is done.

The reliable approach is to fix the site itself. That is how we work: we repair the theme and content directly and never use overlays.

Where to start

1. Work through the content fixes above on your most visited pages and your contact or booking page.
2. Run the five-minute keyboard test to find menu, focus and widget problems.
3. Use our checklist to note anything else you find.
4. Have a full audit done to identify the issues that need code, and to confirm what your own fixes have resolved.

Talk to us

We work with sites built on common platforms and themes, and our repairs keep your design and your ability to edit the site in the builder. Read about our method and services, or contact us to discuss your site.

Last reviewed October 2026.