Practical access features.
The interface uses headings and landmarks, a skip link, labelled native inputs/selects, visible keyboard focus and responsive layouts. Unit/upgrade groups have legends, menus and FAQs use native expandable controls, and a result receives focus after calculation. Custom errors use an alert.
No animation, game installation, audio, drag-and-drop, chart interpretation or mouse-only interaction is needed. Checklist items are native checkboxes. Results are selectable text with download and print alternatives.
The requested palette.
Navy #12243A headings and text sit on white #FFFFFF or pale #F3F7FA surfaces. Teal #087F8C highlights primary actions with white labels; secondary text uses #31546B. Information is expressed in words, not colour alone.
Forced-colour modes and native browser controls may use system colours. Browser zoom is not disabled. The operator should test the full deployed theme/plugin combination and any later style changes.
Keyboard and narrow screens.
Use Tab and Shift+Tab to navigate; Enter or Space toggles menus, FAQs and checkboxes; Escape closes an open header menu. All Tools contains the six direct links and the tool index. Navigation wraps and dropdowns fit narrow screens.
Forms and results stack on mobile, while long notes wrap inside their panels. Text downloads are an alternative for inspecting a long army or upgrade series. No data table requires whole-page horizontal scrolling.
Validation and no-JavaScript behaviour.
Input hints explain whole-number, decimal and size bounds. Native range checks and plain-language custom errors report problems such as a filled custom ledger that has not been enabled. Editing removes stale output before another result is built.
Interactive planning needs a modern JavaScript browser. Without JavaScript, controls stay disabled to prevent ordinary server submission. WordPress still renders the methods, FAQs and information pages. The standalone preview requires JavaScript for routing too.
Testing limits and reporting.
Responsive layouts, menus, form validation, result focus, text downloads and printing are checked in a modern Chromium environment. This is not formal accessibility certification or exhaustive testing with every assistive technology, browser, zoom level or printer.
Use Contact to describe a barrier, the tool/action and any useful device or assistive-technology context. Share only what is necessary and suggest a helpful format if known. The operator should review reports without promising a fixed response time.