<?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 Jayde Ly on Medium]]></title>
        <description><![CDATA[Stories by Jayde Ly on Medium]]></description>
        <link>https://medium.com/@jaydely?source=rss-c75bd8843279------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*AZuJNcCUE58qSLsO9a3vJg.jpeg</url>
            <title>Stories by Jayde Ly on Medium</title>
            <link>https://medium.com/@jaydely?source=rss-c75bd8843279------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 02:27:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jaydely/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[WCAG: Hover and Communicating State?]]></title>
            <link>https://medium.com/@jaydely/wcag-hover-and-communicating-state-4854dc9879d2?source=rss-c75bd8843279------2</link>
            <guid isPermaLink="false">https://medium.com/p/4854dc9879d2</guid>
            <category><![CDATA[wcag]]></category>
            <category><![CDATA[accessibility]]></category>
            <dc:creator><![CDATA[Jayde Ly]]></dc:creator>
            <pubDate>Tue, 09 Jan 2024 00:37:31 GMT</pubDate>
            <atom:updated>2024-01-09T00:37:31.026Z</atom:updated>
            <content:encoded><![CDATA[<p>The other day a designer coworker asked, “Does hover need to contrast with the default or selected states?”</p><p>I was like ummmm good question! After some research, I found my answer and broke it down for him. But rather than sending my answer as a one-off in Slack, I decided to document it as part of our design system knowledge base and am also sharing it here.</p><h3>Contrast requirements</h3><p><strong>All states must pass contrast requirements with adjacent colours (except for the disabled state)</strong></p><ul><li>E.g. text vs backgrounds 4.5:1</li><li>E.g. borders vs backgrounds 3:1</li></ul><p><strong>Hover</strong></p><ul><li>Does not need to contrast against other states within the same component.</li><li>Does not need to have another method of communicating state.</li><li>But does need to pass basic 4.5:1 text and 3:1 non-text against backgrounds</li><li>E.g. hover does not need to contrast when compared to default/selected/focussed</li></ul><p><strong>Other states, except hover, must not use colour as the only means of communicating state.</strong></p><ul><li>E.g. selected vs default</li><li>E.g. focus vs default</li><li>E.g. focus vs selected</li></ul><h3>Use of Color</h3><p>Contrast can help satisfy the use of colour requirement. If you look at the stars example on the <a href="https://www.w3.org/WAI/WCAG21/Understanding/non-text-contrast">Understanding SC 1.4.11:Non-text Contrast (Level AA)</a> page it has a very clear example of this.</p><blockquote><em>Figure 6 </em><strong><em>Two examples which pass this success criterion</em></strong><em>, using either a solid fill to indicate a checked-state that has contrast, or a thicker border as well as yellow fill.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*OVK9rNll7WiMWlYMkRMaTw.png" /></figure><ul><li>The black and white example passes the use of colour because the contrast between black and white is at least 3:1.</li><li>The yellow and white example passes because the border of the yellow selected stars is thicker than the white unselected ones. Without the thicker border, the yellow vs white would fail because the yellow and white do not contrast against each other enough.</li></ul><h3>Resources</h3><ul><li><a href="https://www.w3.org/WAI/WCAG21/Understanding/non-text-contrast">Understanding Success Criterion 1.4.11: Non-text Contrast | WAI | W3C</a></li><li><a href="https://accessibleweb.com/question-answer/what-are-the-contrast-requirements-for-an-elements-focus-mouseover-select-states/">What are the contrast requirements for an element’s focus, mouseover &amp; select states? | Accessible Web</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4854dc9879d2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Galvanize Product Designers Accessibility FAQs]]></title>
            <link>https://medium.com/@jaydely/galvanize-product-designers-accessibility-faqs-6596541c48f1?source=rss-c75bd8843279------2</link>
            <guid isPermaLink="false">https://medium.com/p/6596541c48f1</guid>
            <dc:creator><![CDATA[Jayde Ly]]></dc:creator>
            <pubDate>Wed, 15 Nov 2023 22:30:58 GMT</pubDate>
            <atom:updated>2023-11-15T22:44:45.819Z</atom:updated>
            <content:encoded><![CDATA[<h3>Preface</h3><p>These FAQs were written for <a href="https://medium.com/@jaydely/galvanize-designer-guidelines-75780def136a">accessibility guidelines that were developed for product designers at Galvanize</a>. They are meant to provide the rationale for the guidelines without bloating the original guidelines page.</p><h3>Colour</h3><h4><strong>Why shouldn’t I use colour as the only way to convey information?</strong></h4><p>Users who are colour-blind cannot receive information that is conveyed only through colour, such as in a colour status indicator. Include other visual cues, preferably text, to ensure that information is accessible.</p><h3>Contrast (text)</h3><h4><strong>What is considered purely decorative text?</strong></h4><p>Text is only purely decorative if the words can be rearranged or substituted without changing their purpose.</p><h4><strong>What is considered a non-essential UI element?</strong></h4><p>A UI element is considered non-essential if it does not change the user’s understanding of the UI when it is removed. Examples include a phone number formatting hint that is only used to give the user an idea of what to enter so long as the user can actually use different formats (dashes, no dashes, spaces, periods, etc.).</p><h4><strong>How do I make text links accessible? (</strong><a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/G182"><strong>W3C</strong></a><strong>)</strong></h4><p>There are 2 ways to make links that are contained in a sentence or block of text accessible.</p><ol><li>Add an underline or other visual indicator.</li><li>Choose a colour for the link that has a 3:1 contrast ratio with the surrounding text. This is not an easy thing to do though because the colour of the text link has to have a minimum contrast ratio of 3:1 with the surrounding text AND 4.5:1 with the background.</li></ol><p>When colour is used for links, <a href="https://www.w3.org/WAI/WCAG20/Techniques/working-examples/G183/link-contrast.html">a blue colour is recommended</a> because it is affected very little by red and green colour blindness (Protanopia and Deuteranopia).</p><p>Links that are visually obvious/evident from page design and context, such as navigational links, do not need to meet the 3:1 contrast ratio with surrounding text nor do they require underlines. (<a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/F73">W3C</a>)</p><h3>Non-text contrast</h3><h4><strong>Why do inactive user interface components need to pass contrast?</strong></h4><p>Inactive user interface components do not need to pass contrast. However, many people do not realize that inactive means disabled. So if a UI component is available for interaction then it is not inactive, it is just not the currently selected item.</p><p>A good example are tabs (or button groups) where only 1 is selected. The other ones that are not selected are still available for user interaction so that users can switch to another tab. Therefore all tabs must pass contrast. Disabled components have an aria/html attribute that lets screen readers know that it is disabled.</p><h4><strong>I want to use yellow for my favourite stars. How do I get it to pass?</strong></h4><ul><li>You can use a thicker border for one of the states. For example un-starred has a 1px border and starred has a 2px border.</li><li>You can put a contrasting background colour behind one of the states.</li><li>You can put a border around one of the states.</li></ul><h4><strong>What do I do about hover and active states? Such as default vs hover vs active?</strong></h4><p>When designing an interactive element, it needs to meet a 3:1 contrast ratio with adjacent colours. You need to maintain a 3:1 contrast ratio during all of that element&#39;s states (focus, hover, active, etc). The requirement doesn’t mean that states need to contrast 3:1 <em>with each other</em>.</p><p>For instance, an element’s hover state <em>does not</em> need to contrast 3:1 with its <em>focus state</em>, or even its resting state. You just need to make sure that each state of an element meets the 3:1 contrast ratio with adjacent colours, and is “distinguishable enough” from each other so users are aware of their interactions with the element (focusing, hovering, etc). (<a href="https://accessibleweb.com/question-answer/what-are-the-contrast-requirements-for-an-elements-focus-mouseover-select-states/">Source reference</a>)</p><h3>Motion</h3><h4><strong>Why shouldn’t I use elements that flash more than three times per second?</strong></h4><p>Flashing elements can cause some people to have seizures.</p><h4><strong>What’s the difference between blinking and flashing?</strong></h4><ul><li>Blinking is slower and occurs less than 3 times per second</li><li>Flashing is fast and occurs 3 or more times per second.</li><li>Blinking can be distracting but it can also be used for a short time as long as it stops or the user can stop it.</li></ul><h3>Consistent</h3><h4><strong>Can I add or remove links in a sub-nav menu?</strong></h4><p>Yes as long as the relative order of all the other links is the same. The goal is to make the UI predictable, it is not to make sure that it is exactly the same. You can add/remove sub-links as appropriate.</p><h4><strong>Can I use the same icon for different things?</strong></h4><p>Yes as long as they have different alt text. For example, a checkmark could mean “approved” in one context and “included” in another.</p><h4><strong>Can I change the alt text for icons with the same function?</strong></h4><p>Yes as long as the structure of the alt text remains the same. For example, if you’re using a download icon for downloading PDFs, word, excel, zip, etc. you can change the alt text as long as the structure remains the same.</p><p><strong>Download </strong><strong>X:</strong></p><ul><li>Download PDF → correct</li><li>Download Word → correct</li><li>Download Powerpoint → correct</li><li>Zip Download → wrong</li></ul><h4><strong>What does “buttons with the same functionality” mean?</strong></h4><p>Example: a submit “search” button on one page and a “find” button on another page both have a field to enter a term and list topics related to the term submitted. The buttons have the same functionality but are not labeled consistently but they should be.</p><h3>Predictable</h3><h4><strong>What’s considered a change of context</strong></h4><p>Changes in context include changes of: (<a href="https://www.w3.org/TR/2008/REC-WCAG20-20081211/#context-changedef">W3C</a>)</p><ol><li><a href="https://www.w3.org/TR/2008/REC-WCAG20-20081211/#useragentdef">User-agent</a>;</li><li><a href="https://www.w3.org/TR/2008/REC-WCAG20-20081211/#viewportdef">Viewport</a>;</li><li>Focus;</li><li><a href="https://www.w3.org/TR/2008/REC-WCAG20-20081211/#contentdef">Content</a> that changes the meaning of the <a href="https://www.w3.org/TR/2008/REC-WCAG20-20081211/#webpagedef">Web page</a>.</li></ol><p>A change of content is not always a change of context. Examples of content-only changes include: expanding outline, dynamic menu, or tabbed content. These do not necessarily change the context unless they also change one of the above (e.g. focus).</p><h4><strong>Other examples of changes in context include:</strong></h4><ol><li>Opening a new window</li><li>Moving the focus to a different component</li><li>Going to a new page or major layout changes for single page applications that are normally built as new pages.</li></ol><h4><strong>Why do we need to give users advanced warning before opening new windows? (</strong><a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/G201"><strong>W3C</strong></a><strong>)</strong></h4><p>Opening new windows automatically can be disorientating for users. People who have difficulty perceiving visual content and others with cognitive disabilities are most affected. Providing a warning gives people the choice to leave the current window and lets them know how to find their way back. It will help users understand why the “back” button is not working and that they have to return to the previous window in order to find their previous location.</p><h4><strong>What is an example of an</strong> on focus <strong>failure?</strong></h4><ol><li>The user clicks the “Password field”.</li><li>A tooltip opens up with information about “password strength”.</li><li>The tooltip is automatically passed focus by scripting.</li><li>The user is unable to tab back into the “Password field” because focus is continually given to the tooltip.</li></ol><h4><strong>What are examples of</strong> on input <strong>failures?</strong></h4><ul><li>Automatically submitting a form when the last field is given a value.</li><li>Automatically launching a new window when the user changes the selection of a radio button, check box or select list.</li></ul><h4><strong>What are examples of form control settings being changed which causes a change of context?</strong></h4><ul><li>Changing a radio button or selecting dropdown changes the language of a page.</li><li>A questionnaire with 1 questions presents the user one question at a time. When the user selects an answer the page updates to show the next question.</li></ul><p>You can change the context from a form control setting change but only if you tell the user ahead of time that this will happen, don’t just do it.</p><p><strong>Doesn’t auto-focussing form fields provide a better user experience?</strong><br>It can be for sighted users, in some cases, but for users who rely on screen readers, this can be very confusing. Screen readers lose all context of what is being read back to them, the visual cues that sighted users get (e.g. side panel title, how-to text, etc.) are missing. Screen reader users do not know that they need to tab backwards to get more information or that this information is even available to them.</p><h3>Forms</h3><h4><strong>Why should I add an error notification to the</strong> &lt;title&gt; <strong>of pages that do a full refresh?</strong></h4><p>This is a best practice as a screen reader user is likely to believe that the page was submitted correctly otherwise and continue to navigate away as soon as the new page is returned instead of reading the main content area again.</p><h4><strong>What is an example of a non-descriptive form field label?</strong></h4><p>Example: users need to enter their phone number, sometimes this is broken up into 3 separate fields: a 3-digit area code, a 3-digit prefix and a 4-digit extension. A text label position near the set of phone number fields is required.</p><h4><strong>Why should I group radio buttons and checkboxes with</strong> &lt;fieldset&gt; <strong>and</strong> &lt;legend&gt;?</h4><p>Wrapping things in &lt;fieldset&gt; gives the group context because the labels might only tell you what the value of a radio/checkbox is (e.g. yes, no, true, false) but users might not be able to tell what the options are for. The styles for &lt;fieldset&gt; and &lt;legend&gt; can be hidden from sighted users but still can be available to screen readers.</p><h3>Timing</h3><h4><strong>Exceptions for timed events include</strong></h4><ul><li>Real-time events such as auctions.</li><li>Completing purchases within a given timeframe.</li><li>The default time limit is more than 20 hours already.</li><li>Timed tests such as exams.</li></ul><h4><strong>Moving content includes anything that starts automatically and blinks, scrolls or auto-updates:</strong></h4><ul><li>Slideshows and carousels.</li><li>Automatically updating headlines or other content.</li><li>Pulsing sonar animations.</li></ul><h4><strong>Exceptions</strong></h4><ul><li>Moving content lasts less than 5 seconds.</li><li>Moving content that is not presented in parallel to other content such as a 15+ second full-page advertisement that all users are required to view before they can see the free content. Since the ad is not presented with other surrounding content then it does not require controls to pause or stop it.</li><li>Spinners and progress bars.</li></ul><h3>Audio and Video</h3><h4><strong>Examples of second user-selectable audio tracks</strong></h4><ul><li>A travelogue of the Northeast has additional audio descriptions added during the gaps in the dialogue to let listeners who are blind know what the person is talking about at any point in time.</li><li>A lecture has an audio description added whenever the instructor says things like “and <em>this</em> is the one that is most important.” The audio descriptions let listeners who can not see the video know what “this” is.</li><li>A movie file has two audio tracks, one of which includes an audio description. Users can choose either one when listening to the movie by selecting the appropriate track in their media player.</li></ul><h4><strong>What’s an example of a video that doesn’t need captions or transcripts?</strong></h4><p>Help documentation that has step-by-step instructions written in the text but also has a video that demonstrates the steps is a good example. The video is just an alternative visual aid to the written instructions so captions and transcripts are not required.</p><h3>Navigating the UI</h3><h4>Do we have to show sighted users the “Skip to Content” link?</h4><p>No, this can be hidden from sighted users unless they use the keyboard to navigate.</p><h4>Why should I use the object or destination’s name in the link instead of “Click here?” (<a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/G53">WCAG</a>)</h4><p>Assistive technology can provide users with a list of links that are on a page. If you use “Click here” then the names of the links are not very meaningful to these users. If you must use “click here” as a call to action it should be placed at the end of the sentence. (e.g. To advertise on this page, *click here*.)</p><h4>Why should I put “Learn more.” or other ambiguous links at the end of a sentence? (<a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/H78">WCAG</a>)</h4><p>Putting it at the end of the sentence will give users a better idea as to what that link is about. A screen reader will read the paragraph that appears before the link and will give the user the context to know the purpose and destination of the “Learn more.” link itself.</p><h4>What’s the difference between a table of contents and a Navigation Bar or Site Map?</h4><p>A table of contents is a list of links to different sections of the same document or idea. A Navigation Bar or Site Map is a list of links to different areas. For example, a book has many sections. Each section belongs to the book and the table of contents for the book takes you to different pages within the book. A library has many books and the Navigation Bar or Site Map will take you to different books contained within the library.</p><h4>What’s an example of identifying content only by its shape, size, location or orientation?</h4><p>When providing instructions it is best to also include the label or other text-based information about the object you’re describing.</p><ul><li>Failure Example 1: The button on the left.</li><li>Failure Example 2: The green icon.</li><li>Failure Example 3: The square button.</li></ul><h4>What’s an example of providing instructions through sound?</h4><p>If a form triggers a sound whenever an error occurs. This type of instruction will fail accessibility if it is the only means of communication to the user that an error happened.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6596541c48f1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Galvanize Product Designer Accessibility Guidelines]]></title>
            <link>https://medium.com/@jaydely/galvanize-designer-guidelines-75780def136a?source=rss-c75bd8843279------2</link>
            <guid isPermaLink="false">https://medium.com/p/75780def136a</guid>
            <dc:creator><![CDATA[Jayde Ly]]></dc:creator>
            <pubDate>Wed, 15 Nov 2023 22:17:55 GMT</pubDate>
            <atom:updated>2023-11-15T22:45:57.924Z</atom:updated>
            <content:encoded><![CDATA[<h3>Preface</h3><p>These guidelines were developed for product designers at Galvanize. It was meant to provide basic guidance and introduce them to accessibility/WCAG standards.</p><h3>How to use this guide</h3><p>All of the items listed under <strong>“Do”</strong> are techniques that will help you pass the standards. Items listed under <strong>“Don’t”</strong> are automatic fails if done. Items listed under <strong>“Avoid”</strong> will not trigger a fail but are best avoided because they go against best practices.</p><h3>Colour (<a href="https://medium.com/@jaydely/galvanize-product-designers-accessibility-faqs-6596541c48f1#c9fb">FAQ</a>)</h3><p>Some people have reduced or lack of sensitivity to certain colours (“colour blindness”). Other people have increased sensitivity to bright colours.</p><h4>Do:</h4><ul><li>Use a combination of visual cues to convey information such as colours/icons/text/labels/errors.</li><li>Underline links that are embedded within a sentence/block of text because some users may not be able to discern a difference in text colour.</li><li>Use brightness shifts as a method to convey different states of a ui element such as hover, focus, active, etc. (Best practice)</li></ul><h4>Don’t:</h4><ul><li>Use colour as the only way to convey information (e.g. status, feedback).</li><li>Use colour as the only way to identify required fields or errors.</li></ul><h4>Avoid:</h4><ul><li>Using pure black text on pure white backgrounds.</li></ul><h4>This guideline fulfills the following WCAG guidelines:</h4><ul><li><a href="https://www.w3.org/WAI/WCAG21/Understanding/use-of-color.html">1.4.1 Level A: Use of Colour</a></li></ul><h3>Contrast for text (<a href="https://medium.com/@jaydely/galvanize-product-designers-accessibility-faqs-6596541c48f1#bc6a">FAQ</a>)</h3><p>People don’t always screen readers when they have trouble seeing the screen. This is true especially f it’s situational (e.g. low contrast monitors, glare on their screen from the environment, etc.).</p><h4>Do</h4><ul><li>Ensure sufficient colour contrast between design elements, so that users with low acuity can see and use our apps.</li><li>Meet all <a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html">WCAG 2.0 minimum contrast ratios</a> for text and background colours.<br>– Fonts that are 18 points or larger: 3:1 contrast ratio<br>– Fonts that are 14 points bold or larger: 3:1 contrast ratio<br>– All other text and images of text: 4.5:1 contrast ratio<br>– Use placeholder text to only provide examples of expected value types.</li><li>Icons or other critical elements should comply with contrast standards.</li></ul><h4>Don’t</h4><ul><li>Allow any of the colour contrast ratios to fail.</li><li>Use placeholder text to provide instructions.</li><li>Use placeholder text as a replacement for form labels.</li></ul><h4>Avoid</h4><ul><li><strong>Using thin text weights for regular-sized text.</strong> <br>The contrast ratio standards were created for normal weighted fonts, there are no standards set for fancy or thin fonts. We have not found a tool that will test against fancy/thin fonts, the current tools only run comparisons against the regular or bold font weights. So even if fancy/thin fonts technically pass our contrast checkers it does not mean that they are actually usable. It is best to avoid thin/fancy fonts for regular-sized text and very thin large fonts.</li><li><strong>Avoid using pure black text on a pure white background.</strong> <br>Dyslexic users are sensitive to the brightness of the high contrast colours. Pure black #000 text on a pure white #fff background can cause words to swirl or blur together for many dyslexic users.</li></ul><h4>Exceptions</h4><ul><li>Incidental text as defined by WCAG does not have nor have to meet contrast requirements (<a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html#puredecdef">W3C</a>).</li><li>— Disabled user interface component text (e.g. disabled buttons).</li><li>— Purely decorative text that serves only an aesthetic purpose, providing no information and having no functionality.</li><li>Decorative illustrations. While decorative elements, such as logos and illustrations, don’t have to meet contrast ratios they should be distinguishable if they possess important functionality.</li><li>Non-essential UI elements.</li><li>Branding.</li></ul><p>For more information on contrast minimums see <a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html">Understanding SC 1.4.3</a>.</p><h4>This guideline fulfills the following WCAG guidelines:</h4><ul><li><a href="https://www.w3.org/WAI/WCAG21/Understanding/contrast-minimum.html">1.4.3 Level AA: Contrast (Minimum)</a></li></ul><h3>Non-text contrast (<a href="https://medium.com/@jaydely/galvanize-product-designers-accessibility-faqs-6596541c48f1#c349">FAQ</a>)</h3><h4>Do</h4><ul><li>Meet all <a href="https://www.w3.org/WAI/WCAG21/Understanding/non-text-contrast">WCAG 2.1 non-text content contrast ratios</a> for UI components and graphical objects.</li><li>All components that are available for user interaction must still pass a 3:1 contrast ratio.</li><li>— UI components that are disabled do not need to pass contrast.</li><li>— Note that any text within the UI component still needs to pass at a 4.5:1 contrast ratio.</li><li>Charts and icons must pass a 3:1 contrast ratio.</li><li>— If it’s a pie chart, the user must be able to see where one slice begins and another ends. The exception is if the pie chart has both visible labels and values that show the same equivalent information as the pie chart slices.</li></ul><h4>Don’t</h4><ul><li>Have any icons that don’t have a contrast ratio of 3:1.</li><li>Have any enabled UI components fail a contrast ratio of 3:1</li><li>— Note: In the context of WCAG, inactive means disabled</li></ul><h4>Avoid</h4><ul><li>Putting text in graphics.</li><li>Gradients in icons. If gradients are used, you need to make sure the lightest part of the gradient still passes a 3:1 contrast ratio.</li><li><strong>Removing all borders around interactive items such as buttons and input fields. </strong>People with cognitive disabilities have trouble recognizing controls without a border. For example, you should put borders around buttons, put borders around form inputs, etc.</li></ul><h4>Exceptions</h4><ul><li>The graphic is for aesthetic purposes that does not require the user to see or understand it to understand the content or use the functionality.</li><li>The graphic is part of a logo or brand name (which is considered “essential” to its presentation).</li><li>Photos of people are scenery (but need alt tags).</li><li>Colour gradients that represent a measurement (like heat maps).</li></ul><h4>This guideline fulfills the following WCAG guidelines:</h4><ul><li><a href="https://www.w3.org/WAI/WCAG21/Understanding/non-text-contrast.html">1.4.11 Level AA: Non-text contrast</a></li></ul><h3>Charts</h3><p>Colours should be chosen with colour blind users in mind. Contrast should be sufficient for users who have low visual acuity. Options should be included for users who are blind and require the help of screen readers.</p><h4>Do (<a href="https://designshack.net/articles/accessibility/tips-for-designing-for-colorblind-users/">Article</a>)</h4><ul><li>Have options to turn on patterns, textures, or grayscale.</li><li>Use a range of clearly contrasting colours and hues.</li><li>Have sufficient contrast between elements (e.g. bars, axes and labels).</li><li>Provide a title or short description to identify the chart.</li><li>Provide a long description which is the textual representation of the essential information conveyed by the chart. (<a href="https://www.w3.org/WAI/tutorials/images/complex/">W3C tutorial</a>)</li><li>Use a combination of colours, shapes and labels to convey information.</li><li>Provide a “View Data Table” option.</li><li>Make sure the chart has a visible focus and consistent navigation.</li><li>Line charts include the use of different line styles such as solid, small dashes, large dashes and dots.</li><li>Make text and objects as thick or big as possible.</li></ul><h4>Don’t</h4><ul><li>User colour as the only way to convey information.</li><li>Leave out the “View Data Table” option.</li></ul><h4>Avoid</h4><ul><li>Placing bad colour combos closely together: (<a href="http://blog.usabilla.com/how-to-design-for-color-blindness/">Article</a>)<br>– Green &amp; Red<br>– Green &amp; Black<br>– Green &amp; Brown<br>– Green &amp; Blue<br>– Blue &amp; Purple<br>– Blue &amp; Grey<br>– Green &amp; Grey<br>– Light Green &amp; Yellow</li><li>Situations where important information is conveyed only in the form of colour.</li></ul><h4>Examples</h4><p><a href="http://accessibility.psu.edu/images/charts/">Charts &amp; Accessibility</a></p><h4>This guideline fulfills the following WCAG guidelines:</h4><ul><li><a href="https://www.w3.org/WAI/WCAG21/Understanding/non-text-content.html">1.1.1 Level A: Non-text Content</a></li><li><a href="https://www.w3.org/WAI/WCAG21/Understanding/use-of-color.html">1.4.1 Level A: Use of Colour</a></li><li><a href="https://www.w3.org/WAI/WCAG21/Understanding/non-text-contrast.html">1.4.11 Level AA: Non-text Contrast</a></li><li><a href="https://www.w3.org/WAI/WCAG21/Understanding/contrast-minimum.html">1.4.3 Level AA: Contrast (Minimum)</a></li></ul><h3>Motion (<a href="https://medium.com/@jaydely/galvanize-product-designers-accessibility-faqs-6596541c48f1#cac5">FAQ</a>)</h3><p>Animations are an extremely powerful communication tool. It helps users understand the transition from one screen to another or when panels open or close. It can also make our users feel sick or triggered so be careful how you use it.</p><h4>Do</h4><ul><li>Be purposeful with your animations and use it as a tool for communication:</li><li>— To show continuity and relationships between objects via entry and exit animations.</li><li>— Reduce cognitive load and confusion by effectively communicating user feedback.</li><li>— Guide the user focus to show hierarchy and relationships between screens and elements on the screen.</li><li>— Convey visual hierarchy by animating the order of page elements as they load.</li><li>— Communicate transitions between states.</li><li>Reduce contrast for any flashing content.</li><li>Avoid fully saturated reds for any flashing content.</li></ul><h4>Don’t</h4><ul><li>Have anything that flashes more than 3 times within 1 second.</li><li>Autoplay “big” animations (where a large area of the screen moves).</li></ul><h4>Avoid</h4><ul><li>Large areas of motion that include:</li><li>— Parallax background animations: when the background moves slower than the foreground.</li><li>— Scroll-jacking: This is when the background animates at a speed unrelated to your scrolling efforts.</li><li>Animations that move in a different direction than the user scroll.</li></ul><p><strong>Awesome article on vestibular disorder (motion-triggered illness)<br></strong><a href="https://alistapart.com/article/designing-safer-web-animation-for-motion-sensitivity">Designing Safer Web Animation For Motion Sensitivity</a></p><blockquote><em>Animation that involves only non-moving properties, like opacity, colour, and blurs, are unlikely to be problematic.</em></blockquote><h4>This guideline fulfills the following WCAG guidelines:</h4><ul><li><a href="https://www.w3.org/WAI/WCAG22/Understanding/three-flashes-or-below-threshold.html">2.3.1 Level A: Three Flashes or Below</a></li></ul><h3>Consistent (<a href="https://medium.com/@jaydely/galvanize-product-designers-accessibility-faqs-6596541c48f1#1f4c">FAQ</a>)</h3><p>Being consistent allows our users to learn how things work on one feature and apply that knowledge to other features.</p><h4>Do</h4><ul><li>Keep navigation items in the same relative order.</li><li>Use of sub-nav sections in larger navigation menus.</li><li>Place components that have the same functionality in the same places:<br> — Company logo<br> — Top navigation<br> — Search<br> — Page title<br> — Skip navigation controls<br> — Skip to navigation links.<br> — etc.</li><li>Label things consistently:<br> — Buttons<br> — Form fields<br> — Icons<br> — etc.</li><li>Use icons consistently</li><li>Use consistent alt text for icons</li></ul><h4>Don’t</h4><ul><li>Change the relative order of navigation links in a component that is used across different pages.</li><li>Label buttons with the same functionality differently.</li></ul><h4>This guideline fulfills the following WCAG guidelines:</h4><ul><li><a href="https://www.w3.org/WAI/WCAG21/Understanding/consistent-navigation.html">3.2.3 Level AA: Consistent Navigation</a></li><li><a href="https://www.w3.org/WAI/WCAG21/Understanding/consistent-identification.html">3.2.4 Level AA: Consistent Identification</a></li></ul><h3>Predictable (<a href="https://medium.com/@jaydely/galvanize-product-designers-accessibility-faqs-6596541c48f1#8006">FAQ</a>)</h3><p>Surprises are great but not when they change the user’s context and confuse them.</p><h4>Do</h4><ul><li>Change context only when it is clear that such a change will happen in response to the user’s action (use “activate” instead of “focus”).</li><li>Give users advanced warning before opening a tab/window</li><li>Open new windows only when necessary.</li></ul><h4>Don’t</h4><ul><li>Change context on focus</li><li>Change context on input</li><li>Forget to tell the user what will happen before you change the context of a page if the change is triggered by a form control.</li><li>Automatically open a new window when the user changes the selection of a:<br> — Radio button<br> — Checkbox<br> — Item in a &lt;select&gt; list</li><li>Open a new window as soon as a page loads (no automatic popups either).</li><li>Auto-focus anything besides the current element or view.</li></ul><h4>This guideline fulfills the following WCAG guidelines:</h4><ul><li><a href="https://www.w3.org/WAI/WCAG21/Understanding/on-focus">3.2.1 Level A: On Focus</a></li><li><a href="https://www.w3.org/WAI/WCAG21/Understanding/on-input">3.2.2 Level A: On Input</a></li></ul><h3>Forms (<a href="https://medium.com/@jaydely/galvanize-product-designers-accessibility-faqs-6596541c48f1#9b34">FAQ</a>)</h3><p>Clear labels, error messages and tips benefits everyone.</p><h4>Be clear</h4><ul><li>Distinguish between optional and required fields.</li><li>Provide clear, concise and simple labels for each field (placeholders aren’t enough).</li><li>Show examples of correct data formats (e.g. dates, phone numbers, etc.).<br>— If there are many fields with the same data format requirements then provide instructions at the beginning of the form.</li><li>Position labels so that it’s obvious the relationship between label + field:<br> — Before input fields (text, textarea, select, etc.) to the left or above.<br> — After radios and checkboxes (to the right).</li><li>Group related fields, radio buttons and checkboxes together using (&lt;fieldset&gt; and &lt;legend&gt;).</li><li>Provide success messages for user logins, quizzes, new objects created, edits saved, contact requests sent, etc.</li></ul><h4>Be helpful</h4><ul><li>Highlight missing required fields.</li><li>Tell the user right away if something is missing or entered incorrectly (on blur).</li><li>Write meaningful descriptive error messages.</li><li>Provide suggestions on how to fix errors:<br>— Formatting (MM/DD/YY)<br>— Expected data type (only numbers are accepted<br>— Spelling (did you mean…?)<br>— Search results (0 results, try…)</li><li>If the user submits the form and there are errors:<br>— Keep previously entered data unless it’s a security-related field (e.g. password).<br>— Insert an error message including the number of errors.<br>— Move focus to the error message.<br>— Insert a linked list of fields with errors so that users can navigate easily right to the error field.</li></ul><h4>Be sure</h4><p>Anytime a user is engaging in a legal, financial or data action you must allow a way for them to reverse that action, check that action before completing and then provide a confirmation of the completed action.</p><p>When submitting legal documents, performing financial transactions, making purchases or making changes to data:</p><ul><li>Allow users to cancel the action.</li><li>Allow users to review and make changes before submitting (e.g. filing tax returns or test answers).</li><li>Allow users to confirm that they’ve reviewed everything (e.g. Terms of Service and using a checkbox).</li><li>Allow users to recover deleted data (e.g. archive or soft deletes).</li><li>Tell users what will happen if they delete something (e.g. deleting this will…).</li><li>Ask users to confirm before performing an irreversible action (e.g. are you sure?).</li></ul><h4>Don’t</h4><ul><li>Only indicate that a field has an error by putting an asterisk on its label or turning the label red.</li><li>Forget to provide a clear descriptive text label for a set of fields that make up one single item (e.g. phone numbers, credit card expiration dates, etc.)</li></ul><h4>This guideline fulfills the following WCAG guidelines:</h4><ul><li><a href="https://www.w3.org/WAI/WCAG21/Understanding/error-identification">3.3.1 Level A: Error Identification</a></li><li><a href="https://www.w3.org/WAI/WCAG21/Understanding/labels-or-instructions">3.3.2 Level A: Labels or Instructions</a></li><li><a href="https://www.w3.org/WAI/WCAG21/Understanding/error-suggestion">3.3.3 Level AA: Error Suggestion</a></li><li><a href="https://www.w3.org/WAI/WCAG21/Understanding/error-prevention-legal-financial-data">3.3.4 Level AA: Error Prevention (Legal, Financial, Data)</a></li></ul><h3>Cognition</h3><h4>Avoid using justified text</h4><p>Justified text is difficult to read for dyslexic users. This is because it creates large uneven spaces between letters and words. When these spaces line up above one another. They can cause dyslexic readers to repeatedly lose their place when reading.</p><h4>Avoid using all capital letters</h4><p>Users with cognitive disabilities, such as dyslexia, have problems with all caps regardless of text size. Also, some screen readers read capitalized text letter-by-letter. This occasionally happens when CSS is used for capitalization. Text in all capital letters is more difficult to read for most people, with and without disabilities.</p><p>If you must use all caps then limit it to 1 or 2 words with adequate letter spacing for better readability and not in close proximity to other blocks of all caps text. Also, you will need to consider how the goal of using all caps will be achieved for languages that do not have the concept of all caps such as Chinese and Japanese.</p><h4>Avoid using pure black text on a pure white background.</h4><p>Dyslexic users are sensitive to the brightness of the high contrast colours. Pure black #000 text on a pure white #fff background can cause words to swirl or blur together for many dyslexic users.</p><h3>Wayfinding</h3><p>Help users understand where they are, where they want to go and how to get there.</p><h4>Do</h4><ul><li>Give all pages a descriptive &lt;title&gt;Page - App - HighBond&lt;/title&gt;</li><li>Give all pages a &lt;h1&gt;Page Name&lt;/h1&gt; that’ll be used as part of the &lt;title&gt;.</li><li>Break up long pages with clear and descriptive headings (h1, h2, h3, etc).</li><li>Have a “Skip to Content” link to take users to the main content area.</li><li>Use expanding/collapsing blocks for menus as appropriate.</li><li>Create links using the object or destination’s name instead of “Click here…”.</li><li>“Learn more.” links are wrapped in a &lt;p&gt; tag and inserted it at the end of the paragraph.</li><li>Use different types of menus (e.g. purple app bar, main menu, side menu, etc.) to let users navigate our pages.</li><li>Include the ability to search documents, modules, pages, etc.</li><li>Highlight buttons, links or other controls when a user hovers over it.</li><li>Make it obvious which element has the keyboard focus.</li></ul><h4>Don’t</h4><ul><li>Give a page &lt;title&gt; that does not identify its content.</li><li>Use ambiguous links at the beginning of a sentence (e.g. Click here to go to).</li><li>Identify content or objects only by their shape, size, location or orientation.</li><li>Remove the default browser focus outline without replacing it with a custom one that is also highly visible (don’t make it too subtle).</li></ul><h4>Avoid</h4><ul><li>Instructions that rely on sound</li></ul><h4>This guideline fulfills the following WCAG guidelines:</h4><ul><li><a href="https://www.w3.org/WAI/WCAG21/Understanding/sensory-characteristics">1.3.3 Level A: Sensory Characteristics</a></li><li><a href="https://www.w3.org/WAI/WCAG21/Understanding/bypass-blocks">2.4.1 Level A: Bypass Blocks</a></li><li><a href="https://www.w3.org/WAI/WCAG21/Understanding/page-titled">2.4.2 Level A: Page Titled</a></li><li><a href="https://www.w3.org/WAI/WCAG21/Understanding/link-purpose-in-context">2.4.4 Level A: Link Purpose (In Context)</a></li><li><a href="https://www.w3.org/WAI/WCAG21/Understanding/multiple-ways">2.4.5 Level AA: Multiple Ways</a></li><li><a href="https://www.w3.org/WAI/WCAG21/Understanding/headings-and-labels">2.4.6 Level AA: Headings and Labels</a></li><li><a href="https://www.w3.org/WAI/WCAG21/Understanding/focus-visible">2.4.7 Level AA: Focus Visible</a></li></ul><h3>Timing (<a href="https://medium.com/@jaydely/galvanize-product-designers-accessibility-faqs-6596541c48f1#13d7">FAQ</a>)</h3><p>Give users enough time to do what they need to do and let them control what’s playing on the screen.</p><h4>Do</h4><p><strong>Give users enough time to respond:</strong></p><ul><li>Tell users how much time they have to complete a task.</li><li>Warn them when that time limit is almost reached.</li><li>Allow the user to extend or disable the time limit unless it’s a real-time-based event or critical to the business that users are not able to get an extension.</li><li>Give users at least 20 seconds to respond.</li><li>Allow users to “hit any key” as a response.</li></ul><p><strong>Allow users to control any content that moves</strong></p><ul><li>Provide controls for pause, stop, start, next and previous or allow users to hide the content.</li><li>Minimize the usage of blinking things and keep them under 5 seconds.</li></ul><p><strong>Allow users to control auto-updating content</strong></p><ul><li>Provide the ability to pause, stop, or change the frequency of updates (e.g. scoreboard).</li></ul><h4>Don’t</h4><ul><li>Log users out without warning them and provide 20 seconds for them to respond.</li><li>Automatically page refreshes or redirects that weren’t triggered by the user performing an action.</li><li>Fail to provide controls to pause or stop moving content that lasts longer than 5 seconds.</li></ul><h4>Avoid</h4><ul><li>Adding time limits where possible.</li><li>Content that moves without users triggering the action.</li><li>Auto-play content that lasts longer than 5 seconds.</li></ul><h4>This guideline fulfills the following WCAG guidelines:</h4><ul><li><a href="https://www.w3.org/WAI/WCAG21/Understanding/timing-adjustable">2.2.1 Level A: Timing Adjustable</a></li><li><a href="https://www.w3.org/WAI/WCAG21/Understanding/pause-stop-hide">2.2.2 Level A: Pause, Stop, Hide</a></li></ul><h3>Audio and Video (<a href="https://medium.com/@jaydely/galvanize-product-designers-accessibility-faqs-6596541c48f1#5545">FAQ</a>)</h3><p>Everyone should be able to consume the content in an audio or video recording.</p><h4>Do</h4><p><strong>Provide transcripts for audio and video recordings.</strong></p><ul><li>Identify who is speaking.</li><li>Include a word-for-word record of everything the speakers say.</li><li>Note any other significant sounds such as applause, laughter, questions from the audience, etc.</li><li>Place the transcript or link to the transcript close to the audio or video.</li><li>Provide only a short description for animations or illustrations that support text tutorials and point users to the text tutorial for more information.</li></ul><h4>Also, do</h4><ul><li>Provide a full detailed text description of video-only content.</li><li>Provide synchronized captions for all video that has audio unless that video is used as a visual aid for text already on the page.</li><li>Tell the user if no sound is used in a video clip.</li></ul><h4>Don’t</h4><ul><li>Provide less information in long descriptions or transcripts than what is contained in the audio, video or image.</li><li>Auto-play sounds that last longer than 3 seconds.</li></ul><h4>Exceptions</h4><ul><li>HighBond will not provide a second, user-selectable, audio track that includes audio descriptions for videos.</li></ul><h4>This guideline fulfills the following WCAG guidelines:</h4><ul><li><a href="https://www.w3.org/WAI/WCAG21/Understanding/audio-only-and-video-only-prerecorded">1.2.1 Level A: Audio-only and Video-only</a></li><li><a href="https://www.w3.org/WAI/WCAG21/Understanding/captions-prerecorded">1.2.2 Level A: Captions</a></li><li><a href="https://www.w3.org/WAI/WCAG21/Understanding/audio-description-or-media-alternative-prerecorded">1.2.3 Level A: Audio Description or Media Alternative</a></li><li><a href="https://www.w3.org/WAI/WCAG21/Understanding/audio-description-prerecorded">1.2.5 Level AA: Audio Description (Prerecorded)</a></li><li><a href="https://www.w3.org/WAI/WCAG21/Understanding/audio-control">1.4.2 Level AA: Audio Control</a></li></ul><h3>Public facing pages</h3><p>All previous accessibility guidelines apply when designing public facing plus a few more.</p><h4>Do</h4><ul><li>Create a site map</li><li>Provide links to related pages (e.g. related articles).</li><li>Have a table of contents (e.g. in Help Docs)</li><li>Tell the user when all form fields are required.</li><li>Mark optional fields as (optional).</li></ul><h4>This guideline fulfills the following WCAG guidelines:</h4><ul><li><a href="https://www.w3.org/WAI/WCAG21/Understanding/multiple-ways">2.4.5 Level AA: Multiple Ways</a></li><li><a href="https://www.w3.org/WAI/WCAG21/Understanding/labels-or-instructions">3.3.2 Level A: Labels or Instructions</a></li></ul><h3>Navigating the UI (<a href="https://medium.com/@jaydely/galvanize-product-designers-accessibility-faqs-6596541c48f1#204b">FAQ</a>)</h3><p>These guidelines are meant as best practices. Refer to the FAQ for more details.</p><ul><li>Don’t show sighted users Skip to Content links.</li><li>Use the object’s or destination’s name as the link instead of Click here or Read more where possible.</li><li>Put Learn more or other ambiguous links at the end of a sentence.</li><li>Know the difference between a Navigation Bar and Site Map.</li><li>Don’t identify content only by its shape, size, location, or implementation.</li><li>Don’t provide instructions only through sound.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=75780def136a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Running a remote-friendly virtual design sprint]]></title>
            <link>https://build.diligent.com/running-a-remote-friendly-virtual-design-sprint-48f4cd7badd6?source=rss-c75bd8843279------2</link>
            <guid isPermaLink="false">https://medium.com/p/48f4cd7badd6</guid>
            <category><![CDATA[virtual]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[remote]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[design-sprint]]></category>
            <dc:creator><![CDATA[Jayde Ly]]></dc:creator>
            <pubDate>Thu, 09 Jan 2020 19:12:37 GMT</pubDate>
            <atom:updated>2020-06-11T17:43:45.535Z</atom:updated>
            <content:encoded><![CDATA[<p>At <a href="https://www.wegalvanize.com/">Galvanize</a> we’ve integrated the <a href="https://www.thesprintbook.com/">Design Sprint</a> process with great success. It has helped us arrive at working solutions faster so that we can deliver more value to the customer quicker. It took us a few tries to figure out how to adapt the typical design sprint for our complex domain, but that’s another article for another day.</p><p>One of the biggest drawbacks of design sprints is that they are not remote-friendly. While most of our designers work out of the Vancouver office we do have a few that are remote. We wanted to involve these remote teammates because they have a wealth of insight and ideas to contribute but we didn’t make it easy on them to participate.</p><h3>Regular paper-based design sprints aren’t inclusive</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XEzseI1iIg1qP7IPFxWbFg.jpeg" /></figure><p>Every time we had remote people as core members of the sprint team it was, to put it nicely, less than optimal. Remote folks could help generate ideas but that was about it, they had a hard time following along with each of the activities when discussions and voting happened.</p><p>Remote folks couldn’t see what we were pointing at. They couldn’t vote since they couldn’t put up stickers as they didn’t have access to all of the stuff we put on the walls. They just had to trust that the team would vote on the best direction but this wasn’t fair.</p><p>To compensate, I awkwardly walked around pointing a laptop camera at all the post-its on the walls. I ended up trying to juggle the laptop, guide the activities, and keep everything on track all the while needing to contribute ideas myself (our design sprint facilitators are also core team members). Even with the laptop camera pointed at the walls they couldn’t always read what was on them and we could only show portions of the wall at any given time.</p><h3>Problems with paper</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d7dlEJsxH-J_luhIFvnNzg.jpeg" /></figure><p>Even for participants who are in the room with you:</p><ul><li><strong>It’s hard to read all of the post-its: </strong>Some people have terrible penmanship.</li><li><strong>It’s slow to hand-write and iterate over the sprint goal: </strong>I type way faster than I can print and making changes in ink was more work.</li><li><strong>Grouping the How Might We’s post-its is slow: </strong>People have to scan over a large surface area.</li><li><strong>Voting involved a lot of waiting: </strong>If people were standing in front of the thing you wanted to look at (e.g. HMWs and sketches) you had to wait.</li></ul><h3>Goal: Design a better experience for everyone</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aA2yfhAT4vQVwbB3CbyX4g.jpeg" /></figure><p>Our current design sprints were pretty good for people in the office and terrible for those who weren’t. But I didn’t want to solve for the lowest common denominator only. I wanted to make virtual design sprints awesome for everyone instead of creating an equally sub-optimal experience for the whole team.</p><h3>Step 1: Pick from an existing tool</h3><p>I wanted to use a tool that my team already had access to instead of introducing yet another tool — so I picked <a href="https://whimsical.com/">Whimsical</a>. We already have licenses and most people are familiar with it. For those who weren’t, there’s a very small learning curve.</p><p>Whimsical is not the best tool out there for live collaboration, however. There’s a small delay so you can’t always see when someone is editing the text of a box. I hear that <a href="https://mural.co/">Mural.co</a> is pretty good but I’ve never tried it myself and if you have access to <a href="https://www.figma.com/">Figma</a> that might work better but I decided to try Whimsical for its low learning curve and the fact it was already part of our toolset. We didn’t need much beyond basic boxes that you could easily type text in to, and then rearrange.</p><h3>Step 2: Set up expectations</h3><p>Since we were going digital, at the beginning of the design sprint there was a modification to the no devices rule: <strong>You can use your laptops but only for the design sprint.</strong></p><p>Everyone was asked to turn off all notifications, quit email and quit Slack. Anyone caught breaking the rule would have to buy everyone else coffee and doughnuts — joking not joking. Har har… just don’t break the rule, mmmkay?</p><h3>Step 3: Convert the sprint activities from paper to digital</h3><p>I went through each of the design sprint activities and set up a digital starter template. I went with a horizontal layout because it felt more like a timeline. Also, if your participants generate a lot of cards/ideas you don’t have to shift anything over.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ERd23UY9517F5q979Rwtnw.png" /><figcaption><a href="https://whimsical.com/VDNHULuHgKPJMPHdBF7ALb#VsSo8s35WwDc98wUUYgDKy"><em>View and copy template from Whimsical</em></a></figcaption></figure><h3>Activity 1: Create the sprint goal</h3><p>The first box at the top labeled “Final goal, don’t use this yet” is reserved for the facilitator at the end when we collaboratively create the final goal. I like to put the instructions right in the boxes themselves so that people aren’t looking around for instructions elsewhere.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4l_oSa_P7E7zL5ezZ3XgWA.png" /></figure><h4>Assign out columns</h4><p>Each team member was assigned a column and their names were placed in the boxes. I had to assign out columns to compensate for Whimsical’s non-realtime updates to prevent people from overwriting each other’s ideas.</p><h4>Randomize the assignment order</h4><p>I randomized the assignment order so that at the end of the exercise you wouldn’t be able to tell who generated which set of ideas. This would keep the playing field level and prevent participants from influencing each other when it came time to vote. You can use <a href="https://www.random.org/lists/">random.org’s free online tool</a> to randomize the names.</p><h4>Create the final sprint goal</h4><p>After all of the ideas were generated, the facilitator would be in charge of drafting the final sprint goal with the help of the rest of the team. Being able to type and easily make changes while we iterated over the sprint goal made facilitation so much easier.</p><h3>Activity 2: Sprint questions</h3><p>Most of the post-it type idea generation activities were conducted in a similar format. Everyone was assigned a column and were asked to generate ideas from top to bottom.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sjjgC9vhJxQ2K2Ly8A-zYw.png" /></figure><h4>Create your voting dots beforehand</h4><p>To make things easier when it came time to vote, I created the voting dots along the top ahead of time and assigned them out as well. Each “Px” was replaced with a participant’s name. Our deciders get 4 votes and other members of the team received 2 votes each. Users could then just move their dots around to the cards they wanted to vote for.</p><h4>Separate the final sprint questions</h4><p>After the voting was done, we would then moved the top voted cards to the top voted column. These would then become our sprint questions. In Whimsical, if you put your dots inside the card you could grab the card and it would also move the dots for you.</p><h3>Activity 3: How might we</h3><p>For HMWs I prepared a few group headings which would be replaced with theme names. During the subject matter expert and stakeholder interviews, sprint members would create their HMW cards after which were sorted into themes.</p><p>Everyone helped to sort the cards into their categories. We were able to scan more of the cards quicker than if they were posted on the walls. I found that we were able to get through this part much faster than using paper post-its since everyone could see everything and we didn’t have to deal with post-its falling off the walls.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RBFHJSVekyQHDjtLUYRWZw.png" /></figure><h3>Activity 4: Customer journey map</h3><p>One interesting alteration we’ve made to the design sprint process is that the customer journey map is already created and ready to use. Before even going into a design sprint there’s a lot of research that’s already done up-front, these include customers and subject matter expert interviews. From those interviews, we’ve already built a customer journey map so doing it again in the design sprint seemed redundant.</p><p>Instead, we took a screenshot of the customer journey map that we had created previously in Whimsical, and we pasted it here. Then we put the HMW cards to create a heatmap of where we saw challenges.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mmphW5Wsef3F6dXlLjCgSw.png" /><figcaption>Whimsical courtesy of our awesome product designer <a href="https://www.linkedin.com/in/julie-b%C3%A9langer-b6432348/">Julie Bélanger</a></figcaption></figure><h3>Activity 5: Sketching</h3><p>For the sketching activity, we still stuck with a fat sharpie and paper. Everyone, even those who were remote, was required to sketch using sharpies on paper. The sharpies were all the same medium. In a previous design sprint, some remote people used an iPad and were able to generate much better-looking wireframes which might have skewed the voting results.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EmwuR-uYXvS7OHosYSplaw.png" /></figure><h3>Activity 6: Silent art gallery</h3><p>After we were done sketching everyone was then asked to take photos of their sketches, and then add those photos to Whimsical.</p><p>This way the remote people could easily review all of the sketches and having the sketches in Whimiscal also made it much easier for everyone else who was in the office to look at all of the sketches too. They didn’t have to wait for other people to move on. Another great benefit of voting in Whimsical was that you couldn’t see who voted on which sketch.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y5qJBBDI2DLyMLnrTlI2lg.png" /></figure><h3>Activity 7: Storyboard</h3><p>We like to include some key details with our storyboard so I added an area for notes beside each step. This will help the prototype designer to work quickly without having to ask as many questions. The idea being that as the prototype designer, you should be able to whip something up by referencing all of the activity results including this storyboard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Uq2wIde7S_2YMvL4QWoJyw.png" /></figure><h3>Mission accomplished!</h3><p>Looking back at the problems with a paper-based design sprint, I think we were able to resolve all of them nicely and make the whole process better for everyone involved.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oQGrlg4fRLZDwdBoXc0_zA.png" /></figure><ul><li><strong>Easy to read “post-its”: </strong>You didn’t have to struggle to try to make out what someone wrote down.</li><li><strong>Faster to iterate over the sprint goal: </strong>Typing was way easier than dealing with handwriting.</li><li><strong>Faster HMW grouping: </strong>Everyone could scan the whole area of cards and move them to the right spot faster.</li><li><strong>Faster voting: </strong>You spent less time waiting in line and feeling rushed, and got to spend more time evaluating sketches/ideas.</li><li><strong>Voting was anonymous: </strong>People weren’t influenced by who put which vote where.</li><li><strong>Everyone could see everything: </strong>No more waiting around to look at something.</li><li><strong>People didn’t feel as rushed: </strong>You didn’t feel like you were blocking someone else’s view.</li><li><strong>Self-documenting design sprints: </strong>We no longer had to manually digitize all of the activity results by taking photos and transcribing notes to be used as references during the product design process.</li></ul><h4>Do you want to try this with your team? <a href="https://whimsical.com/VDNHULuHgKPJMPHdBF7ALb#VsSo8s35WwDc98wUUYgDKy">Use our template</a>!</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=48f4cd7badd6" width="1" height="1" alt=""><hr><p><a href="https://build.diligent.com/running-a-remote-friendly-virtual-design-sprint-48f4cd7badd6">Running a remote-friendly virtual design sprint</a> was originally published in <a href="https://build.diligent.com/">Build Diligent</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understanding the types of disabilities to build empathy]]></title>
            <link>https://build.diligent.com/understanding-the-types-of-disabilities-to-build-empathy-f8d6a266d69?source=rss-c75bd8843279------2</link>
            <guid isPermaLink="false">https://medium.com/p/f8d6a266d69</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[disability]]></category>
            <dc:creator><![CDATA[Jayde Ly]]></dc:creator>
            <pubDate>Thu, 12 Apr 2018 21:51:10 GMT</pubDate>
            <atom:updated>2021-04-23T18:31:58.227Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Akujul9G5MtS5G_b-NbHsA.png" /></figure><p>Accessibility is a vast topic that has a lot of misconceptions. When people hear the word “accessibility”, the first things that come to mind are colour blindness, assistive technology (screen readers), people with disabilities and minority.</p><h4><strong>Questions that usually come up</strong></h4><ul><li>How many of our users are actually differently enabled?</li><li>Do we need to spend that much time, effort and energy on something that could be viewed as an edge case?</li><li>Are we focussing too much attention on a small group of people?</li></ul><p>The thing is, not every disability is a visible disability and obvious. You can’t always tell that someone has a disability just by looking at them and not everyone will disclose that they have a non-visible disability. Disabilities can also be environmental or temporary.</p><h4><strong>Environmental disabilities</strong></h4><ul><li>The lighting is poor or your computer monitor isn’t that great so you have trouble reading the screen.</li><li>You’re somewhere noisy so you can’t hear the video/audio very well phone support.</li></ul><h4><strong>Temporary disabilities</strong></h4><ul><li>Someone goes skiing and breaks their arm.</li><li>Your carpal tunnel is flaring up so you don’t want to use the mouse more than you have to.</li><li>You have arthritis in your hands (very common as people age).</li><li>Other temporary impairments could occur because of surgery or medication.</li></ul><p>People who suffer from temporary impairments may not know about accessibility solutions. They may not know how to use accessibility features and will struggle to do their jobs if we don’t make our software accessible.</p><h3>Galvanize’s accessibility goals</h3><p>Here at Galvanize, we believe that building accessible software is the right thing to do for all of our users regardless of ability. Software that is designed and built to pass WCAG 2.0 accessibility standards results in a better experience for everyone. Out of a total of 38 requirements from WCAG 2.0 Level A and AA, there is only a very small numbers of the requirements pertaining to users with disabilities. The rest are related to usability.</p><h4><strong>Be inclusive</strong></h4><p>We want to design software that is accessible to as many people as possible.</p><h4><strong>Improve user efficiency</strong></h4><p>Accessible software allows users to navigate more effectively using a keyboard. (e.g. keyboard shortcuts or terminate an interaction flow using the esc key).</p><h3>Colour blindness</h3><p>Some people have reduced or lack sensitivity to certain colors (“color blindness”) or increased sensitivity to bright colors. These variations in perception of colors and brightness can be independent of the visual acuity.</p><p>The images below are just approximations of what someone with colour blindness would see. As colour blindness varies from person to person, a simulator cannot represent everyone’s vision.</p><h4><strong>Deuteranomaly (people who can’t see green, mild)</strong></h4><p>This affects 5% of males. Greens, yellows, oranges, reds, and browns may appear similar, especially in low light. It can also be difficult to tell the difference between blues and purples, or pinks and greys.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/417/1*6krB2FIMauCgB7OJTSW9Pg.png" /><figcaption>Normal vision</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/421/1*1oE5XGlKPZp-JPXdrmPUuA.png" /><figcaption>Deuteranomaly</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*1vIx7l70tQgk47wC2-UygA.png" /><figcaption>Normal vision</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*X5loc5Gb4SJr6UhRXT-e-A.png" /><figcaption>Deuteranomaly</figcaption></figure><h4><strong>Deuteranopia (people who can’t see green, severe)</strong></h4><p>This affects 1% of males. Greens, yellows, oranges, reds, and browns may appear similar, especially in low light. It can also be difficult to tell the difference between blues and purples, or pinks and grays.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/417/1*6krB2FIMauCgB7OJTSW9Pg.png" /><figcaption>Normal vision</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/423/1*FgN_YOfFciNDRkDtMcTSYA.png" /><figcaption>Deuteranopia</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*1vIx7l70tQgk47wC2-UygA.png" /><figcaption>Normal vision</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*Q_f2z69UR2AtWX37FknPAw.png" /><figcaption>Deuteranopia</figcaption></figure><h4><strong>Protanomaly (people who can’t see red, mild)</strong></h4><p>This affects 1% of males. People with this have difficulty seeing red, orange and yellow. They have great difficulty distinguishing between oak and dark shades. They can confuse deep reds with blacks and dark greens and purples.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/417/1*6krB2FIMauCgB7OJTSW9Pg.png" /><figcaption>Normal vision</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/418/1*vW4rXUrHZV5VRyneMrO2lA.png" /><figcaption>Protanomaly</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*1vIx7l70tQgk47wC2-UygA.png" /><figcaption>Normal vision</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*-C3iQy8Z4s1RGBoCzi0lwg.png" /><figcaption>Protanomaly</figcaption></figure><h4><strong>Protanopia (people who can’t see red, severe)</strong></h4><p>This affects 1% of males. They have difficulty seeing red, orange and yellow. Great difficulty distinguishing between oak and dark shades. Confuse deep reds with blacks and dark greens and purples.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/417/1*6krB2FIMauCgB7OJTSW9Pg.png" /><figcaption>Normal vision</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/423/1*je9vK_LS17e8579AILgThw.png" /><figcaption>Protanopia</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*1vIx7l70tQgk47wC2-UygA.png" /><figcaption>Normal vision</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*zKI3WpSFcYer3NNdWUZRBA.png" /><figcaption>Protanopia</figcaption></figure><h4><strong>Tritanomaly (people who can’t see blue, mild)</strong></h4><p>Extremely rare, only 5% of people who are colour blind have this. Confuses blue with green and yellow with violet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/417/1*6krB2FIMauCgB7OJTSW9Pg.png" /><figcaption>Normal vision</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/418/1*PrpDsrEqJ1qXEIlnaVOo7g.png" /><figcaption>Tritanomaly</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*1vIx7l70tQgk47wC2-UygA.png" /><figcaption>Normal vision</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*xlZ3Nuvzs5qiJD0DnDACvg.png" /><figcaption>Tritanomaly</figcaption></figure><h4><strong>Tritanopia (people who can’t see blue, severe)</strong></h4><p>Extremely rare, only 5% of people who are colour blind have this. Confuses blue with green and yellow with violet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/417/1*6krB2FIMauCgB7OJTSW9Pg.png" /><figcaption>Normal vision</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/416/1*XTf4JTCf4PZE3ZluxlSx2w.png" /><figcaption>Tritanopia</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*1vIx7l70tQgk47wC2-UygA.png" /><figcaption>Normal vision</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*wXqbF_CB2Omly9uoKJcpbw.png" /><figcaption>Tritanopia</figcaption></figure><h4><strong>Incomplete Achromatopsia (limited colour)</strong></h4><p>Extremely rare. Incomplete or partial Achromatopsia compared to complete Achromatopsia may have better vision (20/120 to 20/80). The reduced vision could be compensated with low vision devices (<a href="http://www.achromatopsia.info/low-vision-care/">http://www.achromatopsia.info/low-vision-care/</a>).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/417/1*6krB2FIMauCgB7OJTSW9Pg.png" /><figcaption>Normal vision</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/416/1*uMkv79QjgWoixiOhPOx-_A.png" /><figcaption>Incomplete Achromatopsia</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*1vIx7l70tQgk47wC2-UygA.png" /><figcaption>Normal vision</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*owoRTewi4T8vkrot5089Jw.png" /><figcaption>Incomplete Achromatopsia</figcaption></figure><h4><strong>Complete Achromatopsia (no colour)</strong></h4><p>Extremely rare. Achromatopsia affects an estimated 1 in 30,000 people worldwide. Complete achromatopsia is more common than incomplete achromatopsia.</p><p>Complete Achromatopsia will have reduced vision (20/200 or less) due to an abnormality of the retina. They also have no color vision, sensitivity to light (photophobia) and the presence of nystagmus (shaking of the eyes). The reduced vision could be compensated with low vision devices (<a href="http://www.achromatopsia.info/low-vision-care/">http://www.achromatopsia.info/low-vision-care/</a>).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/417/1*6krB2FIMauCgB7OJTSW9Pg.png" /><figcaption>Normal vision</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/421/1*28WaO91TnmFo9bXsrcqKJg.png" /><figcaption>Complete Achromatopsia</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*1vIx7l70tQgk47wC2-UygA.png" /><figcaption>Normal vision</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*jXT7vrrrUmK4EtNRIXzakA.png" /><figcaption>Complete Achromatopsia</figcaption></figure><p>*Statistics referenced from:</p><ul><li><a href="https://nei.nih.gov/health/color_blindness/facts_about">https://nei.nih.gov/health/color_blindness/facts_about</a></li><li><a href="http://www.colour-blindness.com/general/prevalence/">http://www.colour-blindness.com/general/prevalence/</a></li><li><a href="http://wearecolorblind.com/article/a-quick-introduction-to-color-blindness/">http://wearecolorblind.com/article/a-quick-introduction-to-color-blindness/</a></li></ul><h3>Low vision/blind</h3><p>Visual disabilities range from mild or moderate vision loss in one or both eyes (“low vision”) to substantial and uncorrectable vision loss in both eyes (“blindness”).</p><p>The term vision loss refers to individuals who reported that they have trouble seeing, even when wearing glasses or contact lenses, as well as to individuals who reported that they are blind or unable to see at all.</p><h4><strong>Blind</strong></h4><p>Substantial, uncorrectable loss of vision in both eyes.</p><h4><strong>Low vision (partial sight)</strong></h4><p><a href="http://w3c.github.io/low-vision-a11y-tf/requirements.html#overview-of-low-vision">http://w3c.github.io/low-vision-a11y-tf/requirements.html#overview-of-low-vision</a></p><ul><li>Includes poor acuity (vision that is not sharp)</li><li>Tunnel vision (seeing only the middle of the visual field)</li><li>Central field loss (seeing only the edges of the visual field)</li><li>Clouded vision.</li></ul><h4><strong>Also solves for</strong></h4><ul><li>Keyboard users who work faster with less reliance on using a mouse.</li><li>Users who are in less than ideal lighting situations or have lower contrast monitors.</li></ul><h4><strong>Statistics</strong></h4><ul><li>Worldwide: 253 million</li><li>USA: 16.4 million people were between the ages of 18–64</li><li>Canada: 0.5 million with significant vision loss</li></ul><p>*Statistics referenced from:</p><ul><li><a href="http://www.who.int/mediacentre/factsheets/fs282/en/">http://www.who.int/mediacentre/factsheets/fs282/en/</a></li><li><a href="http://www.afb.org/info/blindness-statistics/adults/facts-and-figures/235">http://www.afb.org/info/blindness-statistics/adults/facts-and-figures/235</a></li><li><a href="http://www.cnib.ca/en/about/media/vision-loss/pages/default.aspx">http://www.cnib.ca/en/about/media/vision-loss/pages/default.aspx</a></li></ul><h4><strong>Examples of low vision</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/420/1*i6fVfDifRlT9F0BRppGMCA.png" /><figcaption><em>Example of central field loss</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/482/1*_lPXX7VbLA9_YGXw5JhELw.png" /><figcaption><em>Example of peripheral field loss</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/482/1*dNd2pOuhq6vb1ZdhKiwLHA.png" /><figcaption><em>Example of other field loss</em></figcaption></figure><p>*Images source from <a href="http://w3c.github.io/low-vision-a11y-tf/requirements.html#overview-of-low-vision">http://w3c.github.io/low-vision-a11y-tf/requirements.html#overview-of-low-vision</a></p><h3>Hearing loss</h3><p>Auditory disabilities range from mild or moderate hearing loss in one or both ears (“hard of hearing”) to substantial and uncorrectable hearing loss in both ears (“deafness”). Some people with auditory disabilities can hear sounds but sometimes not sufficiently enough to understand all speech, especially when there is background noise. This can include people using hearing aids.</p><p>Just a small minority of people needing hearing aids use them even though hearing aids can be vital for holding employment and improve quality of life.</p><h4><strong>Also solves for</strong></h4><ul><li>Noisy Environments such as open offices or coffee shops.</li></ul><h4><strong>Examples of hearing loss</strong></h4><ul><li><strong>Hard of hearing</strong> — mild or moderate hearing impairments in one or both ears</li><li><strong>Deafness</strong> — substantial, uncorrectable impairment of hearing in both ears</li><li><strong>Deaf-blindness</strong> — substantial, uncorrectable hearing and visual impairments</li></ul><h4><strong>Statistics</strong></h4><ul><li>Worldwide: 5% of population (disabling)</li><li>Europe: 16% of adults (hard of hearing)</li><li>USA: 20% of the population (hard of hearing)</li><li>Canada: 10% of the population (hard of hearing)</li></ul><p>*Statistics referenced from:</p><ul><li><a href="http://www.who.int/mediacentre/factsheets/fs300/en/">http://www.who.int/mediacentre/factsheets/fs300/en/</a></li><li><a href="https://www.hear-it.org/hearing-loss-in-europe">https://www.hear-it.org/hearing-loss-in-europe</a></li><li><a href="https://www.hear-it.org/three-million-canadians-suffer-from-hearing-loss">https://www.hear-it.org/three-million-canadians-suffer-from-hearing-loss</a></li><li><a href="http://www.hearingloss.org/content/basic-facts-about-hearing-loss">http://www.hearingloss.org/content/basic-facts-about-hearing-loss</a></li></ul><h3>Cognitive and neurological</h3><p>Cognitive and neurological disabilities may affect any part of the nervous system and impact how well people hear, move, see, speak, and understand information. Cognitive, learning and neurological disabilities do not necessarily affect the intelligence of a person.</p><p>Albert Einstein couldn’t read until he was nine. Walt Disney, General George Patton, and Vice President Nelson Rockefeller had trouble reading all their lives. Whoopi Goldberg and Charles Schwab and many others have learning disabilities which haven’t affected their ultimate success.</p><p>People with learning disabilities are as smart or smarter than their peers. But they may have difficulty reading, writing, spelling, reasoning, recalling and/or organizing information. A learning disability can’t be cured or fixed; it is a lifelong issue.</p><h4><strong>Learning disabilities</strong></h4><ul><li>Reading (dyslexia)</li><li>Writing (dysgraphia)</li><li>Processing numbers (dyscalculia)</li><li>Spatial or temporal orientation</li></ul><p>Fifteen percent of the U.S. population, or one in seven Americans, has some type of learning disability, according to the National Institutes of Health.</p><h4><strong>Also solves for making the user interface more intuitive</strong></h4><ul><li>Simplify complicated layouts.</li><li>Allow users to self-enable with new features (more tooltips or guided tours).</li><li>Break complex sentences into smaller, easier to read pieces.</li><li>Help users understand where they are, where they want to go and how to get there.</li></ul><h4><strong>Statistics</strong></h4><p><strong>Spatial or temporal orientation / worldwide population: unknown</strong><br>Spatial orientation disability- difficulty controlling their body. May not always know where arms and legs are without looking.(Difficulty switching from keyboard to mouse?)</p><p><em>Temporal orientation</em> is a cognitive structure for processing information by comparing events in relationship to <em>when</em> they occur. This involves the critical skill of telling time and much more. It is essential for planning, organizing, communicating, and record keeping.</p><p><strong>Reading (dyslexia) / worldwide population: approximately 15%<br></strong>Characterized by difficulties with accurate and/or fluent word recognition and by poor spelling and decoding abilities.</p><p><strong>Writing (dysgraphia) / worldwide population: unknown<br></strong>The inability to handwrite coherently. Can be compensated with touch typing(keyboard). There are not many studies about dysgraphia, so the prevalence of this learning disability is unknown.</p><p><strong>Processing numbers (dyscalculia) / worldwide population: 3% to 6%<br></strong>Adults with this <a href="https://www.additudemag.com/adhd/article/12223.html">math-related condition</a> will find it difficult to keep track of numbers, perform simple calculations, and memorize basic math facts.</p><p>*Statistics referenced from:</p><ul><li><a href="http://www.dyslexia-reading-well.com/dyslexia-statistics.html">http://www.dyslexia-reading-well.com/dyslexia-statistics.html</a></li><li><a href="https://www.additudemag.com/what-is-dyscalculia-overview-and-symptom-breakdown/">https://www.additudemag.com/what-is-dyscalculia-overview-and-symptom-breakdown/</a></li></ul><h3>Motion and vision Sensitivities</h3><p>Photo-epileptic Seizures (Photo Epilepsy) are caused by strobing, flickering or flashing effects and is more of an extreme reaction to what people see on the screen. A much more common disorder that many people might not even realize they have is vestibular disorder.</p><h4><strong>Vestibular disorders</strong></h4><p>Even if an animating or moving object does not cause a seizure, it may cause nausea or dizziness in some people. Vestibular Disorders are caused by parts of the inner ear and brain that process the sensory information involved with controlling balance and eye movements.</p><ul><li>35% of adults aged 40+ in the USA have experienced some form of vestibular dysfunction.</li><li>After age 55 the rate of new cases start to increase as people develop strokes, brain tumors, or Alzheimer’s.</li><li>Flashing or patterned effects can make people with or without epilepsy feel disorientated, uncomfortable or unwell.</li></ul><h4><strong>The following items can result in difficulties for users with vestibular disorders:</strong></h4><ul><li>High contrast graphics with tight parallel lines.</li><li>Animated scrolling that lasts longer than perhaps 1/4 second.</li><li>Parallax or reverse parallax — simultaneous foreground and background scrolling in different directions or at different speeds.</li><li>Moving images beneath static text.</li></ul><h4><strong>Statistics</strong></h4><ul><li>As many as 35% of adults aged 40 years or older in the United States — approximately 69 million Americans — have experienced some form of vestibular dysfunction.</li></ul><p>*Statistics referenced from:</p><ul><li><a href="https://vestibular.org/understanding-vestibular-disorder">https://vestibular.org/understanding-vestibular-disorder</a></li><li><a href="https://www.epilepsy.com/learn/about-epilepsy-basics/who-gets-epilepsy">https://www.epilepsy.com/learn/about-epilepsy-basics/who-gets-epilepsy</a></li></ul><h3>Speech disabilities</h3><h4><strong>Symptoms</strong></h4><ul><li>Difficulty producing speech that is recognizable by other people or voice recognition software.</li><li>Loudness or clarity of someone’s voice</li></ul><h4><strong>US statistics</strong></h4><ul><li>Estimated 17.9 million adults 18+ (7.6%) reported having a problem with their voice in the past 12 months.</li><li>9.4 million (4%) of adults reported having problems using their voice that lasted 1+ weeks during the past 12 months</li><li>More than 70 million people worldwide stutter (1 in every 100).</li><li>More than 3 million Americans (1%) stutter.</li></ul><h4><strong>How can we make their life easier?</strong></h4><p>By providing alternatives to phone/voice chat support such as live chat and email.</p><h4><strong>Also solves for</strong></h4><ul><li>Loud environments</li><li>Poor/unstable Internet connection that is unable to support voice chat.</li></ul><p>*Statistics referenced from:</p><ul><li><a href="https://www.nidcd.nih.gov/health/statistics/quick-statistics-voice-speech-language">https://www.nidcd.nih.gov/health/statistics/quick-statistics-voice-speech-language</a></li><li><a href="https://www.dosomething.org/facts/11-facts-about-stuttering">https://www.dosomething.org/facts/11-facts-about-stuttering</a></li></ul><h3>Learn to build accessible software</h3><p>Now that you’re empathy is all built up, you should read, “<a href="https://medium.com/@jaydely/29116d9d623c">Learning to build accessible software at Galvanize</a>”. In it I share out the 4 hour course I developed for our teams.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f8d6a266d69" width="1" height="1" alt=""><hr><p><a href="https://build.diligent.com/understanding-the-types-of-disabilities-to-build-empathy-f8d6a266d69">Understanding the types of disabilities to build empathy</a> was originally published in <a href="https://build.diligent.com/">Build Diligent</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Learning to build accessible software at Galvanize]]></title>
            <link>https://build.diligent.com/learning-to-build-accessible-software-at-acl-29116d9d623c?source=rss-c75bd8843279------2</link>
            <guid isPermaLink="false">https://medium.com/p/29116d9d623c</guid>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Jayde Ly]]></dc:creator>
            <pubDate>Thu, 12 Apr 2018 21:51:02 GMT</pubDate>
            <atom:updated>2023-11-15T22:53:01.652Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve worked at a lot of companies and Galvanize is the first one where I didn’t feel like I was alone in my desire to build accessible software. My journey with accessibility at Galvanize started when my UX Manager first approached me and said, “Hey, it’s time we make accessibility a real priority. Can you help me?”</p><p>I’m going to share with you the challenges I had with learning about accessibility and how I distilled it down for the rest our design and development team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x-0swfvK8UYJ7FlOqC_5Gg.png" /></figure><h3>First step, building my own empathy and understanding through research</h3><p>I knew that, “<a href="https://medium.com/@jaydely/f8d6a266d69">there are a lot of people with disabilities</a>” out in the world but this was still a pretty vague concept. I didn’t have any concrete numbers of how many people and what types of disabilities there are. I didn’t understand how these disabilities limited some people’s ability to use our software.</p><h4><strong>Challenge #1: Learn about the most common types of disabilities and gather some statistics.</strong></h4><p>I popped open Google and started searching for stuff like:</p><ul><li>Worldwide disabilities statistics</li><li>Canada disabilities statistics</li><li>US disabilities statistics</li><li>Types of disabilities</li><li>Break down for Canada, US, Europe and Asia</li><li>and so on.</li></ul><p>I learned that there were a lot more people living with disabilities. Not everyone has a “visible disability” and not all disabilities are permanent.</p><h4><strong>Not everyone has a “visible disability”</strong></h4><p>For example, you won’t know if someone is colour blind unless they tell you. You won’t be able to tell if someone has motion sensitivity. That “awesome” large auto-play video on landing pages that you often see could be making people feel nauseous.</p><h4><strong>Not all disabilities are permanent</strong></h4><p>Some people have temporary disabilities as a result of an accident, medication or surgery.</p><p>A big takeaway was that when we solve for people with disabilities, we actually make our software better for everyone:</p><ul><li>Solving for hearing loss also solves for people in loud environments.</li><li>Solving for poor eyesight also solves for people working with poor lighting or poor monitors.</li><li>Making your software keyboard accessible allows power users to fill in forms and do their work faster.</li></ul><h3>Step two, learning about best practices and WCAG 2.0</h3><p>I went back to my good friend, Google, and searched for stuff like:</p><ul><li>Learning about WCAG 2.0</li><li>How to meet WCAG 2.0</li><li>Accessibility best practices</li><li>Designing accessible software</li><li>etc.</li></ul><h4><strong>Challenge #2: The content I found was either too basic, too high level, or too dense.</strong></h4><p>There are a lot of presentation type guides to accessibility to help get you started but they were often too basic. I couldn’t confidently design our software to pass WCAG 2.0 standards without diving deeper to learn more but learning more was difficult.</p><p>Learning more involved reading some pretty overwhelming, convoluted, and confusing websites. I had to read a lot of different websites, viewed many slideshows, bought a couple of digital books and combed through “<a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/">Understanding WCAG 2.0</a>”.</p><p>My process sometimes involved reading something from “Understanding WCAG 2.0” and then I would have to reference other books to see if my understanding aligned with those of the authors. It felt like I was cramming for school again.</p><h3>Step three, making accessibility accessible</h3><p>Now that I had all of this knowledge I had to transfer it to our design and development teams. It’s easy to send someone links or books and say, “Here you go, read this. Oh, and this and this too.” The problem with that approach is that it’s very time consuming for the other person and therefore not repeatable. I knew I wasn’t going to get a lot of traction that way.</p><h4><strong>Challenge #3: Distill down what I’d learned and pass it onto others.</strong></h4><p>I would need to make the journey for everyone else way less painful and much faster. I managed to condense down everything I’d learned into a 4 hour course that involves some reading and an online PluralSight* course. Although PluralSight is a paid site, they do offer a free 10 day trial (up to 200 minutes) that you can sign up for.</p><p>Note: neither I nor Galvanize are affiliates of PluralSight. The link provided below does not have a referral link attached to it. I just found that the PluralSight course was invaluable in my education. It really helped to connect the dots between theory and actual implementation.</p><h3>Passing the baton, here’s the 2-hour accessibility course I created for Galvanize product designers</h3><h4><strong>Getting Started</strong></h4><ol><li><a href="https://medium.com/@jaydely/f8d6a266d69">Understanding the types of disabilities to build empathy</a> — 10 min.</li><li><a href="https://www.pluralsight.com/courses/web-accessibility-meeting-guidelines">Meeting Web Accessibility Guidelines WCAG 2.0 Course</a> (PluralSight) — 2 hours.</li></ol><p>3. Design for Accessibility, 4 articles</p><ul><li><a href="https://medium.com/salesforce-ux/7-things-every-designer-needs-to-know-about-accessibility-64f105f0881b">7 things that every designer needs to know about accessibility</a> — 14 min.</li><li><a href="https://uxdesign.cc/designing-accessible-products-e8aa79b55ebc">Designing accessible products</a> — 10 min.</li><li><a href="https://alistapart.com/article/designing-safer-web-animation-for-motion-sensitivity">Designing safer web animation for motion sensitivity</a> — 10 min.</li><li><a href="https://uxdesign.cc/ui-animation-please-use-responsibly-e707dbdb12d5">UI animation: please use responsibly</a> — 7 min.</li></ul><p>4. <a href="https://medium.com/@jaydely/galvanize-designer-guidelines-75780def136a">Galvanize Product Designer Accessibility Guidelines</a><a href="https://academy.acl.com/unit/view/id:10639"> </a>— 13 min.</p><p>5. <a href="https://medium.com/@jaydely/galvanize-product-designers-accessibility-faqs-6596541c48f1">Galvanize Product Designer Accessibility FAQs</a><a href="https://academy.acl.com/unit/view/id:11735"> </a>— 9 min.</p><h3>Where we are today</h3><p>I am very proud and excited to say that we have support from all levels of management. All Galvanize designers and front-end developers are required to take this course. The first part of this course involves, “<a href="https://medium.com/@jaydely/f8d6a266d69">Understanding the types of disabilities to build empathy</a>”.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=29116d9d623c" width="1" height="1" alt=""><hr><p><a href="https://build.diligent.com/learning-to-build-accessible-software-at-acl-29116d9d623c">Learning to build accessible software at Galvanize</a> was originally published in <a href="https://build.diligent.com/">Build Diligent</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>