Accessibility
We aim for WCAG 2.2 at level AA on every page, on a phone and on a desktop.
What that means here
- The same aim holds for a church’s public page and the pages under it (its blog, its calendar, a post, an event, a month and Report): the heart and Share are named for a screen reader, and the months open without script.
- Every page works with a keyboard alone, and the focus is always visible.
- Text meets the contrast the standard asks for, resizes with the browser, and is never cut off by its box.
- On a phone, every control is at least 44 pixels tall, and a page never scrolls sideways.
- Reels carry their captions burned in, so they read with the sound off.
- Motion is a small lift as sections come into view, the landing’s reel, which has a pause button, and one short glide of a frame; none of it starts on its own when your device asks for reduced motion.
- Pictures that carry meaning have text alternatives; the ones that are decoration are marked so a screen reader skips them.
- Where a QR code is offered for the authenticator app, the key it encodes is also given as text.
How we test
Before a release, every page, including a church’s public page and the pages under it, is checked with an automated accessibility test and opened at a phone size and a desktop size and checked for sideways scrolling, targets under 44 pixels, clipped text, text under 12 pixels, and contrast under 4.5 to 1 (3 to 1 for large text), and the results are kept with the release.
Known gaps
The pictures and the reels are the church’s content, and their alternative text is what the church writes. The PDF and Word exports of a sermon’s understanding have not yet been tested with a screen reader.
Tell us
If something on the site is hard to use, write to support@sundayeverywhere.com or use the contact page, and say which page and what happened. We answer within five working days and fix what we can.