ESC
Nhập từ khóa để tìm kiếm
↑↓ Di chuyển
Enter Mở
ESC Đóng
Đang tìm kiếm...
Accessibility Strategy
Vì sao
- Inclusivity — 15% population disability worldwide.
- Legal: ADA (US), EU EAA, VN Disability Law 2010.
- SEO benefit (alt text, semantic HTML).
- Better UX cho mọi user (curb-cut effect).
WCAG 2.2 levels
- A — minimum compliance.
- AA — industry standard (banking, gov mandatory).
- AAA — gold standard (rarely full compliance).
4 principles (POUR)
- Perceivable — text alt, captions.
- Operable — keyboard nav, no seizure trigger.
- Understandable — readable, predictable.
- Robust — assistive tech compatible.
Automated tools (catch ~30% issues)
- axe-core — Deque, integrate in unit test.
- Lighthouse — Chrome DevTools.
- WAVE — browser extension.
- Pa11y — CLI.
Manual test (catch the other 70%)
- Keyboard only — Tab navigate entire app.
- Screen reader (NVDA, VoiceOver, TalkBack) — actually listen.
- Color contrast checker.
- Zoom 200% — UI still work?
- User testing with disabled users.
Common WCAG fail
- Image no alt text.
- Form label missing.
- Color contrast < 4.5:1.
- Click target < 44px.
- Focus indicator removed (
outline: none).
- Auto-play with no pause.
VN context
- Government website (chinhphu.vn) mandatory WCAG AA.
- Banking app increasingly comply.
- Edtech (Vietnamcos) — strong incentive for inclusivity.
Build into process
- Designer use accessibility annotation in Figma.
- Dev run axe-core in unit test.
- QA include a11y in regression suite.