Skip to content
Back to Eastodox

Accessibility

How Eastodox is built to be read by everyone, what is known to fall short, and how to tell us.

Last updated

The commitment

Eastodox aims to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA on the website, and the equivalent platform guidance on iOS and Android. A prayer book that a partially sighted reader cannot use has failed at the one thing it exists for.

This statement applies to the website at eastodox.com, the prayer application behind sign-in, and the iOS and Android applications.

What is built in

  • Every colour pairing used for text meets the AA contrast ratio. The brand gold is 8.06:1 on the dark ground; light mode substitutes a darker gold at 5.65:1 on white rather than carrying the brand colour into a context where it fails.
  • Colour is never the only signal. The fasting indicator states the rule in words beside the dot, and permitted and forbidden foods carry an icon as well as a colour.
  • Text size for prayers is adjustable independently of the interface, so the words can be enlarged without the navigation growing with them.
  • Every control can be reached and operated from the keyboard, and every hover state has a matching keyboard focus state with a visible ring.
  • Motion is reduced to a plain fade when the operating system asks for reduced motion, including the loading skeletons.
  • Rubric marks, the cross, the bow and the prostration, are announced to a screen reader as the gesture they call for, not as an unlabelled shape.
  • Pages have a single logical heading structure, landmarks for navigation and content, and descriptive titles, so a screen-reader user can move through them by structure.
  • The cookie notice does not trap focus or cover the page; somebody who wants to read before answering can.
  • The website works at phone width without sideways scrolling, and the print stylesheet produces a clean copy of any prayer or of these documents.

Known gaps

  • Greek and Church Slavonic titles are presented without per-language markup, so a screen reader will read them with English pronunciation. Correcting this needs language tagging that has not been added yet.

How this is checked

Contrast ratios are measured against the design tokens rather than estimated, and the public pages are checked with Lighthouse on each release. Keyboard and screen-reader behaviour is checked by hand on the website and in the applications. We would rather hear about a problem from a reader than find it ourselves late; the address below is the fastest route.

Telling us about a problem

If something here is hard to use, please write to admin@tenutech.com and say what you were trying to do, on which device, and with which assistive technology if any. We treat access problems as faults rather than as requests, and we will reply within a reasonable time with what we have done or when we expect to do it.

Questions about this document, or about anything it describes, can be sent to admin@tenutech.com.