Skip to content

Practical access matters

Accessibility

Responsive layouts, labeled controls and readable worksheet outputs are part of making a useful planning desk.

Navigation and reading

The site uses semantic headings, a keyboard skip link, visible focus styles and standard links, buttons and disclosures. The header menu stacks on narrow screens and “Other Pages” can be opened by keyboard. Long text wraps, layouts stack and browser zoom can enlarge the page. No game artwork or animation is needed to understand a result.

Forms and errors

Inputs have visible labels and grouped entries use fieldsets. Repeatable rows have labeled remove controls. Native number and date validation works alongside messages for incomplete rows, all-zero comparison weights and conflicting coin assumptions. Build a result to move focus to its heading. Edit an input to invalidate the old result, then rebuild before printing or saving.

Color, output and device preferences

The site uses the requested dark, secondary, accent and light palette. Dark or secondary text on the light background carries the content; the accent is used for decorative borders rather than small text. Results are available as plain text and print views remove navigation and form controls. Reduced-motion preferences and basic forced-color support are included. Status is expressed in text, not color alone.

Known limits

The interactive calculations need JavaScript; explanation and FAQ content remains readable without it. Native date pickers, browser print dialogs and PDF output vary by operating system and assistive technology. Large worksheets may span several printed pages. This statement is not a certification of WCAG conformance, and every browser and assistive-technology combination has not been tested.

Report a barrier

Contact the operator with the page, control and task involved and, if comfortable, the browser and assistive technology used. Explain which output or interaction would help. No proof of disability or game account information is needed. The operator should review reports and retest after theme, hosting or plugin changes.