Accessibility

Accessibility, stated honestly.

Last updated · October 12, 2026

This is what Church Grid builds to, what is actually checked on every change, and what has not been verified. A church should be able to read this page and know exactly which of those three it is looking at. For accessibility questions, contact info@churchgrid.app.

Clause 01

The standard we build to

WCAG 2.2 Level AA is the floor for the Church Grid product and this marketing site alike. Text reads at 4.5:1 or better against its surface in both light and dark themes, control edges and other meaningful non-text at 3:1 against the worst-case surface they can sit on, and focus is a single visible colour at 3:1 on every interactive element. Colour is never the only thing carrying a meaning.

Clause 02

What is checked automatically

Two gates run before any change can deploy. A contrast check resolves every colour role to a concrete value per theme and fails the build on any pair below its floor. A browser check completes a gift, an event registration and a child check-in with the keyboard alone, including a dialog that must hold and then return focus, and fails the build if any of those screens scrolls sideways or has no page heading at 320 pixels wide. A failure blocks the deploy rather than raising a warning.

Clause 03

What we have not verified

Church Grid has not been audited by an independent accessibility assessor, and we do not claim conformance under Ontario’s AODA, the ACA, the European Accessibility Act, or any other jurisdiction’s regulation. Automated checks cannot confirm reading and focus order, full keyboard journeys, reduced-motion behaviour, or screen-reader announcements end to end; those still depend on manual review, which we have not completed across every screen. We will state a verified conformance level here when one has actually been measured, and not before.

Clause 04

Known exceptions

Disabled controls are the one deliberate departure from the 4.5:1 text floor. WCAG 1.4.3 exempts inactive controls, and lifting their text to full contrast would make a disabled control read as an enabled one, which is the more harmful outcome. Disabled text is held to 3:1 by policy instead.

Clause 05

Telling us about a barrier

If something on Church Grid blocked you, we want the report. Send the page or screen, what you were trying to do, and what stopped you — plus the assistive technology and browser if you were using one. A specific report is far more actionable than a general one, and reported barriers are treated as defects, not feature requests.

Clause 06

Keeping this page honest

This statement describes the state of the product on the date shown above, not an aspiration. It is updated when the floor changes, when a gate is added or removed, or when an audit gives us something verified to report.

Contact

Questions

Questions about accessibility? Email info@churchgrid.app.