Accessibility

Skapa has a high focus on accessibility (a11y) so this is a summary on steps to take to make sure the code lives up to the Accessibility guidelines.

We base the Skapa a11y guidelines on the European Accessibility Act (EAA) and WCAG 2.2, level AA, but even better if we can reach AAA, and the platform's own requirements on Android A11y guidelines for Jetpack Compose.

Testing checklist for Android/Jetpack Compose

Use the following list to test a11y for releases and PRs.

1. Android Accessibility menu (on phone)
   • TalkBack
     • Follow steps here → https://developer.android.com/guide/topics/ui/accessibility/testing#talkback
   • Switch Access
     • Follow steps here → https://developer.android.com/guide/topics/ui/accessibility/testing#switch-access
   • Voice access (Low prio)
     • Follow steps here → https://developer.android.com/guide/topics/ui/accessibility/testing#voice-access
   • Accessibility Tester'
     • Install app: https://play.google.com/store/apps/details?id=com.google.android.apps.accessibility.auditor&gl=SE -
     • Follow steps here → https://developer.android.com/guide/topics/ui/accessibility/testing#accessibility-scanner
   • Text/Display
     • Reduce/Remove animations (AAA, Low prio) https://www.w3.org/TR/WCAG21/#animation-from-interactions
     • Increased contrast, Bold text Check that the changes propagate correctly inside the Demo app
     • Font scaling (up to 200%) Check that the text wrapping looks good and nothing is cut off.
2. Keyboard navigation
   • Test Focused states by using a Bluetooth keyboard and navigating the components
3. Component scaling
   • Does the components scale, should it scale?
4. Dark mode testing
   • Use Skapa Demo app Debug Setting to enable Dark mode
5. Providing Localized strings
   • Add contentDescription to provide Accessibility labels (eg. Talkback label for Icon Button)
6. Screen sizes/orientation
   • Use different sized devices eg. Tablets, phones, and various screen densities.