A little less friction.
Planning tools should be understandable and usable in more than one way.
Built-in support
The plugin uses semantic headings, labelled inputs, native buttons, keyboard-operable menus, visible focus outlines and text-based results. Required fields are identified in text. The small-screen layout stacks form and result panels, and tool status messages are announced through a live region. Content does not depend on animation or colour alone.
Keyboard navigation
Use Tab and Shift+Tab to move between links and controls. Use Enter or Space to activate buttons, menu toggles and FAQ summaries; use the normal controls for your browser’s date and time fields. The first focusable link skips to the main content. When a result is built, focus moves to its heading. Validation errors appear as text and focus moves to the relevant field or error message.
Reading and display
You can enlarge text or zoom the page using your browser. Forms use a single column on narrow screens and long entered text wraps within the result. User text has automatic text direction to support different writing systems. System fonts are used without external font requests. Browser and operating-system support for date pickers and complex scripts varies.
Alternatives to one format
Generated results remain readable on the page. You can download plain UTF-8 text if a print layout or calendar file is unsuitable. Print / Save PDF opens the browser’s dialog; tagged-PDF quality, reading order and font handling depend on the browser and are not guaranteed. A saved text file can be opened in an application that suits you.
Known limitations and scope
JavaScript is needed to generate a result because inputs are not submitted to a server. Calendar importing and notification controls belong to third-party software. This page describes design measures, not a claim of a completed formal accessibility audit or universal compatibility with every assistive technology. Other themes, plugins or browser extensions may introduce separate barriers.
Report a barrier
Use the Contact page to identify the page and control that caused a problem, what you were trying to do and, if helpful, your browser or assistive technology. Request an alternative explanation or format if needed. Please use fictional examples and do not send personal prayer content.
Contact the operator ↗