<?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 paulcollins on Medium]]></title>
        <description><![CDATA[Stories by paulcollins on Medium]]></description>
        <link>https://medium.com/@pcollins?source=rss-6b830888591f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*cVqD43CfkKbH0wiG.gif</url>
            <title>Stories by paulcollins on Medium</title>
            <link>https://medium.com/@pcollins?source=rss-6b830888591f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 05:29:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pcollins/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[5 Ways Virtual Reality will be great for accessibility]]></title>
            <link>https://medium.com/@pcollins/5-ways-virtual-reality-will-be-great-for-accessibility-74c49a9adf57?source=rss-6b830888591f------2</link>
            <guid isPermaLink="false">https://medium.com/p/74c49a9adf57</guid>
            <category><![CDATA[vr]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[inclusive-design]]></category>
            <category><![CDATA[virtual-reality]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[paulcollins]]></dc:creator>
            <pubDate>Fri, 23 Jun 2017 23:37:48 GMT</pubDate>
            <atom:updated>2017-06-26T06:29:15.486Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/780/1*Kmsi9kw0O6DTST1VznI1Lw.jpeg" /></figure><p>Since I first tried it six months ago, I’ve been captivated by <strong>Virtual Reality</strong>. When I first tried a <strong>Google Cardboard</strong>, I could see it’s power. Then I tried on the <strong>HTC Vive</strong> and there was no turning back. I’ve now gone back to School and spent the last 10 weeks studying VR Design at <a href="https://academyxi.com/"><strong>Academy XI</strong></a><strong> </strong>and doing an internship at <a href="https://www.oceanicstudios.com/games"><strong>Oceanic Studios</strong></a>.</p><p>I’m looking to change careers and move into VR, but there’s a part of my background I can’t forget. Over the last 15 years, <strong>web accessibility and inclusive design</strong> have been a focal point of my work as a Front End Developer. I still believe <strong>technology should be for everyone. </strong>VR is in it’s infancy and people are still working out the standards, which will no doubt bring some great features for people with disabilities.</p><p><strong>Here are 5 ways VR will be great for accessibility.</strong></p><p><em>Before I continue, it’s worth mentioning that VR will not “cure disability”. It is hoped that it might help at least make small improvements in the lives of people who are disabled.</em></p><h3>Mobility</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AVhWC0J1PFkHpHP4w0MbKQ.jpeg" /><figcaption>A wheelchair user working with the HTC Vive.</figcaption></figure><p>Being in VR means people with mobility issues can participate in environments they may not normally experience, giving them access to opportunities others take for granted. <strong>Haptic controllers</strong>, such as mouth movement, finger movement, could help people participate if they are unable to use traditional controllers.</p><p>Voice tools, such as <strong>Siri</strong>, or <strong>Amazon Alexa</strong>, could be used to give voice control to users.</p><p><em>NOTE: It’s important to consider when designing that people in wheelchairs will be lower in camera height and may not be able to reach high up objects.</em></p><h3>Cognitive</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/685/1*sbvv0i-b-QUWiGVOZn04Pg.jpeg" /><figcaption>An image of Dr Daniel Yang’s counselling environment.</figcaption></figure><p>People with<strong> Autism Spectrum Disorder</strong> could learn social skills that they might find difficulty grasping in real life. ASD can affect people’s ability to notice subtle cues in social situations. Smart VR apps could offer dedicated learning and work at the pace of the user, as they improve, using <strong>real life situations in the virtual space</strong>. It could be a job interview, a new neighbour or a blind date.</p><p>Dr Daniel Yang has been <a href="https://www.autismspeaks.org/science/science-news/virtual-reality-training-improves-social-skills-and-brain-activity"><strong>experimenting with online counselling</strong></a> for sufferers of ASD, solving the problem of long distance and also being able to take them to new environments at the click of a button.</p><h3>Blindness</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*eBJd2h8kSdP_GtJAatipHw.jpeg" /><figcaption>Occulus user with Haptic glove</figcaption></figure><p><strong>Haptic interfaces</strong> can help users that are visually impaired. When they are unable to use a controller to accurately point, a glove that tracks finger movements could<strong> increase the usability of a VR app.</strong> This can help visually impaired people learn faster as they can interact with the experience.</p><p>Voice tools, such as <strong>Siri</strong>, or <strong>Amazon Alexa</strong>, could be used to give voice control to users.</p><p><em>Organisations such as the </em><a href="http://www.web3d.org/"><strong><em>Web3D Consortium</em></strong></a><em> are trying to develop open standards, such as X3D, so that 3D web-based graphics can be integrated with HTML.</em></p><h3>People who suffer strokes</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j0urRl19Noy3ngaBH_CLmQ.jpeg" /></figure><p>Sufferers of strokes can have difficulty moving, thinking and sensing. This often results in problems with everyday activities such as <strong>writing, walking and driving.</strong> Rehabilitation can be a lengthy process.</p><p>VR can <a href="https://www.cnet.com/au/news/how-virtual-reality-could-soon-help-stroke-victims-recover/"><strong>help with home based rehabilitation</strong></a>, for stroke sufferers, immersing them in the activities they will need help with.</p><h3>Hearing</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fl01sdzJHCCM&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dl01sdzJHCCM&amp;image=http%3A%2F%2Fi.ytimg.com%2Fvi%2Fl01sdzJHCCM%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/cb1ebc613501db6cb7f3619d2654e017/href">https://medium.com/media/cb1ebc613501db6cb7f3619d2654e017/href</a></iframe><p>Due to it’s visual and immersive qualities, VR can be helpful to people who are <strong>deaf and hard of hearing</strong>, by providing visual cues.</p><p>Controllers can communicate sound effects to users, <strong>via vibrations, or haptic feedbac</strong>k, which is beneficial to all users.</p><p>Gloves such as<strong> </strong><a href="http://www.washington.edu/news/2016/04/12/uw-undergraduate-team-wins-10000-lemelson-mit-student-prize-for-gloves-that-translate-sign-language/"><strong>Sign Aloud</strong></a>, can be used to communicate with sign language in VR.</p><p>Dialog in virtual reality applications is normally pre-recorded, so there is no reason why it can’t be converted into captions and sign language</p><p><strong>VR is going to change the world</strong>. It’s important that we bring everyone along for the journey and make it inclusive. <strong>Many great minds are already working to achieve this goal</strong> and some of the above points might just help…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=74c49a9adf57" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[WAI-ARIA Compliant, Accessibile Form Validation: How To Do It Simple and Well]]></title>
            <link>https://medium.com/@pcollins/wai-aria-compliant-accessibile-form-validation-how-to-do-it-simple-and-well-d07e5917b048?source=rss-6b830888591f------2</link>
            <guid isPermaLink="false">https://medium.com/p/d07e5917b048</guid>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[paulcollins]]></dc:creator>
            <pubDate>Sat, 05 Nov 2016 06:26:42 GMT</pubDate>
            <atom:updated>2016-11-05T06:26:42.517Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lKYUa0VzF1BoWeizTkm5PQ.jpeg" /></figure><p>I’ve been building accessible websites for a number of years now and one thing I’ve learned is that <strong>when it comes to accessibility, there’s always more than one way to achieve perfection and form inputs are a prime example of this</strong>! However, after much trial and error in the past, if I could build a form input anyway I want without framework, project or design constraints, <strong>here’s my optimal way to markup an input with accessibility in mind</strong>:</p><h3>The features we need to make it accessible:</h3><ul><li>Label with <strong>“for”</strong> attribute, <strong>id</strong> on input to match</li><li>Use <strong>aria-invalid=”false”</strong> (changed to true when invalid)</li><li>If field needs a hint, use <strong>aria-describedby=”field-hint”</strong></li><li>When in error, use <strong>aria-describedby=”error-message”</strong></li><li>If field is required, a <strong>“required”</strong> attribute</li></ul><h3>A code example:</h3><p><em>A field </em><strong><em>without</em></strong><em> errors</em></p><pre>&lt;label<strong> for=”my-input”</strong>&gt;My field input&lt;/label&gt;<br>&lt;input type=”text” id=”my-input” <strong>aria-invalid=&quot;false&quot; aria-describedby=”my-input-hint”</strong> <strong>required</strong>&gt;</pre><pre>&lt;div <strong>style=&quot;display:none;&quot;</strong> <strong>id=”my-input-error” aria-hidden=&quot;true&quot;</strong>&gt;Text for input hint description, can be any HTML&lt;/div&gt;</pre><pre>&lt;div <strong>id=”my-input-hint”</strong>&gt;Text for input hint description, can be any HTML&lt;/div&gt;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/972/1*1msDM9gMvdiIpHoZVdY_ng.png" /></figure><p><em>A field </em><strong><em>with</em></strong><em> errors</em></p><pre>&lt;label<strong> for=”my-input”</strong>&gt;My field input&lt;/label&gt;<br>&lt;input type=”text” id=”my-input” <strong>aria-invalid=&quot;true&quot; aria-describedby=”my-input-errors my-input-hint”</strong> <strong>required</strong>&gt;</pre><pre>&lt;div <strong>style=&quot;display:block;&quot;</strong> <strong>id=”my-input-error” aria-hidden=&quot;false&quot;</strong>&gt;Text for input hint description, can be any HTML&lt;/div&gt;</pre><pre>&lt;div <strong>id=”my-input-hint”</strong>&gt;Text for input hint description, can be any HTML&lt;/div&gt;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/976/1*qscCYXZ2JuVRA-l7eKiCgw.png" /></figure><h3>The details explained</h3><p><strong>Label contains “for” attribute, with matching id on the input</strong><br>This associates it with the unique matching input ID. This will then be read out by screen readers when the user tabs to or clicks on the input.</p><p><strong>aria-invalid=”false” (changed to true when invalid). </strong><br>The screen reader will announce that the field is in error when you have <em>aria-invalid=”true”</em>.</p><p><strong>aria-describedby=”field-hint”. </strong><br>If field has a hint, associate it with the input using the <em>aria-describedby </em>attribute that matches it’s ID. You can have multiple field IDs being associated with a single <em>aria-describedby</em>, by separating each one with a space. For example: <em>aria-describedby=”field1 field2&quot;</em>. Note: They will be read out in the order they are listed and when the field is in error, the error message should be read out before the hint, so list it first.</p><p><strong>aria-describedby=”error-message”. </strong><br>The id associated to the error field should only be added to the <em>aria-describedby</em> when the field is in error.</p><p><strong>A “required” attribute<br></strong>This will ensure that the field is read out as required by screen readers and assistive software.</p><p><strong>style=”display:none” and “display:”block”</strong><br>This is to visually show and hide your error message and can be a class performing the same action. NOTE: It’s best to use the CSS <em>display</em> property to hide content and not <em>position</em> or any other CSS rule as the screen reader may still read the text out.</p><h3>Some extra DOs and DON’Ts…</h3><p><strong>DO</strong></p><ul><li>Use <strong>aria-invalid=”false”</strong> (changed to true when invalid). Associate errors and hints for form inputs using the above <strong>aria-describedby</strong> way and <strong>NOT</strong> <em>aria-labelledby</em>, etc, even though it’s possible to do so. Although the latter will work, <em>aria-describedby</em> is the standard way of doing things and will be a recognisable pattern for users of assistive software.</li><li>Keep your label text visible and next to the input, not inside it. <a href="https://coolestguidesontheplanet.com/add-a-label-into-a-text-input-field-in-a-html-form/">This was a popular design pattern</a>, but when a user clicks or focuses inside the input, the context is now lost, which can be difficult for those with <strong>cognitive disabilities.</strong></li></ul><p><strong>DON’T</strong></p><ul><li>Worry about hiding text from screen readers, and vice versa. For example if you’ve got an error message, no need to create a hidden version that reads out something verbose at the start like <strong>“this is an error message…”</strong>. With the correct markup, this should all be taken care of without having to do extra work and therefore worry about updating multiple text regions in the future. Users of assistive software are generally “power users” of the web and know how to navigate fields in error, etc, so long as they are marked up correctly.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d07e5917b048" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[9 Ways Facebook Can Improve Accessibility]]></title>
            <link>https://blog.prototypr.io/9-ways-facebook-can-improve-accessibility-aa193ee7591a?source=rss-6b830888591f------2</link>
            <guid isPermaLink="false">https://medium.com/p/aa193ee7591a</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[facebook]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[accessibility]]></category>
            <dc:creator><![CDATA[paulcollins]]></dc:creator>
            <pubDate>Fri, 15 Jul 2016 13:17:33 GMT</pubDate>
            <atom:updated>2016-07-17T02:10:17.553Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iY0FWlczF5JsEwqTISdVjA.png" /></figure><p>Facebook are doing <strong>great things for accessibility. </strong>It’s what inspired me to write this article. If you haven’t seen what they’re doing recently, check out my other post: <a href="https://medium.com/@pcollins/5-awesome-things-facebook-is-doing-for-accessibility-d329e390c6b4#.ovts0podn">5 Awesome Things Facebook is Doing for Accessibility</a></p><p>Behind Google, <strong>Facebook</strong> is the second most used website in the world and people with disabilities rely on it heavily to communicate with peers and share thoughts with their loved ones. With this in mind, I wanted to do a case study and come up with <strong>9 ideas</strong>, some simple, some blue sky, to add to the accessibility mission of Facebook…</p><h3>Idea # 1</h3><p>Automatic transcribing of audio on videos, which is then automatically added to the captioning (swear word filter though perhaps!)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/238/1*5ZrKwOk6t66IGXpYvGRNJw.jpeg" /><figcaption>Auto video captioning shown in video menu</figcaption></figure><h3>Idea # 2</h3><p>A set of controls in the settings section to <strong>filter out inaccessible content</strong> such as:</p><ul><li>Hide posts with video that don’t have captioning</li><li>Hide posts with images that don’t have user created Alt text</li><li>Hide posts that contain content with repetitive flashing movement or rapid animation</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*YuTXCr7eBGxUYPUnybA4NQ.jpeg" /><figcaption>Image of accessibility menu</figcaption></figure><h3>Idea # 3</h3><p>The profile icon in the left navigation appears to be missing alt text. Depending on the impact to the code base, you could do one of the following (in order of preference):</p><ol><li>As both links are going to the same place, remove one and wrap a single <strong>HREF</strong> around both image and text. If needing to satisfy <strong>HTML4 doctype requirements</strong>, remove the block element <strong>DIV</strong> inside the HREF and change to a <strong>SPAN</strong>. A preferred option would be to remove the DIV and use <strong>CSS</strong> to float the image to the left.</li><li>Leave two links as they are and add descriptive ALT text specific to the image. For example: <strong>‘Paul Collins profile image’</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M3-z2pzYqWYUMD4W1Arymg.png" /><figcaption>Image showing missing alt text in Chrome developer tools</figcaption></figure><h3>Idea # 4</h3><p>For instances when an image contains text that is blurry or of low contrast, an option to <strong>print a caption of the text below the image</strong>, for people who have low vision, vestibular disorders or other affected conditions and don’t use screen readers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*It-S3bKk_92PamzFHJ0Kqg.jpeg" /><figcaption>“Having trouble reading this” checkbox to print out text below image</figcaption></figure><h3>Idea # 5</h3><p>For people with <strong>Cognitive and Neurological disorders</strong>, an option to break up large blocks of text within posts.</p><p>This could be done with a simple horizontal rule every ‘nth’ paragraph, or perhaps by increasing the text size for a single paragraph every ‘nth’ paragraph. You could even ask users if they’d like to add images or emoticons into their posts to break the flow up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/380/1*0mYDuVvrrxrMKayyCzQ8VQ.png" /><figcaption>Image of page with lots of text, broken up</figcaption></figure><h3>Idea # 6</h3><p>Build on automatic alt text by automatically reading any text within an image and adding to the alt attribute:</p><p>For example: “This image may contain trees and the sky <strong>and may also contain the words ‘Reach for the sky’</strong>”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/406/1*g1E6pxmv3EImoBONHE9EIQ.jpeg" /><figcaption>Image showing HTML code with descriptive alt text</figcaption></figure><h3>Idea # 7</h3><p>The image carousels are difficult to navigate using keyboard only, the following options could help.</p><ol><li>Add <strong>tabindex=”0&quot;</strong> to the two chevrons</li><li>Add <strong>aria-live=”assertive” </strong>to the chevron and using Javascript, change the text according to what the current image is</li><li>Using <strong>Javascript</strong>, detect how many items in carousel and notify user when they’ve reached the end and are about to start again.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/291/1*ehnkfdb5xiPbTv86A4cV4w.jpeg" /><figcaption>Image show CSS rules to highlight images with empty or missing alt text</figcaption></figure><h3>Idea # 8</h3><p>For people who have Vestibular disorders, are Autistic, or have other affected conditions, have an option to slow down animation in videos.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/988/1*vbL0RuQ4WeyNN0BNY-3Y4g.jpeg" /><figcaption>Image showing controls for video speed</figcaption></figure><h3>Idea # 9</h3><p>For new content from third party developers, such as apps, Accessibility issues could be highlighted using <strong>CSS</strong> or <strong>Javascript</strong>. For instance, you could have a CSS rule that highlights all images that contain empty or missing alt attributes on a page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/294/1*5inrlel-H4Xd_OFSW_UCqg.jpeg" /><figcaption>Image show CSS rules to highlight images with empty or missing alt text</figcaption></figure><p>I’ve been advocating for accessibility in my work since I first convinced my boss to send me on a course back in 2002. Facebook and others are doing a lot for accessibility in recent times and it’s inspiring to see A11y being incorporated into modern libraries, frameworks and testing tools. The future is inclusive if we all work together :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/436/1*y3qj8nFWKQTUjl-2r1pl2A.png" /></figure><p><em>I’m currently looking for a job in San Francisco, wanna chat?! Contact me at </em><a href="https://www.linkedin.com/in/paulcollins4"><em>LinkedIn</em></a><em> or </em><a href="http://twitter.com/paulcollins"><em>Twitter</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aa193ee7591a" width="1" height="1" alt=""><hr><p><a href="https://blog.prototypr.io/9-ways-facebook-can-improve-accessibility-aa193ee7591a">9 Ways Facebook Can Improve Accessibility</a> was originally published in <a href="https://blog.prototypr.io/">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 Awesome Things Facebook is Doing for Accessibility]]></title>
            <link>https://blog.prototypr.io/5-awesome-things-facebook-is-doing-for-accessibility-d329e390c6b4?source=rss-6b830888591f------2</link>
            <guid isPermaLink="false">https://medium.com/p/d329e390c6b4</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[facebook]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[accessibility]]></category>
            <dc:creator><![CDATA[paulcollins]]></dc:creator>
            <pubDate>Fri, 15 Jul 2016 13:14:09 GMT</pubDate>
            <atom:updated>2016-07-21T02:04:23.547Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iY0FWlczF5JsEwqTISdVjA.png" /></figure><p><strong>Facebook are doing awesome things for accessibility</strong> and it’s inspiring to see how far they are pushing what can be done to make the web more inclusive. For those who’d like to know more, I wanted to showcase 5 of the most impressive new features here below.</p><h3>1. React Native Accessibility</h3><p>If you haven’t seen the latest, React now comes with a built in Accessibility API that’s insanely easy to use.</p><p><a href="https://facebook.github.io/react-native/docs/accessibility.html">Read about React Native Accessibility here</a></p><p>This video is also a great showcase of the features:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.facebook.com%2Fvideo%2Fembed%3Fvideo_id%3D10153626114103553&amp;url=https%3A%2F%2Fwww.facebook.com%2FFacebookforDevelopers%2Fvideos%2F10153626114103553%2F&amp;image=https%3A%2F%2Fscontent.xx.fbcdn.net%2Fv%2Ft15.0-10%2Fp128x128%2F12672345_10153626145028553_861117336_n.jpg%3Foh%3D6b58467878b919b8042819f2fa33cf26%26oe%3D57F334EF&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=facebook" width="560" height="315" frameborder="0" scrolling="no"><a href="https://medium.com/media/b67c314cbac32570933dc995c6e39060/href">https://medium.com/media/b67c314cbac32570933dc995c6e39060/href</a></iframe><h3>2. HIKE</h3><p><strong>HIKE</strong> is made by Facebook to teach the essentials of Accessibility through simple exercises, breaking down what can be a complicated subject into easy steps. Here’s the <strong>“HIKE”</strong> acronym broken down:</p><ul><li><strong>H </strong>stands for headings and semantic content.</li><li><strong>I</strong> stands for images and non-text content.</li><li><strong>K</strong> stands for keyboard navigation.</li><li><strong>E</strong> stands for a little extra love to build custom components and to address issues of color contrast and text size.</li></ul><p><a href="http://accessibility.parseapp.com/">Read more about HIKE here</a></p><h3>3. Automatic ALT Text</h3><p><strong>Automatic ALT (alternative) Text </strong>uses artificial intelligence to work out what’s contained in an image posted to Facebook. The description is then automatically added to the ALT attribute. It’s such a great idea and hopefully will become the norm for other sites.</p><p><a href="https://code.facebook.com/posts/457605107772545/under-the-hood-building-accessibility-tools-for-the-visually-impaired-on-facebook/">Read more about Automatic ALT Text here</a></p><p>And as a bonus, they recently just made automatic alt text available in 20 languages:</p><h3>Facebook Access on Twitter</h3><p>We&#39;re very excited to announce that Automatic Alt Text is now available in 20+ languages. You can learn more here: https://www.facebook.com/accessibility/posts/1132872003423190 ...</p><h3>4. The Teach Access Tutorials</h3><p>A new Github project pairing with Teach Access. A series of hands on lessons that anyone can contribute to. Making it open source will really help make this a great set of tutorials.</p><p><a href="https://teachaccess.github.io/tutorial/">View the Teach Access Tutorials Here</a></p><h3>5. A Commitment to a More Inclusive Web</h3><p>Finally, Facebook are helping make it clear that <strong>accessibility is important and a fundamental part of the web</strong>. Some further links for Facebook’s Accessibility updates can be found here:</p><p><a href="https://twitter.com/fbaccess">Facebook Access on Twitter</a><br><a href="https://code.facebook.com/accessibility">Facebook Accessibility Toolkit</a><br><a href="https://www.facebook.com/accessibility/">Facebook Accessibility Page</a></p><p><em>I’ve also written an article called </em><a href="https://medium.com/@pcollins/9-ways-facebook-can-improve-accessibility-aa193ee7591a#.fxytij7gr"><em>9 Ways Facebook Can Improve Accessibility</em></a></p><p><em>I’m currently looking for a job in San Francisco, wanna chat?! Contact me at </em><a href="https://www.linkedin.com/in/paulcollins4"><em>LinkedIn</em></a><em> or </em><a href="http://twitter.com/paulcollins"><em>Twitter</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d329e390c6b4" width="1" height="1" alt=""><hr><p><a href="https://blog.prototypr.io/5-awesome-things-facebook-is-doing-for-accessibility-d329e390c6b4">5 Awesome Things Facebook is Doing for Accessibility</a> was originally published in <a href="https://blog.prototypr.io/">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>