Skip to content

USABLE BY MORE PEOPLE

Accessibility

Designed for clear reading, keyboard use and practical exports on small screens.

Our approach

The supplied interface uses semantic headings, labelled form controls, visible focus indicators, readable contrast and layouts that adapt to narrow screens. Information is not communicated by colour alone. A skip link moves past the main navigation. The mobile navigation button announces whether it is expanded.

Using a planner with a keyboard

Use Tab and Shift+Tab to move through links and fields. Use Enter or Space on buttons. The More menu and FAQ questions use native disclosure controls. Required inputs are identified in their labels; your browser can guide you to missing or invalid entries. Additional validation messages are announced in an alert region.

Results and updates

A status message announces when a result is ready. The generated result receives focus so keyboard and screen-reader users can move into the plan. Editing the form marks the old result as out of date and disables export until you rebuild it, reducing the risk of sharing an outdated version.

Reading and export options

You can zoom the page and use your browser’s text-size settings. The print layout removes navigation and form controls and keeps the result and method. Plain-text downloads provide a simple alternative format. PDF accessibility depends on the browser and print destination; a saved PDF is not guaranteed to be tagged for assistive technology.

Known limitations

JavaScript is required to calculate, filter tools, and export results. Native date and time controls vary by browser and assistive technology. A date is a local planning label, not a time-zone-aware calendar entry. This package has not been independently certified for conformance with an accessibility standard, and the active WordPress environment may introduce other barriers.

If you encounter a barrier

Consult the Contact page for current operator contact availability. If a verified contact is published, describe the affected page, device, browser or assistive technology and the task you could not complete. Use a fictional example instead of including private planning details.