# a11y Published articles for a11y. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Testing A11y Using Cypress And wick-a11y Plugin DevFeed: [Testing A11y Using Cypress And wick-a11y Plugin]() Original publisher: [Read original article]() Author: Gleb Bahmutov Published: 2026-04-07T04:00:00Z Content type: tutorial Language: en Sources: [Gleb Bahmutov]() Topics: [Cypress](), [Accessibility](), [Testing](), [Web app](), [ci]() Tags: [a11y](), [accessibility](), [app](), [browser](), [ci](), [color](), [cypress](), [errors](), [html](), [install](), [plugin](), [products](), [reports](), [test](), [testing](), [tests](), [web-app]() ### AI overview A tutorial on adding accessibility testing to the Gametime web app with Cypress and the wick-a11y plugin. It covers plugin setup, checking for readable text, labeled inputs, landmarks, severity levels, and detailed HTML reports that can be saved as CI artifacts. ### Source excerpt I have a little web app called Gametime I use to keep track of players during youth socc ## What's new in Svelte: May 2023 DevFeed: [What's new in Svelte: May 2023]() Original publisher: [Read original article]() Author: Dani Sandoval Published: 2023-05-01T00:00:00Z Content type: article Language: en Sources: [Svelte blog]() Topics: [Svelte](), [changelog](), [Vite](), [ESLint](), [Hackathon]() Tags: [a11y](), [announcements](), [changelog](), [community](), [embedded](), [eslint](), [hackathon](), [svelte](), [vite]() ### AI overview A May 2023 Svelte newsletter covering new Svelte and SvelteKit features, compiler and language-tool updates, Vite integration changes, and a new official ESLint plugin. It also announces Svelte Ambassadors, previews SvelteHack results, and showcases projects built with Svelte and related tools. ### Source excerpt Before we dive into the updates, there's a few announcements worth mentioning at the top: New Svelte Ambassadors Regular features of this newsletter and all-around great content creators for Svelte JoyOfCode and HuntaByte have been appointed as Svelte Ambassadors. Ambassadors are people who are well known for their helpfulness and contributions and for upholding Svelte's reputation as a friendly, welcoming community, and we're deeply grateful for their involvement! SvelteHack winners will be announced May 6th In a just a few days, we'll find out who won SvelteHack - the Svelte Hackathon that took place between February 17th and April 17th. Tune in to Svelte Summit on May 6th to see if your favorite project was chosen 👀 Lots of submissions to the hackathon are featured in this month's showcase... but first, let's see what's new! What's new in Svelte style blocks now support CSS @container queries (3.58.0) bind:innerText is now available for contenteditable elements (3.58.0) A new accessability warning, a11y-interactive-supports-focus will now warn when interactive elements are not focusable (3.58.0) For all the changes to the Svelte compiler, including unreleased changes, check out the CHANGELOG. What's new in SvelteKit When hot module reloading (HMR) is enabled, the page will reload after an error is fixed (1.14.0, #9497) Two apps loaded into the same html page can now be loaded simultaneously in "embedded" mode (1.15.7, #9610) Vite's compilation will now log warnings for packages that use the svelte field to resolve Svelte files differently than standard Vite resolve (vite-plugin-svelte@2.1.0, kit@1.15.8) What's new in Language Tools Support for (#1958) and intellisense report for new bindings (#1957) (107.3.0) The new fix-all menu option for the "Quick fix..." makes it easy to "Add all missing imports" and other detected errors (107.3.0, #1939) We have a new and better official ESLint plugin! Previous support for Svelte in ESLint did not handle t ## MDC-Android Stable release 1.7.0 DevFeed: [MDC-Android Stable release 1.7.0]() Original publisher: [Read original article]() Published: 2022-10-20T10:00:00Z Content type: release Language: en Sources: [Material.io - Material Design]() Topics: [Material Design](), [Android]() Tags: [a11y](), [android](), [design](), [material-design](), [material-design-3](), [release](), [stable]() ### AI overview MDC-Android Stable release 1.7.0 includes Material Design 3 shape guidance and improved accessibility. ### Source excerpt with Material Design 3 shape guidance and improved a11y ## 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 ## How I deal with colorblindness as a digital product designer DevFeed: [How I deal with colorblindness as a digital product designer]() Original publisher: [Read original article]() Author: Federico Monaco Published: 2021-10-09T00:00:00Z Content type: article Language: en Sources: [The A11Y Project]() Topics: [App](), [Internet](), [Tool]() Tags: [a11y](), [article](), [design](), [digital-products](), [interfaces](), [products](), [user-research]() ### AI overview A colorblind digital product designer describes the barriers colorblind people can encounter when using websites and applications, and the challenges colorblind designers may face when creating digital interfaces. Drawing on personal experience and user research, the article advocates designing digital products that do not rely on color alone to convey information. ### 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 ## It's Not About Morals: Accessibility is for the Masses DevFeed: [It's Not About Morals: Accessibility is for the Masses]() Original publisher: [Read original article]() Published: 2016-06-01T00:00:00Z Content type: article Language: en Sources: [Una Kravets]() Topics: [Accessibility](), [Web](), [User interface design]() Tags: [a11y](), [accessibility](), [aria](), [language](), [screen](), [web]() ### AI overview The article argues that accessibility benefits the majority of users, not only people with disabilities. It discusses semantic markup and ARIA roles, screen readers, and clear language as practical ways to make web products easier for everyone to use. ### Source excerpt Accessibility is often solely discussed in terms of people with disabilities, but in truth, it's something that benefits the majority (if not all) of your users.