Decision block 01
Accessibility standards for the live product
| Area | Standard | Implementation check |
|---|---|---|
| Keyboard access | All links, controls, sliders, accordions and form fields work without a mouse. | Visible focus is not hidden by sticky CTAs. |
| Screen readers | Headings, labels, tables and status messages use semantic markup. | Do not rely on color or visual position alone. |
| Zoom / reflow | Content remains usable at high zoom and narrow widths. | Avoid horizontal scrolling for normal reading content. |
| Forms | Inputs have programmatic labels, clear errors and instructions. | Do not erase user input after an error unless necessary. |
| Targets / touch | Interactive targets meet practical size/spacing expectations. | Avoid tiny text links inside dense financial disclaimers. |
| Consistent help | Support and privacy-help access remains predictable. | Do not move essential assistance between pages without reason. |
Decision block 02
Accessibility for financial decision tools
- Calculator results should be announced to assistive technology when they update.
- Sliders need keyboard alternatives and visible numeric inputs.
- Charts must have text/table equivalents for the key decision data.
- Color-coded risk or affordability states need text labels such as “higher payment burden.”
- Countdowns or funding clocks should never force a time-limited action without an accessible alternative.
Decision block 03
Reporting an accessibility problem
- Identify the page, tool or form step.
- Describe the assistive technology, browser or device if known.
- Explain the action you were trying to complete.
- Provide a safe contact method.
- CTCLoans should offer a reasonable alternative way to access the same information or complete the service while the issue is investigated.
Decision block 04