1. Our Commitment
PreacherDesk seeks to provide equitable access to public information, account functions, sermon preparation, and exported materials. Accessibility is treated as an ongoing part of design, development, testing, and support.
2. Accessibility Goal
PreacherDesk uses the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA as an ongoing reference for improving the website and application.
This statement is not a formal claim that every page, feature, third-party service, or generated export has been independently audited or fully conforms to WCAG 2.2 AA.
3. Current Accessibility Features
Current design and development practices include:
- semantic page headings and clearly identified navigation;
- keyboard-accessible links, buttons, menus, and form controls;
- visible focus indicators for interactive elements;
- text labels and instructions for forms;
- responsive layouts that reflow across screen sizes;
- skip links on public policy and information pages;
- reduced-motion support when requested by the device; and
- text-based error and status messages.
4. Known Limitations
Some complex sermon-editor interactions, older pages, and generated Word, PDF, or PowerPoint files may require further accessibility improvement. Generated or user-provided content may also contain inaccessible structure, wording, images, colors, or reading order.
Users should review exported materials before distribution and add or correct headings, reading order, alternative text, color contrast, document language, and other accessibility information appropriate to the intended audience.
5. Third-Party Services
Stripe-hosted checkout and billing pages, browser features, operating systems, document viewers, and other independently operated services have their own accessibility practices. PreacherDesk does not control those interfaces.
6. Requesting Assistance
If a feature or document is difficult to use, contact PreacherDesk and describe the information or task you need. We will make a reasonable effort to provide the information in another usable format or assist with the requested task.
7. Reporting an Accessibility Barrier
Submit accessibility feedback through the Contact & Support page. If possible, include:
- the page address or feature name;
- a description of the problem;
- the browser, device, and assistive technology used; and
- your preferred method of response.
Do not include passwords, payment-card information, or confidential pastoral information in the support message.
8. Ongoing Review
PreacherDesk will continue reviewing accessibility as the service develops and will update this statement when material practices or known limitations change.