# accessibility-testing Published articles for accessibility-testing. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## tota11y - an accessibility visualization toolkit DevFeed: [tota11y - an accessibility visualization toolkit]() Original publisher: [Read original article]() Author: Khan Academy Published: 2015-06-08T22:00:00Z Content type: release Language: en Sources: [Khan Academy]() Topics: [Accessibility](), [audit](), [Testing](), [Tooling](), [browser](), [Chrome]() Tags: [accessibility](), [accessibility-testing](), [audit](), [browser](), [chrome](), [developer-tools](), [engineering](), [frontend](), [linter](), [news](), [testing](), [tests](), [tooling](), [unit-tests](), [visualization](), [web](), [web-frontend]() ### AI overview Khan Academy announces tota11y, an accessibility visualization toolkit designed to make manual accessibility testing easier for developers. The article describes its development and use of browser-based annotations to help teams understand and fix accessibility issues. ### Source excerpt By Jordan Scales Today we're releasing tota11y (on GitHub), an accessibility visualization toolkit that aims to reduce the ... Read more ## From a long list to a clear signal: baseline-driven accessibility reporting DevFeed: [From a long list to a clear signal: baseline-driven accessibility reporting]() Original publisher: [Read original article]() Author: Benjamin Bischoff Test Automation Engineer; Author; Speaker; Magician Github Profile Linkedin Profile Published: 2026-03-13T00:00:00Z Content type: tutorial Language: en Sources: [Trivago]() Topics: [digital accessibility](), [Accessibility](), [axe-core](), [Test automation](), [Automation](), [Selenium](), [Testing](), [Extension]() Tags: [accessibility](), [accessibility-testing](), [automation](), [axe-core](), [eaa](), [european-accessibility-act](), [frontend](), [quality-assurance](), [selenium](), [test-automation](), [testing]() ### AI overview The article describes a baseline-driven approach to accessibility reporting. It extends an in-house test automation framework so new test runs can be compared with a snapshot of known issues on the main branch, helping teams distinguish regressions from existing technical debt and track changes more clearly. ### Source excerpt The output of most automated accessibility tests is a long list of violations. This format, while comprehensive, makes it difficult to distinguish new issues introduced in a feature branch from ... ## Web Accessibility Trends Expected to Shape 2026 DevFeed: [Web Accessibility Trends Expected to Shape 2026]() Original publisher: [Read original article]() Author: John Northup Published: 2025-12-22T23:22:37Z Content type: opinion Language: en Sources: [WebAIM Blog]() Topics: [Accessibility](), [Web Accessibility (a11y)](), [Artificial Intelligence](), [Testing](), [Automation](), [ChatGPT]() Tags: [2026](), [accessibility](), [accessibility-testing](), [ai](), [automation](), [chatgpt](), [testing](), [uncategorized](), [web-accessibility]() ### AI overview The article forecasts gradual changes in web accessibility during 2026. It argues that AI will improve accessibility testing tools and workflow efficiency but will not replace human expertise, especially for judging context, intent, meaningful alternative text, and user experience. It also expects WCAG 2.2 to increasingly become a procurement baseline. ### Source excerpt I've lived long enough, and worked in accessibility long enough, to have honed a healthy skepticism when I hear about the Next Big Thing. I've seen lush website launches that look great, until I activate a screen reader. Yet, in spite of it all, accessibility does evolve, but quietly rather than dramatically. As I gaze [...] ## Re-introducing Paparazzi's Accessibility Snapshots DevFeed: [Re-introducing Paparazzi's Accessibility Snapshots]() Original publisher: [Read original article]() Author: Colin Marsch Published: 2025-07-14T00:00:00Z Content type: tutorial Language: en Sources: [Cash App Code Blog]() Topics: [Accessibility](), [Testing](), [Compose](), [Android]() Tags: [accessibility](), [accessibility-testing](), [android](), [compose](), [compose-ui](), [library](), [test](), [testing]() ### AI overview This article explains Paparazzi's accessibility snapshots for Android UI tests. It describes how the snapshots expose semantic accessibility properties and layout bounds for legacy Android views and Compose UI, and how they can be recorded and verified like regular Paparazzi tests. The article cautions that snapshots should supplement, not replace, a broader accessibility testing strategy. ### Source excerpt Overview ## Does Junie Create Accessible Android Apps? DevFeed: [Does Junie Create Accessible Android Apps?]() Original publisher: [Read original article]() Author: Eevis Panula Published: 2025-06-10T04:54:16.242000Z Content type: opinion Language: en Sources: [Eevis Blog]() Topics: [junie](), [Accessibility](), [Artificial Intelligence](), [Android](), [Testing](), [IntelliJ IDEA]() Tags: [accessibility-testing](), [ai](), [android](), [android-studio](), [junie]() ### AI overview The article reports on two rounds of testing Junie, JetBrains' coding agent, by generating Android apps and evaluating their accessibility. It also discusses Junie's structured workflow, unnecessary library additions, a KSP version issue, and differences between its Early Access and generally available versions. ### Source excerpt I'm continuing my tests with AI-generated Android code and how accessible these generated apps are. This time, the tool of choice is Junie, the coding agent by JetBrains. If you want to know why I'm doing this or want to read my take on how accessible code Gemini creates, the first post is available at Does Gemini Create Accessible Android Apps?. So, I got into the Early Access Program (EAP) before Junie was generally available and generated the first app. I had all these plans to proceed to the second run and write this blog post sooner, but then life happened, and I founded my own company. Suddenly, time passed, and Junie is now generally available. Before we dive into the application generation and accessibility testing, I'll share a couple of words about Junie I wrote right after the first try, with some additions after the second run. Junie As mentioned, I got access to EAP and was curious to try Junie out, as it differed from the AI solutions for coding I'd used before. Particularly, it also changed the files and didn't just give me the code, and I could skip all the hard work of creating files and copy-pasting the code into those files. Some thoughts I had: I was impressed by the structured approach for doing things. It was easy to follow what was happening next and what was coming after that. When creating the first app, Junie kind of went overboard with adding libraries like Room into the project, but not using them in the code. With the first app, I had to solve one KSP version issue by hand, because I got tired of Junie trying to find a working library version. It used some non-existent version numbers first. The second app used kapt, which resolved the version right away. I had to iterate a bit with the first version to get all the features I wanted, like adding yarn. The second app generation was smooth from this point of view. The App As with the tests with Gemini, I did two rounds of testing - first, with the Early Access Program version back at the b ## Testing Android App Accessibility: Clue DevFeed: [Testing Android App Accessibility: Clue]() Original publisher: [Read original article]() Author: Eevis Panula Published: 2024-09-15T10:39:37.974000Z Content type: opinion Language: en Sources: [Eevis Blog]() Topics: [Accessibility](), [Testing](), [Android](), [App]() Tags: [accessibility](), [accessibility-testing](), [android](), [app](), [blog-post](), [demo](), [droidcon](), [tests](), [tools]() ### AI overview The article summarizes a Droidcon Berlin talk that tested the accessibility of Clue, an Android period-tracking app. It describes why Clue was chosen, notes that the testing was limited, and identifies the accessibility tools and settings used. ### Source excerpt In Droidcon Berlin, I gave a talk titled "Is This App Accessible? A Live Testing Demo," in which I tested one app from an accessibility perspective. The audience voted for the app from three options and selected Clue, a period tracking app. The other two were the Droidcon app and Provinssi's (a Finnish music festival I attended in June) app. In this blog post, I'll summarize the talk and probably add some things I was supposed to say on stage but forgot. So note that this post might slightly differ from the actual talk I gave. If you want to watch the talk, it's available on the Droidcon website: Is this app accessible? A live testing demo Note that as the talk was 40 minutes long, I did not do that extensive accessibility testing, and the app may have more issues than I found. Why I Chose Clue? When I was thinking about the possible apps for testing, I wanted to include an app that's not the most typical example in developer conferences and learning materials. I can't count how many examples of different vehicles I've seen (hello, inheritance!). Or examples having something related to movies. As the gender balance in tech is skewed towards those who don't have cycles, I wanted to bring this topic in. I also think that periods should be talked about way more in different settings - that would help to dismantle the taboo around them, as well as all those stupid stereotypes and jokes around menstruating people. And why Clue, why not some other app? It's because their app is the best one. Their app is the least heteronormative I've encountered out there. It doesn't assume my gender, nor does it assume the gender of the partner if I wanted to share my cycle data with someone. And speaking of the partner mode... I haven't used it, but I haven't also seen any creepy "we will let your (man) partner know that based on your cycle, you want to have sex"-messages. I'm not naming names, but some other period-tracking apps do this. Note! Clue didn't pay me to advertise them! The ## Testing with Accessibility Scanner DevFeed: [Testing with Accessibility Scanner]() Original publisher: [Read original article]() Author: Eevis Panula Published: 2024-02-16T03:38:54.088000Z Content type: tutorial Language: en Sources: [Eevis Blog]() Topics: [Accessibility](), [Testing](), [Android](), [App](), [Google Play](), [Flutter](), [React Native](), [PWA]() Tags: [accessibility](), [accessibility-testing](), [android](), [flutter](), [google-play](), [pwa](), [react-native](), [test-automation](), [testing]() ### AI overview This tutorial explains how to use Accessibility Scanner for semi-automated accessibility testing of Android apps. The tool can identify issues involving content labels, touch target size, clickable items, and text and image contrast, but it cannot detect every accessibility problem, so manual testing remains necessary. It can be used with native Android apps, Flutter and React Native apps, and PWAs. ### Source excerpt When I talk about accessibility with Android developers, I often hear that some easy-to-use tests should automatically catch every possible accessibility issue. And I get it. That would make the whole topic of accessibility so much easier and straightforward. But the truth is that automated testing only catches some things. Studies suggest that the maximum percentage of caught accessibility issues is 40-50%. Deque, the company that develops the aXe accessibility tool, claims that the number is 57% in their study of automated accessibility tools. These studies have been performed with websites, but based on my experience, I have no reason to believe that the number would be higher on Android. So manual testing is always needed. But for that 40-57% (or whatever the exact number is on Android accessibility testing), there are some tools to use. One of them is Accessibility Scanner, and in this blog post, I'll discuss how to test your app with it. Let's start with what it is. What Is Accessibility Scanner Accessibility Scanner is a helpful tool for semi-automated accessibility testing. It's an app which can catch issues from the following categories: Content labels Touch target size Clickable items Text and image contrast It also suggests how to fix some of its findings and provides more info about the issues. However, it does not find every possible accessibility issue and thus does not guarantee the accessibility of your app. Manual testing is still needed. I keep saying this because I've seen these claims so many times that "Well, our test automation didn't find any accessibility issues, so our app is accessible". One great thing is that you can use Accessibility Scanner with any Android app - it can be a native Android app or built with cross-platform technologies such as Flutter or React Native. Or it can even be a PWA - Progressive Web App. Using Accessibility Scanner Installation To use the Accessibility Scanner, you must first download it from Google Play: Acces ## Types of UI Tests and What They Verify DevFeed: [Types of UI Tests and What They Verify]() Original publisher: [Read original article]() Author: Alex Zhukovich Published: 2023-11-17T00:11:25Z Content type: tutorial Language: en Sources: [Alex Zhuk - Android development and testing]() Topics: [ui](), [Testing](), [Accessibility](), [Development]() Tags: [accessibility-testing](), [android-testing](), [how-to](), [software-development](), [testing](), [tests](), [ui](), [ui-testing]() ### AI overview This tutorial explains several types of UI testing: end-to-end tests, UI tests with fake data, screenshot or pixel-perfection tests, and accessibility tests. It describes what each type can verify and introduces ways to begin UI testing in a project. ### Source excerpt The article explores different types of UI testing, such as end-to-end testing, UI testing with fake data, pixel perfection testing, and accessibility testing. The article also includes information on how to get started with UI testing in any project. ## Accessibility insights. How to make the most of Android's accessibility features. DevFeed: [Accessibility insights. How to make the most of Android's accessibility features.]() Original publisher: [Read original article]() Author: Pradeep Kumar HK. Published: 2022-10-14T15:28:31Z Content type: tutorial Language: en Sources: [ymedialabs-innovation - Medium]() Topics: [Accessibility](), [Android](), [Mobile](), [Usability](), [Testing](), [User interface design]() Tags: [a11y](), [accessibility](), [accessibility-testing](), [android](), [everyonematters](), [gestures](), [how-to](), [mobile](), [testing](), [usability]() ### AI overview This tutorial explains how to improve Android app accessibility for people with visual, hearing, cognitive, motor, and situational disabilities. It introduces tools such as TalkBack, Magnification, and Switch Access, and covers identifying accessibility issues, preventing regressions, using Android attributes, and applying accessible design guidelines. ### Source excerpt Note : Accessibility (often abbreviated to A11y -- as in, "a", then 11 characters, and then "y") Improving your product's a11y can enhance the usability for all users, including those with low vision, blindness, hearing impairments, cognitive impairments, motor impairments or situational disabilities (such as a broken arm). You may have experienced difficulties using your phone while wearing gloves when it's cold outside. Maybe you've had a hard time distinguishing items on the screen when it's bright outside. Most people will have at least a short term disability at some time that makes it difficult to use their mobile device. This includes someone who was born blind, or lost fine motor skills in an accident. With so much of the population experiencing decreased vision, hearing, mobility, and cognitive function, you should do your best to give everyone the best experience in your apps. In this write up, we are going to discuss ways we can make Android app more accessible, and by the end of this you will know the most basic ways you can improve your app for a11y. You will learn: Available a11y tools people are using. How to discover existing a11y issues, and prevent a11y regression. Android attributes you can use to make your app more accessible. Design guidelines to allow your user to use your app with ease. A11y tools : Assistive technology helps increase, maintain, or improve the functional capabilities of individuals with disabilities, through devices like screen readers, magnification tools, and hearing aids. There are many tools that people use to interact with their Android devices. This includes TalkBack, Magnification, and Switch Access, to name a few. TalkBack allows you to explore the view using gestures, while also audibly describing what's on the screen.Magnification allows you to zoom in on parts of the screen. Both TalkBack and Magnification are helpful for people with limited visibility.People with limited mobility can use Switch Access to allow them ## Setting up An Accessibility Dashboard from Scratch with Pa11y on DigitalOcean DevFeed: [Setting up An Accessibility Dashboard from Scratch with Pa11y on DigitalOcean]() Original publisher: [Read original article]() Published: 2016-05-04T00:00:00Z Content type: tutorial Language: en Sources: [Una Kravets]() Topics: [Accessibility](), [dashboards](), [Testing](), [Digital Ocean](), [MEAN](), [Angular](), [MongoDB](), [Express]() Tags: [accessibility](), [accessibility-testing](), [angular](), [digitalocean](), [github](), [mongodb](), [open-source](), [ssh](), [terminal](), [testing](), [web](), [website]() ### AI overview A tutorial on setting up a self-hosted accessibility dashboard with Pa11y on DigitalOcean. It covers the dashboard's accessibility-testing features and begins deployment of a MEAN-stack server, including droplet creation and SSH access. ### Source excerpt This post will walk you through setting up an accessibility testing dashboard from A to Z. Let's make the Internet more better together.