<?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 Wayfindr on Medium]]></title>
        <description><![CDATA[Stories by Wayfindr on Medium]]></description>
        <link>https://medium.com/@WayfindrStd?source=rss-c1a4fc3e81a7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*bmmM5Ubw8aNiS6V4OURClg.png</url>
            <title>Stories by Wayfindr on Medium</title>
            <link>https://medium.com/@WayfindrStd?source=rss-c1a4fc3e81a7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 02:33:58 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@WayfindrStd/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[Why openness is key to the Wayfindr Open Standard]]></title>
            <link>https://medium.com/@WayfindrStd/why-openness-is-key-to-the-wayfindr-open-standard-1f112e3ac9be?source=rss-c1a4fc3e81a7------2</link>
            <guid isPermaLink="false">https://medium.com/p/1f112e3ac9be</guid>
            <category><![CDATA[vision]]></category>
            <category><![CDATA[sustainable-development]]></category>
            <category><![CDATA[disability]]></category>
            <category><![CDATA[accessibility]]></category>
            <dc:creator><![CDATA[Wayfindr]]></dc:creator>
            <pubDate>Wed, 05 Oct 2016 15:20:59 GMT</pubDate>
            <atom:updated>2016-10-11T13:19:43.104Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/546/0*Xr01_xkZPbAa7GcA.jpg" /><figcaption>Woman walking with a cane</figcaption></figure><p><em>This is a guest-blog written by </em><a href="https://www.linkedin.com/in/anthonygiannoumis?trk=send_invitation_success_message_name&amp;goback=%2Enpv_ADEAAATuxzEB5*5giyMQvCslJErMNsIYSrGe4oiM_*1_*1_NAME*4SEARCH_6l0l_*1_en*4US_*1_*1_*1_1111071091475580396826_1_1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_vsrp*4people*4res*4name_*1_*1"><em>Anthony Giannoumis</em></a><em>. Anthony is an Assistant Professor of Universal Design at Oslo and Akershus University College of Applied Sciences, and an international research fellow at the Burton Blatt Institute at Syracuse University. Anthony’s research focuses on technology law and policy. He is currently researching the design and implementation of policies aimed at ensuring equal access to technology. Anthony is collaborating with Wayfindr to help promote the use of the Wayfindr standard in practice.</em></p><p>An open standard provides startups, and social enterprises, with an opportunity to empower communities from around the world — by giving them access to information for free. In Wayfindr’s case, it allows them to promote access to society for people with a vision impairment. Wayfindr’s Open Standard is based on three principles, collaboration, quality, and availability.</p><h3>Collaboration</h3><p>When Wayfindr creates their open standard, they use a collaborative process. In other words, businesses, government agencies and public sector organisations have the opportunity to contribute to and initiate standardisation, from the bottom-up.</p><p>This means that standardisation activities are voluntary, that they are <a href="https://www.wayfindr.net/community/">community</a> driven and that they require buy-in and consensus from all relevant parties. These collaborative practices enable Wayfindr to respond to a variety of perspectives and to ensure a fair, reasonably balanced process.</p><p>This results in a standard that represents a variety of interests — rather than a standard that is dominated by one group.</p><h3>Quality</h3><p>By using a collaborative — user centred — process, Wayfindr is also able to create a higher quality standard. The quality of a standard relates to whether — and how — it promotes the interoperability of technology.</p><p>In other words, if a standard is high-quality businesses can use it to create new technologies that can communicate, or fit, with existing products and services.</p><p>By using an open process that focuses on the quality of the standard, Wayfindr is able to help foster an industry — and reward early adopters by creating a network of compatible technologies.</p><p>In addition, Wayfindr can use their open standardisation processes to provide on-going support and maintenance of the standard, feeding advice and consultations from their partners worldwide into future versions of the standard.</p><p>This enables Wayfindr to contribute to the long-term strategic development of audio-based navigation technologies — and to the sustainability of the industry.</p><h3>Availability</h3><p>Wayfindr’s open process provides a unique opportunity to make their standards publicly available. By making the standard available to everyone — <a href="https://www.wayfindr.net/open-standard/#download">free-of-charge</a> — Wayfindr empowers the community to adopt and disseminate the standard around the world.</p><p>By using an open process, Wayfindr maintains the right to publish and reproduce and to give that same right to others that want to use the standard to promote access to society for persons with disabilities.</p><p>These three principles, collaboration, quality and availability, mean that when Anne, who recently got a job at a startup, wants to make sure that her company complies with disability anti-discrimination laws, she’ll be able to use Wayfindr’s standard to ensure that their new product or service is accessible for persons with disabilities.</p><p>It means that when John, who is finishing his engineering degree, decides he wants to create a new product to enable the blind and partially sighted to navigate indoors, he’ll know that his invention will work effectively for persons with disabilities.</p><p>It also means that when Sandra, an industry veteran, wants to pitch a new product line to her supervisor, she’ll be able to assure them that it is compatible with solutions that already exist on the market.</p><p>You can explore the Wayfindr Open Standard <a href="https://www.wayfindr.net/open-standard/">here</a>.</p><p><em>Originally published at </em><a href="https://www.wayfindr.net/reasons-open-standard/"><em>www.wayfindr.net</em></a><em> on October 5, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f112e3ac9be" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[8 times Standards shaped the world]]></title>
            <link>https://medium.com/@WayfindrStd/8-times-standards-shaped-the-world-60f83e318543?source=rss-c1a4fc3e81a7------2</link>
            <guid isPermaLink="false">https://medium.com/p/60f83e318543</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[standards]]></category>
            <dc:creator><![CDATA[Wayfindr]]></dc:creator>
            <pubDate>Fri, 02 Sep 2016 09:59:52 GMT</pubDate>
            <atom:updated>2016-09-16T12:03:14.232Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/718/0*L96HCM62Rk_WeFZm.jpg" /></figure><p>Over the centuries humans have created life-changing inventions that have not only become significant assets by themselves, but have gone on to inspire other creations that many of us use every day. The standards on these ensure uniformity; this means that we can understand how to use a variety of models after learning how to only use one, making each job a little easier.</p><h3>1- Measurements</h3><p>Measurements have literally been around forever, and we couldn’t imagine functioning without them. Whether it’s atmospheric pressure, or the length of our arm, it would be impossible to convey what we meant without some form of measurement scale. Standards in measurement have ensured that we can understand the scale that another person is using.</p><h3>2- Screws</h3><p>They may be small, but screws have become pivotal to our lives. The mechanical advantage of using one has helped us to fix materials, attach one thing to another and create pulleys. The strength and size has meant that they are currently the most commonly used device in engineering and production.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*0VmmFQ5GxDF7f0Hy.jpg" /></figure><h3>3- Light Bulbs</h3><p>Perhaps we wouldn’t be living in complete darkness without the lightbulb, but it has certainly been an extraordinary invention. It was only after its creation that we started to have electricity sent to our homes, creating a network and industry large enough for other inventions to be developed. With our surroundings illuminated, our lifestyles changed as we began to spend longer hours awake completing activities such as reading, increasing higher education enrolment levels around the world.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*cfILy_-uV4QcqfYD.jpg" /></figure><h3>4 — Shipping Containers</h3><p>It used to be that when you were shipping something from one country to another, each box, barrel, or bucket would need to be individually loaded and unloaded. Can you imagine how much time that must take when you’re sending large orders? Freight companies eventually overcame this by developing Intermodular Containers which could be easily moved from rail, to boat or vice versa. This standardisation allowed them to make the most of the space that they had.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*XEuxPQobnH10Z_Ve.jpg" /></figure><h3>5 — HTML</h3><p>HTML: the programming language that allows us to write this blog post. HTML provides a standard format for webpages, and lets us upload text, photos and links. Through this, we have been able to share information with people all around the world, enabling us to gain knowledge and understand other cultures. It has completely transformed the way we think.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*khsbJScGPtvY2Q3D.jpg" /></figure><h3>6 — W3C accessibility</h3><p>W3C accessibility has meant that the barriers between internet users have been cleared. It is crucial that everyone is able to have access to the wealth of information stored on the Internet, including people with disabilities. The web is designed to help everyone and W3C accessibility ensures that that is the case by increasing flexibility for all.</p><h3>7 — USB</h3><p>USB devices are used to share documents across computers. Imagine if on every laptop, or desktop, the creator installed a different socket and device to be used to exchange data. Through standard USB devices, our data has been kept safe and secure, and small enough to take anywhere.</p><h3>8 — Food Standards</h3><p>Hardly a week goes by without a news story on concerns with food safety in a supermarket chain, or a scandalous incident in a restaurant. Standards have ensured that these have been reduced to the minimum, keeping everyone safe in the kitchen and out of it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*4OCHpN4O4VuY_Zfj.jpg" /></figure><p><em>Originally published at </em><a href="https://www.wayfindr.net/8-times-standards-shaped-the-world/"><em>www.wayfindr.net</em></a><em> on September 2, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=60f83e318543" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How we created our IxDA Awards submission]]></title>
            <link>https://medium.com/@WayfindrStd/how-we-created-our-ixda-awards-submission-69615c36b59e?source=rss-c1a4fc3e81a7------2</link>
            <guid isPermaLink="false">https://medium.com/p/69615c36b59e</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[awards]]></category>
            <category><![CDATA[interaction]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Wayfindr]]></dc:creator>
            <pubDate>Tue, 30 Aug 2016 09:14:27 GMT</pubDate>
            <atom:updated>2017-05-11T21:42:20.683Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*XfnERNQmIzhUhkFvWZlnBA.png" /></figure><p>With two team members with a background in Interaction Design, including our CEO Umesh Pandya, entering the IXDA awards in 2015 just felt like the right thing to do. The submission required a video component, which allowed us the freedom to present our project in the way we wanted, with our own voices. We already had a video, which we made to communicate the concept of Wayfindr, and we used this as a starting point. We took this footage and refined the talking heads, to help tighten up the messaging, and then — with the help of a video editor — we came up with our submission video.</p><p>When we won the IxDA Awards 2016 for Best in Empowering and Best in Show it was a truly remarkable moment for all of us on the Wayfindr team. We have been working on the Wayfindr Open Standard for two years now and while we believe that what we are doing is important it was gratifying to see that other people believed in us as well.</p><p>Wayfindr’s mission is to empower people to navigate the world independently, so winning the Empowering award felt like a real acknowledgement of that mission. We have always been a driven team but this gave us an extra push to keep working hard to ensure that the Open Standard is adopted globally.</p><p>The IxDA Awards are important for drawing attention to all manner of innovations that are going on in the tech space. We met so many people who are doing amazing things to try and improve the world through technology and seeing their devotion to it felt like a reflection of our own.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=69615c36b59e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Built-in smart phone accessibility increases my independence and awareness]]></title>
            <link>https://medium.com/@WayfindrStd/built-in-smart-phone-accessibility-increases-my-independence-and-awareness-8ea1518dfe3f?source=rss-c1a4fc3e81a7------2</link>
            <guid isPermaLink="false">https://medium.com/p/8ea1518dfe3f</guid>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[independence]]></category>
            <dc:creator><![CDATA[Wayfindr]]></dc:creator>
            <pubDate>Tue, 23 Aug 2016 13:22:06 GMT</pubDate>
            <atom:updated>2016-09-05T14:33:32.774Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k10ar6ljtVAL03aTUG92BQ.jpeg" /><figcaption>Ben Mustill-Rose</figcaption></figure><p><em>This guest blog post was written by </em><a href="https://twitter.com/bmustillrose"><em>Ben Mustill-Rose</em></a><em>. Ben works at the BBC as a Developer In Test for mobile iPlayer in Salford where he helps maintain the teams servers &amp; writes internal tooling. He can also be found giving accessibility advice to other teams in the organization or helping kids to code / teaching them about STEM. Outside of work he is a keen swimmer and enjoys brewing cider.</em></p><p>On a rainy day, some time in 1998, my family purchased its first computer amidst murmurings of needing to “manage our accounts” and “get connected to the internet”. By and large this was a successful endeavour. My brother and sister spent some time each evening playing some carefully selected educational games, my dad discovered a love for Solitaire, and my mum switched from writing her letters by hand to electronically — almost overnight.</p><p>The spanner in the works came in the form of me. While at the time I was able to see colours, and could just about guide other blind people, I was — in a medical sense — totally blind. It was clear that I wasn’t getting as much out of the computer as the rest of the family were. After a few months it was decided that this would not do and it was declared that my parents would do whatever it took to make sure that I could enjoy the computer in the same way that everyone else was. Shortly after this they became acquainted with the prices of assistive technologies (£1000 for a screen reader that would make the computer talk, and £6000 for a device that would let me read printed materials) and were noticeably less keen on the idea.</p><p>Having not been taught to read print, the next 1.5 years or so found me making do with keeping my face close to the screen and learning to associate various “pictures” / “squiggles” (icons and pieces of text respectively) with actions. E.g. I had no idea that the button on the left of the taskbar was called start, but I knew that the darker part (black text on a grey background) on the bottom left of the screen would give me more options if I clicked it. It was only after a friend stepped in to help that we were finally able to procure a screen reader, although in the future I would use the association technique to make my first game and reinstall Windows.</p><p>Fortunately, its 2016 now and the outlook’s nowhere as bleak as it once was, as all of the most popular computer operating systems have various options for a free screen reader. if you’re running Windows you can use <a href="https://support.microsoft.com/en-gb/help/17173/windows-10-hear-text-read-aloud">Narrator</a>, a comparatively basic but still useful screen reader from Microsoft. Then there’s <a href="http://www.nvaccess.org/">NVDA</a>, a more fully-featured option, or if you have a copy of Microsoft Office 2010 you can use <a href="http://www.windoweyesforoffice.com/">Window-Eyes </a>for free. Mac OS includes <a href="http://www.apple.com/uk/accessibility/osx/voiceover/">VoiceOver</a> and Linux derivatives have <a href="https://wiki.gnome.org/Projects/Orca">Orca</a>, amongst others.</p><p>The mobile landscape’s just as impressive. iOS also has a version of <a href="http://www.apple.com/uk/accessibility/ios/voiceover/">VoiceOver</a>, Android has <a href="https://support.google.com/accessibility/android/answer/6283677?hl=en-GBandref_topic=3529932">TalkBack</a> and Amazon’s range of Fire devices have “<a href="https://www.amazon.co.uk/gp/help/customer/display.html?nodeId=201829330">VoiceView</a>”, all of which are free once again.</p><p>The decreasing cost of hardware accompanied by the proliferation of free screen readers is opening up the world of computing to more and more people as time goes on. The cost of making our computer accessible to me in 1998 was £1000 + an extra £1000 for the computer itself. Now you can purchase an <a href="https://www.amazon.co.uk/dp/B00Y3TM6CO?ref=spkl_6_1_940009367andqid=1470754756andpf_rd_p=940009367andpf_rd_m=A1F83G8C2ARO7Pandpf_rd_t=301andpf_rd_s=desktop-auto-sparkleandpf_rd_r=CHP3KE9K6RJTZZC0QTYCandpf_rd_i=fire+tablet">Amazon Fire Tablet</a> for under £50, which delivers a more than adequate accessibility experience out of the box. That represents a staggering 97.5% reduction in price and the experience that a Fire delivers is arguably better than that of our first computer!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W-TRSUgdHZX6tf01pqcWlA.jpeg" /><figcaption>Ben Mustill-Rose sitting at his desk working on a computer</figcaption></figure><p>One side effect of the increase in promotion of accessibility is the disruption of the assistive technology software industry. No longer are blind people dependant on expensive tools from established software vendors — instead we now have access to a wide variety of inexpensive applications geared towards improving our quality of life, some of which have replaced dedicated hardware devices.</p><p>Now that I am able to <a href="http://www.applevis.com/guides/braille-ios-voiceover/guide-braille-screen-input-ios">write braille on my phone</a> I have much less of a need for my faithful but clunky Perkins brailler. Apps like <a href="http://www.knfbreader.com/">KNFB Reader</a> allow me to read printed materials independently, which increases my autonomy and privacy. If I have a tin of something or other — and I don’t feel like playing some weird game of culinary roulette — <a href="http://www.taptapseeapp.com/">I can now identify it,</a> without opening it.</p><p>Navigation apps such as <a href="http://blindsquare.com/">BlindSquare</a> help me travel independently, as opposed to being the person that my friends have to pick up — and if we go to a restaurant I can now <a href="https://www.abbyy.com/news/abbyy-amedia-partnership-creates-ocr-reader-app-for-the-visually-impaired/#sthash.rSbjtajg.dpbs">read the menu</a> myself. The increase in accessibility of apps like <a href="http://iplayerhelp.external.bbc.co.uk/tv/mobile_iplayer">iPlayer</a> means that I don’t have to feel left out when sighted people are talking about the latest programme that everyone’s watching and colour identification apps like <a href="https://itunes.apple.com/us/app/colorvisor/id511093568?mt=8">Colorvisor </a>go some way towards making sure that the clothing combinations I wear out are relatively sensible. Those apps are just the tip of the iceberg really, but I hope they have helped illustrate just how transformative the increased awareness of blind people and our requirements has been.</p><p>The above paragraph would probably be a nice way to end this post; it paints an incredibly palatable, ‘all is good in the world’ type picture of how things are in 2016 for blind people and it’s not at all inaccurate. However, if we delve a bit deeper, there are several aspects of the above referenced “transformation” that I feel should be of concern to blind people everywhere.</p><p>For most blind people who are looking to purchase a smartphone it’s a given that it will be an iPhone. Even if we put aside my opinion that VoiceOver is actually getting worse over time, it really worries me that so many blind people are dependent on a screen reader that <a href="http://www.macobserver.com/tmo/article/tim-cook-soundly-rejects-politics-of-the-ncppr-suggests-group-sell-apples-s">Apple appears not to make money on </a>. What would happen if one day Apple decided that money does matter after all?</p><p>I currently use NVDA around 50% of the time at work — it’s a great tool and I only see my usage of it increasing. However, I worry that this piece of software that is arguably essential to my role is <a href="http://www.nvaccess.org/about/our-story/">only developed by 2 people</a>. As more and more people come to rely on this screen reader I can’t help but wonder what the consequences would be if even one of the developers — for whatever reason — chose not to continue with the project.</p><p>These worries aside, it’s undeniably a great time to be blind. Technology has allowed me to be more independent than ever before and the overwhelming majority of it is completely mainstream, which drives down prices and helps to foster inclusion. The next 10 years will be incredibly interesting, partly because of the amount of disruptive technologies that will surely appear and partly because of the amount of antiquated companies that will disappear. I can’t wait to see what will happen!</p><p>I’d like to thank Wayfindr for giving me the opportunity to guest on their blog and you, the reader for taking the time to read my post.</p><p>You can explore the Wayfindr Open Standard <a href="https://www.wayfindr.net/open-standard/">here</a>.</p><p><em>Originally published at </em><a href="https://www.wayfindr.net/smart-phone-accessibility-increases-my-independence/"><em>www.wayfindr.net</em></a><em> on August 23, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8ea1518dfe3f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating a sonic identity for Wayfindr]]></title>
            <link>https://medium.com/@WayfindrStd/creating-a-sonic-identity-for-wayfindr-3dcaf0b87bc0?source=rss-c1a4fc3e81a7------2</link>
            <guid isPermaLink="false">https://medium.com/p/3dcaf0b87bc0</guid>
            <category><![CDATA[audio]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[branding]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Wayfindr]]></dc:creator>
            <pubDate>Fri, 12 Aug 2016 11:31:36 GMT</pubDate>
            <atom:updated>2016-08-23T10:33:43.006Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XX1oIcW3BPkayVYm.jpg" /></figure><p><em>This guest blog is written by </em><a href="https://www.linkedin.com/in/henrydaw?authType=name&amp;authToken=B_vn"><em>Henry Daw</em></a><em>, an experienced sound designer and audio branding consultant, based in London. He previously worked for 13 years as an in-house sound designer, for Nokia and later Microsoft, where he composed for billions of devices worldwide whilst overseeing Nokia’s world-renowned audio brand for over a decade. Henry has also worked extensively on user interfaces, working closely with UX, UI, interaction, and motion designers, whilst bringing sound to the forefront of the design process. Following on from Henry’s work for the</em><a href="http://www.citiesunlocked.org.uk/"><em> Microsoft Cities Unlocked</em></a><em> project, which aims at providing a navigational aid for the blind using binaural audio, he became involved with Wayfindr late last year.</em></p><p>The cities of today are notoriously hectic, full of potential hazards, and noisy; from the seemingly non-stop traffic, to the everyday clatter of pedestrians. The majority of people are able to confidently navigate their way through this sonic urban jungle; but what if you had very limited vision or couldn’t see at all? For the 285 million vision impaired people around the world, this is an everyday challenge. Research has suggested that many vision impaired people avoid this by staying at home or sticking to a route they are familiar with. The Wayfindr Open Standard aims to address this by ensuring a consistent navigational experience using clear auditory cues. Late last year, after being put in contact with Umesh Pandya. I was thrilled to join this fantastic project, providing sound design support whilst laying the foundations for a unique sonic identity. I’d like to share with you how that sonic identity came together.</p><h3>Wayfindr Sound Needs</h3><p>The first task was to establish the immediate sound needs for the Wayfindr Open Standard. The voice instructions would be native to the OS, and thus out of our control, but immediately prior to each voice instruction there would be a short notification alert. In the majority of cases it would be a short <strong>general notification alert</strong>, except when you’re about to hear the last voice instruction on your scheduled journey. In which case you will hear the <strong>journey completed notification alert</strong>. In early trials of Wayfindr there was just one placeholder sound, to be used in all instances, but feedback suggested an additional sound for journey’s end was needed. Additional sounds could potentially be added to the Wayfindr Open Standard later, as it is developed, but for the first draft release of the Open Standard there would only be the two sounds, and together with the close relationship between them this would form the core audio brand.</p><p>For the early concept work I focused on the general notification alert. The existing placeholder sound, which Umesh had grabbed from a free online resource, was used as the basis for a lot of the work. The existing sound was based on a synthetic marimba instrument — it was a harsh tone that lacked character, yet during the trials it was shown to be working — functionally — quite well.</p><h3>Sound Design Principles</h3><p>I felt the new sounds wouldn’t need to be radically different from what we already had. Functionality was after all the key factor, so it was a matter of re-designing the sounds to reflect the user-driven design principles and brand character of the Wayfindr experience. The Wayfindr brand was yet to be properly developed (Moving Brands would work on the visual and physical branding later on) but, for my work, I highlighted some key words that I felt the sounds needed to reflect:</p><h3>Functional<br> Confident<br> Humble<br> Modern<br> Friendly</h3><p>Another major consideration was the fact that the sounds were created as part of an Open Standard — sounds that were freely available for use by third parties and developers. After initially exploring the option of retaining a marimba tonality but making it more natural and organic, my attention began to turn towards a more neutral tonality. I focused on a synthetically pure sound, a sound that didn’t necessarily evoke any associations, something that would invariably be the case when using an ‘instrument’ such as a marimba. We would of course be encouraging other brands to use the Wayfindr sounds, so anything too bold or ‘characterful’ had the potential for branding conflicts. A more neutral tone to the sounds and they should fit seamlessly into any third party service.</p><h3>Coherent Pair</h3><p>In the next iteration of sound design work, I focused on the notification alert for “Journey Completed”. Both the general, and journey completed, notification alerts would be created as a coherent pair. Sounds that will typically be similar in tonality or instrumentation (sharing design principles that contribute to a consistent UX), but varied enough in their form to communicate a specific function. Paired sounds are common practise, especially in the context of smartphones — renowned examples include the “Listen” and “Confirmation” sounds used for the personal assistant “Siri” in Apple iOS, or the similarly paired “Google Now” sounds. Other examples of paired UI sounds typically include an on and off, lock and unlock, and connect and disconnect pairing. For the paired Wayfindr sounds, the general notification alert would consist of two notes, and the journey end of three notes. This relationship between the two alerts would form a key part of the DNA, which later on would feed into the work by Moving Brands.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LvsEJqxqXt1-kh8P.jpg" /></figure><h3>Audio Branding</h3><p>When Moving Brands started their work with Wayfindr, we had some workshops around the visual and physical aspects of the brand. We also talked about ideas around a “sound mnemonic” (or audio logo) to use with a logo animation. I was cautious against creating a completely new sound, for which it’s primary role was likely to be in marketing. To me it didn’t really feel aligned to the “user-driven” principles that Wayfindr aspires to. However, if we created an ‘additional’ sound that simply consisted of the two notification sounds together, as one sound playing after each other, this would link well to the actual user experience, and also strengthen the brand recognition. In the future there is also potential for it to become some kind of accreditation sound — for example, you walk into a shopping centre and the first sound you hear will be the “accreditation sound” so that you know it is Wayfindr supported.</p><h3>User Testing</h3><p>After discussions with the Wayfindr team and Moving Brands, we narrowed down our notification pairings to two different concepts, which we would then test and compare. For these elements, including the audio logo, Moving Brands arranged a sit-down session with users to talk about the brand. To test the notification alerts, we had a user testing session in Old Street Underground station. The testing brought up some useful insights such as a need to differentiate the Wayfindr notification alerts from the native phone sounds. Although users preferences and tastes were different, both concepts were received favourably, and reactions to the additional “journey completed” alert were positive. After discussions with Moving Brands and the Wayfindr team, the final concept was selected.</p><h3>Final Sounds</h3><p>Functionally, the selected pairing worked well — it was sufficiently alerting, yet subtle enough to not cause undue alarm. The pairing between the sounds also linked perfectly, and just felt right, with the identically pitched two notes for the general notification and the rising-pitched three notes for the journey completed notification. As the Wayfindr brand took on a really fresh and exciting look and feel, the match-up between the sounds and the logo animation also began to take shape. After some subtle editing to ensure the two sounds linked seamlessly, the end result was a logo animation that we were all happy with. My final task (prior to the first draft release of the Open Standard) was to ensure the Wayfindr Guidelines Document accurately reflected my work with the notification alerts. To assist any third parties or developers who use the Open Standard, it’s vital that we clearly communicate the principles and thinking behind the notification sounds — communication is obviously one of the key factors behind the successful adoption of an Open Standard.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FtOonn43wI2k%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DtOonn43wI2k&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FtOonn43wI2k%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/58aef6dc902809387c8f62cd7b4d7806/href">https://medium.com/media/58aef6dc902809387c8f62cd7b4d7806/href</a></iframe><h3>Just the Beginning</h3><p>Wayfindr is very much at the beginning of its journey, and I find it tremendously exciting to envisage how far it will go. Just imagine a future urban environment that was fully accessible to the vision impaired, based on a consistent audio navigation experience. I’m humbled and privileged to be involved, especially when I reflect on how important sound is to the everyday life of someone who cannot see. Using the Wayfindr platform and community, there is a fantastic opportunity to foster new ideas using sound, and collectively work towards developing the Standard. I’d welcome anyone who has an interest in audio-based navigation to get in touch and join the community. Ideas we’ve already discussed for the future involve the addition of a ‘warning alert’, specific categorized sounds, or even enhanced auditory experiences such as subtle changes in audio feedback as your journey progresses. As we are now though, it feels as if we have built a solid core audio brand and UX for Wayfindr going forward. The Wayfindr audio DNA is born, now let’s make it grow.</p><p>You can explore the Open Standard <a href="https://www.wayfindr.net/open-standard/">here</a>.</p><p><em>Originally published at </em><a href="https://www.wayfindr.net/creating-sonic-identity-wayfindr/"><em>www.wayfindr.net</em></a><em> on August 12, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3dcaf0b87bc0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[6 reasons Wayfindr is an Open Standard, not an App]]></title>
            <link>https://medium.com/wayfindr/6-reasons-wayfindr-is-an-open-standard-not-an-app-74c6f28af9bb?source=rss-c1a4fc3e81a7------2</link>
            <guid isPermaLink="false">https://medium.com/p/74c6f28af9bb</guid>
            <category><![CDATA[indoor-navigation]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[open-standards]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Wayfindr]]></dc:creator>
            <pubDate>Thu, 04 Aug 2016 16:21:57 GMT</pubDate>
            <atom:updated>2016-10-11T13:27:09.406Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/784/1*OilHaj0QLE9JcAHlhZI1Kg.png" /><figcaption>Wayfindr Logo</figcaption></figure><p>When <a href="https://medium.com/@ustwo">ustwo </a>and the RLSB Youth Forum <a href="https://www.wayfindr.net/wayfindr-beginning/">started working on the project</a> which became Wayfindr, we saw the solution as an app. As our understanding of what we needed to do developed, we made the decision to move further than an app and to develop an Open Standard instead. Here’s why:</p><h4>1 — We Want to Stay Neutral</h4><p>In order to build the Open Standard we need to work with lots of different stakeholders. We need them to help us test the Open Standard, to offer their buildings to be used in trials, and to be part of our Community. We want to create a space for them to join forces so that we can create the Open Standard together.</p><h4>2 — Ensure Blind People Have A Consistent, Seamless Experience</h4><p>In order to build confidence in the technology, vision impaired people need a level of consistency across every navigation app that they use. If the directions, e.g. the timing and language, vary from one service to another, and between each environment, then users could become confused. Creating an Open Standard will allow anyone who builds an audio-based navigation app to be working with the same tools to ensure that no matter where the user is, or where they’re going, they will get the same experience — every time.</p><h4>3 — To Build Trust Across Services</h4><p>When you use a Sat Nav and it tells you to turn left when there’s no visible turning you know that you don’t — immediately — have to make that turn. If you are partially sighted or blind then this is more difficult. A user has to be able to trust that the instructions that they have been given are correct every time they use it. Our rigorous testing and iterative design ensures that this will be the case. Every user will be able to navigate in the same way, with any product made using the Open Standard.</p><h4>4 — There Are Already Amazing Navigation Products Available</h4><p>There are already various mainstream navigation apps on the market. Rather than try and compete with them we decided that it would be better to take our own expertise and use it to work with them to achieve our goal. By creating an Open Standard it means that these companies can use it to build audio-navigation into already existing apps. Which leads to…</p><h4>5 — Giving Vision Impaired People As Much Choice As Anyone Else</h4><p>We don’t want to limit VI people to using just one app. Accessibility shouldn’t be the only reason that they use it. They should want to use an app, or service — because it’s right for them — or because they like the company that has made it, not because it’s the only thing available.</p><h4>6 — We Want Wayfindr to go Global</h4><p>We are a small team with big dreams — we know Wayfindr has the potential to change millions of lives and we can’t expect to do that alone. Also, we don’t want to just limit it to VI people, anyone could use it if they need help navigating an unfamiliar and busy train station, or a large shopping mall. We want to give people the tools to take this forward and make it go global.</p><p>You can explore the standard further <a href="https://www.wayfindr.net/open-standard/">here</a>.</p><p><em>Originally published at </em><a href="https://www.wayfindr.net/6-reasons-wayfindr-open-standard-not-app/"><em>www.wayfindr.net</em></a><em> on August 4, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=74c6f28af9bb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wayfindr/6-reasons-wayfindr-is-an-open-standard-not-an-app-74c6f28af9bb">6 reasons Wayfindr is an Open Standard, not an App</a> was originally published in <a href="https://medium.com/wayfindr">Wayfindr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Accessibility CoderDojo at The London Transport Museum]]></title>
            <link>https://medium.com/@WayfindrStd/accessibility-coderdojo-at-the-london-transport-museum-a321051f43bb?source=rss-c1a4fc3e81a7------2</link>
            <guid isPermaLink="false">https://medium.com/p/a321051f43bb</guid>
            <category><![CDATA[vision]]></category>
            <category><![CDATA[coderdojo]]></category>
            <category><![CDATA[accessibility]]></category>
            <dc:creator><![CDATA[Wayfindr]]></dc:creator>
            <pubDate>Mon, 18 Jul 2016 13:18:23 GMT</pubDate>
            <atom:updated>2016-07-28T13:37:52.284Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*0weg7JC8KsO-T7Hw.png" /></figure><p>We had a great day at The London Transport Museum on July 2nd. We were working with <a href="https://www.facebook.com/accessdojo">Accessibility CoderDojo</a> (sponsored by Thomson Reuters and Sales Force) as part of the <a href="http://www.ltmuseum.co.uk/whats-on/exhibitions?gclid=CLPu5tWR_c0CFSco0wodmQ4Mfw">Designology</a> exhibition they are running. We had 10 children, and several students, come in and work with us over the weekend to help create a digital accessibility trail.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*utrSRJykJmyhh34U.jpg" /></figure><p>They used <a href="https://www.microbit.co.uk/">BBC micro:bits</a> to create a digital tour of the museum, using sound to ensure it was accessible to vision impaired people. The whole idea was to demonstrate the power of the Open Standard to museum visitors, getting them to think about how they move around a space, what directions and information they need and how it is transmitted to them.</p><p><em>Below is a Storify of the reactions from people who attended, as well as a short video created for the event.</em></p><p><a href="https://storify.com/WayfindrStd/wayfindr-and-coderdojo-at-the-london-transport-mus">Wayfindr and CoderDojo at The London Transport Museum (with images, tweets) · WayfindrStd</a></p><p>It was inspiring to see the kids getting so engaged and excited about coding. Some of them had never tried it before so not only was it fun but they were able to get something educational out of it as well. We treated the exercise like a treasure hunt, with each child using their micro:bit to guide their partner around the museum while they wore a blindfold, to help them connect with what it would be like for a vision impaired person visiting The London Transport Museum.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*Lezp1eCsD7E5KsZc.jpg" /></figure><p>If you want to come and see what we have been up to for yourselves then you can attend The London Transport Museum Late Debate: Social behaviour and mapping event on Thursday 28th July. You will be able to go on an accessibility trail around the museum using the BBC micro:bits the kids coded in the CoderDojo session.</p><p><em>Tickets to the Late Debate cost £12 (£10 concessions) and are for adults only (18+), you can buy them </em><a href="http://www.ltmuseum.co.uk/whats-on/events-calendar#latedebates"><em>here</em></a><em>.</em></p><p><em>Originally published by </em><a href="https://twitter.com/DevineWrites"><em>Andy Devine</em></a><em> at </em><a href="https://www.wayfindr.net/accessibility-coderdojos-london-transport-museum/"><em>www.wayfindr.net</em></a><em> on July 18, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a321051f43bb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Wayfindr will increase my confidence and independence]]></title>
            <link>https://medium.com/@WayfindrStd/how-wayfindr-is-increasing-my-confidence-and-independence-3f789de3eb0a?source=rss-c1a4fc3e81a7------2</link>
            <guid isPermaLink="false">https://medium.com/p/3f789de3eb0a</guid>
            <category><![CDATA[vision]]></category>
            <category><![CDATA[navigation]]></category>
            <category><![CDATA[transportation]]></category>
            <category><![CDATA[london]]></category>
            <dc:creator><![CDATA[Wayfindr]]></dc:creator>
            <pubDate>Wed, 13 Jul 2016 15:01:33 GMT</pubDate>
            <atom:updated>2016-10-11T13:29:01.725Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*wr4K6zldWovPfK3F.jpg" /><figcaption>Courtney using the tube</figcaption></figure><p>Courtney Nugent is 26 and has been vision impaired since she was three. She has been involved with the <a href="http://www.rlsb.org.uk/about-us/whos-who/youth-forum">Royal London Society for Blind People’s (RLSB) Youth Forum</a> since its inception in 2013 until she turned 25 last year. We spoke to her about her experience taking Wayfindr from an idea in a Youth Forum meeting a few years ago to reality.</p><p>The RLSB brought the Youth Forum together in 2013. There were eight vision impaired people, coming together twice a month to talk about issues that they had with every-day living and social perception as a person with a vision impairment. In 2014 they released their <a href="http://www.rlsb.org.uk/wp-content/uploads/2015/06/RLSB-Youth-Forum-Manifesto-28-Feb-WEB.pdf">Youth Manifesto</a> which laid out solutions to the challenges they face as blind young people in London. Later that year they released their<a href="http://www.rlsb.org.uk/wp-content/uploads/2014/10/Lets-Work-It-Out-PDF.pdf"> employment pack</a>, both of which they presented to parliament. One of the big issues that they had was with transport, and independent travel. This is where the <a href="http://www.rlsb.org.uk/tech-hub/wayfindr">idea for Wayfindr</a> came from.</p><blockquote>(Working on Wayfindr) was amazing! We were involved in it right up to the time it was launched, so we were always active with our ideas — and the aim of it — and how we wanted it to work.</blockquote><p>At the moment Courtney uses her white cane to get around. When she wants to use the tube she gets assistance from a member of the Transport for London (TfL) staff, at the ticket barrier. Although sometimes she may have to wait for a few minutes, this assistance is vital, without it big stations like Euston would be out of bounds for her. She wouldn’t attempt to navigate on her own because she feels there are too many people. Wayfindr will ensure that these types of journey are made easier for Courtney as she will be able to decide if she wants to wait or if she’ll just put on her headphones and go.</p><blockquote>It’s been a great project to work on as it’s increased my confidence and independence. The team have made sure they’ve asked us how we’ve found using Wayfindr, if we have difficulties with it, what we liked about it, even down to the voices that they use and the sounds that come out of the demonstration app. It’s been a good working partnership.</blockquote><p>If, as we hope, the Wayfindr Open Standard is rolled out across the TfL network Courtney is looking forward to making an independent journey through a station she already knows. The core idea of Wayfindr has always been about empowering blind and partially sighted people to travel independently.</p><blockquote>The first time testing (Wayfindr) at Pimlico was like we were just ‘normal people’ — well — we are normal people but we were just able to travel on our own through a station, without another human being there to help us. I like to travel, so being able to travel through Euston station alone would be incredible.</blockquote><p>To find out more, <a href="http://www.wayfindr.net/open-standard">explore the Wayfindr Open Standard</a>.</p><p><em>Originally published at </em><a href="https://www.wayfindr.net/wayfindr-increasing-confidence-independence/"><em>www.wayfindr.net</em></a><em> on July 13, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3f789de3eb0a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Audio navigation opening up London to the vision impaired]]></title>
            <link>https://medium.com/@WayfindrStd/this-piece-was-written-by-umesh-pandya-and-originally-published-on-virgin-com-6568ef7af354?source=rss-c1a4fc3e81a7------2</link>
            <guid isPermaLink="false">https://medium.com/p/6568ef7af354</guid>
            <category><![CDATA[wayfindr]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[beacons]]></category>
            <category><![CDATA[vision]]></category>
            <category><![CDATA[ibeacon]]></category>
            <dc:creator><![CDATA[Wayfindr]]></dc:creator>
            <pubDate>Fri, 17 Jun 2016 13:15:30 GMT</pubDate>
            <atom:updated>2016-07-14T15:50:56.445Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This piece was written by </em><a href="https://medium.com/@the_uMe"><em>Umesh Pandya</em></a><em>, and originally published on </em><a href="https://www.virgin.com/virgin-unite/audio-navigation-opening-london-vision-impaired"><em>Virgin.com</em></a><em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QqSlOazy-jIS9r-DQ7L6tg.jpeg" /><figcaption>Courtney, Joy, and Ruskana</figcaption></figure><p>As a Londoner born and bred, taking the Underground is second nature to me; it has always been a part of my life. A warren of tunnels and trains, it has opened up my city to me and everyone I know, whether for work or leisure.</p><p>I stopped taking the tube for granted and my life course changed two years ago when I met a group of people who found themselves excluded from travelling independently, despite having grown up in the city too.</p><p>The <a href="http://www.rlsb.org.uk/about-us/whos-who/youth-forum">Royal London Society for Blind People’s Youth Forum</a>, made up of vision impaired Londoners, wanted to be able to travel around their city as freely as their sighted peers. And whilst they were able to get sighted guide assistance from the TfL staff, what everyone really wanted to do was travel on their own — they wanted the freedom to be able to get to work, college and see their friends when they wanted to. They saw their smartphones as a potential solution.</p><p>After learning of their situation I decided to offer the group the assistance of ustwo, the digital product studio where I worked as associate user experience director, to explore potential solutions to this problem.</p><p>As part of ustwo’s pro bono Invent Time program, I led a small group of designers and developers working for a month on the project. We settled on using versatile Bluetooth Low Energy (BLE) beacons and a prototype smartphone app that we designed to deliver audio navigation instructions such as ‘Turn left’ or ‘You are now at the ticket barriers’. We took the system to Transport for London which agreed to host trials at London Underground stations, <a href="http://www.bbc.co.uk/news/health-31757593">generating much excitement </a>in 2015 in the process.</p><p>We soon came to appreciate that the prize could be much larger and that emerging technologies such as Bluetooth Low Energy (BLE) Beacons could be deployed across any indoor setting from museums to shopping centres and hospitals, creating a network that could open up a city to vision impaired people: The potential demand is huge globally, with 285 million vision impaired people across the world.</p><p>We also started thinking about how we could use the experience we had collectively gained on the project to have the most impact globally. Despite coming from a digital production studio, in the business of creating apps both for clients and our own ventures, we decided to expand on this and go one step further. We identified a pressing need to develop a consistent standard across wayfinding systems, which others could adopt to facilitate the spread of this technology.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R1T3G3I2vGj1_8tribPByA.jpeg" /><figcaption>Joy using Wayfindr at Euston</figcaption></figure><p>The <a href="https://www.virgin.com/virgin-unite/www.wayfindr.net">Wayfindr</a> Open Standard aims to do just that, by standardising the way audio navigation instructions are delivered through smartphones. Together with the RLSB, we set up Wayfindr as a joint venture — <a href="http://google.org/">Google.org</a> saw the potential and donated $1m to accelerate our work in December 2015.</p><p>Built on a foundation of rigorous user research Open Standard, which launched on May 13 2016, gives venue owners and digital navigation services the tools to implement high quality, consistent audio wayfinding solutions. It includes an open-source demo app that enables people who download it to use BLE beacons to understand and implement systems with real users, in real contexts and in real time.</p><p>We originally set out with the ambition to change access to transportation in London for blind and partially sighted people — but we discovered a much larger opportunity, namely creating the conditions for beacon and smartphone navigation systems to appear everywhere.</p><p>The story does not end there however, indoor navigation technology can play out in many other contexts, consider the Underground in isolation. You have four million passengers travelling on it every day, among them:</p><ul><li>First time visitors to the city, some who speak other languages</li><li>People with cognitive impairments, who may need a level of reassurance</li><li>Commuters and Londoners who may want to get from A to B even faster</li></ul><p>A system built using the Wayfindr Open Standard would support all of these needs. Apps could provide audio or written directions in tourists’ native languages, allow users to preview instructions before they travel to build confidence and provide reassurance to every traveller that they are on the right track.</p><p>We have set up the Wayfindr Community of venue owners, digital navigation product makers and technologists, experts in vision impairment and other interested parties to take these systems into every setting.</p><p>I look forward in particular to making progress for vision impaired people in the UK, where almost half want to leave their homes more often to be fully engaged in employment and socialising. Everything that we take for granted when we hop on the tube.</p><p>To find out more, <a href="http://www.wayfindr.net/open-standard">explore the Wayfindr Open Standard</a>.</p><p><em>Originally published at </em><a href="https://www.virgin.com/virgin-unite/audio-navigation-opening-london-vision-impaired"><em>www.virgin.com</em></a><em> on June 17, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6568ef7af354" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Developing Accessible Apps]]></title>
            <link>https://medium.com/wayfindr/developing-accessible-apps-4311163fb0b6?source=rss-c1a4fc3e81a7------2</link>
            <guid isPermaLink="false">https://medium.com/p/4311163fb0b6</guid>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[visual-impairment]]></category>
            <category><![CDATA[ustwo]]></category>
            <dc:creator><![CDATA[Wayfindr]]></dc:creator>
            <pubDate>Thu, 19 May 2016 10:47:26 GMT</pubDate>
            <atom:updated>2016-06-23T14:27:11.828Z</atom:updated>
            <content:encoded><![CDATA[<p>As part of Global Accessibility Awareness Day (<a href="https://twitter.com/hashtag/gaad">#GAAD</a>) we wanted to share some of the lessons learned from developing the Wayfindr Demo mobile app, testing it in real settings with users who have one or more disabilities. In our case, we were developing an iOS app to be primarily used on an iPhone by someone who is vision impaired. However, many of the ideas are equally applicable to other software platforms, hardware devices, venues, and users with varied disabilities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/804/0*nXuZlWtI_FcOdLh0.jpeg" /></figure><h4>VoiceOver</h4><p>Apple has provided a way to read-aloud any text on the screen automatically since the early days of the iPhone. This tool is called VoiceOver. It allows a user to quickly swipe between elements of the screen and get a description of what is contained within the element and what interactions can take place. For many text-based elements, support for VoiceOver comes free to developers — no extra work is needed.</p><p>For non-text based elements or for elements where additional description may be needed for users with vision impairments, there are additional properties a developer can specify. Using accessibilityLabel we can provide the system with a short bit of text to be read aloud to describe the element. If this is not sufficiently unambiguous, the accessibilityHint can be used to provide additional context. The last major accessibility tool to make the user interface accessible using VoiceOver is the accessibilityTraits. These are pre-defined traits that describe the element and interactions that are available (e.g. Is it a button? Does it play a sound? etc.).</p><p>There are many other items defined in the <a href="https://developer.apple.com/library/ios/documentation/UIKit/Reference/UIAccessibility_Protocol/#//apple_ref/doc/constant_group/Accessibility_Traits">UIAccessibility protocol</a>, but those are the big three that can quickly make your app more accessible.</p><h4>Dynamic Type</h4><p>Starting with iOS 7, Apple introduced the idea of Dynamic Type. Rather than having the developer specify the font and its appropriate size for each element of the screen, Dynamic Type allows the system to do this. As a developer, simply request the appropriate font from the system by using theUIFont.preferredFontForTextStyle constructor and pass in the desired text style (Title1, Body, Caption1, etc.). This is very similar to how web developers specify fonts.</p><p>While this takes the sting out of making sure every font and size is correct, new problems arise by supporting Dynamic Type. Since the user can change the default size (and whether or not the text is bold) by using the Settings app on their phone, suddenly the text can become much larger than you originally designed the element to handle.</p><p>While supporting auto-layout does allow some elements to grow automatically, most do not when the text becomes too large to display. Even UILabel does not automatically expand to display all of the text. To do this, we often need to set the lineBreakMode to something other than truncating and set the numberOfLines either to zero (which allows it to have an infinite number of lines, which is often what we want) or a number other than one.</p><p>Similarly, tables do not grow their cell size to support the enlarged text. Nor do UITableViewCell’s by default support Dynamic Type. Instead we must modify the UITableViewCell’s labels appropriately. In addition, we must set an estimated row height for the cells at the table level and the row height to UITableViewAutomaticDimension to allow the cell itself to resize accordingly.</p><h4>Buttons</h4><p>I would like to draw particular attention to text-based buttons. While this has become the norm over the last few years and VoiceOver provides automatic support for these, there are some additional thoughts that need to be considered.</p><p>When a user navigates through an app, by default the title of the previous screen becomes the name of the back button to return to that screen. While VoiceOver reads this aloud and even states that this is a back button, we found that our users became very confused by this. We had much better success by replacing the default back button with one that actually says ‘Back’.</p><h4>Graphics</h4><p>While very few graphics were used in producing this prototype app, I wanted to add a few thoughts surrounding this topic.</p><p>Using the accessibilityLabel, we can help paint a picture in the user’s mind about what the graphic contains. For example, if you are displaying a profile picture on a screen, you could write “Image of [INSERT NAME HERE]” to provide some context for a user with vision impairments.</p><h4>Audio</h4><p>In developing Wayfindr, we found that even using VoiceOver was insufficient most of the time. We wanted realtime instructions to be provided to the user. VoiceOver generally requires the user to initiate some interaction before any screen elements are read aloud.</p><p>To combat this, we used AVFoundation’s text-to-speech capabilities extensively throughout the prototype app. AVSpeechSynthesizer provides an easy to use audio engine. After instantiating, simply create an AVSpeechUtterance with whatever text you would like read aloud and ask the synthesizer to speak.</p><p>In addition to reading aloud the instructions, we took a cue from <a href="http://nshipster.com/avspeechsynthesizer/">NSHipster</a> and highlighted the words as they were being spoken.</p><h4>Aaron’s Top Tips</h4><ul><li>The biggest tip I have for developers creating accessible apps is to turn on and use the accessibility features yourself. Don’t just use them when testing your app, but use them throughout all of your apps. You will quickly understand some of the pains users with disabilities go through when trying to use a mobile device.</li><li>Buried at the bottom of the Accessibility screen in the Settings app on iOS is an item called “Accessibility Shortcut”. I use this be able to quickly turn on and off VoiceOver with a triple-click of the home button.</li></ul><h3>Resources</h3><h4>General Resources</h4><ol><li><a href="https://www.wayfindr.net/open-standard/">The Wayfindr Open Standard</a>: The first working draft of the Wayfindr Open Standard gives venue owners and digital navigation services the tools to implement high quality, consistent audio wayfinding solutions. It includes an open-source demo app that enables people who download it to use BLE beacons to understand and implement the open standard with real users, in real contexts, in real time.</li><li><a href="http://boingboing.net/2015/12/05/games-reveal-the-contrasting-c.html">Games Reveal the Contrasting Colors of Accessibility</a>: This is a great discussion about how important color is in video games (and many other apps), yet how frustrating this is to those who are colorblind or have some other vision impairment.</li></ol><h4>Apple Developers</h4><ol><li><a href="https://developer.apple.com/accessibility/">Accessibility for Developers</a>: This is the homepage for developing accessible apps on all of Apple’s platforms.</li><li><a href="https://developer.apple.com/videos/play/wwdc2015-103/">WWDC 2015: Apple Design Awards</a>: In 2015, the app <em>Workflow</em> won an Apple design award specifically for its phenomenal accessibility support. The demonstration is worth many a re-watch.</li><li><a href="https://overcast.fm/+FrCGVaP1w">Mac Power Users 293: It Kinda Is Rocket Science</a>: In this episode of Mac Power Users, David and Katie interview a PhD student who is vision impaired and how she uses the accessibility features on a daily basis.</li><li><a href="https://developer.apple.com/videos/play/wwdc2015-804/">WWDC 2015: Introducing the New System Fonts</a>: This WWDC video describes the care taken by Apple in designing the new system fonts (San Fransico) to improve readability.</li><li><a href="http://www.applevis.com/">AppleVis</a> A website containing news about accessible apps in the Apple ecosystem. This is a great resource for inspiration.</li></ol><h4>Android Developers</h4><ol><li><a href="http://developer.android.com/guide/topics/ui/accessibility/index.html">Accessibility for Developers</a>: This is the homepage for developing accessible app on Android.</li></ol><h4>Windows Developers</h4><ol><li><a href="https://msdn.microsoft.com/en-us/enable/dn916121.aspx">Accessibility Developer Hub</a>: This is the homepage for developing accessible apps on all of Microsoft’s platforms.</li></ol><p>Find out more about the Open Standard <a href="https://www.wayfindr.net/about-wayfindr/">here</a>.</p><p><em>Originally published at </em><a href="https://www.wayfindr.net/developing-accessible-apps/"><em>www.wayfindr.net</em></a><em> on May 19, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4311163fb0b6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wayfindr/developing-accessible-apps-4311163fb0b6">Developing Accessible Apps</a> was originally published in <a href="https://medium.com/wayfindr">Wayfindr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>