1. Our commitment
Churches serve everyone, and the software a church runs on should not decide who can take part. We want a member using a screen reader to read a sermon, a volunteer navigating by keyboard to sign up to serve, and someone with low vision to give — without help and without asking.
This page says plainly how far we have got. It names the places we fall short, because a statement that only lists successes is not useful to the person who has just hit a barrier.
2. The standard we measure against
We assess OnChurch against WCAG 2.2, Level AA — the Web Content Accessibility Guidelines published by the W3C. It is the standard most commonly referenced in US accessibility requirements and in school and public-sector procurement.
Current status: partially conformant. Partially conformant means most of the standard is met, and some parts are not. The specific gaps are in section 5.
3. How we tested
Last assessed 6 August 2026, covering the public church websites, the member app, the sign-in flow, the marketing site, the church dashboard, the school module and the internal back office.
- Automated testing with axe-core against every screen, with real content rather than empty states.
- Keyboard-only testing — every screen navigated with no mouse, checking that every control can be reached, used and escaped, and that focus is always visible.
- Assistive-technology semantics — reading the accessibility tree each screen exposes, to check what a screen reader would actually announce.
- Contrast measured from rendered pixels, not from the stylesheet, so what we report is what is on screen.
- Zoom and reflow at 200% and at a 320-pixel viewport.
4. What we fixed in this assessment
| Area | Before | After |
|---|---|---|
| Contrast failures, church dashboard | 245 | 48 |
| Contrast failures, back office | 555 | 1 |
| Screens with no main landmark | 55 of 56 | 0 |
| Content regions outside any landmark | 143 | 0 |
We also added text alternatives to images on the public church sites and the member app, gave a name to form controls that had none, restored the ability to pinch-zoom in the member app, added skip links, corrected heading structure, and made previously mouse-only controls reachable by keyboard.
5. What still falls short
These are known, and listed deliberately. If one of them is what stands between you and using OnChurch, please tell us — it moves up the list.
Focus indicator on the sign-in field
The highlight around the sign-in field uses our brand colour, which measures 1.71:1 against the white card. WCAG 2.2 asks for 3:1. We strengthened the surrounding glow to recover what we could without changing the colour. This is a deliberate choice we have recorded rather than left unnoticed, and we will revisit it. (1.4.11 Non-text Contrast)
Small coloured text in the church dashboard
48 instances of low-contrast text remain, mostly small labels in muted colours, and initials shown on colour-coded avatars where the colour is generated from a person's name. The avatar case needs a palette change rather than an instance-by-instance fix. (1.4.3 Contrast Minimum)
Text over photographs a church has uploaded
Church websites place a headline over a photo the church chooses. We darken the image behind the text enough that a headline stays readable even over a bright photo, but a church controls its own imagery and some combinations may still be hard to read. If your church's site has this problem, contact us and we will help. (1.4.3)
The website builder's device preview toggle
The desktop/mobile switch in the website editor is announced incorrectly to assistive technology. It is usable, but its role is wrong. (4.1.2 Name, Role, Value)
The school module
Fixes to the school admissions board have been written but not yet verified with a keyboard against a live school account. We will not claim it conforms until we have tested it. (2.1.1 Keyboard)
Uncaptioned photos in event galleries
Where a church uploads an event photo without a caption, we have no text to offer a screen reader. We are changing the upload flow to ask for one.
6. Known limitations we do not control
OnChurch lets each church write its own website content, upload its own images and choose its own wording. We can make the template accessible; we cannot guarantee that every church fills it in accessibly. We give churches alt-text fields, readable defaults and contrast protection, and we are adding guidance in the editor itself.
Payment pages are hosted by Stripe and follow Stripe's own accessibility practices.
7. Telling us about a barrier
If any part of OnChurch is difficult or impossible for you to use, we want to know — whether you are a church administrator, a member, or someone visiting a church's website.
Email support@myonchurch.com with the page or screen, what you were trying to do, and the assistive technology you use if any. We aim to reply within five business days and to tell you what we can do and by when.
If you need information from OnChurch in a different format, ask and we will provide it.
8. Scope of this statement
This statement covers www.myonchurch.com, the church websites we host, the OnChurch member app for iOS, and the church and school dashboards.
It is an engineering self-assessment against WCAG 2.2 Level AA, based on the testing described in section 3. It is not a legal opinion, and it is not a certification by a third party. It does not by itself establish compliance with the Americans with Disabilities Act, Section 508, or any other law.
Last reviewed 6 August 2026. We reassess when we ship significant changes.