<?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 Georgia Burnside on Medium]]></title>
        <description><![CDATA[Stories by Georgia Burnside on Medium]]></description>
        <link>https://medium.com/@burnsidegeorgia?source=rss-4c47b7c48574------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*XNrDYy1ZNB1HIFxF</url>
            <title>Stories by Georgia Burnside on Medium</title>
            <link>https://medium.com/@burnsidegeorgia?source=rss-4c47b7c48574------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 12:31:39 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@burnsidegeorgia/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[5 Easy Steps to Make Your Website More Accessible]]></title>
            <link>https://medium.com/@burnsidegeorgia/5-easy-steps-to-make-your-website-more-accessible-5474a9da88d?source=rss-4c47b7c48574------2</link>
            <guid isPermaLink="false">https://medium.com/p/5474a9da88d</guid>
            <category><![CDATA[css]]></category>
            <category><![CDATA[how-to]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[lists]]></category>
            <category><![CDATA[html]]></category>
            <dc:creator><![CDATA[Georgia Burnside]]></dc:creator>
            <pubDate>Sun, 05 Jun 2022 03:18:43 GMT</pubDate>
            <atom:updated>2022-06-05T03:21:09.144Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Website Accessibility Header" src="https://cdn-images-1.medium.com/max/786/0*bYgnddXwq4RSMcqe" /></figure><p>As a software engineer, I can readily attest that we are busy. Deadlines and due dates push us to deliver projects as quickly as possible. Our primary goal is to get our main deliverables fully functioning and finished on time, which very often leaves us little to no time to work on the small details. The little things that bring our website or application’s quality from 100% to 110%.</p><p>Sometimes it’s a feature that toggles your navigation bar in an interesting manner or some CSS to spice up the visual appeal of each page. But what very often gets overlooked is your website’s accessibility features. These small things that usually go unnoticed by an average user can make a world of difference to those who need them. So in the hopes of making your site even more accessible, <em>and </em>saving you time, here are my top 5 accessibility features and how to implement them ASAP.</p><blockquote><strong>1. Mute auto-playing videos</strong></blockquote><blockquote><strong>2. Word wrap for enlarging text</strong></blockquote><blockquote><strong>3. Providing alt information for your media</strong></blockquote><blockquote><strong>4. Provide examples for form validators</strong></blockquote><blockquote><strong>5. Visible navigation and interaction</strong></blockquote><h3>#1 Mute auto-playing videos</h3><p>Include <strong>“?autoplay=1&amp;amp;mute=1”</strong> in the <strong>src</strong> of your iframe element.</p><figure><img alt="Mute auto playing videos html example" src="https://cdn-images-1.medium.com/max/749/0*aDwWFIF6kyEy6NyR" /></figure><p><strong>Why: </strong>Similar to users with light sensitivity, some users have sound sensitivity. Understanding that auto-playing media is good for engagement, muting the audio can help prevent some individuals from becoming overstimulated. And to be fair, I can’t think of a person who actually <em>likes </em>to be surprised by an auto-playing video.</p><h3>#2 Word wrap for enlarging text</h3><p>Apply word-wrap CSS for large font or lengthy text</p><figure><img alt="CSS word wrap format" src="https://cdn-images-1.medium.com/max/354/0*-2MtqPvBll8Wg9wf" /></figure><p><strong>Why</strong>: It’s common nowadays for users to zoom in on a web page to make things more legible. But for those who need it to utilize a webpage, having a long word inside a small div or large text in a header, these elements can become too wide for the page. While having to pan over to read the rest of a line sounds simple enough, it can really disrupt the flow of reading for certain users. Making sure your website fits on their screen will make their experience better and help the overall look of your site.</p><h3>#3 Providing alt information for your media</h3><p>Always include an <strong>alt </strong>attribute in important media</p><figure><img alt="Alt attribute example" src="https://cdn-images-1.medium.com/max/1024/0*FbG8hGBhantyOqK4" /></figure><p>But also leave the <strong>alt </strong>attribute blank for decorative elements that <em>aren’t useful</em> for those who cannot see them.</p><figure><img alt="empty alt attribute example for unimportant images" src="https://cdn-images-1.medium.com/max/1024/0*SQKFLA03vg1es80X" /></figure><p><strong>Why: </strong>Not only is this feature useful as a placeholder if your <strong>src </strong>becomes invalid over time but for people using Text To Speech (TTS) this information is what is read aloud by the software. Having concise yet descriptive alt attributes such as “cute cat photo” makes much more sense than “3e0d39.jpg”. Conversely, leaving the alt attribute blank for media that does not contribute to the content of the page will allow these items to be skipped over by a TTS reader.</p><h3>#4 Provide examples for form validators</h3><p>Simply adding a <strong>&lt;p&gt;</strong> tag under the field that’s using a validator can make your requirements easy for others to grasp</p><figure><img alt="example for phone number format required by a form" src="https://cdn-images-1.medium.com/max/607/0*bl3CtSzytmJq3dwZ" /></figure><p><strong>Why: </strong>Regardless of accessibility needs, it’s just nice to not make your users guess what format you require.</p><h3>#5 Visible navigation and interaction</h3><p>Adding pseudo-classes to your CSS can make navigating and interacting with a page much easier.</p><p>:focus — useful for keyboard navigation</p><p>:hover — useful for mouse navigation</p><p>:active — useful when item is selected</p><figure><img alt="CSS styling options for hover, active, and focus" src="https://cdn-images-1.medium.com/max/410/0*xjixd2pJRTF2xaCI" /><figcaption>This example probably won’t look too pretty. But I’m sure you get my point.</figcaption></figure><p><strong>Why:</strong> There are a variety of users who benefit from this type of styling but for those who don’t use a mouse or need help comprehending what they have selected or are focused on, these features can make their time on your website much more enjoyable. Not to mention it’s fun as a developer to make things a little prettier to interact with! This article by Eric Bailey has plenty of more details on this subject in his article <a href="https://css-tricks.com/focusing-on-focus-styles/"><strong>here</strong></a> if you want to spend more time on it.</p><h3>Conclusion:</h3><p>This list is a small drop in the bucket of features you can incorporate to make your hard work accessible to everyone. If you want to look through a much larger collection of features head to <a href="https://www.w3.org/WAI/fundamentals/accessibility-intro/"><strong>W3C Web Accessibility Initiative</strong></a><strong> </strong>to view a fantastic resource for these types of features.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5474a9da88d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>