We build this site so church media people can actually use it, including the ones using a screen reader, a keyboard, magnification, or captions. This page says what we aim for, what we know is not there yet, and how to tell us when we have got it wrong.
What we aim for
We target WCAG 2.1 Level AA. That is the standard most commonly used to judge whether a website is accessible, and it is the one we measure ourselves against rather than a looser internal idea of "good enough".
Concretely, across the site we hold ourselves to:
- a skip link, so a keyboard user does not have to tab through the whole menu on every page;
- real landmarks — header, navigation, main, footer — so a screen reader can jump straight to the content;
- a visible focus outline on everything you can reach with a keyboard;
- a label on every form field, and alternative text on every image that carries meaning;
- one
h1per page and headings that step down in order, so the page has a real outline; - text contrast that meets the 4.5:1 ratio at body size, in both our dark and light surfaces;
- no autoplaying audio or video, and reduced-motion support for anyone who has asked their device to limit animation.
What we know is not there yet
We would rather list this than claim we are finished.
- Captions on training videos. Our lessons are hosted on YouTube, which generates automatic captions. Automatic captions are not the same as accurate ones, particularly for names and ministry vocabulary. We are working through the library adding corrected captions, and we are not done.
- Downloadable PDFs. Our worksheets and checklists are designed to be printed. They are not yet tagged for screen readers. If you need one in an accessible format, ask and we will send you a plain-text or Word version.
- Third-party content. The embedded YouTube player and the Shopify checkout are built by other companies. We have chosen the more accessible options where we get a choice, but we do not control their code.
Tell us when something does not work
If any part of this site blocks you, we want to know, and we will fix it. You do not need to know the technical term for the problem — "I cannot get past the sign-in with my keyboard" is a perfect bug report.
Email contact@didiomedia.org with the page address and what happened. A person reads it. We aim to reply within five business days, and if the fix will take longer than that, we will tell you what we are doing and find you another way to get the same material in the meantime.
You can also write to us:
DiDio Media
P.O. Box 123
Albemarle, North Carolina 28001
Getting the material another way
If something on this site is not usable for you, that is not the end of it. We will get you the content another way — a transcript, a plain-text version of a worksheet, or a phone or video call to walk you through the same material. Ask, and we will sort it out. There is no charge for this and you do not need to explain why you need it.
How this page is kept honest
We re-test the site against the checklist above when we ship significant changes, using both automated checks and a keyboard-only pass. This statement is updated when what we know changes — including when we find something new that is broken.
Last reviewed: 16 August 2026.