<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Larene Lg on Medium]]></title>
        <description><![CDATA[Stories by Larene Lg on Medium]]></description>
        <link>https://medium.com/@larenelg?source=rss-65fd28fe6596------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*9Qc2W81yoboSmlO8.jpeg</url>
            <title>Stories by Larene Lg on Medium</title>
            <link>https://medium.com/@larenelg?source=rss-65fd28fe6596------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 23:00:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@larenelg/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[React Native Accessibility: Creating Inclusive Apps in React Native - the coding bit]]></title>
            <link>https://medium.com/@larenelg/creating-inclusive-apps-in-react-native-the-coding-bit-bd3832349009?source=rss-65fd28fe6596------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd3832349009</guid>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[accessibility]]></category>
            <dc:creator><![CDATA[Larene Lg]]></dc:creator>
            <pubDate>Wed, 20 Sep 2017 15:00:52 GMT</pubDate>
            <atom:updated>2018-06-01T22:20:45.615Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rqkMSuBj7qjGTTyWNFGXjQ.png" /></figure><h3>React Native Accessibility: Creating Inclusive Apps in React Native — the coding bit</h3><h4>You may have come here looking for <a href="https://medium.com/@larenelg/mobile-accessibility-resources-dab97a739080">a list of recommended mobile accessibility resources</a>, which I’ve compiled in a separate article.</h4><p>This article is a companion to <a href="http://bit.ly/2stxH1c">my talk at YOW! Connected Conference 2017</a> in Melbourne, Australia.</p><p><strong>Abstract:</strong></p><blockquote>Creating inclusive and accessible apps is easy using React Native! Javascript developers can have a working app on their phone in less than an hour. Join me to see a working demo of how to plan, develop, and test for accessibility in the mobile space.</blockquote><blockquote>I will also be talking about resources and guidelines you can use and share with your organisation to develop apps for everyone — including what the bare minimum looks like to help you prioritise your requirements!</blockquote><p>Continue below to learn how to code and debug accessible UI components in React Native.</p><p>Prior to reading this article, it is helpful if you have some experience in creating apps with React Native. If you are completely new to React Native, here’s a <a href="https://facebook.github.io/react-native/docs/getting-started.html">guide to get started</a> — you’ll have a native app running on a simulator or your own device less than an hour! React Native currently only supports Android and iOS, with <a href="https://www.youtube.com/watch?v=JaRtmgaNZos">more platforms</a> coming very soon…</p><h3>React Native Accessibility</h3><p>The most important and most useful resource is the <a href="https://facebook.github.io/react-native/docs/accessibility.html">React Native docs for Accessibility</a>. There’s also a <a href="https://code.facebook.com/posts/435862739941212/making-react-native-apps-accessible/">companion blog post</a> about building accessibility into Facebook’s Ads Manager App.</p><p>From the React Native docs, there are many accessibility properties available to use with your JavaScript components, which will talk to the native accessibility APIs for both iOS and Android, providing an interface for which assistive technologies such as screen readers, braille displays, and switch controls can interact with your app. Here is the list of native accessibility attributes exposed in the React Native framework —</p><p><em>Used frequently:</em></p><ul><li><strong>accessible={true|false}</strong></li><li><strong>accessibilityLabel={&#39;some label read by the screen reader&#39;}</strong></li></ul><p><em>Sometimes used:</em></p><ul><li>(iOS) accessibilityTraits={&#39;none&#39;|&#39;button&#39;|&#39;link&#39;|…}</li><li>(Android) accessibilityComponentType={&#39;none&#39;|&#39;button&#39;|&#39;radiobutton_checked&#39;|&#39;radiobutton_unchecked&#39;}</li></ul><p><em>Have never used:</em></p><ul><li>(iOS) accessibilityViewIsModal={true|false}</li><li>(iOS) onAccessibilityTap={someFunction()}</li><li>(iOS) onMagicTap={someFunction}</li><li>(Android) accessibilityLiveRegion={&#39;none&#39;|&#39;polite&#39;|&#39;assertive&#39;}</li><li>(Android) importantForAccessibility={&#39;auto&#39;|&#39;yes&#39;|&#39;no&#39;|&#39;no-hide-descendants&#39;}</li><li><a href="https://facebook.github.io/react-native/docs/accessibilityinfo.html">AccessibilityInfo.fetch()</a></li></ul><p>I found I’ve rarely needed to use anything except accessible and accessibilityLabel which I’ve highlighted in <strong>bold</strong> in the above list.</p><p>I’ve only used accessibilityTraits and accessibilityComponentType to describe button-like components that don’t use &lt;Button&gt;, e.g. &lt;TouchableHighLight&gt; or similar touchable components.</p><p>Next, let’s take a closer look at the most frequently used accessibility properties in React Native —</p><h4><a href="https://facebook.github.io/react-native/docs/accessibility.html#accessible-ios-android">accessible={true}</a> and <a href="https://facebook.github.io/react-native/docs/accessibility.html#accessibilitylabel-ios-android">accessibilityLabel</a></h4><p>The accessible property is a little confusing to begin with.</p><p>When an element has the property accessible={true}, it’s actually makes the children of that element <em>inaccessible</em>. See the following example:</p><pre>// The following code makes the button **inaccessible**</pre><pre>&lt;View accessible={true}&gt;   <br>  &lt;Text&gt;Here is some text&lt;/Text&gt;<br>  &lt;Text&gt;And some more text&lt;/Text&gt;<br>  &lt;Button   <br>    onPress={() =&gt; console.log(&#39;Button pressed!&#39;)}<br>    title=&quot;Press me!&quot;<br>    accessibilityLabel=&quot;The button&#39;s accessibility label&quot; /&gt;<br>&lt;/View&gt;</pre><pre>// Screenreader transcript: <br>// &quot;Here is some text And some more text The button&#39;s accessibility label&quot;</pre><p>A few things to note here:</p><ol><li>The screen reader can only focus on the parent &lt;View&gt; component, and cannot access the children — therefore a screen reader user cannot navigate to the &lt;Button&gt; to tap on it</li><li>The screen reader will read the component as a concatenation of its children’s accessibility labels or contents (if there’s no accessibilityLabel)</li><li>The button’s accessibilityLabel has precedence over the button’s title. Without an accessibilityLabel, the screen reader will announce the button’s title instead</li></ol><p>You will not often set accessible={true} on a &lt;View&gt;, and by default it is set to false. If you remove the accessible property altogether, the screen reader will be able to focus on each the children, and also activate the &lt;Button&gt;. Here’s how you make the above component completely accessible:</p><pre>&lt;View&gt;   <br>  &lt;Text&gt;Here is some text&lt;/Text&gt;<br>  &lt;Text&gt;And some more text&lt;/Text&gt;<br>  &lt;Button   <br>    onPress={() =&gt; console.log(&#39;Button pressed!&#39;)}<br>    title=&quot;Press me!&quot; /&gt;<br>&lt;/View&gt;</pre><pre>// Screenreader transcript: <br>// &quot;Here is some text&quot; (user swipes right)<br>// &quot;And some more text&quot; (user swipes right)<br>// &quot;Press me!, button&quot; (user double taps to activate button)</pre><h4><a href="https://facebook.github.io/react-native/docs/accessibility.html#accessibilitytraits-ios">accessibilityTraits</a> and <a href="https://facebook.github.io/react-native/docs/accessibility.html#accessibilitycomponenttype-android">accessibilityComponentType</a></h4><p>As much as possible, try to use semantic components when creating any user interface (that includes web too!). Semantic components reinforce the <em>meaning </em>of the component — i.e. what role is that component playing in the scheme of things?</p><p>Using a &lt;Button&gt; for a component that behaves like a button is always a good idea, because you get a lot of accessibility and usability properties for <em>free</em>. For example, the screen reader will announce “button” after reading the label of a &lt;Button&gt; component, and allow the user to activate it.</p><p>In real life, however, the primitive semantic components might not be enough to satisfy our requirements for a particular component. You might want to do some fancy styling, or add an icon, which isn’t possible with the primitive &lt;Button&gt; component — you might want to use a &lt;TouchableHighlight&gt; instead. For example:</p><pre>&lt;TouchableOpacity&gt;<br>  &lt;View&gt;<br>    &lt;Text&gt;  +  &lt;/Text&gt;<br>  &lt;/View&gt;<br>&lt;/TouchableOpacity&gt;</pre><pre>// Screenreader transcript:<br>// &quot;Plus&quot;</pre><p>Not particularly descriptive, right? This is a common mistake that is made for icon buttons, a very common pattern in mobile apps, and the screen reader simply doesn’t read anything out.</p><pre>&lt;TouchableOpacity <br>  accessible={true} // optional, this is the default<br>  accessibilityLabel={&#39;Add new thing&#39;} // overrides child content<br>  accessibilityTraits={&#39;button&#39;} // only works in ios<br>  accessibilityComponentType={&#39;button&#39;} // only works in android<br>&gt;<br>  &lt;View&gt;<br>    &lt;Text&gt;  +  &lt;/Text&gt;<br>  &lt;/View&gt;<br>&lt;/TouchableOpacity&gt;</pre><pre>// Screenreader transcript:<br>// &quot;Add new thing, button&quot;</pre><p>If you are using the native-base library for your base UI components, be weary of the &lt;Button&gt; component! It actually uses &lt;TouchableOpacity&gt; in iOS, and &lt;TouchableNativeFeedback&gt; in Android. You can <a href="https://github.com/GeekyAnts/NativeBase/blob/master/src/basic/Button.js">check the code out here</a>. You’ll need to add both accessibilityTraits and accessibilityComponentType properties (someone should raise a pull-request to make those properties default to &#39;button&#39;!)</p><p>For native app developers (and the curious) I’ve included the code snippets showing how native accessibility properties are mapped to React Native accessibility properties, below —</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eRFuNu0-2-pYAbbwdZM_Wg.png" /><figcaption>Bridge for accessibility properties in iOS — <a href="https://github.com/facebook/react-native/blob/1e8f3b11027fe0a7514b4fc97d0798d3c64bc895/React/Views/RCTViewManager.m">RCTViewManager.m</a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7ffJmlxacTS_gg4cfF_rRQ.png" /><figcaption>Native bridge for accessibility properties in Android — <a href="https://github.com/facebook/react-native/blob/1e8f3b11027fe0a7514b4fc97d0798d3c64bc895/ReactAndroid/src/main/java/com/facebook/react/views/view/ReactViewManager.java">ReactViewManager.java</a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DeDewySMuASM69Ki4sm1dA.png" /><figcaption>Native bridge for accessibility properties in Android — <a href="https://github.com/facebook/react-native/blob/1e8f3b11027fe0a7514b4fc97d0798d3c64bc895/ReactAndroid/src/main/java/com/facebook/react/uimanager/BaseViewManager.java">BaseViewManager.java</a></figcaption></figure><h3>Debugging</h3><p>I usually use OSX’s Accessibility Inspector to inspect my app in the iOS simulator, to check that the structure of my component is correct. After I finish a chunk of work, I then turn on VoiceOver and TalkBack to double-check everything is structured and labelled correctly.</p><p>Check my <a href="https://medium.com/@larenelg/mobile-accessibility-resources-dab97a739080">Mobile Accessibility Resources article</a>, if you need a refresher on using Accessibility Inspector, VoiceOver, or TalkBack</p><h3>Gotchas</h3><p>In the many months that I’ve worked with React Native this year, I wanted to share a few gotchas that break accessibility in your app that took a while to catch, and caused me to pull a good chunk of my hair out.</p><p>1. All Touchable components are accessible={true} by default.</p><p>2. Some React Native libraries don’t expose (therefore, don’t pass through) accessibility properties in their UI components. I’ve had to fork a repo just to add one line to make an entire modal accessible again.</p><p>3. Things that work fine in iOS, often break horribly in Android. To create robust React Native apps that look good, get it working in Android first, and more than likely you will not have to change anything for iOS.</p><p>4. Upgrading libraries, especially React Native, can either fix everything, or break everything more. Always check a package’s Github Issues page first, if something strange is happening… like when a fresh React Native project crashes on launch.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*187zd6xy0j7xDFHe_ErAzQ.png" /><figcaption>Recently, a ‘stable’ release of React Native was horribly <a href="https://github.com/facebook/react-native/issues/15762">broken</a>.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*48kvRcslMCe35zVrs1Ni3A.png" /><figcaption>“React Native is the most extreme love &amp; hate relationship I have.” — my favourite quote about React Native so far.</figcaption></figure><h3>More coming soon… stay tuned!</h3><blockquote>Go forth and make amazing apps!</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd3832349009" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mobile Accessibility Resources]]></title>
            <link>https://medium.com/@larenelg/mobile-accessibility-resources-dab97a739080?source=rss-65fd28fe6596------2</link>
            <guid isPermaLink="false">https://medium.com/p/dab97a739080</guid>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <dc:creator><![CDATA[Larene Lg]]></dc:creator>
            <pubDate>Wed, 20 Sep 2017 14:47:48 GMT</pubDate>
            <atom:updated>2017-09-20T17:25:26.952Z</atom:updated>
            <content:encoded><![CDATA[<p>Here is a list of my favourite mobile accessibility resources, with a focus on native apps.</p><p>I’m an engineer/developer, so I’m (pragmatically) lazy — as such, I’ve only provided resources that are concise and easy to understand and instantly applicable. These are resources that I constantly refer to and use, and always share with my teams on new clients and projects. I hope you find these useful, and share these resources to raise awareness and inspire your team or company to create wonderful mobile apps with accessibility in mind.</p><p>You’ll find general accessibility resources from the top of the page, moving to more mobile-specific resources further down the page.</p><p><strong>Note: </strong>this article is a companion to my talk on Creating Inclusive Apps with React Native presented at YOW! Connected, 2017.</p><h4>You may have come here to learn about <a href="https://medium.com/@larenelg/creating-inclusive-apps-in-react-native-the-coding-bit-bd3832349009">creating accessible UI components in React Native</a> — the article you’re looking for is elsewhere.</h4><h3>General Accessibility Resources</h3><h4><a href="https://www.microsoft.com/en-us/design/inclusive">Inclusive Design at Microsoft</a></h4><p>Microsoft has an incredible toolkit that includes a manual, activities, and support cards and materials to print out and put around the office. These materials aim to shift your mindset away from “accessibility == disability” towards true universal design thinking.</p><p>This is <strong>required reading</strong> for all designers, developers, and anyone involved in creating inclusive products. Here’s some easy links to the Microsoft Inclusive Design toolkit:</p><ul><li><a href="https://download.microsoft.com/download/B/0/D/B0D4BF87-09CE-4417-8F28-D60703D672ED/INCLUSIVE_TOOLKIT_MANUAL_FINAL.pdf">Microsoft Inclusive Design Manual</a></li><li><a href="https://download.microsoft.com/download/B/0/D/B0D4BF87-09CE-4417-8F28-D60703D672ED/Inclusive_Toolkit_Activities.pdf">Microsoft Inclusive Design Activities and Support Cards</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A5Ry80qzxj48-QOUPqzs9g.png" /><figcaption>Inclusive design at Microsoft: to empower every person on the planet to achieve more.</figcaption></figure><h4><a href="https://accessibility.blog.gov.uk/2016/09/02/dos-and-donts-on-designing-for-accessibility/">Gov.UK — Dos and Don’ts of Designing for Accessibility</a></h4><p>Gov.UK department of Home Office Digital have created some <a href="https://github.com/UKHomeOffice/posters/tree/master/accessibility">great open source posters</a> that you can hang around the office, and they’ve been translated into around 10 languages. They provide a great introduction to designing for accessibility as well as common mistakes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ivU52-owBQdxDFMj1nf9jQ.png" /><figcaption>Designing for accessibility posters, created by <a href="https://accessibility.blog.gov.uk/2016/09/02/dos-and-donts-on-designing-for-accessibility/">Karwai Pun, courtesy of gov.uk</a> — follow <a href="https://accessibility.blog.gov.uk/2016/09/02/dos-and-donts-on-designing-for-accessibility/">this link</a> for text version of the posters</figcaption></figure><h4><a href="http://accessibility.voxmedia.com/">Vox Media Accessibility Guidelines</a></h4><p>Vox Media, a digital media company whose most popular brand is The Verge, created an accessibility checklist for every role in the team; designer, developer, project managers, quality analysts, and content editors. They’ve created an easy checklist creation tool, where you can check the guidelines that apply to your project, and copy-paste those checkboxes into your favourite project management tool — e.g. Trello, or Jira</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WRYRnkS0cy2N3atUBjgLxw.png" /><figcaption>A screenshot of the Accessibility Guidelines from Vox Media, showing a checklist of requirements starting with designers and colour contrast.</figcaption></figure><h4><a href="https://teachaccess.github.io/tutorial/">Teach Access Tutorial</a> (web accessibility and screen reader)</h4><p>Teach Access is an interactive web page that teaches you how to instantly improve the accessibility of your webpage through simple examples of semantic HTML code snippets, which you can see straight away while using the screen reader to navigate the tutorial. It was originally named “HIKE”, an accessibility primer created by Facebook, but was later renamed to the Teach Access Initiative. Must like Microsoft, Facebook also has a <a href="https://code.facebook.com/accessibility">great accessibility toolkit</a>.</p><p>It only teaches the keyboard commands for OSX’s VoiceOver, but you can also use NVDA on Windows to navigate the tutorial —though, you’ll need to learn the <a href="https://www.nvaccess.org/files/nvda/documentation/userGuide.html">NVDA keyboard commands first</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jb8qfRegXTXPsb8CYAYWiA.png" /><figcaption>Screenshot of the Teach Access website, showing an example of how to make images accessible on a web page using alt-tags.</figcaption></figure><h4><a href="https://blogs.dropbox.com/tech/2017/04/creating-a-culture-of-accessibility/">Creating a Culture of Accessibility</a></h4><blockquote>To create accessible products, you need to find opportunities to spread accessibility knowledge and enthusiasm in a sustainable way throughout your company.</blockquote><p>This is a fantastic blogpost I read earlier this year about activities and practices at Dropbox to strive towards their mission of making products easy for anyone to use. Raising awareness and building accessibility and inclusivity into your organisation is the best way to create products for everyone.</p><h3>Standards for Mobile Accessibility</h3><p>The next section includes resources for standards in mobile accessibility, in a similar fashion that <a href="https://www.w3.org/TR/WCAG20/">WCAG 2.0</a> or <a href="https://webaim.org/">WebAIM</a> provides standards and guidelines for web accessibility. Mobile standards and guidelines are not as well-defined as smart phones and smart devices haven’t been around as long as the World Wide Web. To save you the search, here are the best resources I’ve found so far.</p><h4><a href="http://www.bbc.co.uk/guidelines/futuremedia/accessibility/mobile">BBC Mobile Accessibility Guidelines</a></h4><p>These are the best mobile accessibility guidelines I have found to date. They apply to web-based, hybrid, or native apps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U1sOMmUuCEYaPEQ7HbjLXw.png" /><figcaption>A screenshot of the BBC Mobile Accessibility Guidelines summary page, showing a list of best practices.</figcaption></figure><h4><a href="https://www.deque.com/blog/introduction-native-mobile-accessibility-featuring-deque-university-iosandroid/">Deque University App</a></h4><p>You can’t possibly mention accessibility without Deque. Deque is the leading automation and tooling company that creates amazing open-source software to make the web (and mobile) more accessible. The Deque University app is available on both iOS and Android, and teaches you the dos and don’ts of native mobile accessibility.</p><ul><li><a href="https://itunes.apple.com/us/app/deque-university-for-ios/id973198091?mt=8">Download Deque University on the App Store</a> and <a href="https://github.com/dequelabs/Deque-University-for-iOS">Github</a></li><li><a href="https://play.google.com/store/apps/details?id=com.dequesystems.accessibility101&amp;hl=en">Download Deque University on Google Play</a> and <a href="https://github.com/dequelabs/Deque-University-for-Android">Github</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KHJDFNTbOl1fvxfHCysJ2w.png" /><figcaption>Screenshots of Deque University app (courtesy the <a href="https://itunes.apple.com/us/app/deque-university-for-ios/id973198091?mt=8">Apple Store</a>) which gives basic demonstrations of how to correctly implement accessibility features on native apps.</figcaption></figure><h3>Design Guidelines for Mobile Accessibility</h3><h4><a href="https://developer.apple.com/ios/human-interface-guidelines/app-architecture/accessibility/">Apple Developer — Human Interface Guidelines</a></h4><p>Apple have gone above and beyond to create the most human-friendly user experiences and accessible products. Apple’s built-in VoiceOver screen reader is almost as widely used as JAWS or NVDA, and screen reader users strongly prefer to use an iOS devices over Android, compared to people who don’t use a screen reader, <a href="https://webaim.org/projects/screenreadersurvey6/">based on a survey by WebAIM</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7t2E42gbSZS7nwZQ58e6EQ.png" /><figcaption>A screenshot of Apple’s Human Interface Guidelines for accessibility, which gives a brief introduction to Apple’s accessibility features followed by links to in-depth Apple accessibility resources.</figcaption></figure><h4><a href="https://material.io/guidelines/usability/accessibility.html#accessibility-principles">Android Material Design Guidelines</a></h4><p>Material design is a set of mobile UI design principles and guidelines created by Google primarily for Android app development. Material design also outlines accessibility principles and practices.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ugSNjjIe10fnMisYRatfhg.png" /><figcaption>Material design’s core accessibility principles — “Clear”, “Robust”, and “Specific”. Followed by a list of best practices and common mistakes.</figcaption></figure><h3>Mobile Screen Readers</h3><h4>Turning your Screen Reader On (and Off again)</h4><ul><li>VoiceOver (iOS) — Settings &gt; General &gt; Accessibility &gt; VoiceOver (I recommend you turn on the Accessibility Shortcut, so that you can turn your screen reader on and off by triple-clicking the Home button)</li><li>TalkBack (Android) — Settings &gt; Accessibility &gt; TalkBack (you can also turn on the Accessibility Shortcut, where you can turn TalkBack on or off holding both volume keys for 3 seconds)</li></ul><p>Once you have your screen reader on, open one of the cheatsheets below to learn how to use it.</p><h4>Screen Reader Cheatsheets</h4><p>Once you’ve worked out how to turn your mobile screen reader on (and, hopefully, off), it’s hard to remember all the gestures, especially if you’re not using it everyday. These cheat sheets are great to hang in the office as a quick reference to how to navigate your phone with a screen reader.</p><ul><li><a href="http://www.interactiveaccessibility.com/education/training/downloads/iOS-Cheatsheet.pdf">iOS VoiceOver Cheatsheet</a></li><li><a href="http://www.interactiveaccessibility.com/education/training/downloads/Android-Cheatsheet.pdf">Android TalkBack Cheatsheet</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kZ2sshWTE1GDFUO0HtUL4A.png" /><figcaption>An image of some of the basic screen reader gestures — swipe left/right to navigate between items on the screen, and double tap to activate selected item.</figcaption></figure><h4>VoiceOver on your iOS Simulator</h4><p>You can actually do preliminary debugging of you app, by turning on VoiceOver on your Mac and clicking into the iOS Simulator.</p><p>To turn on VoiceOver, use <strong>command+F5</strong> shortcut, or under Accessibility in System Preferences. Use <strong>control+option+left/right arrow</strong><em> </em><strong>keys</strong> to navigate, and <strong>control+option+spacebar</strong> to activate a selection. This is almost as good as testing with VoiceOver on the device.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/733/1*twiDfkhUmuXhjLjL9gWl3A.png" /><figcaption>A screen shot of the OSX VoiceOver introduction screen prompt.</figcaption></figure><h4>TalkBack on your Android Emulator</h4><p>This is great for testing your app without needing to put it on a physical device.</p><p><strong>TalkBack</strong> — you can <a href="https://apkpure.com/google-talkback/com.google.android.marvin.talkback">download the TalkBack APK</a> and drag-and-drop into your Android Emulator. If you’re new to mobile screen-readers, start with the tutorial! Mobile screen-reader gestures are largely the same between both Android and iOS.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/402/1*1rufmmFmdLsGy7lkKJECaQ.png" /><figcaption>Screenshot of Android Emulator (running Nexus_5X_API_26_x86). To turn on TalkBack first install the APK, then go to Apps &gt; Settings &gt; Accessibility &gt; TalkBack &gt; and toggle it to On</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/316/1*hJRWQ2cplhH7pTDsUF3U1Q.png" /><figcaption>The Google TalkBack tutorial is a great starting point for learning how to use a mobile screen reader.</figcaption></figure><h3>Auditing/Inspection Tools</h3><p>What you won’t find here are automatic testing tools. I’ll be adding a separate article on mobile UI testing frameworks at a later date. These are manual accessibility inspection tools that are still very useful.</p><h4><a href="https://developer.apple.com/library/content/documentation/Accessibility/Conceptual/AccessibilityMacOSX/OSXAXTestingApps.html">Accessibility Inspector (OSX &amp; iOS Simulator only)</a></h4><p>If you’re developing an iPhone app, you can use the Accessibility Inspector to take a peak at how accessible your app is. The text under “Quicklook” in the inspector indicates what is spoken by the screen reader, and clicking the left/right arrows simulate screen reader navigation. It can be a bit buggy, so always check on your device with a screen reader, but it’s great for debugging during app development.</p><p>Unfortunately, the audit functionality doesn’t work within the iOS simulator, so just stick with inspection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/744/1*uTqH882gSC_bj4BAjUKETQ.png" /><figcaption>A screen shot of the OSX Accessibility Inspector, inspecting an element in the iOS Settings app on the iPhone simulator.</figcaption></figure><h4><a href="https://play.google.com/store/apps/details?id=com.google.android.apps.accessibility.auditor&amp;hl=en">Google Accessibility Scanner (Android only)</a></h4><p>You can <a href="https://play.google.com/store/apps/details?id=com.google.android.apps.accessibility.auditor&amp;hl=en">download the Accessibility Scanner App</a> onto your device. It will take a screen shot of your app, and suggest improvements. It also explains the principle behind each suggestion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/312/1*5sM4crqIBXoxgcFrhay6og.gif" /><figcaption>Google’s Accessibility Scanner plonks a big blue tick in the middle of your Android screen, and you can tap on it any time to have it audit the current screen of any open app.</figcaption></figure><h3>That’s all for now, folks!</h3><p>Thanks for reading my first blog on developing inclusive software! I hope it was helpful. Stay tuned, more content coming very soon.</p><blockquote>Go forth and make amazing apps!</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dab97a739080" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>