<?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 Mike Goodwin on Medium]]></title>
        <description><![CDATA[Stories by Mike Goodwin on Medium]]></description>
        <link>https://medium.com/@goodo73?source=rss-da865d67c7ab------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Hi3cf3vgcpS7p7fs1DNS-w.jpeg</url>
            <title>Stories by Mike Goodwin on Medium</title>
            <link>https://medium.com/@goodo73?source=rss-da865d67c7ab------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 16:31:39 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@goodo73/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[A11y for Rookies]]></title>
            <link>https://medium.com/@goodo73/a11y-for-rookies-b6f24d1cfa41?source=rss-da865d67c7ab------2</link>
            <guid isPermaLink="false">https://medium.com/p/b6f24d1cfa41</guid>
            <category><![CDATA[a11y]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Mike Goodwin]]></dc:creator>
            <pubDate>Tue, 06 Feb 2018 23:18:40 GMT</pubDate>
            <atom:updated>2018-02-09T03:37:28.170Z</atom:updated>
            <content:encoded><![CDATA[<p>In mid-2015, after 15+ years as a bank software programmer, I became a front-end developer at <a href="http://www.opencities.com/"><strong>OpenCities</strong></a>, whose clients are mostly local shires and councils. So, not only were my days now filled with HTML, CSS and JavaScript, I was exposed to this thing called ‘accessibility’.</p><p>Web accessibility (or ‘a11y’, for short) is concerned with making web page content available to everyone, no matter their physical or mental abilities. A user’s location or language, or the available software and hardware, also shouldn’t limit their access.</p><blockquote>“The power of the web is in its universality. Access by everyone, regardless of disability, is an essential aspect.”</blockquote><blockquote>Tim Berners-Lee (inventor of the World Wide Web)</blockquote><p>Close to 1 in 5 Australians have a disability, which amounts to roughly 4.5 million people. Australia also has an ageing population. As vision and hearing impairment is strongly age-related, we can expect disability numbers will rise.</p><p>You might ask yourself, “Why should I care?”.</p><p>I’m no business person, but you’d be hard-pressed to argue that it’s wise to ignore 20% of potential customers. Secondly, by making your website accessible you’re more likely to win the loyalty and trust of users. You can also apply the less business-focussed rationale that making your site accessible to all users is the right thing to do.</p><p>The <a href="https://www.legislation.gov.au/Details/C2017C00339"><strong>Disability Discrimination Act 1992</strong></a> makes it a legal requirement in Australia that websites are accessible (refer to sections 5, 6 &amp; 24). Note that this requirement applies to all websites, not just those of government bodies.</p><p>The Web Content Accessibility Guidelines (WCAG 2.0) are the standard against which websites are judged.</p><blockquote>“[WCAG 2.0] covers a wide range of recommendations for making Web content more accessible. Following these guidelines will make content accessible to a wider range of people with disabilities, including blindness and low vision, deafness and hearing loss, learning disabilities, cognitive limitations, limited movement, speech disabilities, photosensitivity and combinations of these. Following these guidelines will also often make your Web content more usable to users in general.”</blockquote><blockquote>Excerpt from <a href="https://www.w3.org/TR/WCAG20"><strong>Web Content Accessibility Guidelines 2.0</strong></a></blockquote><p>The guidelines are split into three levels of conformance:</p><ul><li>A — the least strict</li><li>AA — more strict</li><li>AAA — the most strict</li></ul><p>‘AA’ is the level to which Australian websites need to conform.</p><p>The guidelines can be a daunting read, and may leave you looking like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*tUG39vcXs49GkijxPTymdw.gif" /><figcaption>Jack in The Shining can’t work out what just happened</figcaption></figure><p>However, there are some simple ways you can implement a11y in your site.</p><p><strong>Make your text easy to read<br></strong>The easier your content is to read, the more people can understand it and make use of it. You can do this in a number of ways:</p><ul><li>Break up ‘slabs’ of text into smaller, more understandable chunks, such as multiple paragraphs or bulleted lists</li><li>Include definitions of any acronyms and abbreviations</li><li>Ideally avoid unusual words, technical terms or jargon, but if you must use them, provide definitions (e.g. a glossary)</li><li>Text that is complex by necessity can be accompanied by a visual aid (e.g. a diagram or video)</li><li>Text should be left-aligned rather than centred or justified. This means the reader will know where the next line will start, and avoids annoying white space between words.</li></ul><p><strong>Use headings properly<br></strong>Headings give structure to your content by separating text into meaningful sections. Although this is important for every user, it’s especially relevant for people who use screen readers, as they often navigate a page using headings.</p><blockquote>“Computer screen readers read out loud the content that is on the computer screen. Screen readers enable access to a computer and all the things it does when magnification no longer helps or when you might experience visual fatigue if you have to read large amounts of on-screen text.”</blockquote><blockquote>Excerpt from <a href="http://www.visionaustralia.org/learn-more/learning-to-live-independently/using-technology-and-computers/technology-overview/computer-screen-readers"><strong>Vision Australia’s definition of a computer screen reader</strong></a></blockquote><p>To put this structure in place, use the HTML heading elements (i.e. &lt;h1&gt;, &lt;h2&gt;, … &lt;h6&gt;). Create a proper hierarchy by not skipping heading levels:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/570/1*HCcId1R3Pm_rQfNR2YwY3Q.png" /><figcaption>An H4 following an H2? Bad front-end developer. No more laptop stickers for you!</figcaption></figure><p>As headings indicate what information will follow, make your heading text descriptive.</p><p><strong>Provide meaningful alternative text for images<br></strong>All images implemented with the &lt;img&gt; element require an alt attribute. The text in the attribute will be read out by a screen-reader, so it should accurately describe the image. Essentially you want to convey the same content to a screen reader user as is conveyed to someone viewing the image. For that reason, don’t use the name of the image file as the alternative text.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*oX1QODL-n1NWev3_iATN3A.jpeg" /></figure><p>Avoid this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/724/1*l7rSPxNF-3d9Tbw853g6Gg.png" /><figcaption>“alt=’abc_12–34.jpg’. What the hell does that tell me about the image??”</figcaption></figure><p>This is definitely preferred:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/593/1*xCBCiqLutM2bcWmil0-JqQ.png" /><figcaption>“alt=’Woman sitting holding a camera’. I guess this image is of a woman sitting holding a camera.”</figcaption></figure><p>If the image is purely decorative, alternative text is not required. However, the alt attribute is still necessary.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/483/1*RmAhsnu4J4jcsKDxyF3tGQ.png" /><figcaption>“Looks like this image isn’t content I need to know about”</figcaption></figure><p><em>Tip: Avoid beginning alternative text with ‘Image of’. A screen reader will, by default, announce to the user that the content is an image. Hearing “Image image of” is both redundant and annoying.</em></p><p><em>Tip: If you’re a Twitter user, you can add descriptions to images you tweet.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/610/1*J7u5FXuInd-f6qtZbYt3sA.png" /><figcaption>Check the Compose image descriptions checkbox within your Twitter account’s Accessibility settings.</figcaption></figure><p><strong>Use an acceptable colour contrast ratio<br></strong>WCAG 2.0 specifies minimum contrast ratios for text and background colours. Meeting or exceeding these minimums means the text can still be read by people with moderately low vision, without the use of contrast-enhancing assistive technology. It’s also beneficial when viewing screens in sunlight.</p><p>To meet the ‘AA’ conformance level, two colours must have a contrast ratio of at least 4.5:1. Where large text is used, the ratio must be at least 3:1. Large text is defined as at least:</p><ul><li>14pt (approx. 19px) AND bold; or</li><li>18pt (24px)</li></ul><p>To meet the ‘AAA’ conformance level, the contrast ratio must be a minimum of 7:1 (or 4.5:1 for large text).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/614/1*2TUdgTZqQpsNrWdamfB5Zg.png" /><figcaption>Visual examples of colour contrast and font combinations which pass (and fail) WCAG requirements.</figcaption></figure><p>One of the best ways to comply with this guideline is to use an online colour contrast checker. These will accept two colours and present the user with their contrast ratio. Generally they’ll also include some sort of pass/fail indicator.</p><p>There is no shortage of online colour contrast checkers, but two I’d recommend are:</p><ul><li><a href="http://leaverou.github.io/contrast-ratio"><strong>Contrast Ratio (by Lea Verou)</strong></a></li><li><a href="http://webaim.org/resources/contrastchecker"><strong>Color Contrast Checker (by WebAIM)</strong></a></li></ul><p><strong>Make your link text descriptive<br></strong>It’s common for users to scan a page, looking at just the links. Similarly, screen reader users will often navigate the page by the links alone. It’s therefore important that link text describes the link destination, and the description has meaning when read in isolation (without the context of the surrounding text). Text such as ‘Read more’ and ‘Click here’ shouldn’t be used as it tells the user nothing about where the link will take them.</p><p><em>Tip: Avoid beginning link text with “Link to …”. Similar to alt-text for images, a screen reader will tell the user it’s encountered a link.</em></p><p><strong>Supply text alternatives for audio<br></strong>If your site includes audio files, each one should be accompanied by a text transcript. In the case of a video with an audio track, it should include captions within the video. Primarily, these text versions are included for deaf users, or users with some amount of hearing loss. However, a text alternative is also helpful for users watching a video in a public place with the sound turned off, or whose first language is different to the language of the content.</p><p>No doubt there can be challenges in making a website accessible. But after reading the above, I trust you’re encouraged by the knowledge that there are simple accessibility techniques available to you, with the ones shown here just a small sample.</p><p>Further reading and some handy tools:</p><ul><li><a href="https://webaim.org/techniques/alttext"><strong>WebAIM’s Alternative Text article</strong></a> is a fantastic, in-depth discussion about the correct use of alternative text.</li><li><a href="https://ambrosedesigns.co.uk/aligning-text"><strong>Readability: Aligning Text (by Ambrose Designs)</strong></a> explains why left-aligned text improves readability and is a better option than centred or justified text.</li><li><a href="http://www.accessify.com/tools-and-wizards/accessibility-tools/table-builder"><strong>Accessible Table Builder (from Accessify)</strong></a> is a really helpful tool for setting up an accessible table.</li><li><a href="https://a11yproject.com/"><strong>The A11Y Project</strong></a> is an Open Source project which features short pieces of content (such as How To’s, code patterns and general info) aimed at making accessibility easier to understand.</li></ul><p>In closing, I have to give a shout-out to two of my OpenCities teammates: <a href="https://medium.com/u/f08b92fb82d">Remya Ramesh</a> for prodding me, quite often, to write this (my first) article, and <a href="https://medium.com/u/6b1f7aba9465">Rachael Mullins</a> for her proof-reading genius.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b6f24d1cfa41" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>