Keyboard and focus
All preview controls have visible focus and semantic labels. Use the skip link to reach main content.
Accessibility statement
Keyboard, focus, zoom, contrast, screen-reader labels and 44-pixel targets are release requirements.
Zoom and contrast
The PC shell is designed to reflow at 200% zoom without hiding core actions; system contrast preferences are respected.
Support route
If a financial decision or accessibility need requires help, use the support route instead of relying on an offer.
Open supporttrust · human review pending
Accessibility commitment
Core tasks must work with keyboard, visible focus, zoom, screen-reader labels and 44-pixel touch targets.
Safe next action: Use the support-status page if a barrier blocks a core task. Open related page
Audience, steps, example, risks and evidence
Understand the reasoning
Keyboard use, focus visibility, readable contrast and touch targets are separate checks. Automated accessibility findings cover only some barriers; actual assistive-technology use needs its own evidence.
Worked learning example
A details control should be reachable with Tab and expandable with the keyboard. At a narrow viewport its text should wrap without forcing the entire page sideways.
Check your understanding
Does a perfect automated accessibility score prove every user can finish a task?
Show answer and explanation
No. It does not replace screen-reader, keyboard and real-user task checks.
Common mistake: Do not convert a design target such as 44-pixel controls into a claim of universal compliance.
Examples are invented educational scenarios, not provider quotes, forecasts or tax rates.
Who this is for
People using the KR educational release who want to understand a money decision before contacting a provider.
Not for
This is not a personal recommendation, provider quote, eligibility decision, tax opinion or legal opinion.
Key concepts
- Accessibility commitment
- assumptions
- limits
Steps
- Write down the values you know.
- Run the matching local calculator.
- Read the assumptions, limits and next action before deciding.
Worked example
A details control should be reachable with Tab and expandable with the keyboard. At a narrow viewport its text should wrap without forcing the entire page sideways.
Risks and limits
- Do not convert a design target such as 44-pixel controls into a claim of universal compliance.
- Actual provider terms and future outcomes can differ.
- A missing fee, tax or timing assumption can materially change the result.
Scope: Initial educational scope: Republic of Korea (KR), KRW and English interface. Provider, tax and legal rules are not inferred.
Author: FinanceScanner educational content
Review: Automated structure checks only. Human financial and language review not completed. Listed sources are background references, not claim-by-claim approval.
Next review: 2027-02-28
Background sources — not claim-by-claim verification
- Web Content Accessibility Guidelines — W3C Web Accessibility Initiative, checked 2026-08-29