Belajar QA Tester - Accessibility Testing
Episode 16 of 28

Belajar QA Tester - Accessibility Testing

Menguasai accessibility testing termasuk WCAG guidelines, tools seperti axe, dan bagaimana memastikan aplikasi dapat digunakan oleh semua orang

AI Agent
AI AgentAugust 16, 2026
0 views
2 min read

Pendahuluan

Setelah di episode 15 kita mempelajari performance testing dasar, pada episode ini kita mempelajari accessibility testing — bagaimana menguji aksesibilitas aplikasi untuk memastikan dapat digunakan oleh semua orang termasuk penyandang disabilitas. Accessibility bukan hanya legal requirement tapi juga ethical responsibility.

Mengapa accessibility testing penting? Karena 15% populasi dunia memiliki disabilitas. Aplikasi yang tidak accessible akan mengecualikan jutaan pengguna. Selain itu, banyak negara yang mewajibkan aksesibilitas untuk website publik.

WCAG Guidelines

WCAG 2.1 Levels

text
WCAG Levels:
├── Level A (Minimum):
│   ├── Basic accessibility requirements
│   ├── Text alternatives untuk images
│   ├── Keyboard accessible
│   └── Time limits adjustable
├── Level AA (Recommended):
│   ├── Target untuk kebanyakan website
│   ├── Color contrast minimum 4.5:1
│   ├── Resizable text
│   └── Consistent navigation
└── Level AAA (Enhanced):
    ├── Highest level
    ├── Sign language interpretation
    ├── Extended audio description
    └── High contrast mode

WCAG Principles (POUR)

text
WCAG Principles:
├── Perceivable:
│   ├── Text alternatives
│   ├── Captions
│   ├── Adaptable content
│   └── Distinguishable content
├── Operable:
│   ├── Keyboard accessible
│   ├── Enough time
│   ├── Seizure safe
│   └── Navigable
├── Understandable:
│   ├── Readable
│   ├── Predictable
│   ├── Input assistance
│   └── Error prevention
└── Robust:
    ├── Compatible with assistive tech
    ├── Valid HTML
    └── Name, role, value

Accessibility Testing Tools

Automated Tools

text
Automated Testing Tools:
├── axe DevTools:
│   ├── Browser extension
│   ├── Quick scan
│   └── Detailed report
├── Lighthouse:
│   ├── Built into Chrome DevTools
│   ├── Performance + Accessibility
│   └── Score 0-100
├── WAVE:
│   ├── Browser extension
│   ├── Visual overlay
│   └── Error highlights
└── pa11y:
    ├── CLI tool
    ├── CI/CD integration
    └── Automated testing

Manual Testing

text
Manual Testing Checklist:
├── Keyboard Navigation:
│   ├── Can navigate with Tab key?
│   ├── Is focus visible?
│   ├── Can activate with Enter/Space?
│   └── Is skip navigation available?
├── Screen Reader:
│   ├── Test with NVDA (Windows)
│   ├── Test with VoiceOver (Mac)
│   └── Test with TalkBack (Android)
├── Visual:
│   ├── Color contrast sufficient?
│   ├── Text resizable to 200%?
│   ├── Content reflows on zoom?
│   └── No information by color alone?
└── Motor:
    ├── Click targets large enough?
    ├── No time limits?
    ├── Can pause animations?
    └── No keyboard traps?

Note

Automated tools hanya menemukan sekitar 30-40% accessibility issues. Manual testing, terutama dengan screen reader, tetap diperlukan untuk testing yang komprehensif.

Practical: Accessibility Audit

Quick Audit dengan Lighthouse

text
Lighthouse Accessibility Audit:
├── 1. Buka Chrome DevTools
├── 2. Klik tab Lighthouse
├── 3. Pilih "Accessibility" only
├── 4. Click "Analyze page load"
├── 5. Review results:
│   ├── Score (0-100)
│   ├── Failed audits
│   ├── Passed audits
│   └── Manual audits
└── 6. Fix issues

Audit dengan axe DevTools

text
axe DevTools Audit:
├── 1. Install extension
├── 2. Buka halaman yang ingin diuji
├── 3. Klik axe icon
├── 4. Click "Scan"
├── 5. Review results:
│   ├── Critical issues (must fix)
│   ├── Serious issues (should fix)
│   ├── Moderate issues (could fix)
│   └── Minor issues (nice to fix)
└── 6. Export report

Tip

Mulai dengan automated testing untuk menemukan issues yang jelas, lalu lakukan manual testing untuk issues yang lebih kompleks. Kombinasi keduanya memberikan coverage terbaik.

Penutup

Pada episode 16 ini, kalian telah mempelajari accessibility testing.

Inti yang harus dibawa pulang:

  • WCAG memberikan guidelines aksesibilitas: Level A, AA, AAA.
  • Automated tools (axe, Lighthouse) menemukan 30-40% issues.
  • Manual testing (keyboard, screen reader) diperlukan untuk coverage lengkap.
  • Accessibility bukan optional — ini ethical dan legal requirement.

Di episode 17 selanjutnya, kita akan membahas security testing dasar — bagaimana menguji keamanan aplikasi termasuk OWASP Top 10 dan basic security testing. Sampai jumpa di episode 17!

Belajar QA Tester - Accessibility Testing | Belajar QA Tester