# The A11Y Project

A community-driven effort to make digital accessibility easier.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Automated tools can ensure full accessibility compliance

DevFeed: [Automated tools can ensure full accessibility compliance](<https://devfeed.tech/articles/automated-tools-can-ensure-full-accessibility-compliance-9375.md>)

Original publisher: [Read original article](<https://a11yproject.com/posts/automated-tools-can-ensure-full-accessibility-compliance/>)

Author: Melwyn Joseph

Published: 2025-03-10T00:00:00Z

Content type: article

Language: en

Sources: [The A11Y Project](<https://devfeed.tech/sources/the-a11y-project.md>)

Topics: [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [Web Content Accessibility Guidelines](<https://devfeed.tech/topics/web-content-accessibility-guidelines.md>), [axe DevTools](<https://devfeed.tech/topics/axe-devtools.md>), [audit](<https://devfeed.tech/topics/audit.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [alt text](<https://devfeed.tech/topics/alt-text.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [accessibility-compliance](<https://devfeed.tech/tags/accessibility-compliance.md>), [accessibility-tools](<https://devfeed.tech/tags/accessibility-tools.md>), [alt-text](<https://devfeed.tech/tags/alt-text.md>), [approach](<https://devfeed.tech/tags/approach.md>), [audit](<https://devfeed.tech/tags/audit.md>), [audits](<https://devfeed.tech/tags/audits.md>), [automated](<https://devfeed.tech/tags/automated.md>), [automation](<https://devfeed.tech/tags/automation.md>), [axe](<https://devfeed.tech/tags/axe.md>), [axe-devtools](<https://devfeed.tech/tags/axe-devtools.md>), [best](<https://devfeed.tech/tags/best.md>), [call](<https://devfeed.tech/tags/call.md>), [can](<https://devfeed.tech/tags/can.md>), [color](<https://devfeed.tech/tags/color.md>), [combines](<https://devfeed.tech/tags/combines.md>), [complex](<https://devfeed.tech/tags/complex.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [full](<https://devfeed.tech/tags/full.md>), [tools](<https://devfeed.tech/tags/tools.md>)

### AI overview

Automated accessibility tools can quickly scan many pages and flag straightforward issues such as missing alt text, poor color contrast, and incorrect heading structures; WebYes and axe DevTools are cited as examples. They cannot reliably judge whether image descriptions are meaningful, keyboard navigation is usable, or form instructions and errors are clear. The excerpt reports that a GDS audit found tools detect 30-40% of known issues, while Karl Groves estimates only 25-33% of WCAG guidelines can be reliably tested with automation. It recommends pairing automated scans with manual reviews, usability tests, user feedback, and ongoing team training. Automation supports accessibility work but cannot guarantee full compliance on its own.

### Source excerpt

Can automated tools guarantee full compliance with accessibility standards like WCAG? The short answer is no. While automated accessibility tools are often marketed as comprehensive solutions, they are only part of the equation. What automated tools can do Automated tools are good at detecting straightforward accessibility issues, such as missing alt text, poor color contrast, and incorrect heading structures. Tools like WebYes and axe DevTools are examples of automated tools that efficiently flag these issues. The speed and efficiency of automated accessibility tools make them ideal for initial audits. They can scan hundreds of web pages in minutes, pinpointing the most straightforward problems--what we often call "low-hanging fruit." The results of the initial audit provide a strong foundation, allowing teams to prioritize critical fixes and plan for deeper manual testing to address more complex accessibility issues. What automated tools miss While automated tools are excellent for identifying straightforward issues, they cannot evaluate issues that require human judgment, such as: Whether alternative text for images is meaningful. The logical flow and usability of keyboard navigation. The clarity of instructions or error messages for forms. When human judgment is missing, important accessibility issues can go unnoticed, making the experience difficult and frustrating for users with disabilities. This can prevent them from fully accessing or using the website as intended. Studies highlight this gap. A Government Digital Service (GDS audit revealed that even the best automated tools detect only 30-40% of known accessibility issues. Accessibility expert Karl Groves notes that only 25 to 33% of WCAG guidelines can be reliably tested with automation. Striking the right balance The most effective approach combines automation with manual efforts. Automated scans identify technical issues, while manual reviews and usability tests uncover the subtle barriers tools miss. By

## What is Semantic HTML?

DevFeed: [What is Semantic HTML?](<https://devfeed.tech/articles/what-is-semantic-html-9425.md>)

Original publisher: [Read original article](<https://a11yproject.com/posts/what-is-semantic-html/>)

Author: David A Kennedy

Published: 2023-04-04T00:00:00Z

Content type: article

Language: en

Sources: [The A11Y Project](<https://devfeed.tech/sources/the-a11y-project.md>)

Topics: [HTML](<https://devfeed.tech/topics/html.md>), [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [aria](<https://devfeed.tech/topics/aria.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [assistive-technology](<https://devfeed.tech/tags/assistive-technology.md>), [browser](<https://devfeed.tech/tags/browser.md>), [code](<https://devfeed.tech/tags/code.md>), [computer-science](<https://devfeed.tech/tags/computer-science.md>), [content](<https://devfeed.tech/tags/content.md>), [element](<https://devfeed.tech/tags/element.md>), [elements](<https://devfeed.tech/tags/elements.md>), [example](<https://devfeed.tech/tags/example.md>), [form](<https://devfeed.tech/tags/form.md>), [functionality](<https://devfeed.tech/tags/functionality.md>), [giving](<https://devfeed.tech/tags/giving.md>), [header](<https://devfeed.tech/tags/header.md>), [html](<https://devfeed.tech/tags/html.md>), [keyboard](<https://devfeed.tech/tags/keyboard.md>), [language](<https://devfeed.tech/tags/language.md>), [markup](<https://devfeed.tech/tags/markup.md>), [meaning](<https://devfeed.tech/tags/meaning.md>), [semantic](<https://devfeed.tech/tags/semantic.md>), [what-is](<https://devfeed.tech/tags/what-is.md>)

### AI overview

Semantic HTML means choosing elements that match the content and purpose of a page, so its structure and meaning are conveyed to browsers and assistive technologies. For example, `<header>` supplies an implicit banner landmark that screen reader users can navigate; a `<div>` does not provide that role unless extra code adds it. The excerpt lists other benefits of appropriate elements: built-in keyboard behavior in some cases, state communication for radio buttons and checkboxes, default browser styling, more efficient search indexing, and better parsing by RSS readers and Reader mode. Replacing semantic elements with generic `<div>` or `<span>` elements can mean recreating functionality and may make the result unusable for people who rely on semantic HTML.

### Source excerpt

A common refrain comes up often in the accessibility field. "Use semantic HTML," people say. But what does that mean and why does it matter? More importantly, what do you get with semantic HTML? What is Semantic HTML? The word "semantic" has a few meanings. In computer science, semantics provides the rules for interpreting expressions of code. In this case, semantics lays out the rules for how HTML (the code) gets interpreted. Those rules govern structure and meaning. Structure HTML stands for Hypertext Markup Language. Invented by Tim Berners-Lee as a way to link together important research documents, HTML has evolved to do much more than that. Early versions had heading elements (h1, h2, etc.), but not the structural elements like <header>, <main> and <footer>. Those came later. Each of these elements gives structure to the document, the web page. Creating semantic code means picking the right element for the job, giving your page structure. Meaning The elements also have a meaning underneath. Every element has an implicit role. For example, the <header> element has the implicit role of "banner." That means that a screen reader will read that role as a landmark. People who use screen readers can navigate by those landmarks, granting an easier way to skim the content of a page. If a developer used a <div> instead of a <header>, the implicit role would be absent, unless provided with extra code. That means the HTML won't be as useful to the machines that interpret it. What you get with Semantic HTML When you select the right element for the content you have, you get some things for free. Free as in the web platform gives it to you without any other effort. We talked about one already: Structure and meaning gets conveyed to browsers and assistive technologies. Some elements come with built in keyboard functionality, for example, the <form> element. Other elements may communicate state to the browser and assistive technology. Radio buttons and checkboxes do this. The

## The power of ChatGPT as a cognitive accessibility assistive technology for Traumatic Brain Injury survivors

DevFeed: [The power of ChatGPT as a cognitive accessibility assistive technology for Traumatic Brain Injury survivors](<https://devfeed.tech/articles/the-power-of-chatgpt-as-a-cognitive-accessibility-assistive-technology-for-traumatic-brain-injury-survivors-9416.md>)

Original publisher: [Read original article](<https://a11yproject.com/posts/the-power-of-chatgpt-as-a-cognitive-accessibility-assistive-technology-for-traumatic-brain-injury-survivors/>)

Author: Jamie Vanderwall

Published: 2023-03-14T00:00:00Z

Content type: article

Language: en

Sources: [The A11Y Project](<https://devfeed.tech/sources/the-a11y-project.md>)

Topics: [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [ChatGPT](<https://devfeed.tech/topics/chatgpt.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Conversational AI](<https://devfeed.tech/topics/conversational-ai.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [assistive-technology](<https://devfeed.tech/tags/assistive-technology.md>), [attention](<https://devfeed.tech/tags/attention.md>), [chatgpt](<https://devfeed.tech/tags/chatgpt.md>), [communication](<https://devfeed.tech/tags/communication.md>), [community](<https://devfeed.tech/tags/community.md>), [deep-learning](<https://devfeed.tech/tags/deep-learning.md>), [essay](<https://devfeed.tech/tags/essay.md>), [information](<https://devfeed.tech/tags/information.md>), [information-retrieval](<https://devfeed.tech/tags/information-retrieval.md>), [language-model](<https://devfeed.tech/tags/language-model.md>), [large-language-model](<https://devfeed.tech/tags/large-language-model.md>), [learning](<https://devfeed.tech/tags/learning.md>), [memory](<https://devfeed.tech/tags/memory.md>), [natural-language](<https://devfeed.tech/tags/natural-language.md>), [openai](<https://devfeed.tech/tags/openai.md>), [social](<https://devfeed.tech/tags/social.md>), [technology](<https://devfeed.tech/tags/technology.md>), [training](<https://devfeed.tech/tags/training.md>)

### AI overview

The essay presents ChatGPT as a possible cognitive accessibility aid for traumatic brain injury survivors, who may experience memory, attention and executive-function difficulties. It describes four proposed uses: answering questions to support information retrieval; reminders and prompts for appointments, tasks and medication schedules; practicing conversations with feedback; and exercises targeting memory or attention. It argues these uses could make daily tasks and communication easier, support participation and reduce reliance on others. These are proposals in the essay; the supplied text does not establish their effectiveness.

### Source excerpt

This article was written by ChatGPT with the below prompt written by Jamie Vanderwall. "Write about how ChatGPT can be used as a cognitive accessibility assistive technology specifically for traumatic brain injury survivors and how this impacts the disability community." Introduction This essay explores the use of ChatGPT as a cognitive accessibility assistive technology for traumatic brain injury (TBI) survivors, discussing the impact it has on the disability community. The essay outlines the cognitive impairments experienced by TBI survivors, and how ChatGPT can provide support in the form of information retrieval, memory aids, communication aids, and cognitive training. Traumatic brain injury (TBI) is a life-changing injury that can affect people of all ages, genders, and backgrounds. TBI can cause a range of physical, cognitive, and emotional impairments, making it difficult for people with TBI to perform daily activities, engage in social interactions, and access information. Cognitive accessibility assistive technology, such as ChatGPT, can help TBI survivors overcome some of the cognitive challenges they face and improve their quality of life. This essay will explore how ChatGPT can be used as a cognitive accessibility assistive technology specifically for TBI survivors and how it impacts the disability community. What is ChatGPT? ChatGPT is a large language model developed by OpenAI that can generate human-like responses to natural language queries. It is a type of artificial intelligence that uses deep learning algorithms to analyze and understand natural language input and generate a relevant and contextually appropriate response. ChatGPT can be used in various contexts, such as customer service, chatbots, and conversational agents. How can ChatGPT be used as a cognitive accessibility assistive technology for TBI survivors? TBI can cause a range of cognitive impairments, including memory loss, attention deficits, and difficulty with executive functioning.

## Getting started with TalkBack on Android

DevFeed: [Getting started with TalkBack on Android](<https://devfeed.tech/articles/getting-started-with-talkback-on-android-9386.md>)

Original publisher: [Read original article](<https://a11yproject.com/posts/getting-started-talkback/>)

Author: Cooper Hollmaier

Published: 2023-03-06T00:00:00Z

Content type: tutorial

Language: en

Sources: [The A11Y Project](<https://devfeed.tech/sources/the-a11y-project.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [Web](<https://devfeed.tech/topics/web.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [android](<https://devfeed.tech/tags/android.md>), [applications](<https://devfeed.tech/tags/applications.md>), [article](<https://devfeed.tech/tags/article.md>), [devices](<https://devfeed.tech/tags/devices.md>), [getting-started](<https://devfeed.tech/tags/getting-started.md>), [google](<https://devfeed.tech/tags/google.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [touchscreen](<https://devfeed.tech/tags/touchscreen.md>), [voice](<https://devfeed.tech/tags/voice.md>), [voice-commands](<https://devfeed.tech/tags/voice-commands.md>), [web](<https://devfeed.tech/tags/web.md>)

### AI overview

This introductory tutorial explains TalkBack 13.1, an Android screen reader that helps people with visual disabilities use mobile applications and the web through audible and haptic feedback. It covers how to enable TalkBack and basic touch, swipe, and voice-command navigation, including selecting and activating items with taps and double taps.

### Source excerpt

Introduction to TalkBack TalkBack is assistive technology that helps users with visual disabilities access native mobile applications and the web by providing audible and haptic responses to touchscreen gestures. It is the default screen reader software included on Google touchscreen devices running the Android operating system. As of 2017, TalkBack is part of a family of software products in the Android Accessibility Suite including: Accessibility Menu Select to Speak Switch Access The Android Accessibility Suite comes pre-installed on devices running Android 9 or greater. This article is an introduction to TalkBack version 13.1. We will walk you through the basics of enabling the software and navigating websites and applications with it. Getting Started There are three ways to activate Talkback: From the settings menu: Accessibility > TalkBack > Toggle On On the physical device: Press and hold both volume keys for three seconds Via the Google Assistant: "Hey, Google. Turn on TalkBack" Once TalkBack is on, it will begin speaking instructions to you. While there are more robust features to explore, the basic commands you should know are: Tapping the screen selects an item, and Double tapping the screen activates your selection. TalkBack also makes use of single finger, two finger, and three finger gestures to perform additional actions. Navigation Modes There are at least three recognized ways to navigate with TalkBack: touch, swipe, and voice commands. Navigating by touch To navigate by touch, touch anywhere on the screen, selecting any element. It will be highlighted by a green border box similar to what you would find when using a keyboard to navigate a web page. With pressure still applied, slowly drag your finger around the screen. As you move around the screen, TalkBack will jump to the next available item and announce its contents aloud. Once you've found the content you'd like to interact with, double-tap the screen. Navigating by swiping Navigating by swipi

## Are you making these five mistakes when writing alt text?

DevFeed: [Are you making these five mistakes when writing alt text?](<https://devfeed.tech/articles/are-you-making-these-five-mistakes-when-writing-alt-text-9370.md>)

Original publisher: [Read original article](<https://a11yproject.com/posts/are-you-making-these-five-mistakes-when-writing-alt-text/>)

Author: Daniel Sage

Published: 2023-03-02T00:00:00Z

Content type: article

Language: en

Sources: [The A11Y Project](<https://devfeed.tech/sources/the-a11y-project.md>)

Topics: [alt text](<https://devfeed.tech/topics/alt-text.md>), [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [Image](<https://devfeed.tech/topics/image.md>), [search-engines](<https://devfeed.tech/topics/search-engines.md>), [User Experience](<https://devfeed.tech/topics/user-experience.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [alt-text](<https://devfeed.tech/tags/alt-text.md>), [course](<https://devfeed.tech/tags/course.md>), [image](<https://devfeed.tech/tags/image.md>), [images](<https://devfeed.tech/tags/images.md>), [seo](<https://devfeed.tech/tags/seo.md>), [ux](<https://devfeed.tech/tags/ux.md>), [vision](<https://devfeed.tech/tags/vision.md>), [writing](<https://devfeed.tech/tags/writing.md>)

### AI overview

The article recommends classifying images before writing alt text: leave decorative images with an empty `alt` attribute, describe informative images, and make active images' text state their action. For informative images, describe relevant content accurately and concisely in context rather than inserting the article's argument into the description. Avoid "image of" phrasing, keyword stuffing, and repeating captions; screen readers already announce images and read alt text aloud, so use simple sentences with correct punctuation. Complex charts may need fuller description, for which the article points to W3C guidance and notes that `longdesc` is no longer valid. The excerpt emphasizes that every image needs an `alt` attribute, though some should have empty values.

### Source excerpt

There are many benefits to writing alt text for images, especially from accessibility and legal standpoints. But most don't know how to write alt text well. I should know because, for an awful number of years, I was one. I first learned about alt text in high school while building websites. But my proper lesson began when I took the Udacity Digital Marketing Nanodegree course, which was also my first introduction to marketing. Screenshot from the SEO module of the Udacity Marketing Nanodegree course. In this module, I learned about building easy navigation site structures, title tags, breadcrumbs, and meta descriptions--all the good stuff. We also learned about writing alt text and its importance. Their overall advice? Describe what you see. I thought that I finally understood it. Sometimes it is simplicity that kills When you ask them, most experts' advice also boils down to: Describe what you see. And while it's valid advice and may seem simple, it's not. Take the Udacity example earlier: Is this suitable alt text? Source: Udacity Nanodegree Marketing Course. If you close your eyes and someone reads out the words "eating apple heart disease" to you, does that in any way help you make sense of what's in the image? What about this example? Source: Business Insider. Does it? The answer is a big no. I used to just describe what I saw Then two weeks ago, I watched Tommy Walker, an ex-Shopify senior content marketer and editor, critique an article for its alt text usage. A snippet from The Cutting Room Show, hosted by Tom Walker. Notice that the alt text does not communicate what the audit results are. Ironically, the article was arguing for accessibility. But it made the point clearer. And for the first time, it dawned on me that I've been writing alt text the wrong way. This got me curious, so I started researching: I read numerous UX and SEO blogs, I spoke with practitioners in those fields, and I chatted with some members of the low vision community. Here's what I le

## A guide to troublesome UI components

DevFeed: [A guide to troublesome UI components](<https://devfeed.tech/articles/a-guide-to-troublesome-ui-components-9362.md>)

Original publisher: [Read original article](<https://a11yproject.com/posts/a-guide-to-troublesome-ui-components/>)

Author: Martin Lexelius

Published: 2023-02-14T00:00:00Z

Content type: article

Language: en

Sources: [The A11Y Project](<https://devfeed.tech/sources/the-a11y-project.md>)

Topics: [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [UI components](<https://devfeed.tech/topics/ui-components.md>), [aria](<https://devfeed.tech/topics/aria.md>), [User Experience](<https://devfeed.tech/topics/user-experience.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [Interaction Design](<https://devfeed.tech/topics/interaction-design.md>), [HTML](<https://devfeed.tech/topics/html.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [article](<https://devfeed.tech/tags/article.md>), [html](<https://devfeed.tech/tags/html.md>), [keyboard](<https://devfeed.tech/tags/keyboard.md>), [screen-readers](<https://devfeed.tech/tags/screen-readers.md>), [ui-components](<https://devfeed.tech/tags/ui-components.md>)

### AI overview

The article's central advice is to plan for accessibility with the whole team before building; retrofitting it can cost more. Across components, ensure keyboard operation, visible and logical focus, meaningful screen-reader announcements, and valid HTML and ARIA. Prefer native controls where possible: native <select> elements work consistently across platforms but offer little styling for options. Use <dialog> cautiously and test it with assistive technology; check that state is announced, Escape closes it, the close control has a clear name, focus stays within the modal, and returns to its trigger. Autosuggest requires substantial JavaScript and often has confusing keyboard and screen-reader behavior; test it with users, or consider popular search links. Date inputs have browser support issues, so allow alternative date entry; text fields with validation may be simpler. The author advises against carousels, citing frequent critical accessibility flaws and low engagement. For dynamically loaded content, announce updates and manage focus; pagination and regular page loads can improve assistive technology support and provide shareable URLs and browser find. Evaluate third-party npm组件

### Source excerpt

A common opinion is that accessibility is expensive, and that if you think accessibility is expensive, you can deal with it later. Here's the twist: it will be expensive if you deal with it later. However, accessibility is not expensive if you discuss it as a team early in the process. It is possible to build just about anything, it comes down to time and money. But no client ever has said, "Hey, we have a lot of time and money!" Accessibility is not expensive if you proactively plan for it. That's why you need to learn how to avoid some of the common pitfalls. Before we start User interface (UI) elements are the parts we use to build apps or websites, such as links, accordions and checkboxes etc. Some UI components are more complicated than other components. And some components are really complicated. All roles that build for the web (product owners, UX designers, art directors, developers, QA engineers) must know this. The challenges The components in this article all have the following challenges in common: Keyboard interaction. Everything that can be done with a mouse, must be possible to do with a keyboard. This includes navigating, opening and closing items, activating, stopping, starting, selecting, etc. Focus appearance and management. Users navigating by keyboard must know where they are. Always show the user's current position in the interface. The focus order should be logical and intuitive. Consistent announcements. All events and interactions should correspond as understandable and relevant audio feedback in screen readers. Buttons should describe themselves as buttons, links as links, etc. Code quality. Using the correct elements and ARIA attributes, as well as valid HTML. The components Following are some UI components that have non-trivial considerations to use in an accessible way: Custom selects Native HTML <select> elements (sometimes referred to as dropdowns, not to be confused with disclosures) has the most understandable and usable experience a

## Blind people need to be considered more when making data visualizations

DevFeed: [Blind people need to be considered more when making data visualizations](<https://devfeed.tech/articles/blind-people-need-to-be-considered-more-when-making-data-visualizations-9376.md>)

Original publisher: [Read original article](<https://a11yproject.com/posts/blind-people-need-to-be-considered-more-when-making-data-visualizations/>)

Author: Johny Cassidy

Published: 2022-09-22T00:00:00Z

Content type: opinion

Language: en

Sources: [The A11Y Project](<https://devfeed.tech/sources/the-a11y-project.md>)

Topics: [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [Data visualization](<https://devfeed.tech/topics/data-visualization.md>), [inclusive design](<https://devfeed.tech/topics/inclusive-design.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [data](<https://devfeed.tech/topics/data.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [audio](<https://devfeed.tech/tags/audio.md>), [content](<https://devfeed.tech/tags/content.md>), [covid](<https://devfeed.tech/tags/covid.md>), [data](<https://devfeed.tech/tags/data.md>), [data-visualization](<https://devfeed.tech/tags/data-visualization.md>), [digital](<https://devfeed.tech/tags/digital.md>), [graphs](<https://devfeed.tech/tags/graphs.md>), [journalism](<https://devfeed.tech/tags/journalism.md>), [mask](<https://devfeed.tech/tags/mask.md>), [mit](<https://devfeed.tech/tags/mit.md>)

### AI overview

Visual data journalism can exclude blind readers when charts and other graphics lack meaningful text or audio descriptions. The author recalls COVID charts being inaccessible and argues for creative alternatives that serve people who use screen readers and others who absorb information differently, including neurodiverse people and people with cognitive disabilities. Basic alternate descriptions can help, but the author considers them limited and calls for journalists to collaborate with designers and developers to make visual journalism more equitable.

### Source excerpt

Visual data representation is being used more and more in digital newsrooms across the world. The downside, however, is how exclusionary this can be for people with visual impairments. It's clear that visual journalism will play a huge part in the digital future for media outlets. From audience analytics tools measuring the impact of content, to representing complicated data in an easy to digest format, it's easy to see the benefits of such tools and production techniques for creating impactful digital journalism. It's also clear that without a better understanding of how to make visual journalism work for everyone that huge parts of the audience are going to be left behind. In the UK alone, the Royal National Institute of Blind People estimate that around 2 million people are living with some sort of sight loss. Globally, the World Health Organization claim the number is close to 2.2 billion, with that number set to rise dramatically as people continue to age. As a blind journalist, I'm concerned that the increased use of visual data representation without careful and creative thought about accessibility is widening the inaccessibility gap. An example During the COVID pandemic I wasn't easily able to access COVID data represented on digital graphs, and I wasn't alone. A project by MIT researching the problem of data visualization accessibility cited a simple chart from the beginning of the pandemic. The cited chart demonstrated the benefits of mask wearing and social distancing for limiting the spread of the disease. The chart was amplified by many global media outlets, but was missed by millions of blind readers due to lack of meaningful text or audio description. Data journalism's access issues and greater potential In my job as a digital journalist, I'm becoming increasingly aware of the desire to publish more and more impactful visual data journalism. For a lot of people, visual representations of complicated data has the ability to translate data into a format

## What is WAI? The Web Accessibility Initiative

DevFeed: [What is WAI? The Web Accessibility Initiative](<https://devfeed.tech/articles/what-is-wai-the-web-accessibility-initiative-9426.md>)

Original publisher: [Read original article](<https://a11yproject.com/posts/what-is-wai/>)

Author: Ilknur Eren

Published: 2022-07-18T00:00:00Z

Content type: article

Language: en

Sources: [The A11Y Project](<https://devfeed.tech/sources/the-a11y-project.md>)

Topics: [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [aria](<https://devfeed.tech/topics/aria.md>), [Web Content Accessibility Guidelines](<https://devfeed.tech/topics/web-content-accessibility-guidelines.md>), [browser](<https://devfeed.tech/topics/browser.md>), [W3C](<https://devfeed.tech/topics/w3c.md>), [web-standards](<https://devfeed.tech/topics/web-standards.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [accessibility-guidelines](<https://devfeed.tech/tags/accessibility-guidelines.md>), [accessible](<https://devfeed.tech/tags/accessible.md>), [aria](<https://devfeed.tech/tags/aria.md>), [assistive-technology](<https://devfeed.tech/tags/assistive-technology.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [guidance](<https://devfeed.tech/tags/guidance.md>), [guidelines](<https://devfeed.tech/tags/guidelines.md>), [implementation](<https://devfeed.tech/tags/implementation.md>), [initiative](<https://devfeed.tech/tags/initiative.md>), [internet](<https://devfeed.tech/tags/internet.md>), [research](<https://devfeed.tech/tags/research.md>), [resources](<https://devfeed.tech/tags/resources.md>), [standards](<https://devfeed.tech/tags/standards.md>), [support](<https://devfeed.tech/tags/support.md>), [the-web](<https://devfeed.tech/tags/the-web.md>), [w3c](<https://devfeed.tech/tags/w3c.md>), [wai](<https://devfeed.tech/tags/wai.md>), [web-accessibility](<https://devfeed.tech/tags/web-accessibility.md>), [white-house](<https://devfeed.tech/tags/white-house.md>)

### AI overview

W3C's Web Accessibility Initiative (WAI), launched in 1997, brings together disability organizations, governments, and researchers to develop web accessibility standards, guidance, evaluation resources, education, and outreach. Its work addresses auditory, cognitive, neurological, physical, speech, and visual disabilities. The excerpt highlights WCAG, which sets web accessibility criteria under four principles--perceivable, operable, understandable, and robust--with A, AA, and AAA success levels; and WAI-ARIA, which guides accessible dynamic content and custom interface components, including ways to support assistive technology. WAI working groups develop guidelines, and interested people can participate.

### Source excerpt

The Web Accessibility Initiative is W3C's effort to improve accessibility of the Web for people with disabilities. What is the World Wide Consortium? In order to know about the Web Accessibility Initiative, we must first talk about the World Wide Consortium, also known as W3C. Founded in 1994 and currently led by director Tim Berners-Lee and CEO Jeffrey Jaff, W3C is an international community where organizers develop international standards for the Web. As described by W3's website, "W3C's mission is to lead the Web to its full potential." Organizers from all around the world, involved in many different fields, join W3C to develop guidelines that ensure long-term growth for the Web. The Web Accessibility Initiative is one initiative that was launched by W3C. What is the Web Accessibility Initiative? The power of the Web is in its universality. Access by everyone regardless of disability is an essential aspect. Tim Berners-Lee, W3C Director and inventor of the World Wide Web W3C launched The Web Accessibility Initiative, (WAI), in 1997, with support from the White House. The Web Accessibility Initiative's main goal is to make the internet accessible for people with disabilities. WAI brings people from disability organizations, governments, and research labs from all around the world to develop guidelines and resources to make the Web accessible to people with disabilities. This includes: auditory, cognitive, neurological, physical, speech and visual disabilities. In short, WAI develops accessibility standards and offers implementation guidance. As described by W3C Website, WAI "pursues accessibility of the web through these primary activities": Ensuring that W3C standards support accessibility Developing accessibility guidelines for web content and applications, browsers, and authoring tools Developing resources to improve web accessibility evaluation processes and tools Supporting education and outreach on web accessibility Coordinating with research and development

## Use Firefox for accessibility testing

DevFeed: [Use Firefox for accessibility testing](<https://devfeed.tech/articles/use-firefox-for-accessibility-testing-9422.md>)

Original publisher: [Read original article](<https://a11yproject.com/posts/using-firefox-for-accessibility-testing/>)

Author: Todd Libby

Published: 2022-07-17T00:00:00Z

Content type: article

Language: en

Sources: [The A11Y Project](<https://devfeed.tech/sources/the-a11y-project.md>)

Topics: [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [Firefox](<https://devfeed.tech/topics/firefox.md>), [Developer Tools](<https://devfeed.tech/topics/developer-tools.md>), [axe DevTools](<https://devfeed.tech/topics/axe-devtools.md>), [axe-core](<https://devfeed.tech/topics/axe-core.md>), [browser](<https://devfeed.tech/topics/browser.md>), [tabbing](<https://devfeed.tech/topics/tabbing.md>), [Web Content Accessibility Guidelines](<https://devfeed.tech/topics/web-content-accessibility-guidelines.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [accessibility-testing](<https://devfeed.tech/tags/accessibility-testing.md>), [accessibility-tools](<https://devfeed.tech/tags/accessibility-tools.md>), [audits](<https://devfeed.tech/tags/audits.md>), [firefox](<https://devfeed.tech/tags/firefox.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

Firefox's Accessibility tab helps inspect a page's accessibility tree and selected nodes, including their name, role, value, color contrast, and other properties. Its issue checks can flag contrast, keyboard, and form-label concerns; simulations cover several color-vision differences and contrast loss; and Show Tabbing Order displays keyboard tab stops and their sequence. The WAVE extension provides quick scans with errors, warnings, locations, and related code. The axe DevTools extension adds issue descriptions, severity estimates, best-practice toggles, and links into Firefox Inspector and Deque guidance. The excerpt also lists other extensions, and emphasizes that automated tools supplement rather than replace manual testing.

### Source excerpt

Firefox has become one of the best tools for accessibility audits. Let's go over Firefox's accessibility features that you can use today. Built-in accessibility tools In this article I'll discuss The Accessibility Tab, where we will begin and then move through to each component of the Accessibility Tab. First, the Check for issues tab, the Simulate menu, and end with the Show Tabbing Order checkbox. I'll finish with the Checks and Properties panel. The Accessibility tab Whenever you right-click on an element in a page, you can select Inspect Accessibility Properties to directly view that element in Firefox's accessibility tools. Similarly, if you're using the Inspector pane in Firefox's dev tools, you can right-click on any node and choose Show Accessibility Tools to view that node in Firefox's accessibility tools. Firefox's built-in accessibility tool is probably one of the best features in browsers' dev tools out there now. It shows you the current web page's accessibility tree, and it has panels for color-contrast checks and the current node's accessibility-tree properties. You can traverse the accessibility tree, and as you hover over each node, Firefox will show a tooltip over that node in the viewport with the name of the node and some basic properties. And the Checks and Properties panels can show you all the pertinent information for that node like its color and contrast ratio, name, role, and value. The Check for issues menu If you enable this handy feature, Firefox can check for color-contrast issues,it can do its best to try to find keyboard issues, and it can try to find form-label issues. There's also an All Issues option that will run all of those checks for the page. Each issue will show you the role and name of the element that has an issue, and the Checks and Properties panels will provide some information and values to help you resolve the issues. The Simulate menu This is a great tool for simulating visual differences. This can simulate: Protanopi

## Accessible heading structure

DevFeed: [Accessible heading structure](<https://devfeed.tech/articles/accessible-heading-structure-9392.md>)

Original publisher: [Read original article](<https://a11yproject.com/posts/how-to-accessible-heading-structure/>)

Author: Rian Rietveld

Published: 2022-01-03T00:00:00Z

Content type: article

Language: en

Sources: [The A11Y Project](<https://devfeed.tech/sources/the-a11y-project.md>)

Topics: [HTML](<https://devfeed.tech/topics/html.md>), [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [Web Content Accessibility Guidelines](<https://devfeed.tech/topics/web-content-accessibility-guidelines.md>), [aria](<https://devfeed.tech/topics/aria.md>), [Search engine optimization (SEO)](<https://devfeed.tech/topics/seo.md>), [markup](<https://devfeed.tech/topics/markup.md>)

Tags: [accessible](<https://devfeed.tech/tags/accessible.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [content](<https://devfeed.tech/tags/content.md>), [design](<https://devfeed.tech/tags/design.md>), [h2](<https://devfeed.tech/tags/h2.md>), [header](<https://devfeed.tech/tags/header.md>), [html](<https://devfeed.tech/tags/html.md>), [html-elements](<https://devfeed.tech/tags/html-elements.md>), [index](<https://devfeed.tech/tags/index.md>), [it](<https://devfeed.tech/tags/it.md>), [multiple](<https://devfeed.tech/tags/multiple.md>), [screen](<https://devfeed.tech/tags/screen.md>), [search](<https://devfeed.tech/tags/search.md>), [semantic](<https://devfeed.tech/tags/semantic.md>), [seo](<https://devfeed.tech/tags/seo.md>), [structure](<https://devfeed.tech/tags/structure.md>), [structured](<https://devfeed.tech/tags/structured.md>), [top](<https://devfeed.tech/tags/top.md>), [unique](<https://devfeed.tech/tags/unique.md>), [web](<https://devfeed.tech/tags/web.md>)

### AI overview

Use one descriptive `h1` for each page, then organize meaningful subheadings in a logical hierarchy without skipping levels. Headings should describe the content that follows, support scanning and screen-reader navigation, and not be chosen just for visual size; style them with CSS instead. The text says WCAG 2 AA requires headings and labels to describe topic or purpose and semantic relationships to be programmatically available, while explicit structured sections are required at AAA. It cautions that multiple `h1`s based on the HTML document outline are unsupported by browsers and assistive technology, and that `hgroup` lacks assistive technology support; it offers ARIA attributes and a paragraph subtitle as a proposed workaround. Reusable components should adapt heading levels to their page context, and logos generally should not be repeated as each page's `h1`. For checking structure, the text names Axe Devtools, HeadingsMap, WAVE, and WordPress's visual heading information.

### Source excerpt

Headings are the backbone of the content of a page. A visitor should be able to scan the webpage using headings to get a good impression of its content. Heading levels have meaning, especially for screen reader users and search engines. That means one unique first level heading per page, with the other headings representing the page content similar to the index of a book: easily scannable and semantic. Write well-structured headings, because what is good for your reader, is also good for your SEO. Headings in HTML Headings are HTML elements. The main heading, h1, is level 1. The other levels are h2 up to h6. The HTML Living Standard states on headings: A heading can be used where heading content is expected. Heading content defines the header of a section (whether explicitly marked up using sectioning content elements, or implied by the heading content itself). The HTML Living Standard, The h1, h2, h3, h4, h5, and h6 elements In short: use a heading when the content or the page structure requires it. Best practices summarized Use one unique h1 per page that describes what that page is about. That h1 preferably starts just above the main content. Use headings to describe the content below. Do not use an HTML heading just to make the text appear bigger or stand out. Use heading levels like the index of a book: hierarchical. Do not choose a heading by its size, but by its level in the context of the content. Do not skip a heading level from the top down. Common mistakes: Using a h2 heading for quotes because of its nice big font size. Using a h4 heading for the first paragraph of the text because it's just the size of bold text you need. Exclusively using h2 headings on a web page because all headings are the same size in the designs. Using multiple h1 headings on a web page. Omitting headings because the design clearly indicates the start of a new section. Leaving headings empty (usually a CMS glitch). What does hierarchical mean? Hierarchical means arranged in order

## How I deal with colorblindness as a digital product designer

DevFeed: [How I deal with colorblindness as a digital product designer](<https://devfeed.tech/articles/how-i-deal-with-colorblindness-as-a-digital-product-designer-9391.md>)

Original publisher: [Read original article](<https://a11yproject.com/posts/how-i-deal-with-colorblindness-as-a-digital-product-designer/>)

Author: Federico Monaco

Published: 2021-10-09T00:00:00Z

Content type: article

Language: en

Sources: [The A11Y Project](<https://devfeed.tech/sources/the-a11y-project.md>)

Topics: [color](<https://devfeed.tech/topics/color.md>), [UI/UX Design](<https://devfeed.tech/topics/ui-ux-design.md>), [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>)

Tags: [a11y](<https://devfeed.tech/tags/a11y.md>), [accessible](<https://devfeed.tech/tags/accessible.md>), [application](<https://devfeed.tech/tags/application.md>), [career](<https://devfeed.tech/tags/career.md>), [color](<https://devfeed.tech/tags/color.md>), [colors](<https://devfeed.tech/tags/colors.md>), [community](<https://devfeed.tech/tags/community.md>), [consoles](<https://devfeed.tech/tags/consoles.md>), [design](<https://devfeed.tech/tags/design.md>), [designer](<https://devfeed.tech/tags/designer.md>), [designers](<https://devfeed.tech/tags/designers.md>), [digital](<https://devfeed.tech/tags/digital.md>), [digital-products](<https://devfeed.tech/tags/digital-products.md>), [experience](<https://devfeed.tech/tags/experience.md>), [green](<https://devfeed.tech/tags/green.md>), [information](<https://devfeed.tech/tags/information.md>), [interfaces](<https://devfeed.tech/tags/interfaces.md>), [internet](<https://devfeed.tech/tags/internet.md>), [manifesto](<https://devfeed.tech/tags/manifesto.md>), [product](<https://devfeed.tech/tags/product.md>)

### AI overview

The designer says deuteranomaly made color-dependent interfaces harder to use, leading them to prefer products that do not rely on color alone. At work, adjacent Post-it colors can become indistinguishable, and vague requests such as "more blue" are insufficient; they need exact color codes and context about what shades should convey. They tell coworkers about their colorblindness, use sampled colors from screenshots, favor high contrast, and treat color as decoration rather than the sole carrier of information. They also seek feedback from other designers on how colors may appear to people without colorblindness. The excerpt mentions a ten-rule accessibility manifesto but does not include its rules.

### Source excerpt

Colorblindness is any visual anomaly where someone has an altered perception of colors. It can be total or partial. The A11Y Project already has an article that exhaustively covers the different types of color blindness while also providing tools that you can use during your design phases. In this article, I'd like to tell you what it means to be a colorblind designer and what the main problems are that someone with colorblindness can encounter if they decide to pursue a career as a designer. Colorblindness from a user's point of view During elementary school, like most colorblind people, I discovered that I have deuteranomaly, the most common form of colorblindness: I have a deficit in the sensitivity of my green color receptors. In my offline life, it's never caused me too much inconvenience, other than the strange color combinations of my clothes. Growing up and during my introduction to the internet and the first video-game consoles, I encountered more barriers than I had expected. From then on, I started using special filters if an application offered them, and I preferred to browse sites that didn't over rely on color alone to convey information. Recently, I was pondering whether most people with colorblindness had problems online or whether I was one of the few people to experience that. Through deep user research I found two interesting answers: the first is that I wasn't the only person with colorblindness to have problems online; the second is that, unfortunately, I found many more people than I had imagined. In light of this, I decided to write a manifesto of ten rules that all designers should follow to create digital products that are more accessible to the colorblind community. Working as a colorblind designer In addition to being a colorblind internet user, I am also a colorblind designer. This part of me comes into play when I have to design digital interfaces, either alone or as part of a team. When I'm part of a team, I immediately let people know

## Getting started with Orca screen reader on Gnome desktop environment on Ubuntu 20.04 LTS

DevFeed: [Getting started with Orca screen reader on Gnome desktop environment on Ubuntu 20.04 LTS](<https://devfeed.tech/articles/getting-started-with-orca-screen-reader-on-gnome-desktop-environment-on-ubuntu-20-04-lts-9388.md>)

Original publisher: [Read original article](<https://a11yproject.com/posts/getting-started-with-orca/>)

Author: Joseph Mawa

Published: 2021-09-03T00:00:00Z

Content type: tutorial

Language: en

Sources: [The A11Y Project](<https://devfeed.tech/sources/the-a11y-project.md>)

Topics: [Ubuntu](<https://devfeed.tech/topics/ubuntu.md>), [Linux](<https://devfeed.tech/topics/linux.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [Terminal](<https://devfeed.tech/topics/terminal.md>), [GUI](<https://devfeed.tech/topics/gui.md>), [dialog](<https://devfeed.tech/topics/dialog.md>)

Tags: [article](<https://devfeed.tech/tags/article.md>), [desktop](<https://devfeed.tech/tags/desktop.md>), [dialog](<https://devfeed.tech/tags/dialog.md>), [distribution](<https://devfeed.tech/tags/distribution.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [feature](<https://devfeed.tech/tags/feature.md>), [free](<https://devfeed.tech/tags/free.md>), [getting-started](<https://devfeed.tech/tags/getting-started.md>), [laptop](<https://devfeed.tech/tags/laptop.md>), [launch](<https://devfeed.tech/tags/launch.md>), [learn](<https://devfeed.tech/tags/learn.md>), [learning](<https://devfeed.tech/tags/learning.md>), [linux](<https://devfeed.tech/tags/linux.md>), [lts](<https://devfeed.tech/tags/lts.md>), [open](<https://devfeed.tech/tags/open.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [terminal](<https://devfeed.tech/tags/terminal.md>), [third-party](<https://devfeed.tech/tags/third-party.md>), [ubuntu](<https://devfeed.tech/tags/ubuntu.md>)

### AI overview

This tutorial introduces the Orca screen reader on the GNOME desktop environment in Ubuntu 20.04 LTS. It explains several ways to launch Orca, discusses accessibility of applications, describes its desktop and laptop keyboard layouts and modifier keys, and introduces Learn Mode for discovering commands and documentation.

### Source excerpt

Introduction to Orca Orca is a free, open-source screen reader developed under the GNOME project. Several Linux distributions have it installed by default. This article will introduce you to the basics of Orca on Gnome desktop environment on Ubuntu version 20.04 LTS. There might be some slight variations if you are using a different desktop environment or using GNOME on a different Linux distribution. You need to consult the manual for your Linux distribution or desktop environment. Launching Orca There are three ways you can launch Orca on Ubuntu 20.04 LTS. Below are the descriptions of these three methods. Use the keyboard shortcut Super + Alt + S. Type orca on a terminal window and then press the Return key. Alternatively, you can type orca in the Run dialog and press the Return key. You can use the key combination Alt + F2 to open the Run dialog and the ESC key to close it. If you launch Orca using the Run dialog, you can close it by typing the command pkill orca or killall orca on the terminal or in the the Run dialog and then pressing the Return key. Open the Settings dialog and then select Universal access. You can then toggle the screen reader on or off. After launching Orca, it will immediately announce the title of the topmost open application window if it is accessible to Orca. Though most applications that come pre-installed with the Gnome desktop environment are accessible, some third-party applications installed by you may not be accessible to Orca. The Orca Modifier keys The modifier key used by Orca depends on the keyboard layout. Orca has two keyboard layouts, namely: Desktop keyboard layout Laptop keyboard layout The Desktop keyboard layout is the default keyboard layout. Its Modifier key is the key combination Insert + KP_Insert. KP_Insert is the same as KP_0. If it is your first time using Orca, most likely you are in the Desktop keyboard layout. The modifier key for the Laptop layout is CapsLock . You can change the keyboard layout from the pref

## Starting a design with accessibility

DevFeed: [Starting a design with accessibility](<https://devfeed.tech/articles/starting-a-design-with-accessibility-9414.md>)

Original publisher: [Read original article](<https://a11yproject.com/posts/starting-a-design-with-accessibility/>)

Author: Steve Barnett

Published: 2021-08-25T00:00:00Z

Content type: tutorial

Language: en

Sources: [The A11Y Project](<https://devfeed.tech/sources/the-a11y-project.md>)

Topics: [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [HTML](<https://devfeed.tech/topics/html.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [inclusive design](<https://devfeed.tech/topics/inclusive-design.md>), [alt text](<https://devfeed.tech/topics/alt-text.md>), [Web](<https://devfeed.tech/topics/web.md>), [Forms](<https://devfeed.tech/topics/forms.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [alt-text](<https://devfeed.tech/tags/alt-text.md>), [design](<https://devfeed.tech/tags/design.md>), [html](<https://devfeed.tech/tags/html.md>)

### AI overview

The article recommends building accessibility into design from the start through three steps: write a numbered, text-only outline of headings, images, links, buttons, and form elements; turn it into a one-column, HTML-only page using semantic elements; then test scenarios where things go wrong. The outline clarifies reading, heading, and focus order and encourages meaningful link and button text, image descriptions, and form labels. HTML makes each element's role explicit, such as choosing a link for navigation and a button for an action. Breaking the design by trying missing or incorrectly formatted input helps identify needed help text and error messages. Once presentation is added, check color, contrast, animation, timing, and interactive states such as focus styles.

### Source excerpt

Designing with accessibility in mind from the start is even better than reviewing a design for accessibility. It helps us consider the wide range of people who use our products and services. Here are three things we can do to start a design with accessibility. Do a text-only design Doing a text-only design to helps us clarify the order and content of a page. What to do We can write out the design in text before opening up our favorite design tool (like Sketch or Figma or Adobe XD). Start by making a numbered list with pen and paper, or in a text editor. Write out the: Section headings, Content and function of each image, Text of each link, Text of each button, and Name of each form element. Why to do it Writing the content in a numbered list lets us be clear on: The source order of elements in the HTML. This is the order that a screen reader will read the page in. The hierarchy of elements on the page. This helps us make choices about layouts on different screen sizes. The focus order of the page. This helps us make sure it's logical and meaningful. Writing headings lets us divide the page up into logical sections. Screen reader users often use headings as a way of navigating around a page. Writing the text of images means we'll already have alt text (or something that's a good start on it). It helps us be clear on what information (if any) the image is conveying. Writing the text for links highlights why "Click here" isn't helpful link text. Link text should describe where the person goes when they follow the link. Writing the text for buttons highlights why "Submit" usually isn't helpful button text. Button text should describe what happens when the person presses the button. Writing the names of form elements forces us to think of good labels. It forces us to think about the clearest name for each element. Do an HTML-only design Doing an HTML-only design helps us clarify the order and content of a page. It also helps us clarify the single function of each interac

## Reviewing a design for accessibility

DevFeed: [Reviewing a design for accessibility](<https://devfeed.tech/articles/reviewing-a-design-for-accessibility-9411.md>)

Original publisher: [Read original article](<https://a11yproject.com/posts/reviewing-a-design-for-accessibility/>)

Author: Steve Barnett

Published: 2021-08-14T00:00:00Z

Content type: tutorial

Language: en

Sources: [The A11Y Project](<https://devfeed.tech/sources/the-a11y-project.md>)

Topics: [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [inclusive design](<https://devfeed.tech/topics/inclusive-design.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [alt text](<https://devfeed.tech/topics/alt-text.md>), [Forms](<https://devfeed.tech/topics/forms.md>), [Web Content Accessibility Guidelines](<https://devfeed.tech/topics/web-content-accessibility-guidelines.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [annotations](<https://devfeed.tech/tags/annotations.md>), [color](<https://devfeed.tech/tags/color.md>), [context](<https://devfeed.tech/tags/context.md>), [design](<https://devfeed.tech/tags/design.md>), [designers](<https://devfeed.tech/tags/designers.md>), [developers](<https://devfeed.tech/tags/developers.md>), [figma](<https://devfeed.tech/tags/figma.md>), [form](<https://devfeed.tech/tags/form.md>), [icons](<https://devfeed.tech/tags/icons.md>), [input](<https://devfeed.tech/tags/input.md>), [name](<https://devfeed.tech/tags/name.md>), [radio](<https://devfeed.tech/tags/radio.md>), [review](<https://devfeed.tech/tags/review.md>), [semantics](<https://devfeed.tech/tags/semantics.md>), [standard](<https://devfeed.tech/tags/standard.md>), [text](<https://devfeed.tech/tags/text.md>)

### AI overview

Reviewing designs before development can catch accessibility barriers early. The source recommends clearly annotating element semantics and accessibility needs, using printout notes, Figma comments, or another method. Its checklist covers unique, descriptive page titles; logical heading levels; text alternatives for images and empty alt text for confirmed decorative images; descriptive link and button names, made unique when repeated; standard form controls where they fit the design; named inputs and groups; and clear error messages that explain the problem and remedy without relying only on color or sensory descriptions. The excerpt ends during its discussion of form labels, so it does not establish full-document coverage.

### Source excerpt

I'm a big believer in shifting left: considering accessibility as early in the process as we can. One way we can do this is by reviewing designs for accessibility. This helps us catch anything we've missed before we start developing it. What to do: annotate By adding annotations about the semantics and accessibility of elements on a page we can remove barriers to access. The best way to do annotations might be sticky notes on a printout or adding comments on a Figma file, or something else. The important thing is that we want to be clear and explicit. Here are a handful of things that I've found give good value / effort balance when reviewing a design for accessibility. Things to check Page title Is the page title unique? Does it concisely describe the page content? Headings Are headings used to divide content up in a logical way? Are the levels shown, without skipping any? Text alternatives Do all images (including icons) have a text alternative (using the alt attribute)? You can see WebAIM's guide to alternative text for more about what this is, and what makes good alternative text. If the image is decorative, is it marked as such (using alt="")? Are we sure it's only decorative? Link and button text Does each link describe where we'll go when we follow it? Does each button describe what will happen when we use it? Where links or buttons have the same text repeated on a page, do they have a longer accessible name that is unique? For example: "View details of Quarter 1 review" instead of "View details". Standard controls Do form controls match standard ones (like selects, radio, and checkbox) where possible? If not, is it possible to use a standard control instead? Are standard controls being used to match the design intent? Names for form elements Do all form controls (one input plus one label) have a name? You can reference MDN's article on the <label> HTML element for an example of how the label and input elements work together with the id and for attributes to

## Accessibility and SEO

DevFeed: [Accessibility and SEO](<https://devfeed.tech/articles/accessibility-and-seo-9365.md>)

Original publisher: [Read original article](<https://a11yproject.com/posts/accessibility-seo/>)

Author: Cooper Hollmaier

Published: 2021-07-01T00:00:00Z

Content type: article

Language: en

Sources: [The A11Y Project](<https://devfeed.tech/sources/the-a11y-project.md>)

Topics: [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [Search engine optimization (SEO)](<https://devfeed.tech/topics/seo.md>), [HTML](<https://devfeed.tech/topics/html.md>), [Google](<https://devfeed.tech/topics/google.md>), [Web](<https://devfeed.tech/topics/web.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [content](<https://devfeed.tech/tags/content.md>), [google](<https://devfeed.tech/tags/google.md>), [html](<https://devfeed.tech/tags/html.md>), [html-elements](<https://devfeed.tech/tags/html-elements.md>), [links](<https://devfeed.tech/tags/links.md>), [search](<https://devfeed.tech/tags/search.md>), [seo](<https://devfeed.tech/tags/seo.md>), [web](<https://devfeed.tech/tags/web.md>)

### AI overview

This article explains that accessibility and search engine optimization often benefit from the same people-centered practices. It discusses meaningful section headings, page structure, HTML headings, and descriptive anchor text as ways to improve navigation for people while helping search engines understand and discover content.

### Source excerpt

Search engine optimization and accessibility have a lot more in common than you would think. Many of the same practices that we use to enable everyone to enjoy our digital experiences also open the doors for search engines. The intersection of people and search engines Search engine optimization often gets a bad reputation. In the early years, marketers were adding blocks of keywords into pages by the truck load. Getting to the top of the results by any means necessary was the game. Companies focused on publishing content that was machine-first, not people-first. The Search Engine Optimization (SEO) industry has since evolved. Marketers who choose to build for people over profit, are those that gain increased visibility online. Catering to bots and algorithm changes, by contrast, is often a game of whack-a-mole and traffic gains are short lived. Below, we will examine some of the ways accessibility and SEO teams can work together towards a future where everyone wins. Headings Search engines crawl through an endless sea of webpages everyday. Assembling information into search results would be impossible without some semblance of structure. This is where section headings come into play. When implemented to provide meaning rather than styling, headings create an easy way to scan and navigate a document for all people. <!-- Meh --> <strong>Animals</strong> <p>Monkeys, Lions, Bears</p> <!-- Better --> <h1>Animals</h1> <p>Monkey, lions, and bears are all examples of animals.</p> <h2>Monkeys</h2> <p>Monkeys are primarily found in tropical rain forests.</p> <h2>Lions</h2> <p>All wild lions live on the African continent, with the exception of a small population in western India.</p> <h2>Bears</h2> <p>Species of bears exist almost everywhere in the world.</p> Properly implemented HTML section headings help search engines, too. To determine if a page is relevant to a person's search, Google has to know about the contents of a page. If a page title isn't present in the code, se

## Everyday Accessibility

DevFeed: [Everyday Accessibility](<https://devfeed.tech/articles/everyday-accessibility-9382.md>)

Original publisher: [Read original article](<https://a11yproject.com/posts/everyday-accessibility/>)

Author: Michele A Williams; PhD

Published: 2021-06-15T00:00:00Z

Content type: article

Language: en

Sources: [The A11Y Project](<https://devfeed.tech/sources/the-a11y-project.md>)

Topics: [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [alt text](<https://devfeed.tech/topics/alt-text.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [alt-text](<https://devfeed.tech/tags/alt-text.md>), [images](<https://devfeed.tech/tags/images.md>), [readability](<https://devfeed.tech/tags/readability.md>), [social-media](<https://devfeed.tech/tags/social-media.md>), [speech](<https://devfeed.tech/tags/speech.md>), [text-to-speech](<https://devfeed.tech/tags/text-to-speech.md>), [writing](<https://devfeed.tech/tags/writing.md>)

### AI overview

This practical accessibility article explains how to make social media, digital, and multimedia content more inclusive. It recommends capitalizing words in hashtags, providing written text alongside images of text, adding concise alt text to images, limiting disruptive emoji use, and using built-in document styling features so assistive technologies can interpret content correctly.

### Source excerpt

Even with the best of intentions, you may be making decisions that exclude disabled users. Below are practical, intentional steps you can start today to create and share more accessible social media, digital, and multimedia content. Watch this post as a video Social Media Posts Social media is central to the world's conversations, so ensure you're not leaving anyone out. Use capital letters in hashtags Punctuation helps text-to-speech tools like screen readers speak more accurately, and helps with readability overall. This includes in hashtags, where capital letters help distinguish words. Key Point: Make it a habit to #UseCapitalLetters rather than #hardtoreadlowercase. Don't share just images of text Images of text (such as your favorite quote or saying) can be difficult for people with visual impairments to read and don't allow people with reading difficulties to leverage text-to-speech read-aloud features. When posting these kinds of images, also write out the text in your post. Key Point: Typing out the text in an image makes the content more accessible. Use "alt text" features to describe images Pictures are significant in social media, but also inaccessible to visually impaired readers unless they have a text-based description. When uploading, find the "image description" or "alternative/alt text" feature in the software to write a description. For sample instructions, review Alt Text for Social Media. When adding descriptions, don't write every detail, just enough to ensure everyone can understand your post and share in the image's meaning. For examples, read Scott Vinkle's Considerations when writing alt text. Key Point: Features like Twitter's "Add description" allow adding "alt text" for visually impaired readers. Limit your emojis Emojis are great for emphasis and playfulness, but adding too many sounds cluttered with text-to-speech software. Also, when placed unconventionally (such as throughout a sentence) this is distracting and hard to read for those

## Fixing contrast issues, on your own site and elsewhere

DevFeed: [Fixing contrast issues, on your own site and elsewhere](<https://devfeed.tech/articles/fixing-contrast-issues-on-your-own-site-and-elsewhere-9383.md>)

Original publisher: [Read original article](<https://a11yproject.com/posts/fixing-contrast-issues-on-your-own-site-and-elsewhere/>)

Author: Kilian Valkhof

Published: 2021-06-07T00:00:00Z

Content type: article

Language: en

Sources: [The A11Y Project](<https://devfeed.tech/sources/the-a11y-project.md>)

Topics: [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [Web Content Accessibility Guidelines](<https://devfeed.tech/topics/web-content-accessibility-guidelines.md>), [inclusive design](<https://devfeed.tech/topics/inclusive-design.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [accessibility-guidelines](<https://devfeed.tech/tags/accessibility-guidelines.md>), [accessible](<https://devfeed.tech/tags/accessible.md>), [automatically](<https://devfeed.tech/tags/automatically.md>), [found](<https://devfeed.tech/tags/found.md>), [ratio](<https://devfeed.tech/tags/ratio.md>), [sites](<https://devfeed.tech/tags/sites.md>), [wcag](<https://devfeed.tech/tags/wcag.md>), [web-content-accessibility-guidelines](<https://devfeed.tech/tags/web-content-accessibility-guidelines.md>), [websites](<https://devfeed.tech/tags/websites.md>)

### AI overview

The excerpt explains that WCAG contrast ratios range from 1 to 21, with minimums of 4.5 for regular text and 3 for large text. Colors just below and above the threshold can look nearly identical, so visual judgment alone can miss failures. The author describes Polypane's checker, which scans text elements and suggests a nearby color that meets the threshold, and a free online checker. For other people's sites, the Fix Contrast browser extension automatically adjusts low contrast text to a selected minimum ratio; users can choose medium or high defaults, set ratios for small and large text, and add a background color when changing the text color is insufficient. The excerpt lists Chrome, Edge, Firefox, Vivaldi and Brave as supported browsers, with Opera and Safari described as hoped-for additions.

### Source excerpt

Insufficient text contrast is the most common accessibility issue on websites today. According to the WebAIM Million report for 2021, 86.4% of home pages world wide have low contrast text. What's worse, this number has been increasing the past three years. Text contrast issues can by and large be automatically found (and fixed, more on that later), so why do nearly 9 out of 10 sites have contrast issues? Before we answer that, a quick intro on what text contrast is When we talk about text contrast, what we mean is the difference between the color of the text and the color that's behind the text. To make sure the text is readable for everyone, you need a certain amount of difference between them. This difference can be measured using a formula that yields a number between 1 (no contrast, white text on a white background) and 21 (the most contrast possible, black text on a white background). That number is called the "contrast ratio". The formula is part of WCAG, the Web Content Accessibility Guidelines. How the formula works is not that important, but there are a few numbers you should be aware of. For regular text, you need a contrast value of at least 4.5, and for large text just 3, to pass the text for sufficient contrast. (There are more strict rules available too). Having to score a 4.5 out of 21 doesn't seem like a very high bar to clear, so why do 86% of websites still have contrast issues? We could blame our own visual perception for that. For example, here's a text with a contrast ratio of 4.12: This text does not have enough contrast For you this might be fine or it might not be, but in any case you're going to have a hard time seeing the difference between it and this text which has a contrast ratio of 4.54: This text does have enough contrast One of them does not have sufficient color contrast and would fail an accessibility audit, and the other would pass. And if you couldn't tell them apart that wouldn't be odd, they're very close. And herein lies a pot

## Should I use an accessibility overlay?

DevFeed: [Should I use an accessibility overlay?](<https://devfeed.tech/articles/should-i-use-an-accessibility-overlay-9412.md>)

Original publisher: [Read original article](<https://a11yproject.com/posts/should-i-use-an-accessibility-overlay/>)

Author: The A

Published: 2021-03-08T00:00:00Z

Content type: opinion

Language: en

Sources: [The A11Y Project](<https://devfeed.tech/sources/the-a11y-project.md>)

Topics: [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [inclusive design](<https://devfeed.tech/topics/inclusive-design.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [overlay](<https://devfeed.tech/tags/overlay.md>), [web-app](<https://devfeed.tech/tags/web-app.md>)

### AI overview

The A11Y Project advises against permanent accessibility overlay plugins. These JavaScript tools alter a site after it renders; unlike temporary overlays used to address specific critical issues until the underlying code is fixed, permanent plugins remain in place. The article argues that plugins cannot reliably fix issues needing human judgment, such as whether image alt text is accurate, and may introduce new barriers. It also raises concerns about overriding users' settings, unclear data practices, slowing or crashing sites--especially on lower-powered devices--and interfering with automated accessibility audits. Temporary stopgaps are described as paired with training, while permanent plugins may leave teams repeating the same mistakes. The article recommends learning about disability and assistive technology, checking and testing sites with varied assistive technologies and users, and including disabled people in product creation.

### Source excerpt

Due to their technical, social, and moral issues, The A11Y Project does not recommend using permanent overlay plugins. We view these kinds of products as actively harmful, and a step backwards for digital accessibility efforts. Background Accessibility overlays have become a controversial topic recently. Let's clarify what they are, and how they impact accessibility. An accessibility overlay is JavaScript that is written with the goal of helping to fix accessibility issues on a website or web app. Overlay code is applied after the website or web app is rendered by the browser, to transform it. Generally speaking, there are two types of accessibility overlays: Temporary bandage solutions, and More permanent plugins. Of the two, the more permanent plugins are incredibly problematic. Temporary bandage solutions Temporary bandage solutions have been around for awhile. Historically, they have been used by professional accessibility auditing companies as a stopgap measure. With the bandage approach, the overlay serves as a temporary measure. It is designed to be used to temporarily fix specific, critical accessibility issues until the underlying website or web app code can be updated. Think of these kinds of overlays like a bandage. Bandages are not intended to be left on permanently. They are removed after the injury they cover has healed. Bandage overlays usually have a process to signal when their code should be removed. This process is typically a negotiation between the accessibility auditors and the company who has the inaccessible experience. Permanent plugins Permanent plugins are more of a recent phenomenon. Unlike temporary bandage solutions, permanent plugins are designed to be a persistent presence on the inaccessible website or web app. Four examples of permanent plugins are accessiBe, AudioEye, FACIL'iti, and Max Access. There are numerous issues with permanent plugins. To build off the bandage metaphor, a permanent plugin left on a website or web app for to

## Dyslexia fonts

DevFeed: [Dyslexia fonts](<https://devfeed.tech/articles/dyslexia-fonts-9381.md>)

Original publisher: [Read original article](<https://a11yproject.com/posts/dyslexia-fonts/>)

Author: Hamsa Harcourt

Published: 2021-02-22T00:00:00Z

Content type: article

Language: en

Sources: [The A11Y Project](<https://devfeed.tech/sources/the-a11y-project.md>)

Topics: [Font](<https://devfeed.tech/topics/font.md>), [Web](<https://devfeed.tech/topics/web.md>), [pdf](<https://devfeed.tech/topics/pdf.md>)

Tags: [fonts](<https://devfeed.tech/tags/fonts.md>), [pdf](<https://devfeed.tech/tags/pdf.md>), [readability](<https://devfeed.tech/tags/readability.md>), [research](<https://devfeed.tech/tags/research.md>), [typography](<https://devfeed.tech/tags/typography.md>), [web](<https://devfeed.tech/tags/web.md>)

### AI overview

The article explains dyslexia as a language-processing disorder and discusses how font design and typography can affect readability. It questions whether specialized dyslexia fonts improve reading, noting that research has not shown faster reading or fewer mistakes and that many people with dyslexia prefer common fonts such as Comic Sans, Verdana, and Helvetica. It also recommends general web typography practices, including adequate font size and increased line spacing.

### Source excerpt

Dyslexia is a Phonological Processing disorder. This means it is an issue with language processing, not vision. Dyslexia is a slight disorder of the brain that causes difficulty in reading and spelling, for example, but does not affect intelligence. Dyslexia - Oxford Advanced Learner's Dictionary Dyslexia affects about 1 in 5 people worldwide. Its symptoms range in severity from mild to extreme. It causes your brain to transpose letters, numbers, punctuation, and other characters, which affects your ability to read. This means that making Dyslexic-friendly fonts and typography choices are important things to consider. Background When designing fonts, some typographers flip and rotate one character to form other characters. Letters b, p, d and q are usually created using this method. This is because it makes it easier to make the font. However, this practice may cause problems for people with Dyslexia. It can make some letters, numbers, punctuation, and other characters become indistinguishable. This can make it easy to confuse one character for another. As a result, people with Dyslexia may prefer fonts where all the characters are unique. The questionable utility of Dyslexic fonts? Dyslexia fonts are typefaces designed so that each character is unique and distinguishable. Dyslexia fonts also make each character unique by using thicker lines in some parts of the letters, as well as slanting them a bit. They are intended to help people with Dyslexia. According to recent studies, it has been proven that Dyslexia fonts do not help people read faster and make fewer mistakes. In fact, most people with Dyslexia prefer Comic Sans, Verdana, and Helvetica to other fonts. For a detailed review of the research, see Good Fonts for Dyslexia (PDF). General font tips The following are general tips that improve the overall quality of your website's typography: Font size should be at least 12-14pt or its equivalent. This help people with cognitive disabilities, language and learning

## Use the tabindex attribute

DevFeed: [Use the tabindex attribute](<https://devfeed.tech/articles/use-the-tabindex-attribute-9395.md>)

Original publisher: [Read original article](<https://a11yproject.com/posts/how-to-use-the-tabindex-attribute/>)

Author: Eric Bailey

Published: 2021-01-28T00:00:00Z

Content type: article

Language: en

Sources: [The A11Y Project](<https://devfeed.tech/sources/the-a11y-project.md>)

Topics: [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [tabbing](<https://devfeed.tech/topics/tabbing.md>), [aria](<https://devfeed.tech/topics/aria.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [assistive-technology](<https://devfeed.tech/tags/assistive-technology.md>), [focus](<https://devfeed.tech/tags/focus.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [key](<https://devfeed.tech/tags/key.md>), [keyboard](<https://devfeed.tech/tags/keyboard.md>)

### AI overview

Positive tabindex values disrupt the expected keyboard tab order, and manually assigning tab order is difficult to maintain. Use native interactive elements in document reading order; they already support Tab navigation. Avoid tabindex="0" on ordinary non-interactive content, which can confuse users, add keyboard stops, and fail to communicate the element's name or role. Use tabindex="-1" when JavaScript needs to focus a widget that manages focus internally. For scrollable overflow containers, use tabindex="0" and provide a concise label and semantic context, such as a sectioning element or suitable role. Use tabindex="0" for interactive controls without a relevant native HTML element.

### Source excerpt

tabindex is a global attribute that allows an HTML element to receive focus. It needs a value of zero or a negative number in order to work in an accessible way. When tabindex's value is set to zero or a positive number, the element can be navigated to via the keyboard's Tab key. When it is set to a negative number, its element can be programmatically focused via JavaScript. Common mistakes Unfortunately, the tabindex attribute is often misunderstood and consequently misused. Following are some common examples of tabindex use that have a negative impact on accessibility: Using a positive tabindex value Using tabindex with a value of 1, 2, 3, etc. places the element the tabindex is applied first in the keyboard tabbing order. This can create a confusing experience for anyone who relies on the keyboard's Tab key to navigate. Setting a manual tab order You don't need to manually set tab order for every page or view on a website or web app. Not only is this extra, unnecessary work that is difficult to maintain, it may deviate from someone's expected or desired way to navigate. This results an annoying, confusing, and potentially inaccessible experience. Instead, use appropriate interactive elements (a for links, button for buttons, etc.) and put them in the reading order of the document. Interactive elements come with native browser behavior already built in that allows them to be navigated to via Tab without the need for a tabindex declaration. Making non-interactive elements focusable There is a myth that applying tabindex="0" to non-interactive elements (paragraphs, headings, lists, etc.) helps "improve" accessibility by providing a way for a person who uses a screen reader to focus on all the content present in a webpage or web app. Unfortunately, this well-intentioned idea actually does not create a good assistive technology experience. In the same way that you don't need to add a tabindex attribute declaration to native interactive elements, you also don't need to

## Text resizing in iOS and Android

DevFeed: [Text resizing in iOS and Android](<https://devfeed.tech/articles/text-resizing-in-ios-and-android-9415.md>)

Original publisher: [Read original article](<https://a11yproject.com/posts/text-resizing-in-ios-and-android/>)

Author: Lucia Cerchie

Published: 2021-01-28T00:00:00Z

Content type: tutorial

Language: en

Sources: [The A11Y Project](<https://devfeed.tech/sources/the-a11y-project.md>)

Topics: [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [Android](<https://devfeed.tech/topics/android.md>), [Responsive Design](<https://devfeed.tech/topics/responsive-design.md>), [iOS](<https://devfeed.tech/topics/ios.md>), [Web Content Accessibility Guidelines](<https://devfeed.tech/topics/web-content-accessibility-guidelines.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [android](<https://devfeed.tech/tags/android.md>), [html](<https://devfeed.tech/tags/html.md>), [ios](<https://devfeed.tech/tags/ios.md>), [responsive-design](<https://devfeed.tech/tags/responsive-design.md>), [scale](<https://devfeed.tech/tags/scale.md>)

### AI overview

Support text enlargement across mobile platforms. On iOS, use Dynamic Type and avoid manually capping text scaling; the excerpt gives 17pt as the minimum body size and notes that Full Screen Zoom and Window Zoom magnify screen areas. On Android, use scale-independent pixels, provide text scaling at different sizes yourself, and preview device variations with Android Emulator; the suggested body minimum is 16sp. Make content containers scrollable so enlarged text is not cut off. For HTML views, use relative units to avoid forcing both horizontal and vertical scrolling, which the excerpt says violates WCAG 1.4.10. It also warns that `maximum-scale=1.0` in the meta element frustrates pinch zoom on mobile iOS versions below 10.

### Source excerpt

When you're designing for mobile, it's important to remember that some people will need to change the size of the content to read it easily. There are so many ways to view content on mobile devices, from zooming in to orienting the screen differently, so a failure to design in a dynamic environment can lead to accessibility issues. There are different ways you can attend to this, whether you're writing an app for iOS or Android. Considerations for iOS In iOS, users can use Full Screen Zoom or Window Zoom to magnify parts of the screen. To allow them to resize the type, use dynamic type, which enables your app's type to be resized. If you manually limit how large your text scales it may cause issues for people who need a bigger font. You want the text to scale dynamically instead of stopping at the point you set, because that size may still not be visible to all people. Minimum font-size for body text should be 17pt. Considerations for Android You can use a tool called the Android Emulator to preview how your app works in the context of different android devices. This can help you stay aware of how people who use different types of androids experience your app. Again, users can only zoom in on specified areas, so you'll need to use scale-independent pixels to determine the size of your text. There isn't a tool like Dynamic Type in Android, so you'll need to scale the text at different sizes yourself. Material design has a resource that makes a good starting point. Minimum font-size for body text should be 16sp: android: textSize=16sp You'll also want to remember to make your content container scrollable. If it's not, you'll just cut off the extra content when a person zooms in. Also consider that apps may contain HTML views. There are a couple things to keep in mind here for accessibility as well. HTML In your HTML, make sure to use relative units for responsive design. Here's a resource from The CSS Layout Workshop for applying them to your HTML via CSS. If you don'

## Designing accessible animation

DevFeed: [Designing accessible animation](<https://devfeed.tech/articles/designing-accessible-animation-9380.md>)

Original publisher: [Read original article](<https://a11yproject.com/posts/design-accessible-animation/>)

Author: Kelly Gillit

Published: 2020-12-22T00:00:00Z

Content type: article

Language: en

Sources: [The A11Y Project](<https://devfeed.tech/sources/the-a11y-project.md>)

Topics: [animations](<https://devfeed.tech/topics/animations.md>), [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [inclusive design](<https://devfeed.tech/topics/inclusive-design.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [accessible](<https://devfeed.tech/tags/accessible.md>), [animation](<https://devfeed.tech/tags/animation.md>), [animations](<https://devfeed.tech/tags/animations.md>), [controllers](<https://devfeed.tech/tags/controllers.md>), [design](<https://devfeed.tech/tags/design.md>), [designing](<https://devfeed.tech/tags/designing.md>), [desktop](<https://devfeed.tech/tags/desktop.md>), [developers](<https://devfeed.tech/tags/developers.md>), [devices](<https://devfeed.tech/tags/devices.md>), [digital](<https://devfeed.tech/tags/digital.md>), [focus](<https://devfeed.tech/tags/focus.md>), [fun](<https://devfeed.tech/tags/fun.md>), [handheld](<https://devfeed.tech/tags/handheld.md>), [interaction](<https://devfeed.tech/tags/interaction.md>), [motion](<https://devfeed.tech/tags/motion.md>), [motion-design](<https://devfeed.tech/tags/motion-design.md>), [navigation](<https://devfeed.tech/tags/navigation.md>), [number](<https://devfeed.tech/tags/number.md>), [play](<https://devfeed.tech/tags/play.md>)

### AI overview

Animation can focus attention and add character, but dramatic motion may trigger dizziness, nausea, disorientation, migraines, or seizures. The text recommends treating accessibility as part of design: use caution with parallax and horizontally scrolling navigation, make animation responsive to viewing context so it does not overwhelm or distract, and avoid endless loops. Limit cycle count or duration, start animation paused, or provide controls to pause, stop, or hide it. It also notes that developers can implement these design choices and points to further reading, without specifying implementation details.

### Source excerpt

Animation is used in digital products in many ways, such as drawing a user's focus to a particular area on the screen, providing another layer to a brand's style with unique and ownable motion design, and adding a spark of unexpected fun to an otherwise robotic interaction. But designing animation that surprises and delights accessibly is trickier than it sounds. Dizziness, nausea, disorientation, migraines, and even seizures can all be caused by well-executed yet inaccessible motion design. Because of this, it is critical to design your animation with both aesthetics and accessibility in mind. Consider parallaxing--large-scale animation where the foreground and background slide past each other at different speeds--and primary navigation based on horizontal scrolling. These effects, especially when dramatic, can trigger the symptoms mentioned earlier. Animations inherently carry a lot of visual and cognitive weight, so always take into account how the user will be viewing it. Desktop screens are interacted with at a greater distance than handheld devices, therefore any animation should be responsive to avoid overwhelming or distracting users from anything essential. Users with cognitive and learning disabilities may especially appreciate this. Next, rein in the animations. Endlessly looping animations at any size can be more disorienting than delightful. Specifying the number of cycles it will play, limiting the duration that it plays, or having the animation paused by default will ensure its accessibility. Another way to handle this is by designing controllers that allow the user to pause, stop, or hide the animation altogether. While it's essential that accessible animation starts at the design level, there are additional ways developers can implement these tips behind the scenes. We've included some links to help show you how.

## Getting started with VoiceOver on iOS

DevFeed: [Getting started with VoiceOver on iOS](<https://devfeed.tech/articles/getting-started-with-voiceover-on-ios-9389.md>)

Original publisher: [Read original article](<https://a11yproject.com/posts/getting-started-with-voiceover-ios/>)

Author: Anh Pham

Published: 2020-11-23T00:00:00Z

Content type: tutorial

Language: en

Sources: [The A11Y Project](<https://devfeed.tech/sources/the-a11y-project.md>)

Topics: [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [iOS](<https://devfeed.tech/topics/ios.md>), [iphone](<https://devfeed.tech/topics/iphone.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [apple](<https://devfeed.tech/tags/apple.md>), [for-developers](<https://devfeed.tech/tags/for-developers.md>), [gestures](<https://devfeed.tech/tags/gestures.md>), [getting-started](<https://devfeed.tech/tags/getting-started.md>), [guide](<https://devfeed.tech/tags/guide.md>), [helps](<https://devfeed.tech/tags/helps.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [introduced](<https://devfeed.tech/tags/introduced.md>), [ios](<https://devfeed.tech/tags/ios.md>), [iphone](<https://devfeed.tech/tags/iphone.md>), [ipod](<https://devfeed.tech/tags/ipod.md>), [macos](<https://devfeed.tech/tags/macos.md>), [screen](<https://devfeed.tech/tags/screen.md>), [test](<https://devfeed.tech/tags/test.md>), [testing](<https://devfeed.tech/tags/testing.md>), [toggle](<https://devfeed.tech/tags/toggle.md>)

### AI overview

VoiceOver is an iOS screen reader that announces selected items and their hints, values, and traits as users navigate by touch. Enable it in Settings > Accessibility > VoiceOver; for quicker toggling, add it under Accessibility Shortcut and triple-click the side button on iPhone X or later, or the Home button on earlier models. Siri can also turn it on or off. Common gestures include touching or dragging to hear items and flicking left or right to move among them; double-tap to activate an item. The two-finger Rotor selects settings such as speaking rate or headings, which users then apply with one-finger swipes up or down. The excerpt recommends developers test VoiceOver on their chosen device and distinguishes the iOS reader from the separate macOS VoiceOver.

### Source excerpt

VoiceOver is a screen-reading tool built into Apple Inc.'s iOS. It helps people navigate and use their iPhone without needing to see the screen. First introduced in 2009 with the iPod Shuffle and iPhone 3GS, VoiceOver has been in the picture in every Apple's iOS release ever since. For developers, it is always a good idea to test out VoiceOver with your project on your chosen testing device. There is also VoiceOver for macOS - a separate screen reader from VoiceOver iOS. If interested, you can check out Mat Marquis's detailed guide to macOS VoiceOver! How does VoiceOver work? On an iPhone, VoiceOver responds to gestures (single tap, double tap, et cetera) and audibly communicates to us all the information we need to know (for example, what we have selected or done, the hints, values and traits of the items). How to start using VoiceOver on iOS The easiest way to turn on VoiceOver on your iPhone is to: Open Settings app on your iPhone. Select Accessibility. Under Vision, select VoiceOver. Turn on VoiceOver. You can also make it easier to activate/deactivate VoiceOver and use it frequently, by adding an Accessibility Shortcut: Open Settings app on your iPhone. Select Accessibility. Under General, select Accessibility Shortcut. Select VoiceOver. Then you can toggle VoiceOver feature on or off by triple clicking the side button (on iPhone X or later). If it is an earlier version of iPhone, triple click the Home button. You can also ask Siri to turn on VoiceOver on or off instantly by saying "Hey Siri, turn on VoiceOver!" or "Hey Siri, turn off VoiceOver!". Basic VoiceOver gestures Here are some common gestures you can use to navigate our iPhone with VoiceOver: Gesture Description Touch the screen anywhere Hear an item Drag finger on screen Explore items Quickly flick left or right with one finger Locate items or apps Double tap Select and activate app, link or button Triple tap Double tap items Tap once with two fingers Pause VoiceOver Swipe up from bottom edge (ends wi

## Enabling keyboard culture with No Mouse Days

DevFeed: [Enabling keyboard culture with No Mouse Days](<https://devfeed.tech/articles/enabling-keyboard-culture-with-no-mouse-days-9406.md>)

Original publisher: [Read original article](<https://a11yproject.com/posts/no-mouse-days/>)

Author: Marcy Sutton

Published: 2020-10-15T00:00:00Z

Content type: article

Language: en

Sources: [The A11Y Project](<https://devfeed.tech/sources/the-a11y-project.md>)

Topics: [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [inclusive design](<https://devfeed.tech/topics/inclusive-design.md>), [Front end](<https://devfeed.tech/topics/frontend.md>), [npm](<https://devfeed.tech/topics/npm.md>), [CSS](<https://devfeed.tech/topics/css.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [css](<https://devfeed.tech/tags/css.md>), [front-end-development](<https://devfeed.tech/tags/front-end-development.md>), [inclusive-design](<https://devfeed.tech/tags/inclusive-design.md>), [npm](<https://devfeed.tech/tags/npm.md>), [processes](<https://devfeed.tech/tags/processes.md>), [tooling](<https://devfeed.tech/tags/tooling.md>), [web](<https://devfeed.tech/tags/web.md>)

### AI overview

The article advocates regular mouse-free testing to reveal keyboard and screen reader accessibility problems in websites and applications. It introduces No Mouse Days, an npm package that hides the mouse cursor with CSS, and encourages teams to use the practice to identify inaccessible controls and missing focus outlines early.

### Source excerpt

Wouldn't it be great if designers and developers tested their digital experiences for keyboard accessibility on the regular? And by extension, screen reader accessibility? That's where the #NoMouse challenge and No Mouse Days come in. The DO-IT Center at University of Washington originally started the No Mouse challenge, complete with its own website, logo, and hashtag to spread awareness about the need for keyboard-accessible websites and applications. The challenge is pretty straight-forward: Step 1. Use the Web without a mouse. Can you access all features? Can you reach and operate all interactive controls? Can you easily tell where you are on the page? Step 2. Learn more about accessible web design. Step 3. Spread the Word! Building on that initiative came No Mouse Days, an npm package that disables the mouse cursor on web pages with CSS. It started as a cheeky joke, and then it actually became popular. The idea of No Mouse Days was to make it easy to hide the mouse cursor so it would become extremely obvious when a user interface didn't support the keyboard, perhaps disabling it automatically for front-end development one day a week. If you have further ideas for No Mouse Days or other culture-changing techniques, contributions are always welcome on GitHub and Twitter! No matter how you go about it, establishing a mouse-free development day at least once a week could work wonders for people who can't use a mouse at all. You might find interactive controls that aren't actually interactive for large segments of the population and lacking visible focus outlines which make keyboard navigation difficult. Surfacing issues with keyboard-support early and often will give teams something to react to, and hopefully dedicated tooling and processes can make it second nature through more inclusive design and development.

[Next page](<https://devfeed.tech/sources/the-a11y-project.md?cursor=WyIyMDIwLTEwLTE1VDAwOjAwOjAwKzAwOjAwIiwgImQ1ZDc1YjFlLTNhNDctNDRkZS05NTg2LTc2YmQ3NzcyODI4NyJd>)