Skip to the content
Documentation
Help Start
Reading in:
  • German: 9,110 of 9,110 pages
About the help in other languages
All help pages

Accessibility upkeep

How a site owner keeps an Exponential site usable for people with disabilities after launch - the split between template work and content work, the shipped features that help, a quarterly spot check, handling visitors'…

Download as PDF

Address: https://doc.exponential.earth/exphelp/viewer/help/customers/day-to-day/accessibility-upkeep.md

On this page

Accessibility upkeep

This page is for the owner who is responsible for the site being usable by everyone, including people who use screen readers, keyboards, magnification or voice control. Accessibility is built into templates and stylesheets by the site builder and kept up by editors (Accessibility for site builders). The reference most legislation points to is the W3C's Web Content Accessibility Guidelines (WCAG). This page is not legal advice about which rules apply to you.

Contents

  1. Two kinds of work
  2. What Exponential helps with
  3. A quarterly spot check
  4. When a visitor reports a barrier
  5. After design changes

Two kinds of work

Template work (once, for every page)Content work (editors, page by page)
page language, landmarks, skip linkalternative texts for images
one main heading per page, visible focusheadings used as headings, in order
contrast of text and buttonslink texts that say where they lead
zoom to 200% and phone widthstables with header rows, not for layout
accessible forms and error messagesplain language, short paragraphs

Source: Accessibility for site builders. Problems in the left column go to your partner; problems in the right column are fixed by your team, using the Accessibility checklist for editors.

What Exponential helps with

  • Image fields can require an alternative text; ask your administrator to switch it on for your image classes (The content model and editing).
  • The online editor writes structured rich text (headings, lists, tables) rather than free HTML.
  • Right-to-left content is marked with its language and direction (Right-to-left sites).
  • The administration itself follows an accessibility design, so editors with disabilities can work too (admin4 design).
  • The content checks find broken relations and missing files (The content checks).

A quarterly spot check

Do not test every page; test one page of every kind (Testing your site's accessibility):

  1. Pick the front page, one landing page, one article, one list, the search results and every form.
  2. Run an automatic checker (a browser extension) on each. Note errors.
  3. Put the mouse away and use Tab, Enter and Escape: can you reach and use everything, and do you always see where you are?
  4. Zoom the browser to 200%: nothing cut off, no sideways scrolling.
  5. Read five recent articles for the content rules: alternative texts, headings, link texts.
  6. Sort what you found into template work (to the partner) and content work (to the editors).

Keep the findings in a table such as the one on Testing your site's accessibility.

When a visitor reports a barrier

Give visitors a way to report barriers, for example a contact form, and answer them (Testing your site's accessibility).

StepWho
Thank the visitor and offer the information another way at once (phone, e-mail, a plain text version)whoever reads the form
Find the page and the problem; decide template or contenteditor-in-chief
Fix content problems the same weekeditors
Send template problems to the partner with the page address, what happens and the visitor's tool if knownowner
Tell the visitor when it is fixedwhoever answered first

After design changes

  • Ask your partner to run the automatic checks after every design change, as part of their release checks (Testing your site's accessibility).
  • Check the new pages yourself with the keyboard and at 200% zoom before you accept them (Quality gates and acceptance).
  • Make sure every new color scheme or dark mode keeps enough contrast.

Become an Exponential Partner

Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.

Something wrong on this page? Report an error

Documentation license

This documentation is free documentation, licensed under the GNU Free Documentation License 1.3 or later.

Exponential Copyright © 1998-2026 Exponential Foundation and 7x