Accessibility
Planning should feel approachable.
The site is designed for readable text, clear controls and more than one way to navigate. Accessibility is an ongoing practice, not a blanket certification.
Navigation and controls
Pages use headings, landmarks and a skip link. Inputs have visible labels, required fields are marked in words, and buttons have text descriptions. Links, tool controls and FAQ disclosure elements are keyboard reachable, with visible focus outlines.
Reading and small screens
The layout reflows to a single column on smaller screens. Text is resizable through browser zoom, and content does not rely on colour alone. Dark text is used on the light palette; the accent is primarily a surface or decorative cue rather than low-contrast body text.
Results and errors
A generated result receives keyboard focus and announces completion through a status message. Validation errors are shown in text. Checklists use native checkboxes. Date inputs and print dialogs are native browser controls and may look or behave differently across devices.
Printing and motion
Results can be printed or downloaded as plain text. There is no autoplay media, flashing content or required animation. You can use your browser’s reduced-motion and zoom preferences without losing the main workflow.
Known limits
The site has not been represented as independently certified to any accessibility standard. Browser-native date controls, print dialogs and other WordPress plugins may introduce differences. Plain-text downloads are an alternative for reading or adapting a result, not a substitute for fixing a reported barrier.
Report a barrier
Use the Contact page to name the page or control, explain what happened, and share your browser and assistive technology if you wish. Do not send sensitive details. A short reproduction example helps the operator investigate.