Accessibility
Readable colours, keyboard controls, flexible layouts, and a clear way to report barriers.
Built around ordinary browser controls
The interface uses semantic headings and landmarks, labelled inputs, native buttons and selection controls, keyboard-operable links and disclosures, a skip link, visible focus outlines, and status messages for generated results or validation problems. There are no timed questions, autoplaying media, or hover-only essential controls.
Layouts reflow on narrow screens. Use browser zoom and your own text settings as needed. Result tables have a labelled scrolling region when their columns require extra space. Reduced-motion and forced-colour settings are respected. JavaScript is required for calculations and editing; a no-script message explains this limitation.
Palette and print
The requested palette uses #25343F for dark text, #BFC9D1 for secondary surfaces and decorative rules, #EAEFEF for the light canvas, and #FF9B51 for buttons and accents. Buttons use dark text on orange, not light text on orange. The footer reverses to dark background with light text. Decorative pale rules are not the only way to identify an input or communicate an error.
The optional system-colour view in the header uses your browser’s own text and background colours. It lasts for the current loaded page session. Print uses system ink and paper colours for legibility and removes navigation and form controls from a generated plan. Browser print dialogs and PDF saving have their own accessibility behaviour.
Limits and reporting
This is not a claim of complete WCAG conformance or testing with every assistive-technology combination. WordPress administration, unrelated plugins, external email applications, file handling, and operating-system controls are outside the tool interface. Browser restrictions can also prevent optional storage.
To report a barrier, use Contact and include the tool or page, your device and browser, assistive technology if useful, what you attempted, and what happened. Use an invented title when possible instead of sharing your private list. Specific reports help identify a practical fix; no response-time promise is made.