<?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 Holden Foreman on Medium]]></title>
        <description><![CDATA[Stories by Holden Foreman on Medium]]></description>
        <link>https://medium.com/@hs4man21?source=rss-bda4adac756b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*JtK_yxp-PNQxjpXP7xcz8g.jpeg</url>
            <title>Stories by Holden Foreman on Medium</title>
            <link>https://medium.com/@hs4man21?source=rss-bda4adac756b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 12:47:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@hs4man21/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[My goals as The Washington Post’s first-ever Accessibility Engineer]]></title>
            <link>https://washpost.engineering/my-goals-as-the-washington-posts-first-ever-accessibility-engineer-453adeb13d51?source=rss-bda4adac756b------2</link>
            <guid isPermaLink="false">https://medium.com/p/453adeb13d51</guid>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[journalism]]></category>
            <category><![CDATA[disability]]></category>
            <category><![CDATA[medium]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Holden Foreman]]></dc:creator>
            <pubDate>Wed, 25 Jan 2023 15:52:34 GMT</pubDate>
            <atom:updated>2023-01-25T15:52:34.380Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A stick figure stands inside a dark blue circle with arms outstretched. There is another, thinner blue circle outlining the one in which the stick figure stands. The background color, including the stick figure’s body and space between the circles, is white. This icon is commonly associated with web accessibility." src="https://cdn-images-1.medium.com/max/615/1*3UiFA7Zg_LERUyEbrTSZTA.jpeg" /><figcaption>Image by <a href="https://commons.wikimedia.org/wiki/User:Dave_Braunschweig">Dave Braunschweig</a> (<a href="https://en.wikipedia.org/wiki/en:Creative_Commons">Creative Commons</a> <a href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Attribution-Share Alike 4.0 International</a> license)</figcaption></figure><p>Note: To make this blog post understandable to more readers, we also published <a href="https://washpost.engineering/my-goals-as-the-washington-posts-new-accessibility-engineer-in-plain-language-492c7c61ae9e?source=collection_home---4------0-----------------------">a shorter version in plain language</a>. If you have questions regarding either post, please contact me via <a href="/service/mailto:holden.foreman@washpost.com">email</a>, <a href="https://twitter.com/hsforeman">Twitter</a>, <a href="https://www.linkedin.com/in/holdenforeman">LinkedIn</a> or <a href="https://twitter.com/hsforeman">Ma</a><a href="https://mas.to/@hsforeman">stodon</a>.</p><p>The Washington Post is furthering its commitment to accessibility, and the work employees are already doing to make our content more accessible, by naming its first-ever dedicated Accessibility Engineer. I’ve long cared about accessibility, and I’m excited to serve in this new role.</p><p>So what do we mean by accessibility?</p><p>According to <a href="https://accessibility.iu.edu/understanding-accessibility/">Indiana University</a>, “Accessibility is the degree to which a product, device, service, environment, or facility is usable by as many people as possible, including by persons with disabilities.” A common example of accessibility in practice is including wheelchair-accessible seats at event venues, which may be reachable via ramps and/or elevators instead of only stairs.</p><p>At The Post, we care about the accessibility of our digital products. We have <a href="https://www.washingtonpost.com/accessibility/">a statement on our website</a> outlining some of our goals. We aim to include <a href="https://support.microsoft.com/en-us/topic/df98f884-ca3d-456c-807b-1a1fa82f5dc2">alternative text (alt text)</a> on images, captions on videos and transcriptions of audio content such as podcasts. We also know that accessibility considerations stretch far beyond these fundamental measures. The underlying code of our products should be written with accessibility in mind. There are extensive guidelines to consider, such as <a href="https://www.w3.org/WAI/standards-guidelines/wcag/">the Web Content Accessibility Guidelines (WCAG) international standard</a>. I’ve blogged in the past about some of our steps toward <a href="https://washpost.engineering/improving-screen-reader-and-keyboard-accessibility-on-election-results-pages-e6f6cdbab25f?source=collection_home---4------2-----------------------">screen reader</a> and <a href="https://washpost.engineering/keyboard-focus-helping-users-navigate-the-post-without-a-mouse-83c572385240?source=collection_home---4------8-----------------------">keyboard</a> accessibility.</p><p>We know at The Post that everyone must care about accessibility in order for it to happen. Having an engineer dedicated to accessibility will help us align our efforts, maintain up-to-date standards and explore new opportunities in research and feature development. The Accessibility Engineer will also help educate others on the latest accessibility practices and will be a resource for internal support.</p><p>I like Indiana University’s definition of accessibility because it emphasizes two things:</p><ol><li>Accessibility is not something you either “have” or “don’t have.” There are levels to it. Your website may have appropriate alt text for some images but not all of them. You may have considered certain forms of color blindness, but not others, when choosing your color palette.</li><li>Accessibility is important for everyone. <a href="https://ssir.org/articles/entry/the_curb_cut_effect">“The curb-cut effect”</a> describes how cutting ramps into sidewalk curbs made the sidewalks more accessible not just to people in wheelchairs but to many others as well: people pushing strollers or carts, for instance.</li></ol><p>Parts of WCAG relate to assistive technology, which is used primarily by people with disabilities to help them navigate digital content. An example of this is a screen reader, which may be used by people who are blind or low-vision to hear digital content described to them. They use controls to move between elements on a page, and the associated text and/or function is read aloud. This is one purpose of alt text; it is read by a screen reader to describe an image for those who cannot see it clearly. Similarly, interactive elements should often be labeled in code using <a href="https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-label">aria-labels</a>.</p><p>While standards are helpful, accessibility is more than meeting a checklist and calling it a day.</p><p>We want to create a dialogue with our users to better understand how you interact with our products and how we can make your experiences not only accessible but also user-friendly and efficient. Some changes may be as simple as adjusting labeling and page structures, while others may involve developing brand new features and experiences. And others may require updating the internal products that are used by The Post’s employees.</p><p>An essential part of my new role is doing my research and listening to you, The Post’s users. So please send any questions, feedback and thoughts that you have to accessibility@washpost.com. We can’t promise a response to everyone, but we will monitor our inbox carefully as we continue along this never-ending journey.</p><p>If you have questions for me personally or notice any errors in this blog post, please don’t hesitate to contact me via <a href="/service/mailto:holden.foreman@washpost.com">email</a>, <a href="https://twitter.com/hsforeman">Twitter</a>, <a href="https://www.linkedin.com/in/holdenforeman">LinkedIn</a> or <a href="https://twitter.com/hsforeman">Ma</a><a href="https://mas.to/@hsforeman">stodon</a>. Thanks so much for reading.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=453adeb13d51" width="1" height="1" alt=""><hr><p><a href="https://washpost.engineering/my-goals-as-the-washington-posts-first-ever-accessibility-engineer-453adeb13d51">My goals as The Washington Post’s first-ever Accessibility Engineer</a> was originally published in <a href="https://washpost.engineering/">Washington Post Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My goals as The Washington Post’s new Accessibility Engineer (in plain language)]]></title>
            <link>https://washpost.engineering/my-goals-as-the-washington-posts-new-accessibility-engineer-in-plain-language-492c7c61ae9e?source=rss-bda4adac756b------2</link>
            <guid isPermaLink="false">https://medium.com/p/492c7c61ae9e</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[medium]]></category>
            <category><![CDATA[journalism]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[disability]]></category>
            <dc:creator><![CDATA[Holden Foreman]]></dc:creator>
            <pubDate>Wed, 25 Jan 2023 14:51:53 GMT</pubDate>
            <atom:updated>2023-01-25T15:54:21.691Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A stick figure stands inside a dark blue circle with arms outstretched. There is another, thinner blue circle outlining the one in which the stick figure stands. The background color, including the stick figure’s body and space between the circles, is white. This icon is commonly associated with web accessibility." src="https://cdn-images-1.medium.com/max/615/1*3UiFA7Zg_LERUyEbrTSZTA.jpeg" /><figcaption>Image by <a href="https://commons.wikimedia.org/wiki/User:Dave_Braunschweig">Dave Braunschweig</a> (<a href="https://en.wikipedia.org/wiki/en:Creative_Commons">Creative Commons</a> <a href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Attribution-Share Alike 4.0 International</a> license)</figcaption></figure><p>Note: This is the plain language version of <a href="https://washpost.engineering/my-goals-as-the-washington-posts-first-ever-accessibility-engineer-453adeb13d51">my Accessibility Engineer blog post</a>. If you have questions, please contact me via <a href="/service/mailto:holden.foreman@washpost.com">email</a>, <a href="https://twitter.com/hsforeman">Twitter</a>, <a href="https://www.linkedin.com/in/holdenforeman">LinkedIn</a> or <a href="https://twitter.com/hsforeman">Ma</a><a href="https://mas.to/@hsforeman">stodon</a>.</p><p>I am The Washington Post’s new Accessibility Engineer. I am excited to serve in this new role.</p><p>To me, accessibility is about making something useful to as many people as possible. This includes people with disabilities. Some examples of accessibility are:</p><ul><li>ramps and elevators for people in wheelchairs</li><li>braille for people who are blind or have low vision</li></ul><p>I am a software engineer. I focus on the accessibility of things online. Some of those things are:</p><ul><li>alternative text, also called alt text or image descriptions</li><li>captions for videos</li></ul><p>Accessibility includes a lot of other things. There are standards that software engineers should consider, like <a href="https://www.w3.org/WAI/standards-guidelines/wcag/">the Web Content Accessibility Guidelines international standard</a>. It is often called WCAG.</p><p>The Washington Post cares about accessibility, and it is helpful to have an Accessibility Engineer. This job will give me time to focus on accessibility. I will help teach my coworkers about accessibility, too.</p><p>Accessibility is not only about standards and checklists.</p><p>We want to understand how you use The Washington Post’s products. Some of our products are:</p><ul><li>our website</li><li>our mobile apps</li><li>our newspapers</li></ul><p>Do you have accessibility questions, ideas or feedback for The Washington Post? Please send them to accessibility@washpost.com. We might not respond to everyone. But part of my new job is listening to you.</p><p>If you have questions or feedback just for me, then please send them to my <a href="/service/mailto:holden.foreman@washpost.com">email</a>, <a href="https://twitter.com/hsforeman">Twitter</a>, <a href="https://www.linkedin.com/in/holdenforeman">LinkedIn</a> or <a href="https://twitter.com/hsforeman">Ma</a><a href="https://mas.to/@hsforeman">stodon</a>. Thank you so much for reading.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=492c7c61ae9e" width="1" height="1" alt=""><hr><p><a href="https://washpost.engineering/my-goals-as-the-washington-posts-new-accessibility-engineer-in-plain-language-492c7c61ae9e">My goals as The Washington Post’s new Accessibility Engineer (in plain language)</a> was originally published in <a href="https://washpost.engineering/">Washington Post Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Accessibility case study: Pairing election data visualizations with tables]]></title>
            <link>https://washpost.engineering/accessibility-case-study-pairing-election-data-visualizations-with-tables-6bd5db221a1c?source=rss-bda4adac756b------2</link>
            <guid isPermaLink="false">https://medium.com/p/6bd5db221a1c</guid>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[screen-reader]]></category>
            <category><![CDATA[maps]]></category>
            <category><![CDATA[html]]></category>
            <category><![CDATA[data-visualization]]></category>
            <dc:creator><![CDATA[Holden Foreman]]></dc:creator>
            <pubDate>Mon, 14 Mar 2022 20:58:57 GMT</pubDate>
            <atom:updated>2022-03-14T21:14:36.782Z</atom:updated>
            <content:encoded><![CDATA[<p>In <a href="https://washpost.engineering/improving-screen-reader-and-keyboard-accessibility-on-election-results-pages-e6f6cdbab25f">a previous blog post</a>, we discussed ways to make election results pages more accessible to users navigating via screen readers. An improvement we discussed was using <a href="https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-hidden">aria-hidden</a> so that screen readers would skip inaccessible county-level result maps, which are valuable for sighted readers but hindered page navigation for screen readers. While hiding the visualization was an improvement, it masked the problem of the county data being inaccessible rather than truly solving it.</p><p>For <a href="https://www.washingtonpost.com/elections/election-results/texas/2022-primaries/">the 2022 Texas primaries</a>, The Post tried out a solution for inaccessible county-level results by sharing these results in tables below the maps. On mobile devices, these tables are always shown to both screen readers and to sighted readers. (On mobile, the maps are quite small, so the tables are useful to everyone.) On desktop, the tables are hidden to sighted readers using our sr-only class below— a <a href="https://webaim.org/techniques/css/invisiblecontent/">screen-reader-only class</a> — to simplify the page appearance.</p><pre><em>.sr-only</em> {<em><br>  </em>clip: rect(0,0,0,0);<br>  border: 0;<br>  height: 1px;<br>  margin: -1px;<br>  overflow: hidden;<br>  padding: 0;<br>  position: absolute;<br>  width: 1px;<br>}</pre><p>Sighted readers on desktop can view the county-level results map, and screen readers can access these results in table format (since the table is still part of the DOM despite being hidden from sighted users).</p><figure><img alt="Screenshot of Texas 2022 primaries results page on mobile, specifically showing the county-level results table is visible to the naked eye" src="https://cdn-images-1.medium.com/max/418/1*a_yR0oUVA3WlkXoZGk5riw.png" /><figcaption>On mobile, the county-level results table is shown to the naked eye since it is difficult to click on one of the many counties on the small map of Texas.</figcaption></figure><figure><img alt="Screenshot of Texas 2022 primaries results page on desktop, specifically showing the county-level results table is invisible to the naked eye" src="https://cdn-images-1.medium.com/max/1024/1*2rATGoSZYvGS8-g052QWig.png" /><figcaption>On desktop, note that the county-level results table is invisible to the naked eye. We made the table accessible only to screen readers to save space on the page while retaining screen reader accessibility of these results.</figcaption></figure><p>Of course, sharing information in a table does not guarantee that it will be accessible to screen readers. <a href="https://washpost.engineering/improving-screen-reader-and-keyboard-accessibility-on-election-results-pages-e6f6cdbab25f">Our previous post</a> addressed some ways to make tables more accessible to screen readers, including using the &lt;caption&gt; tag, organizing headers correctly with &lt;th&gt; tags and ensuring that abbreviations are read correctly by writing them out as aria-labels.</p><p>And this is just one example of a broader reality: While we can and should increase the accessibility of content in any given format, we also need to present the same content in multiple formats to make it accessible to all.</p><p>If you’re interested in a similar approach for one of your projects and have questions, or if you notice any errors in this post, please don’t hesitate to contact me <a href="/service/mailto:holden.foreman@washpost.com">via email</a> and/or <a href="https://twitter.com/hsforeman">via Twitter</a>. Thanks so much for reading.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6bd5db221a1c" width="1" height="1" alt=""><hr><p><a href="https://washpost.engineering/accessibility-case-study-pairing-election-data-visualizations-with-tables-6bd5db221a1c">Accessibility case study: Pairing election data visualizations with tables</a> was originally published in <a href="https://washpost.engineering/">Washington Post Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Keyboard focus: Helping users navigate The Post without a mouse]]></title>
            <link>https://washpost.engineering/keyboard-focus-helping-users-navigate-the-post-without-a-mouse-83c572385240?source=rss-bda4adac756b------2</link>
            <guid isPermaLink="false">https://medium.com/p/83c572385240</guid>
            <category><![CDATA[keyboard-accessibility]]></category>
            <category><![CDATA[tabindex]]></category>
            <category><![CDATA[keyboard-focus]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[a11y]]></category>
            <dc:creator><![CDATA[Holden Foreman]]></dc:creator>
            <pubDate>Tue, 14 Dec 2021 23:35:47 GMT</pubDate>
            <atom:updated>2021-12-14T23:35:47.354Z</atom:updated>
            <content:encoded><![CDATA[<p>Imagine that you are in the middle of making a search on your computer, and you break your mouse. This search is urgent; you need to disprove a statement your in-law made ASAP. So what do you do without your mouse?</p><p>Some people with motor disabilities do not use a mouse at all. Instead, they navigate content using their keyboard. You can try this for yourself by opening <a href="https://www.washingtonpost.com/">The Post’s homepage</a> and hitting the “tab” key. Notice the blue outline that appears on buttons such as the search button shown below. This outline tells you which button is currently selected, also known as having <a href="https://cccaccessibility.org/resources/htctu/81/">keyboard focus</a>.</p><p>Hit “tab” until you see the search button highlighted.</p><figure><img alt="A screenshot of The Washington Post website with the search button highlighted with a blue outline" src="https://cdn-images-1.medium.com/max/936/0*TmomLTYiQ_x-XUK2.png" /></figure><p>If you hit the “return” key while a button has keyboard focus, then it should perform the behavior that it would perform when clicked with a mouse. Hit “return” to open the search bar.</p><figure><img alt="A screenshot of The Washington Post website with the search bar opened up for typing and highlighted with a blue outline" src="https://cdn-images-1.medium.com/max/840/0*x7aRJtrh-njDrG0p.png" /></figure><p>If you try this on different websites, you will come across instances where you hit the “tab” key multiple times but struggle to find any button or other clickable element highlighted on the page. This is an accessibility issue because it can make it difficult or impossible to use links and buttons without a mouse. We have certainly come across this issue on our site at The Post.</p><p>Issues with keyboard focus often appear in two distinct areas.</p><h3>Tab index</h3><p>Things that receive keyboard focus are part of the “tab index” on a page. As the name indicates, this is the order in which the “tab” key navigates elements on the page. By default, things like button and links are included in the tab index of a page in the order they appear programmatically. Manually modifying <a href="https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/tabindex">the tabindex HTML attribute</a> can make or break page accessibility.</p><p>For the purposes of this guide, we will only worry about two possible values of tabindex: “0” and “-1.”</p><p>If the thing that should be keyboard focusable is not an inherently clickable element like a link or button, but has been made clickable for the purposes of a page, then you should make sure it has been assigned tabindex=&quot;0&quot; so that it is included in the page’s tab index.</p><p>By assigning tabindex=&quot;-1&quot; to an inherently clickable element, you exclude it from the tab index, and it thus cannot be reached with the keyboard. This is sometimes desirable, but it can also be applied erroneously and is the first thing to look for as a developer if someone is unable to see — or hear — a button on a page when they should.</p><h3>Focus styles</h3><p>When tab index is correct but you still can’t see an element highlighted on a page when it has received keyboard focus, then your CSS is likely to blame.</p><p>Browsers generally have default styles for keyboard focus, but these defaults can often be insufficient, so you need to be diligent in testing and fixing any issues.</p><p>At The Post, we have a class called focus-highlight that we apply to many elements on our site (including the search button demoed above) in order to establish the desired focus behavior.</p><p>Here is the corresponding CSS:</p><pre>.focus-highlight:focus {<br>    outline: 1px auto -webkit-focus-ring-color<br>}</pre><p>Note the :focus after the class name. This means that the style will be applied to the element with this class only when it has keyboard focus. We use the outline CSS property to indicate focus here, but there are instances where other methods of indicating focus are appropriate, such as drastically changing the color of a large button. It’s important that your focus styles have sufficient color contrast; you can verify this via tools like <a href="https://webaim.org/resources/contrastchecker/">the WebAIM contrast checker</a>.</p><p>If you consult users and accessibility guides to ensure appropriate tabindex and focus styles, then you will make your site more keyboard accessible.</p><p>If you notice any errors in this post, or if you have any questions for me, please let me know <a href="/service/mailto:holden.foreman@washpost.com">via email</a> and/or <a href="https://twitter.com/hsforeman">via Twitter</a>. Thanks so much for reading.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=83c572385240" width="1" height="1" alt=""><hr><p><a href="https://washpost.engineering/keyboard-focus-helping-users-navigate-the-post-without-a-mouse-83c572385240">Keyboard focus: Helping users navigate The Post without a mouse</a> was originally published in <a href="https://washpost.engineering/">Washington Post Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Improving screen reader and keyboard accessibility on election results pages]]></title>
            <link>https://washpost.engineering/improving-screen-reader-and-keyboard-accessibility-on-election-results-pages-e6f6cdbab25f?source=rss-bda4adac756b------2</link>
            <guid isPermaLink="false">https://medium.com/p/e6f6cdbab25f</guid>
            <category><![CDATA[aria]]></category>
            <category><![CDATA[keyboard]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[screen-reader]]></category>
            <category><![CDATA[a11y]]></category>
            <dc:creator><![CDATA[Holden Foreman]]></dc:creator>
            <pubDate>Thu, 07 Oct 2021 18:52:04 GMT</pubDate>
            <atom:updated>2021-10-07T19:16:19.543Z</atom:updated>
            <content:encoded><![CDATA[<p>Between <a href="https://www.washingtonpost.com/elections/election-results/ohio/house-districts-11-15-primaries/">primaries</a>, <a href="https://www.washingtonpost.com/elections/election-results/california/governor-recall/">a recall effort</a> and <a href="https://www.washingtonpost.com/elections/election-results/world/germany-election-results/">a German election</a> — and with the November elections imminent—<a href="https://www.notion.so/news-engineering/Newsroom-Engineering-at-the-Washington-Post-b898410f09a342dd97b9a07c7973bc8e">The Washington Post’s News Engineering team</a> (of which I’m a part) has been busy building and maintaining live results pages.</p><p>We are always making improvements to the UX of these pages, but one thing that was often being missed in our roadmaps is <a href="https://webaim.org/intro/">accessibility</a>. For instance, many users with motor disabilities <a href="https://webaim.org/techniques/keyboard/">use keyboard controls instead of a mouse</a> to navigate content. And many users who are hard of sight listen to content <a href="https://webaim.org/techniques/screenreader/">using a screen reader</a>. It’s essential that we build our content for navigation via these methods just as we do for those who can see the page and use a mouse. And while there is much more to web accessibility, these two areas are the focus of this blog post.</p><p>For those unfamiliar with using a screen reader, <a href="https://www.smashingmagazine.com/2018/12/voiceover-screen-reader-web-apps/">here’s a good reference</a>. One way to use a screen reader is by “stepping” through elements on a page in order. When doing this, each step should take you to the next meaningful element of the page in a logical order and read useful text aloud to the user.</p><p>Over the summer, we identified issues by simply stepping through our pages via keyboard and with the built-in Mac screen reader <a href="https://www.apple.com/voiceover/info/guide/_1121.html">VoiceOver</a>. The focus of this post is on our fixes to those issues. (As we made these fixes, we thought about our workflow and the need to incorporate accessibility throughout the development cycle. Stay tuned for a future blog post with more on that.)</p><p>Feel free to jump around to the different sections of this post using the links below.</p><ol><li><a href="#6f29">Providing “skip to main content” links for quicker page navigation</a></li><li><a href="#7ff7">Using </a><a href="#7ff7">aria-label on abbreviated text so screen readers read full words</a></li><li><a href="#c261">Making tables easier for screen readers to navigate</a></li><li><a href="#bdc2">Using </a><a href="#bdc2">aria-hidden on maps so that screen readers skip them</a></li></ol><h3>Providing “skip to main content” links for quicker page navigation</h3><p>As noted by excellent web accessibility resource <a href="https://webaim.org/techniques/skipnav/">WebAIM</a>, “The main content is not usually the first thing on a web page. Keyboard and screen reader users generally must navigate … navigation links, sub-lists of links, corporate icons, site searches, and other elements before ever arriving at the main content.”</p><p>Many sites feature <a href="https://css-tricks.com/how-to-create-a-skip-to-content-link/">a “skip to main content” link</a>, an anchor link that jumps the user from the top of a page to its content, skipping over header links and other auxiliary content in the process. For screen reader users, the “skip to main content” link is a time-saver that keeps them from needing to hear every element in a page header read aloud before they get to hear article text, for instance. Similarly, sighted users navigate pages via keyboard don’t want to have to tab through every link in a page header in order to reach a link in an article.</p><p>You may not have seen a “skip to main content” link before because they often use CSS to hide from view unless currently selected via the keyboard. Press the tab key after opening one of our pages, and the “skip to main content” link appears on the top left corner of the page.</p><p>The Post long ago embedded a “skip to main content” link in the site header for use on all pages. However, we noticed earlier this year that this resource was malfunctioning on our live election results pages. The link ended with #main-content, and no element had id=main-content on our results pages.</p><p>I recommend <a href="https://css-tricks.com/how-to-create-a-skip-to-content-link/">this guide to setting up one of these links</a>. The key is testing it on all the pages of your site to ensure that one and only one element on each page has an id matching the link’s href. We had to fix this retroactively, reinforcing the importance of including accessibility checks like this from the start of the development cycle to avoid gaps in coverage.</p><p>Below is a demo of using the “skip to main content” link on <a href="https://www.washingtonpost.com/elections/election-results/ohio/house-districts-11-15-primaries/">our Ohio U.S. House special election primary results page</a>. (Press the tab key to access the link in the top left corner of the screen. Then press enter.)</p><figure><img alt="gif showing the skip to main content link on our Ohio election results page being highlighted and clicked, then jumping the user down to highlight the first link in the page’s main content" src="https://cdn-images-1.medium.com/max/1024/1*ZSo6Lk88oq73-xjwweG0MA.gif" /></figure><h3>Using aria-label on abbreviated text so screen readers read full words</h3><p>While screen readers are constantly improving, they still often fail to discern abbreviations, especially less common ones. In many of our live elections results pages we include abbreviations of certain words, such as the “Unc.” for “Uncontested” and “Pct.” for “Percent.” We noticed screen readers reading aloud “Unc.” and “Pct.” literally instead of reading aloud the full words.</p><p>Our team often uses “*” to indicate someone is an incumbent in an election. Screen readers won’t know this unless we make the connection for them.</p><p>In both cases, we use <a href="https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques/Using_the_aria-label_attribute">HTML’s</a><a href="https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques/Using_the_aria-label_attribute">aria-label attribute</a> as a space for text that is read by screen readers instead of the on-screen text. The aria-label attribute is often associated with labeling things that lack text, but it is also useful when you want to have a screen reader-friendly version of specific text on a page:</p><pre>// Situation A: Only full word is read by screen readers,<br>// but only the abbreviation is shown to sighted users<br>&lt;span aria-label=&quot;Uncontested&quot;&gt;Unc.&lt;/span&gt;</pre><pre>// Situation B: * is used to represent incumbent,<br>// and a legend under the results table notes this,<br>// but we use aria-label since someone using a<br>// screen reader may not know what * represents til<br>// reaching the legend below the table and hearing it<br>&lt;span aria-label=&quot;incumbent&quot;&gt;*&lt;/span&gt;<br>...<br>{entire results table}<br>...<br>&lt;span&gt;* indicates incumbent&lt;/span&gt;</pre><h3>Making tables easier for screen readers to navigate</h3><p>The Post’s election results pages generally present information in two ways: interactive maps and tables of text. Users who are hard of sight can use <a href="https://www.afb.org/blindness-and-low-vision/using-technology/assistive-technology-products/screen-readers">a screen reader</a>, which navigates the web content and reads it aloud to them, to hear what content is in the text tables.</p><p>As developers, we can make content easier for screen readers to navigate, and <a href="https://www.w3.org/WAI/tutorials/tables/">tables are no exception</a>.</p><h4>The &lt;caption&gt; tag</h4><p>The &lt;caption&gt; tag is read aloud by screen readers when the table containing it is first reached by the user. This gives the user context for what the table contains without needing to listen to what&#39;s in each cell individually. The caption may be unnecessary for sighted users and can be hidden from the visible page via use of <a href="https://webaim.org/techniques/css/invisiblecontent/#offscreen">an sr-only className</a>.</p><pre>&lt;table&gt;<br>  &lt;caption className=&quot;sr-only&quot;&gt;<br>    Total votes for Biden, Sanders and Warren in Super Tuesday states<br>  &lt;/caption&gt;<br>  &lt;thead&gt;<br>  ...</pre><h4>The &lt;thead&gt; tag</h4><p>For a table with only column headers, the &lt;thead&gt; tag contains the headers for each column. Even though the tag is called &lt;thead&gt;, the header elements must still be &lt;th&gt; tags, not &lt;td&gt; tags, in order for the screen reader to read the contents of the table correctly.</p><p>This is because screen readers read the header of the column for every cell within that column as a reminder to the reader of what is being read aloud. For instance, if our table contains vote totals and we have:</p><pre>&lt;thead&gt;<br>  &lt;tr&gt;<br>    &lt;td&gt;State&lt;/td&gt;<br>    &lt;td&gt;Votes for Biden&lt;/td&gt;<br>    &lt;td&gt;Votes for Sanders&lt;/td&gt;<br>    &lt;td&gt;Votes for Warren&lt;/td&gt;<br>  &lt;/tr&gt;<br>&lt;/thead&gt;<br>&lt;tbody&gt;<br>  &lt;tr&gt;<br>    &lt;td&gt;Alabama&lt;/td&gt;<br>    &lt;td&gt;15,000&lt;/td&gt;<br>    &lt;td&gt;7,000&lt;/td&gt;<br>    &lt;td&gt;2,000&lt;/td&gt;<br>  &lt;/tr&gt;<br>  ... // table rows and data for a bunch of other states<br>  &lt;tr&gt;<br>    &lt;td&gt;Virginia&lt;/td&gt;<br>    &lt;td&gt;13,000&lt;/td&gt;<br>    &lt;td&gt;8,000&lt;/td&gt;<br>    &lt;td&gt;3,000&lt;/td&gt;<br>  &lt;/tr&gt;<br>&lt;tbody&gt;</pre><p>Then the screen reader will only read the headings once, at the top of the table, and the listener has to remember the order of (1) Biden, (2) Sanders and (3) Warren for the rest of their time reading the table, as they will only be read a bunch of state names and numbers sequentially.</p><p>On the contrary, if we have:</p><pre>&lt;thead&gt;<br>  &lt;tr&gt;<br>    &lt;th&gt;State&lt;/th&gt;<br>    &lt;th&gt;Votes for Biden&lt;/th&gt;<br>    &lt;th&gt;Votes for Sanders&lt;/th&gt;<br>    &lt;th&gt;Votes for Warren&lt;/th&gt;<br>  &lt;/tr&gt;<br>&lt;/thead&gt; <br>&lt;tbody&gt;<br>  &lt;tr&gt;<br>    &lt;td&gt;Alabama&lt;/td&gt;<br>    &lt;td&gt;15,000&lt;/td&gt;<br>    &lt;td&gt;7,000&lt;/td&gt;<br>    &lt;td&gt;2,000&lt;/td&gt;<br>  &lt;/tr&gt;<br>  ... // table rows and data for a bunch of other states<br>  &lt;tr&gt;<br>    &lt;td&gt;Virginia&lt;/td&gt;<br>    &lt;td&gt;13,000&lt;/td&gt;<br>    &lt;td&gt;8,000&lt;/td&gt;<br>    &lt;td&gt;3,000&lt;/td&gt;<br>  &lt;/tr&gt;<br>&lt;tbody&gt;</pre><p>Then the screen-reader user will hear “Votes for Warren — 3,000” when they get to the last cell in the table. This makes for a much more user-friendly experience, and this is why you should make sure to use &lt;th&gt; instead of &lt;td&gt; when working in &lt;thead&gt; elements.</p><h3>Using aria-hidden on maps so that screen readers skip them</h3><p>In testing, we noticed stepping through the election results pages with the <a href="https://www.apple.com/voiceover/info/guide/_1121.html">VoiceOver</a> screen reader was cumbersome due to it reading useless information from map components. For instance, when attempting to step through the text on our results page for May 2020’s <a href="https://www.washingtonpost.com/elections/election-results/texas-2021/">Texas 6th District U.S. House special election</a>, the screen reader will not go directly from the introductory text on the page to the text in the results table on the right-hand side of the page. Instead, the screen reader gets caught up on various parts of the left-hand side map.</p><p>It took 10 “forward steps” with VoiceOver just to pass through this map and get to the actual results table with useful information to the user. Here’s what was read aloud at each step:</p><ol><li>“A layer behind the map image”</li><li>“Dallas”</li><li>“Ft. Worth”</li><li>“Waxahachie”</li><li>“Corsicana”</li><li>“A locator map showing the placement of this map within the state”</li><li>“Detail”</li><li>“LEAD/WON”</li><li>“Wright”</li><li>“Ellzey”</li></ol><p>For someone who cannot see the screen, hearing all this is unhelpful and more confusing than skipping the map altogether.</p><p>Realizing this, we took action to hide map components (and thus the steps above) from the path of screen readers. The solution was simple: There’s <a href="https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques/Using_the_aria-hidden_attribute">an HTML attribute called aria-hidden</a> that hides the component with the attribute and all of its child components from screen readers only. (The component is still visible on the page for sighted users.)</p><p>When we applied the aria-hidden attribute to the outermost div of the map component, everything within it was removed from the path of the screen reader so that it could skip the maps and reach the results tables in a timely manner.</p><p>You can see this fix in action on our page for the <a href="https://www.washingtonpost.com/elections/election-results/texas/house-district-6-special-election/">Texas 6th District U.S. House special election runoff</a> in July. Since the Texas runoff page from July uses the same map as the page from May, it’s a great way to see how use of aria-hidden has screen readers skip all the steps listed above.</p><p>When we apply the aria-hidden attribute to the outermost div of the map component, everything within it is removed from the path of screen readers, and thus they will skip the steps listed above and instead begin reading the results table info immediately, as desired.</p><p><em>(In this case, the map is after the only results table in the page order, so the utility of skipping it isn’t as obvious, but you can get a better idea of how useful this is on our </em><a href="https://www.washingtonpost.com/elections/election-results/new-york/nyc-primary/"><em>New York City</em></a><em> and </em><a href="https://www.washingtonpost.com/elections/election-results/ohio/house-districts-11-15-primaries/"><em>Ohio U.S. House special election</em></a><em> primary results pages from this year, which also have the fix.)</em></p><figure><img alt="Screenshot of the map container on our Texas election results page being highlighted with the Chrome developer tools to show the aria-hidden=true property is set" src="https://cdn-images-1.medium.com/max/1024/1*0hRwBZV9nUXj5fjd7OIH_w.png" /></figure><p>We still have work to do. While this effort has made for a smoother screen reader experience on our election results pages, we have not implemented a way to convey the information the map provides for sighted users — specifically the vote counts in specific geographic areas — in a way that is accessible for screen reader users.</p><h3>Facing forward</h3><p>At The Post, we understand that you are never really “done” making content more accessible. The improvements described in this post are important, but we have much more work to do here and elsewhere. Stay tuned for future updates on the work we are doing across our site and apps.</p><p>If you notice any errors in this post, or if you have any questions for me, please let me know <a href="/service/mailto:holden.foreman@washpost.com">via email</a> and/or <a href="https://twitter.com/hsforeman">via Twitter</a>. Thanks so much for reading.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e6f6cdbab25f" width="1" height="1" alt=""><hr><p><a href="https://washpost.engineering/improving-screen-reader-and-keyboard-accessibility-on-election-results-pages-e6f6cdbab25f">Improving screen reader and keyboard accessibility on election results pages</a> was originally published in <a href="https://washpost.engineering/">Washington Post Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How we enhanced our site’s UX and boosted Core Web Vitals scores]]></title>
            <link>https://washpost.engineering/how-we-enhanced-our-sites-ux-and-boosted-core-web-vitals-scores-960fb49e7eab?source=rss-bda4adac756b------2</link>
            <guid isPermaLink="false">https://medium.com/p/960fb49e7eab</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[google-search]]></category>
            <category><![CDATA[page-ranking]]></category>
            <category><![CDATA[core-web-vitals]]></category>
            <category><![CDATA[performance]]></category>
            <dc:creator><![CDATA[Holden Foreman]]></dc:creator>
            <pubDate>Thu, 19 Aug 2021 20:53:14 GMT</pubDate>
            <atom:updated>2021-08-27T14:01:52.241Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Snapshot showing how our CWV scores where roughly the same throughout July 2021 until the end of the month, at which point the percent of URLs in the red or yellow dropped steeply while the percent of URLs in the green rose steeply" src="https://cdn-images-1.medium.com/max/490/1*w55dp9BEOcVfcdYwRebZSg.png" /></figure><p><em>By </em><a href="https://twitter.com/hsforeman"><em>Holden Foreman</em></a><em> (Software Engineer) and </em><a href="https://twitter.com/juliebaconator"><em>Julie Bacon</em></a><em> (Site Engineering Manager)</em></p><p>Ever opened an article and started reading, only to lose your spot because you were bumped down the page? This annoying occurrence is the result of layout shift, one of many performance issues that can crop up without consistent care and attention.</p><p>Improving the experience of our users is always a top priority here at The Washington Post. With Google’s focus on user-centric performance metrics via new <a href="https://developers.google.com/search/docs/advanced/experience/page-experience">page experience</a> signals called Core Web Vitals (CWV), we can better monitor and iterate on those experiences.</p><p>CWV signals are <a href="https://developers.google.com/search/blog/2021/04/more-details-page-experience">currently being rolled out globally</a>. They consist of three new performance metrics: Largest Contentful Paint (<a href="https://web.dev/lcp/">LCP</a>), Cumulative Layout Shift (<a href="https://web.dev/cls/">CLS</a>) and First Input Delay (<a href="https://web.dev/fid/">FID</a>). We set a target to reach the highest threshold across all three metrics by August 2021, as Google’s rollout of the new signals is set to be completed by the end of the month.</p><p>For publications like The Post, which need to balance rich advertising, rich content and page speed, CWV poses an interesting challenge: How do we ensure a performant experience on all pages across our domain in the short term? And, looking ahead, how can we bake good performance and attention to UX into our long-term processes and culture?</p><p>Last summer, the engineering team at The Washington Post began exploring just that. Since then, we’ve seen significant lifts across all three scores.</p><p><em>The data below is for our entire domain on mobile devices only</em>.</p><p><strong>In August 2020, aggregate CWV scores show room for improvement:</strong></p><figure><img alt="The Post’s web vitals scores as of August 2020: 56% of URLs have passing FCP scores, 84% have passing FID scores, 78% have passing LCP scores and 73% have passing CLS scores." src="https://cdn-images-1.medium.com/max/964/0*ANQkY6Puf2EVjAIS.png" /></figure><p><strong>In August 2021, aggregate CWV scores show significant lifts after performance investments:</strong></p><figure><img alt="The Post’s web vitals scores as of August 2021: 85% of URLs have passing FCP scores, 88% have passing FID scores, 84% have passing LCP scores and 81% have passing CLS scores." src="https://cdn-images-1.medium.com/max/739/1*8AlD60mC5nsosLbK3kbRxQ.png" /></figure><p>To accomplish this positive shift, we put our users at the forefront of our engineering and design practices. Here are some key takeaways.</p><h3>Understand the baseline</h3><p>We began by determining a baseline for our CWV scores across our site using several different monitors to understand the complete picture. Luckily, there are a lot of awesome tools to help.</p><p><strong>Step 1: Identify Patterns with GSC</strong></p><p>The <a href="https://search.google.com/">Google Search Console</a> dashboard for CWV provided a good first pulse. This allows us to drill down into our less-performant urls and begin to identify patterns in templates or features.</p><figure><img alt="Snapshot showing how our CWV scores where roughly the same from the start of June to the end of July, at which point the percent of URLs in the red or yellow dropped steeply while the percent of URLs in the green rose steeply" src="https://cdn-images-1.medium.com/max/932/0*8L4cYQRjJN-zIjLX.png" /></figure><p><strong>Step 2: Get more granular segments with real-user data</strong></p><p>Next, we collaborated with our Analytics team to set up dashboards that would show us an approximate distribution of scores for real users. This gives us more granular insight to triage issues on lower connection speeds, varying devices, etc.</p><p><strong>Step 3: Automate and monitor release impact</strong></p><p>We highly value continuous deployments and set up synthetic monitoring using <a href="https://calibreapp.com/">Calibre App</a> against our common page templates, with automated alerts going to Slack when we fell below our threshold. This allows us to gauge impact of each release so we can <a href="https://paper.dropbox.com/?q=%23alwaysbeshipping">#alwaysbeshipping</a>.</p><figure><img alt="Snapshot of Calibre dashboard showing that CLS budget is exceeded" src="https://cdn-images-1.medium.com/max/1024/0*YTGO_0qtyFQcVqEL.png" /></figure><h3>Make it a priority and assemble the team</h3><p>Communication and a shared commitment to deliver high-quality user experiences are the cornerstones of our success. From engineering to design to advertising and our newsroom, web vitals became a common language and a common goal through a series of communication and alignment methods:</p><ul><li>Recurring (and actionable) checkpoints across departments and teams to check in on progress, flag concerns and share tips</li><li>Slack channel for sharing web vitals wins, resources and questions</li><li>Company-wide presentations on web vitals in town halls</li></ul><p>Getting company buy-in for performance work is possible by illustrating to stakeholders <em>how </em>CWV will benefit customers, increase the bottom line and speed up engineering productivity to ship more features, faster! It’s a win-win-win.</p><h3>Fix the things!</h3><p>We took several strategic steps to improve CWV scores at The Post.</p><p><strong>Optimize Rendering of Main Images for LCP</strong></p><p>We reworked the way we rendered the main image in our standard article layout, and as a result, it was the biggest improvement we saw in LCP.</p><p>How it worked:</p><ul><li>Preloaded the img element’s srcset</li><li>Used an <a href="https://www.freecodecamp.org/news/using-svg-as-placeholders-more-image-loading-techniques-bed1b810ab2c/">LQIP</a> (low-quality image placeholder) in the form of a blurred svg as the background-image of the image element until the high-res request loaded</li><li>Assigned the attribute decoding=”async” to the img element</li></ul><p>These changes resulted in an improvement to our LCP score that was immediately noticeable.</p><p><strong>Reserved Space for Components to Minimize CLS</strong></p><p>Anywhere we used <a href="https://en.wikipedia.org/wiki/Lazy_loading">lazy loading</a>, we used a placeholder element with a min-height — and potentially min-width — to reserve the space so the element would not jump in and push content elsewhere on the page. We invested in skeleton states to improve the user experience for our readers. This is one of those techniques that became a pattern for us in our quest to improve our CLS scores.</p><p>One example of this execution is with our advertisement placeholder. Previously, ads would jump into the slot and push content down the page, which could be frustrating for users, particularly on mobile devices or on smaller displays.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_sFOoUPueZNvNLOPVeia7A.gif" /></figure><p>Improving our CLS score required close collaboration with the advertising team. To evaluate impact, we developed and ran extensive A/B tests that served different creative with predictable sizes into the slot for a split segment of users. By analyzing the CWV and broader impact, we were able to make data-driven business decisions. In most cases — and to our surprise — serving predictable creative sizes <em>increased</em> revenue and we were able to commit several units to a set size and eliminate CLS. By opting to serve larger ad sizes (300x600 units only instead of a combination of multiple sizes, which caused a layout jump), we saw higher CPMs. We also eliminated several ad format types that were jumpy. These were traditionally poor performers with our users. We replaced those formats with units that loaded fully in view, resulting in higher ad viewability metrics and, ultimately, higher engagement and improved ad performance.</p><p><strong>As the page loads, min-height is reserved with a skeleton state for inline ads:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-qSwQrdaTVP3kt7I.png" /></figure><p><strong>Because of this, the ad can be fully loaded in without impacting CLS:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*M9euIfjWOrzw5sOH.png" /></figure><p><strong>Code-splitting for Faster FID</strong></p><p>While we have made continuous improvements to our FID, we found opportunities to further enhance the score by <a href="https://webpack.js.org/guides/code-splitting/">utilizing code-splitting</a>. We were able to ensure that, on any given page, unnecessary code was excluded from our JavaScript or CSS bundles, making our files lighter and our pages faster.</p><p>FID is <a href="https://web.dev/fid/">described</a> as a phenomenon that <em>“happens because the browser’s main thread is busy doing something else, so it can’t (yet) respond to the user. One common reason this might happen is the browser is busy parsing and executing a large JavaScript file loaded by your app.”</em></p><p>By leveraging Next.js <a href="https://nextjs.org/docs/advanced-features/dynamic-import">dynamic imports</a>, we can conditionally load the JavaScript for components that are needed by each page. We took a similar approach to <a href="https://webpack.js.org/guides/code-splitting/">code-splitting CSS</a> with updates to our webpack build:</p><pre>import dynamic from &quot;next/dynamic&quot;;<br>const AudioPlayer = dynamic(() =&gt;<br>   import(&quot;./components/article/audio-player&quot;)<br>);</pre><pre>...</pre><pre>return (<br>   &lt;&gt;<br>      {hasAudioPlayer &amp;&amp; &lt;AudioPlayer /&gt;<br>   &lt;/&gt;<br>);</pre><h3>Maintain, maintain, maintain</h3><p>As with many things, improving CWV scores is not something you do once and then move on. We’re working at The Post to integrate CWV into our ongoing product, design and development processes, in addition to regular review of changes in our scores. It’s an ongoing effort.</p><p>We were able to introduce CWV as a new set of standards in cross-team collaboration — and dedicate resources to maintaining these standards. This will serve as a point of reference for other cross-team initiatives in the future. Now, we’re looking at structuring other projects the same way, for example, on web accessibility.</p><p>Want to share CWV tips, interested in <a href="https://washpost.wd5.myworkdayjobs.com/washingtonpostcareers/jobs">working with us</a>, or just feel like saying hi?</p><p>Contact us at julie.bacon@washpost.com and holden.foreman@washpost.com.</p><p><em>This project wouldn’t be made possible without the hard work of this outstanding team: Holden Foreman, Robyn Bortz, Anna Scalamogna, Taylor Scott, Christopher Kankel, Erika Johnson, Hannah Mahon, Amanda Bozzi, Arturo Silva, Dan Weaver, Joey Weed, Sarah House, Amanda Hicks, Ted Cook, Thomas Chan, Tommy Lisiak, Eric Lin, Hope Tambala, Ryan Luu, Leo Dominguez, Nathan Walker, Gregory Auld, Ryan Coughlin, Matt Callahan, Dave Merrell, Jeff Turner, Julie Bacon and Kat Styons.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/64/0*ReqL63d7lLi-W8jP" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=960fb49e7eab" width="1" height="1" alt=""><hr><p><a href="https://washpost.engineering/how-we-enhanced-our-sites-ux-and-boosted-core-web-vitals-scores-960fb49e7eab">How we enhanced our site’s UX and boosted Core Web Vitals scores</a> was originally published in <a href="https://washpost.engineering/">Washington Post Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We can’t automate alt text. Here are some mistakes, lessons and what we can do for accessibility.]]></title>
            <link>https://washpost.engineering/we-cant-automate-alt-text-here-are-some-mistakes-lessons-and-what-we-can-do-for-accessibility-4e8631c2b3?source=rss-bda4adac756b------2</link>
            <guid isPermaLink="false">https://medium.com/p/4e8631c2b3</guid>
            <category><![CDATA[alt-text]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[medium]]></category>
            <category><![CDATA[publication]]></category>
            <category><![CDATA[screen-reader]]></category>
            <dc:creator><![CDATA[Holden Foreman]]></dc:creator>
            <pubDate>Wed, 21 Jul 2021 15:21:55 GMT</pubDate>
            <atom:updated>2021-07-22T19:59:32.360Z</atom:updated>
            <content:encoded><![CDATA[<h3>When fallbacks don’t work: Lessons on alt text for improving accessibility</h3><p>Imagine listening to an audio book and hearing the same paragraph repeated twice in a row. For people who use <a href="https://www.afb.org/blindness-and-low-vision/using-technology/assistive-technology-products/screen-readers">screen readers</a> to read online content, this could happen anywhere, from retail and government sites to media sites like The Post’s. In fact, a screen reader user contacted us in fall 2020 to note that captions on our article pages were being repeated to them against their will.</p><p>In the case of many media sites, the root of this issue is inappropriate alt text.</p><p>Alt text is essential to <a href="https://webaim.org/intro/">web accessibility</a>, and reusing captions as alt text is (a) annoying — like hearing paragraphs repeated in an audio book — and (b) not enough to make an image accessible in the first place. Why? Because alt text and captions serve different purposes and should thus be written separately.</p><p>Adding alt text isn’t time-consuming. According to <a href="https://webaim.org/techniques/alttext/">WebAIM’s excellent explainer</a> (which I recommend even to those already familiar with alt text), “Typically no more than a few words are necessary, though rarely a short sentence or two may be appropriate.”</p><p>Publications already caption their images manually. It’s just a matter of adding alt text to that workflow.</p><p>As we push for this, it’s important to highlight failures that occur when we try using fallbacks to get around this small manual effort.</p><p>Let’s consider this case in which the alt text for an image is the same as the image caption. This will result in screen readers reading aloud the same text to a user multiple times in a row, unless either the image or caption is hidden to screen readers via the aria-hidden attribute.</p><p>The alt text of the image in the Post article shown below was previously the same as the caption text. (You can see this on <a href="https://web.archive.org/web/20200904060015if_/https://www.washingtonpost.com/technology/2020/06/28/facebook-zuckerberg-trump-hate/">Internet Archive</a>, since the issue has since been fixed.) When a user uses <a href="https://www.apple.com/accessibility/vision/">VoiceOver</a> to navigate the page content, the text is repeated twice in a row.</p><figure><img alt="A Washington Post article with the Chrome developer tools open to show the featured image alt text and caption text are the same" src="https://cdn-images-1.medium.com/max/1024/1*SHKX6oj4YStRr98OaT9eBQ.png" /></figure><p>Watch the video of me using VoiceOver on the page (since this has since been fixed, I manually set the alt text equal to the caption for demo purposes): <a href="https://www.dropbox.com/s/p7uw0jycsopkufx/duplicate-alt-text-demo-for-blog.mov?dl=0">https://www.dropbox.com/s/p7uw0jycsopkufx/duplicate-alt-text-demo-for-blog.mov?dl=0</a></p><p>Some publications get around this specific issue by using the aria-hidden attribute, as mentioned previously. Elements with aria-hidden=&quot;true&quot; (and their child elements) are skipped by screen readers. You can just add the aria-hidden attribute with no assigned value or explicitly assign aria-hidden=&quot;true&quot;. Either works.</p><p>See <a href="https://www.nytimes.com/live/2021/07/08/us/scripps-spelling-bee">the New York Times article</a> shown below for an example of this: The alt attribute of the image contains the caption text (which, again, is inadequate alt text in the first place). However, since the span containing the caption text has aria-hidden=&quot;true&quot;, that span is not read aloud by screen readers and the redundancy is avoided.</p><figure><img alt="An NYT article with the Chrome developer tools open to show the featured image alt text is repeated in the below caption, but with aria-hidden=true applied to the caption" src="https://cdn-images-1.medium.com/max/1024/0*1SUHt59u8EZ_4OKx" /></figure><p>In 2020, a reader contacted The Post to note their screen reader was repeating the caption text twice in a row. So we applied aria-hidden=&quot;true&quot; to the figcaption below article images to prevent this.</p><p>Then, something changed elsewhere in our code: Images no longer used the caption as alt text, and our fallback alt text was used. This fallback is &quot;Image without a caption&quot;.</p><p>As indicated in the <a href="https://webaim.org/techniques/alttext/">WebAIM explainer</a>, this is really bad alt text!</p><p>Screen readers already tell users when the text in question is for an image, so if alt=&quot;Image without a caption&quot; then the user will hear something like “Image without a caption, image” when the image is reached. This does not provide useful information.</p><p>If the alt attribute is provided but not assigned a value, e.g. &lt;img src=&quot;url&quot; alt /&gt;, or if it&#39;s set to &quot;&quot;, then screen readers will skip the image. Thus, a default of alt=“” would reduce repetition and improve user experience.</p><p>Note that the alt attribute (even if it’s set to &quot;&quot;) should always be provided for an image. If the alt attribute is missing entirely, e.g. &lt;img src=&quot;url&quot; /&gt;, then the behavior is <a href="https://www.powermapper.com/tests/screen-readers/labelling/img-no-alt/">inconsistent</a> and often more problematic than just skipping the image.</p><p>Furthermore, a fallback of alt=&quot;Image without a caption&quot; is inaccurate. It is trying to say that custom alt text was not provided, but the image does have a caption.</p><figure><img alt="A Washington Post article with VoiceOver in use to show how it reads the featured image alt text" src="https://cdn-images-1.medium.com/max/1024/0*5WpKlMBd5Uaz2qYo" /></figure><p>There is a caption below the image in <a href="https://www.washingtonpost.com/world/2021/07/08/haiti-health-crisis/#main-content">the article</a> shown above, but the alt text was still &quot;Image without a caption&quot;.</p><p>Remember how we used aria-hidden=&quot;true&quot; at The Post to keep captions from being read twice in a row by screen readers? Since the default alt text was no longer the caption, and since the caption still had aria-hidden=&quot;true&quot;, screen readers weren&#39;t reading the caption at all.</p><p>This is, on one hand, a cautionary tale in the behavior of default values. We fixed this particular issue by changing our alt fallback to &quot;&quot; and removing aria-hidden=&quot;true&quot; from the figcaption.</p><p>On the other hand, this doesn’t address the issue of appropriate alt text missing in the first place.</p><p>An idea that has surfaced in recent years is that of <a href="https://about.fb.com/news/2021/01/using-ai-to-improve-photo-descriptions-for-blind-and-visually-impaired-people/">automating alt text using AI</a>. This should be avoided, as we do not know if it will create appropriate alt text, and AI tools have historically misidentified someone or incorrectly — or unnecessarily — gender them.</p><p>Automation and substitutes — whether via AI, reuse of captions or pre-programmed fallback values — will not fix the issue. For an issue as sensitive as describing news images accurately, taking the time to write alt text manually for each image is the only real solution.</p><p>This requires a great understanding of the purpose of the alt attribute, and why guides like <a href="https://webaim.org/techniques/alttext/">WebAIM’s explainer</a> are important to read.</p><p>&quot;An older man in a white T-shirt&quot; is an example of manually written alt text I came across on one publication’s website. The image was Bill Cosby wearing his former high school’s T-shirt after his sexual assault conviction was overturned.</p><p>His wearing of that shirt led to outcry among others from the school. A screen reader user, meanwhile, will hear alt text that doesn’t even note Cosby is the man in the image.</p><p>As engineers in the media industry, alt text is not something we should attempt to handle for journalists. Alt text is a first-class piece of content and for accessibility reasons must be written manually. As engineers, we can highlight the accessibility issues posed by misuse and lack of alt text, and develop tools for making alt text easier and better.</p><p>We need to be collecting input from actual screen reader users sensitively and respectfully. But it should not always fall solely upon their shoulders to push for this change.</p><p>If you notice any errors in this post, or if you have any questions for me, please let me know <a href="/service/mailto:holden.foreman@washpost.com">via email</a> and/or <a href="https://twitter.com/hsforeman">via Twitter</a>. Thanks so much for reading.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4e8631c2b3" width="1" height="1" alt=""><hr><p><a href="https://washpost.engineering/we-cant-automate-alt-text-here-are-some-mistakes-lessons-and-what-we-can-do-for-accessibility-4e8631c2b3">We can’t automate alt text. Here are some mistakes, lessons and what we can do for accessibility.</a> was originally published in <a href="https://washpost.engineering/">Washington Post Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>