Accessibility Statement
In plain language
- We are partially conformant with WCAG 2.1 Level AA, not fully, and we would rather say so than overstate it.
- The public pages and the forms your respondents fill in are the parts we have worked on hardest.
- Two builder features rely on drag-and-drop. Both have a keyboard-workable alternative, listed below.
- If something blocks you, email us and we will help directly while we fix it.
1. Our commitment
AdvanceForm is used to run sign-ups for events, classes, congregations and volunteer teams. The people filling in those forms are the general public: which means some of them use screen readers, some navigate only by keyboard, some need high contrast or larger text, and some need motion reduced. A sign-up form that excludes them excludes them from the event itself.
We aim to meet WCAG 2.1 Level AA. We are not fully there. This page says where we are.
2. Conformance status
AdvanceForm is partially conformant with WCAG 2.1 Level AA. "Partially conformant" means most of the service meets the standard, but some parts do not.
We have deliberately not claimed full conformance. Doing so without a complete independent audit would be a claim we could not stand behind, and it would not help anyone who then hit a barrier we had quietly known about.
3. What works today
Across the public website, the legal pages, and the published form pages your respondents use:
- Keyboard access: all interactive elements are reachable and operable by keyboard, with a visible focus indicator. A "skip to content" link is the first focusable element on every page.
- Structure: pages use real landmarks (
nav,main,footer) and a logical heading order, so screen-reader users can navigate by structure rather than reading linearly. - Contrast: text and interface colours meet the 4.5:1 ratio for body text and 3:1 for large text, in both the light and dark themes.
- Reduced motion: decorative animation, including the background gradient and reveal-on-scroll effects, is disabled when your system requests reduced motion.
- Zoom and reflow: layouts reflow to 320px width and support 200% zoom without loss of content or horizontal scrolling.
- Form labelling: form fields have programmatically associated labels; required fields are marked in text as well as visually; validation errors are described in text, not colour alone.
- Decorative content: icons and illustrative mockups are hidden from assistive technology so they do not clutter the reading experience.
- Themes: a light and a dark theme are both available, and the choice persists.
4. Known gaps
These are real, current, and stated deliberately.
4.1 The visual flow builder (drag-and-drop)
The flow builder lets you rearrange questions and branches by dragging cards. Drag-and-drop is not operable by keyboard alone and is not announced usefully by screen readers. Affects: WCAG 2.1.1 Keyboard.
4.2 The roster board (drag-and-drop)
The roster's board view assigns people to jobs by dragging between columns, with the same limitation. Affects: WCAG 2.1.1 Keyboard.
4.3 Charts and diagrams
The summary dashboard's charts and attendance heat-matrix, and the Mermaid flow diagram, convey information visually without a complete text equivalent. Underlying numbers are available in the responses table and export, but the graphics themselves are not adequately described. Affects: WCAG 1.1.1 Non-text Content.
4.4 Interior application screens not yet fully audited
The signed-in application (dashboard, editors, roster, hand-out list, admin) has had less scrutiny than the public pages. We expect further issues there and have not yet catalogued them.
4.5 Form content is authored by our customers
Question wording, option labels and form structure are written by whoever built the form. We cannot guarantee that content is accessible, see section 8.
5. Alternatives available now
Where a feature is not yet accessible, there is a route to the same outcome:
| Instead of… | Use… |
|---|---|
| Dragging cards in the visual flow builder | The List view, which builds exactly the same form, with ▲▼ buttons to reorder questions. Toggle between views at any time; both save the same result. |
| Dragging people on the roster board | The Table view of the roster, plus auto-assign and auto-balance, which fill the roster without any dragging. |
| Reading the summary charts | The responses table, and CSV or Excel export, which contain the same underlying figures as text. |
If none of these work for you, email us, see section 7. We will get you the result you need directly.
6. How we assessed this
This statement is based on a self-evaluation carried out on 7 August 2026, covering the public landing pages, the legal pages and the published form experience. It combined manual keyboard testing, inspection of markup semantics and contrast measurement against the WCAG 2.1 AA thresholds.
It has not been independently audited or certified, and the signed-in application has not been fully evaluated. We will commission an independent review as the service grows, and will update this page when we do.
7. Feedback
If you encounter a barrier, please tell us. Reports from people who actually hit the problem are the most useful thing we receive.
Email zhengda@sohsimple.sg, with the page or feature, what you were trying to do, and any assistive technology you were using.
We aim to acknowledge within 5 working days and to give you a plan or a workaround within 15 working days. If a fix will take longer, we will offer a direct alternative so you are not blocked in the meantime.
8. A note for form owners
We provide the platform; you write the questions. A few things you control that materially affect whether your respondents can complete your form:
- Write question labels that make sense read aloud on their own, without surrounding visual context.
- Do not rely on colour or emoji alone to carry meaning in a label or option.
- Keep option lists as short as the task allows, and word them distinctly.
- Explain in text why you need any sensitive detail, so people can decide before answering.
- If you have a legal duty of accessibility, many public bodies and charities do, remember it extends to the content of your form, not only to the platform hosting it.
This statement is offered in other languages for convenience; the English version governs.