Accessibility on SiteGround
SiteGround is best known for managed WordPress and WooCommerce hosting. On a WordPress site, accessibility comes down to the theme, the page builder and every plugin that adds markup to the page, not the server it runs on.
Hosting features can still affect what visitors get. Optimization settings that combine, delay or defer scripts can change how menus, sliders and pop-ups behave, so it is worth rescanning after you change them.
Common Accessibility Issues on SiteGround Sites
Page builder markup
Page builders often produce deeply nested layouts and text styled to look like headings, which leaves screen reader users without a usable page structure.
WooCommerce product and cart pages
Product galleries, quantity selectors and mini-carts are common sources of keyboard traps and unlabeled buttons.
Plugin forms
Contact, newsletter and booking forms from plugins frequently miss field labels or fail to announce errors.
Delayed or combined scripts
When scripts are delayed for speed, menus and dialogs can load late or lose their keyboard handling. Test them with a keyboard after changing optimization settings.
Low-contrast theme colors
Many themes ship light gray body text and pale buttons that fail WCAG contrast.
How AccessBell Scans Your SiteGround Site
- Enter any public page. Paste the address of a page on your SiteGround site into the scanner above. There is nothing to install on your hosting account: no plugin, no code snippet and no login.
- We load it in a real browser. AccessBell opens the page in headless Chrome and runs its scripts, so it tests what your visitors actually see, including content added by your theme, builder or plugins.
- We run the WCAG rules. The open-source axe-core engine checks the page against the standard you choose, and every result is mapped to the WCAG success criteria it affects.
- You get a report in seconds. Each issue comes with the failing HTML and how to fix it. Our methodology explains exactly what runs and what still needs a person.
What's Included in Every Scan
- 63 automated rules for WCAG 2.2 Level AA, or presets for WCAG 2.1 AA, the ADA, Section 508 and EN 301 549
- Every issue ranked by severity, from critical to minor
- The WCAG success criteria each issue fails, which you can look up in our WCAG library
- The failing HTML, so you can find the element in your site editor or code
- How to fix each issue, with a link to the rule's full documentation
- A list of checks that need a person to review, so nothing is missed
- Filters by WCAG version, level, principle, success criterion and severity
The free scan checks one page at a time. AccessBell Pro scans up to 500 pages per domain every day and alerts you when something changes.
How to Fix What the Scan Finds
- Fix issues in the theme and reusable blocks first, then work through plugins one by one. Replace plugins that cannot be fixed.
- Rescan after theme, plugin and optimization changes. A passing scan today does not mean the next update will not break something.
- Run a free scan above on your homepage and a few key pages, fix issues starting with critical and serious, then rescan to confirm.
- For ongoing protection, AccessBell Pro monitors up to 500 URLs per domain every day and alerts you when a theme, app or plugin update introduces a new issue.
Related Guides
SiteGround Accessibility — Frequently Asked Questions
Is SiteGround hosting accessible?
Hosting does not make a website accessible or inaccessible. On SiteGround, as anywhere, the theme, plugins and content decide the result.
Can AccessBell scan a WordPress site on SiteGround?
Yes. It loads your live page in a real Chrome browser and tests what WordPress, your theme and your plugins actually render.
Do caching and speed settings affect accessibility?
They can. Settings that delay or combine JavaScript can change how interactive parts of the page behave. Scan and test with a keyboard after changing them.
Sources
This page explains general accessibility patterns for SiteGround sites and is not legal advice. AccessBell is not affiliated with SiteGround. See our disclaimer.