Slide 1

Slide 1 text

No content

Slide 2

Slide 2 text

Android Accessibility Apps

Slide 3

Slide 3 text

Talkback is used for Accessibility in Android. Steps to enable Talkback: 1. On your device, open Settings . 2. Select Accessibility > TalkBack. 3. Turn Use TalkBack on or off. 4. Select Ok. Reference Link

Slide 4

Slide 4 text

Make apps more accessible link Easy ways: ● Increase text visibility ○ Set the color contrast ratio to at least 3:1. ● Use large, simple controls ○ Each interactive UI element have a focusable area, or touch target size, of at least 48dpx48dp. Larger is even better. ● Describe each UI element ○ Include description in the element's contentDescription attribute to describe element’s purpose.

Slide 5

Slide 5 text

Editable elements link

Slide 6

Slide 6 text

Pairs of elements where one describes the other link

Slide 7

Slide 7 text

Elements in a collection link

Slide 8

Slide 8 text

Group of related content link

Slide 9

Slide 9 text

Custom group label link

Slide 10

Slide 10 text

Nested groups link

Slide 11

Slide 11 text

Headings within text link ● Headings are used to summarize groups of text that appear on screen. ● If a particular View element represents a heading, you can indicate its purpose for accessibility services by setting the element's android:accessibilityHeading=true.

Slide 12

Slide 12 text

Decorative elements link ● If an element in your UI exists only for visual spacing or visual appearance purposes, set its android:importantForAccessibility="no".

Slide 13

Slide 13 text

Make all actions accessible link ● A user of TalkBack, Voice Access, or Switch Access might need alternate ways to complete certain user flows within the app. ● For example, if your app allows users to swipe on an item, you can also expose the functionality through a custom accessibility action, like this:

Slide 14

Slide 14 text

Make available actions understandable link ● When a view supports actions such as touch & hold, an accessibility service such as TalkBack announces it as "Double tap and hold to long press." ● To make this announcement more descriptive, "Double tap and hold to favorite," will help users understand the purpose of the action.

Slide 15

Slide 15 text

Define custom events (overriding) link ● For every view-based callback you override, you also need to redefine the corresponding accessibility action by overriding ViewCompat.replaceAccessibilityAction(). ● In your app's tests, you can validate the behavior of these redefined actions by calling ViewCompat.performAccessibilityAction().

Slide 16

Slide 16 text

How this principle can work for TriSwitch objects link ● Tapping a TriSwitch object cycles through 3 possible states. Therefore, corresponding ACTION_CLICK accessibility action needs to be updated.

Slide 17

Slide 17 text

CO Accessibility Wiki link ● Talkback for images ● Heading-by-heading controls ● Announcing Links ● Skip talkback announcement ● Keyboard tab order ● Requesting focus and announcing explicitly ● Contrast Issues

Slide 18

Slide 18 text

Android Accessibility Scanner app Scanner audits features by taking snapshots: ● Content labels ● Touch target size ● Clickable items ● Color contrast for text and images Watch: Accessibility scanner - Accessibility on Android

Slide 19

Slide 19 text

Accessibility test framework and Espresso ● Accessibility Test Framework is a library that checks Android UI to identify area of improvement related to accessibility ● Integrate ATF into existing Espresso tests with AccessibilityChecks.enable () Watch: Accessibility test framework and Espresso - Accessibility on Android

Slide 20

Slide 20 text

Accessibility Demo App link ● Github

Slide 21

Slide 21 text

References ● Principles for improving app accessibility ● Android Accessibility Codelab ● Testing Accessibility ● Mobile Android Accessibility Thank you! Chetan Sachdeva ([email protected])