Home/Legal/Accessibility Statement

Grace Unworthy Ministries, LLC


Accessibility Statement


Effective Date: July 26, 2026

Last Updated: July 26, 2026

Document URL: https://graceunworthy.com/legal/accessibility

Download PDF generates a letter-size Times document with page numbers. Print uses your browser's print dialog.

1. Our Commitment

Grace Unworthy Ministries, LLC ("we," "our," or "us") wants everyone to be able to use what we build. This statement covers our web properties, applications, and services, including The Story Haven mobile application. This document applies to the properties listed in our Covered Properties notice, which is incorporated by reference.

We are committed to continually improving the accessibility of our websites and applications so that people with disabilities can perceive, understand, navigate, and interact with our content. We treat accessibility as ongoing work rather than a finished state, and we take reported barriers seriously.

Plain-language summary

We are working toward WCAG 2.2 Level AA as a goal. We have not been audited or certified against it, and we know parts of our sites and app fall short today. If you hit a barrier, email [email protected] and we will work with you on it — we aim to acknowledge within five business days.

2. Standard We Are Working Toward

We use the Web Content Accessibility Guidelines (WCAG) 2.2 published by the World Wide Web Consortium as our reference standard, and we aim for Level AA conformance. WCAG explains how to make web content more accessible to people with a wide range of disabilities, including visual, auditory, physical, speech, cognitive, language, learning, and neurological disabilities.

This is a goal, not a claim of conformance

We do not claim that our websites or applications currently conform to WCAG 2.2 Level AA, and we do not hold an accessibility certification, a completed third-party audit, or a published Accessibility Conformance Report (VPAT). We are a small organization and would rather state our actual position than imply a level of assurance we cannot back up. Where we describe practices below, we are describing what we work toward and test informally — not a verified conformance result.

3. Measures We Take

In building and maintaining our properties, we work to:

  • Use semantic HTML and native controls, so that headings, lists, landmarks, buttons, and form fields are conveyed correctly to assistive technology
  • Provide text alternatives for meaningful images, and mark decorative images so they are skipped by screen readers
  • Support keyboard navigation for interactive elements, including menus, dialogs, and forms, with a visible focus indicator
  • Associate form fields with labels and present error messages in text rather than by color alone
  • Aim for sufficient color contrast for text and essential interface elements
  • Design layouts that reflow and remain usable when text is enlarged or the viewport is small
  • Respect reduced-motion preferences where animation is used
  • Support native accessibility features on mobile, including screen readers, dynamic text sizing, and system contrast settings
  • Consider accessibility when reviewing new features and when selecting third-party components

4. Known Limitations

Despite our efforts, some parts of our properties are not yet fully accessible. We would rather list the gaps we know about than leave you to discover them:

  • Third-party embeds. Embedded video and audio players, payment and checkout components, maps, social feeds, forms, and scheduling widgets are supplied by other companies. Their keyboard support, labeling, and contrast are outside our direct control, and some fall short of our goal.
  • User-generated content. Posts, comments, images, audio, and files uploaded by community members on The Story Haven may lack alternative text, captions, or clear structure. We encourage members to add descriptions, but we do not author this content and cannot guarantee its accessibility.
  • Media captions and transcripts. Not all of our video and audio has human-verified captions or transcripts. Automated transcription is used in places and can contain errors, particularly with names, Scripture references, and theological terms.
  • Older pages and legacy content. Some archived blog posts, older course material, and downloadable documents (including PDFs) predate our current practices and may have unstructured headings, missing alternative text, or untagged content.
  • Complex interactive components. Rich editors, drag-and-drop ordering, charts, and some administrative interfaces may not be fully operable by keyboard or fully described to screen readers.
  • Mobile application. The Story Haven app is under active development, and some screens have incomplete accessibility labels or focus order.

If you encounter a barrier that is not listed here, please tell us. Reports directly shape what we prioritize.

5. Compatibility

Our web properties are built to work with current versions of major browsers — Chrome, Firefox, Safari, and Edge — on desktop and mobile, used together with the assistive technology available on your platform, such as VoiceOver on macOS and iOS, TalkBack on Android, NVDA and JAWS on Windows, browser zoom and text scaling, operating system contrast and reduced-motion settings, and speech recognition software.

Compatibility depends on the combination of browser, operating system, and assistive technology, and we have not tested every combination. Older browsers, unsupported platforms, and browsers with scripting disabled may not render our sites correctly. Use of The Story Haven mobile app is additionally governed by our End User License Agreement (EULA) and the accessibility features provided by your device platform.

6. Feedback: Report an Accessibility Barrier

We want to hear from you

Email [email protected] with "Accessibility" in the subject line. There is no form to fill out and no account required.

To help us reproduce and fix the problem quickly, please include whatever of the following you can:

  • The URL of the page — or, for the mobile app, the screen name and what you did to get there
  • A description of the barrier — what you were trying to do, what happened, and what you expected instead
  • The assistive technology you were using, including its name and version — for example VoiceOver on iOS 18, NVDA on Windows, or browser zoom at 200%
  • Your browser and operating system, or your device model and app version
  • A screenshot, screen recording, or copy of any error message, if you are able to share one
  • How you would like us to reach you if we need to follow up

6.1 How we respond

  • Acknowledgement: we aim to acknowledge accessibility reports within five (5) business days
  • Assessment: we investigate, try to reproduce the barrier, and tell you what we found and whether we can fix it
  • Remediation: we prioritize fixes by how severely they block access, and we tell you when a fix is not straightforward or depends on a third-party provider
  • Alternative access: where a fix will take time, we will work with you to provide the information or complete the transaction another way — for example by email, by phone arrangement, or by sending content in an accessible format

These are our service aims, not contractual guarantees. If you have not heard back from us within a reasonable time, write again and reference your original message — we would rather receive a duplicate than miss a report.

7. Ongoing Effort

Accessibility improvements are part of our normal development work rather than a one-time project. We review reported barriers, address issues as we encounter them in new and existing features, and consider accessibility when choosing third-party components. As our resources allow, we intend to expand testing with assistive technology and to improve captioning and transcript quality for our media.

We will update this statement as our practices change, and we will keep it honest about where we stand rather than describing an aspiration as an achievement.

8. Contact

Accessibility feedback, requests for content in an alternative format, and questions about this statement all go to our support team. For the broader agreement governing use of our services, see our Terms of Service.

Accessibility Feedback

General Support

Email: [email protected]

Mailing Address:
Grace Unworthy Ministries, LLC
5753 Highway 85 N PMB 3496
Crestview, FL 32536

End of Accessibility Statement

Grace Unworthy Ministries, LLC

https://graceunworthy.com/legal/accessibility