Account, privacy, and operation
Use YARCalc with accessibility and display needs
Understand the accessibility behavior YARCalc is designed to provide and the places that still require verification or improvement.
The planning result must remain understandable without one particular input method or color
SupportedYARCalc is intended to use labeled controls, semantic headings, ordinary links, keyboard-operable actions, visible focus, and text beside status colors. A person should not need to infer a retirement conclusion from green, yellow, or red alone.
Browser zoom and operating-system text settings are the general way to increase text size. YARCalc does not currently provide a separate universal text-size or high-contrast preference.
Report a barrier instead of assuming it is part of the model
Use Tab and Shift+Tab to move through interactive controls, Enter or Space to activate them, and Escape to close supported dialogs or contextual Help. A control that cannot be reached, has no useful name, hides focus, or loses unsaved work is a product defect.
Charts should be accompanied by labels, legends, tables, or prose that convey the result. If a chart communicates only through color or has no accessible evidence, report it rather than trying to reconstruct the answer visually.
Use contextual Help when you need an explanation without losing the active plan. Report clipped text, inaccessible tables, missing focus, and unusable zoom with the page and control involved.
Choose the representation that makes the result verifiable
Wide tables may require horizontal scrolling on a small screen. Dense analysis screens are often easier to review on a larger display, although ordinary access remains browser based. Column resizing and arbitrary reordering are not general features.
Print and spreadsheet exports vary by report. Use the export actually offered on the current page and confirm that headings, units, dates, and labels remain understandable. Do not assume every chart has an identical accessible export.
When reporting a barrier, describe the browser or device, zoom level, input method, page, and the task you could not complete. Do not include sensitive plan data merely to demonstrate the issue.
Design intent is not a certification
This guide does not claim conformance with an accessibility standard that has not been formally audited. Individual pages and states still require keyboard, zoom, contrast, screen-reader, mobile, and print verification.
Animations, column rearrangement, a dedicated high-contrast switch, and identical accessible exports are not currently universal capabilities.