# Web Content Accessibility Guidelines Published articles for Web Content Accessibility Guidelines. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## EN 301 549 v4.1.1 is final! What changed, what it means, and what you should do. DevFeed: [EN 301 549 v4.1.1 is final! What changed, what it means, and what you should do.]() Original publisher: [Read original article]() Author: Matthew Luken Published: 2026-09-08T12:28:32Z Content type: article Language: en Sources: [Deque]() Topics: [Accessibility]() Tags: [accessibility](), [accessibility-compliance](), [compliance](), [eaa](), [en-301-549](), [europe](), [european-accessibility-act](), [hardware](), [post](), [products](), [real-time](), [testing](), [update](), [web](), [web-content-accessibility-guidelines]() ### AI overview EN 301 549 v4.1.1 was officially published on September 2, 2026, but it still needs citation in the Official Journal of the European Union and reference in national laws before its legal effect is fully established. The article explains why organizations should begin preparing now, highlighting revised real-time text requirements, six new WCAG 2.2 Level A/AA success criteria, updated User Preferences requirements, and changes affecting real-time communication. ### Source excerpt On September 2, 2026, EN 301 549 v4.1.1 was officially published. This represents a major update to Europe's accessibility standard for ICT products and services, and it's a big milestone. But in practice, it's only the first step along a three-point timeline. The post EN 301 549 v4.1.1 is final! What changed, what it means, and what you should do. appeared first on Deque. ## The anatomy of accessible forms: Required form fields DevFeed: [The anatomy of accessible forms: Required form fields]() Original publisher: [Read original article]() Author: Aparna Pasi Published: 2026-08-06T15:47:31Z Content type: article Language: en Sources: [Deque]() Topics: [Accessibility](), [Forms](), [Web Content Accessibility Guidelines](), [Usability](), [Web](), [User interface design]() Tags: [a11y-for-developers](), [accessibility](), [accessibility-best-practices](), [accessible-forms](), [accessible-required-form-field](), [eaa](), [errors](), [european-accessibility-act](), [standards](), [usability](), [web](), [web-content-accessibility-guidelines]() ### AI overview This article explains why accessible forms matter for inclusive digital experiences, usability, and compliance with the European Accessibility Act, the Americans with Disabilities Act, and WCAG. It uses a rental-car booking example to show how unclear required-field indicators and vague error messages can make forms difficult to complete, then introduces methods for indicating required fields, including placing the word "required" in the visible label. ### Source excerpt Creating accessible forms ensures your forms are accessible to all users while meeting standards like ADA, WCAG, and EAA compliance. The post The anatomy of accessible forms: Required form fields appeared first on Deque. ## For your business to thrive in the agentic AI era, treat accessibility as foundational to your AI strategy DevFeed: [For your business to thrive in the agentic AI era, treat accessibility as foundational to your AI strategy]() Original publisher: [Read original article]() Author: Preety Kumar Published: 2026-07-29T10:51:43Z Content type: article Language: en Sources: [Deque]() Topics: [Accessibility](), [AI Strategy](), [Artificial Intelligence](), [agentic browsing](), [AI Bots](), [aria](), [HTML](), [Web]() Tags: [accessibility](), [accessibility-best-practices](), [agentic-ai](), [agentic-browsing](), [ai](), [ai-bots](), [ai-strategy](), [article](), [digital-accessibility](), [html](), [web](), [web-accessibility](), [web-content-accessibility-guidelines]() ### AI overview The article argues that digital accessibility should be foundational to AI strategy because AI agents increasingly browse, click, complete forms, and interpret web pages through structures also used by assistive technologies. It highlights semantic HTML, ARIA, WCAG conformance, and a sound accessibility tree as important for both human access and agentic navigation, while warning that accessibility failures remain widespread. ### Source excerpt You need to build accessibility into how AI writes code from the first prompt, not fix it after the fact. And because the disability community has been perfecting human-computer interaction for different input and output modalities for decades, their expertise isn't just morally important; it's technically essential for building robust, reliable AI that actually works. The post For your business to thrive in the agentic AI era, treat accessibility as foundational to your AI strategy appeared first on Deque. ## More Accessible Focus Indicators with Compose DevFeed: [More Accessible Focus Indicators with Compose]() Original publisher: [Read original article]() Author: Eevis Panula Published: 2026-04-30T07:11:56.799000Z Content type: tutorial Language: en Sources: [Eevis Blog]() Topics: [Jetpack Compose](), [Accessibility](), [Android](), [Web Content Accessibility Guidelines](), [keyboard]() Tags: [accessibility](), [accessible](), [android](), [compose](), [focus](), [jetpack-compose](), [keyboard](), [web-content-accessibility-guidelines]() ### AI overview A tutorial on creating more visible keyboard focus indicators in Jetpack Compose. It explains relevant WCAG Focus Appearance requirements, notes that Android's default ripple may be insufficiently visible, and introduces the Indication API for drawing custom indicators such as an underline on focused interactive components. ### Source excerpt Last summer, I wrote a blog post about focus management with Compose. Ever since, I've had drafts of this post, but I didn't get to finalize it until now. The blog post is available in: It's All About (Accessibility) Focus And Compose. So, in this blog post, we're talking about focus indicators and how to make them more accessible with Compose. But let's first talk about focus indicators in general. Focus Indicators Focus indicators are, as the name suggests, indicators that show where keyboard focus currently is in the UI. They need to be visible so that keyboard and keyboard-emulating device users can navigate around the app effortlessly. An important thing to note is that the focus indicator I'm talking about here is not for the screen reader (e.g., TalkBack) focus. That is handled on the system level. Web Content Accessibility Guidelines (the standard behind accessibility legislation and used with apps as well, despite the name) has some requirements for accessible focus indicators. Per SC 2.4.13 Focus Appearance, the focus indicator needs to be either User agent's (Android system) default styles At least 2 pixels thick and has a contrast ratio of at least 3:1 between the same pixels of focused and unfocused states. Android's default focus indicator is the ripple, which isn't very visible. Technically, it would pass, but if you want to make the application accessible, you'll need to improve the visibility of the focus indicator. Let's next discuss one way to build more visible (and thus, more accessible) focus indicators with Compose. Building More Accessible Focus Indicators with Compose There are several ways of creating the focus indicators. You can, for example, add a border based on the focused state, as Appt.org suggests in their code snippets: Accessibility focus indicator in Jetpack Compose, but if you want anything more complex, you'll want to turn to Indication API. Indication API with a DrawModifierNode can be used to draw complex focus indicators. In ## Why Is WCAG Level AA the Standard for Digital Accessibility? DevFeed: [Why Is WCAG Level AA the Standard for Digital Accessibility?]() Original publisher: [Read original article]() Author: Mark Published: 2026-03-06T16:56:18Z Content type: article Language: en Sources: [Blog-Main]() Topics: [Accessibility](), [Web Content Accessibility Guidelines](), [digital accessibility](), [Web Accessibility (a11y)](), [Usability]() Tags: [accessibility](), [accessibility-guidelines](), [accessibility-requirements](), [color](), [compliance](), [digital-accessibility](), [keyboard](), [readability](), [usability](), [wcag](), [web-content-accessibility-guidelines]() ### AI overview This article explains why WCAG Level AA is commonly used as the goal for digital accessibility. It contrasts Levels A, AA, and AAA, describing Level A as a baseline and highlighting Level AA requirements such as color contrast and visible focus. ### Source excerpt When you're building an accessibility initiative, it's a good idea to establish your goals up front -- and most accessibility experts will tell you that means seeking Level AA conformance with the Web Content Accessibility Guidelines (WCAG). ## Web Accessibility Is Less Rigid Than You Think DevFeed: [Web Accessibility Is Less Rigid Than You Think]() Original publisher: [Read original article]() Author: Vince Published: 2026-02-19T18:30:00Z Content type: article Language: en Sources: [Blog-Main]() Topics: [Web Accessibility (a11y)](), [Web Content Accessibility Guidelines](), [Web]() Tags: [accessibility](), [accessibility-guidelines](), [defining-terms](), [developer](), [wcag](), [web-accessibility](), [web-content-accessibility-guidelines]() ### AI overview This article explains that WCAG 2.2 is an extensive but flexible framework for digital accessibility. It focuses on removing barriers and achieving accessible outcomes rather than prescribing one rigid implementation, with examples involving alt text, keyboard-friendly navigation, and color contrast. ### Source excerpt The Web Content Accessibility Guidelines (WCAG) contain 86 success criteria, as of version 2.2. That's a lot of requirements -- and if you're a developer, web designer, or content creator, digital accessibility probably sounds like a lot of extra work. ## Beyond Font Scaling: Large Content Viewer with Compose DevFeed: [Beyond Font Scaling: Large Content Viewer with Compose]() Original publisher: [Read original article]() Author: Eevis Panula Published: 2026-02-28T04:24:34.139000Z Content type: tutorial Language: en Sources: [Eevis Blog]() Topics: [Compose](), [Accessibility](), [iOS](), [Mobile](), [Web Content Accessibility Guidelines]() Tags: [accessibility](), [accessibility-guidelines](), [bottom-navigation](), [compose](), [ios](), [mobile](), [wcag](), [web-content-accessibility-guidelines]() ### AI overview This tutorial explains how to build a Large Content Viewer-like item previewer with Compose for bottom navigation items whose text cannot be adequately enlarged through font scaling. It describes the iOS accessibility pattern and discusses WCAG text-resizing considerations and the limitation that the proposed interaction relies on long press. ### Source excerpt If you've worked with accessibility issues and have a bottom bar with multiple items, you've probably come across a problem with larger font sizes, where it's impossible to scale the bottom navigation bar texts properly with larger font sizes. You might have wondered whether there are any alternative ways to support larger font sizes beyond just, well, font scaling. That's what happened to me. There was a bottom bar with five items with long texts. The developer who implemented the bottom bar had restricted font scaling because larger font sizes made the bottom bar's items essentially unreadable. I started investigating options and came across one solution: a large content viewer from iOS. As Compose doesn't support this out of the box, I had to build it. This blog post explains what a Large Content Viewer is and how to build similar functionality with Compose. I call it the item previewer in this blog post. But before diving into that, let's discuss the large content viewer on iOS. Large Content Viewer on iOS Large content viewer is an accessibility tool for iOS that helps, for example, low-vision users display non-scaling elements, such as bottom-bar items, as previews with a larger font size. It's enabled only when the Large text (an accessibility setting) is enabled. Here's an example of what it looks like on the Files app: Accessibility Considerations There are accessibility considerations for this solution. First of all, yes, it can be WCAG-compliant. WCAG, which stands for Web Content Accessibility Guidelines, is the standard used, for example, in legislation. It applies to mobile apps as well. It states in success criteria 1.1.4 Resize text that Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality. If the mechanism is not the default font size setting, then another supported mechanism would suffice to pass the success criteria. With this solution, users can resize ## How Interrupting Your Users Can Create Accessibility Concerns DevFeed: [How Interrupting Your Users Can Create Accessibility Concerns]() Original publisher: [Read original article]() Author: Chris Published: 2025-12-22T12:30:00Z Content type: article Language: en Sources: [Blog-Main]() Topics: [Web Accessibility (a11y)](), [Web Content Accessibility Guidelines](), [digital accessibility](), [Website](), [Users](), [notifications]() Tags: [accessibility](), [accessibility-guidelines](), [accessibility-ux](), [automatic](), [digital-accessibility](), [display](), [people-with-disabilities](), [send](), [stop](), [time](), [timeout](), [web-accessibility](), [web-content-accessibility-guidelines](), [web-developers](), [websites]() ### AI overview The article explains how dynamic website behavior, including unexpected notifications, automatic refreshes, and other interruptions, can create accessibility barriers for screen reader users and people with attention disorders. It discusses WCAG Success Criterion 2.2.4, which says interruptions can be postponed or suppressed except in emergencies, while noting that this Level AAA criterion is not generally required for conformance goals. ### Source excerpt If you're building a dynamic website, there are plenty of valid reasons to interrupt your users. You might need to tell someone if their session is about to timeout, for example, or you might want your content to refresh periodically in order to show more up-to-date information. ## Web Accessibility Myths: Can a Font Choice Violate the ADA? DevFeed: [Web Accessibility Myths: Can a Font Choice Violate the ADA?]() Original publisher: [Read original article]() Author: Alexa Published: 2025-12-21T07:45:00Z Content type: article Language: en Sources: [Blog-Main]() Topics: [Web Content Accessibility Guidelines](), [Web Accessibility (a11y)](), [Font](), [Accessibility](), [web design]() Tags: [accessibility](), [accessibility-guidelines](), [accessibility-requirements](), [accessibility-ux](), [accessible](), [color](), [fonts](), [legibility](), [sans-serif-fonts](), [serif-fonts](), [wcag](), [web-accessibility](), [web-content-accessibility-guidelines]() ### AI overview This article explains that WCAG and the ADA do not require a specific font family. It distinguishes typeface choice from accessibility requirements involving text resizing, color contrast, and avoiding images of text. ### Source excerpt On December 9th, 2025, U.S. Secretary of State Marc Rubio ordered diplomats to stop using Calibri -- a sans serif font -- and to switch back to Times New Roman. Normally, a change in typeface wouldn't make headlines, but Rubio's department took the unusual step of decrying Calibri as both unprofessional and wasteful. ## Can User-Generated Content Lead to an ADA Demand Letter? DevFeed: [Can User-Generated Content Lead to an ADA Demand Letter?]() Original publisher: [Read original article]() Author: Marissa Published: 2025-11-24T21:00:00Z Content type: article Language: en Sources: [Blog-Main]() Topics: [Accessibility](), [digital accessibility](), [Web Content Accessibility Guidelines](), [Website]() Tags: [accessibility](), [accessibility-guidelines](), [accessibility-requirements](), [lawsuit](), [lawsuits-settlement](), [legal](), [web-accessibility](), [web-content-accessibility-guidelines](), [websites]() ### AI overview The article examines whether user-generated content on websites can create exposure to ADA or other web accessibility claims. It explains that users may create content that fails WCAG, but suggests a demand letter is unlikely when the rest of the site is accessible; providing tools and a framework that support accessible user content may reduce vulnerability. ### Source excerpt There's a decent chance that your site has some amount of user-generated content: forum posts, product reviews, and even user accounts can qualify. If you've got a fairly complex website, you might provide users with a considerable degree of control over the content they create -- they might be able to change fonts, for example, or embed links. ## How we are using AI in Mercado Libre's accessibility team DevFeed: [How we are using AI in Mercado Libre's accessibility team]() Original publisher: [Read original article]() Author: Martín Di Luzio Published: 2025-10-08T12:58:25Z Content type: article Language: en Sources: [Mercado Libre Tech]() Topics: [Accessibility](), [Artificial Intelligence](), [Large Language Model](), [Retrieval Augmented Generation (RAG)](), [Automation](), [Design system]() Tags: [accessibility](), [ai](), [automation](), [developers](), [large-language-model](), [retrieval-augmented-generation-rag](), [web-content-accessibility-guidelines]() ### AI overview Mercado Libre's accessibility team is exploring AI to support designers and developers, automate tasks, provide immediate answers, and encourage collective learning. Its A11Y assistant uses an LLM with Retrieval-Augmented Generation to answer questions using internal documentation, training materials, historical queries, accessibility tickets, and design-system resources. AI also adds contextual explanations and recommendations to accessibility audit tickets. ### Source excerpt AI isn't here to replace accessibility work -- it's here to make it stronger. Today, our accessibility team faces a challenge: supporting hundreds of designers and developers with questions, reviews, and continuous improvements. To scale this impact, we're exploring how artificial intelligence (AI) can help us automate tasks, provide immediate answers, and foster collective learning. That's why we've launched several initiatives to speed up work, increase independence, and strengthen execution capacity. Note: In many of these initiatives, we rely on automatization tools available in our internal development ecosystem, Fury. The A11Y assistant for everyday workImage 1: Automation flow that integrates different nodes, from the user's question to obtaining relevant information, processing it, and providing an answer.How does it work? This assistant: Activates when mentioned in the support channel. Processes both messages and screen images. Consults internal documentation, training materials, historical queries, previously reported accessibility tickets, and our design system. Uses a large language model (LLM) with Retrieval-Augmented Generation (RAG) to deliver reliable answers. The result: contextualized responses grounded in internal resources and standards. From the query initiation to gathering additional context, and finally to delivering a response backed by verified information, the entire pipeline is crucial. This approach helps avoid "hallucinations" (invented or incorrect answers) and ensures the A11Y assistant stays focused on trusted resources. Thus, it provides solutions and resources that are not only accurate but also directly applicable and aligned with Mercado Libre's internal accessibility standards and tools. Understanding problems better to deliver better solutions One of our biggest learnings is that teams need information that's clear and easy to understand -- not just technical reports. In manual accessibility audits, we provide technical details s ## What Is ISO/IEC 40500, And Why Is It Important for Web Accessibility? DevFeed: [What Is ISO/IEC 40500, And Why Is It Important for Web Accessibility?]() Original publisher: [Read original article]() Author: Alexa Published: 2025-09-15T15:45:00Z Content type: article Language: en Sources: [Blog-Main]() Topics: [Web Accessibility (a11y)](), [Web Content Accessibility Guidelines](), [Accessibility](), [digital accessibility](), [W3C]() Tags: [accessibility](), [accessibility-compliance](), [accessibility-guidelines](), [accessibility-requirements](), [standard](), [w3c](), [wcag](), [web-accessibility](), [web-content-accessibility-guidelines]() ### AI overview This article explains that ISO/IEC 40500 is identical to WCAG 2.0 and discusses why adopting WCAG as an ISO/IEC standard can simplify accessibility compliance. It also describes how ISO recognition may increase awareness of digital accessibility among governments, businesses, and lawmakers. ### Source excerpt ISO/IEC 40500 is the standard for digital accessibility under the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC). It's identical to the Web Content Accessibility Guidelines (WCAG) version 2.0. ## Basic Web Accessibility Tests: Turn Your Monitor to Grayscale DevFeed: [Basic Web Accessibility Tests: Turn Your Monitor to Grayscale]() Original publisher: [Read original article]() Author: Vince Published: 2025-09-05T16:15:00Z Content type: tutorial Language: en Sources: [Blog-Main]() Topics: [Accessibility](), [Web Accessibility (a11y)](), [Web Content Accessibility Guidelines](), [color](), [digital accessibility](), [Testing]() Tags: [accessibility](), [accessibility-guidelines](), [accessibility-ux](), [color](), [digital-accessibility](), [people-with-disabilities](), [testing](), [tests](), [wcag](), [web](), [web-accessibility](), [web-content-accessibility-guidelines]() ### AI overview This article explains how viewing a website in grayscale can help reveal accessibility problems caused by using color as the only way to convey information. It places the exercise within a broader strategy combining automated and manual testing for WCAG Level AA conformance and gives examples involving links, form fields, charts, and status indicators. ### Source excerpt To truly test content for accessibility, you need an extensive strategy that combines automated testing with manual tests. You should have a goal in mind -- for most websites, that's Level AA conformance with the Web Content Accessibility Guidelines (WCAG). ## Fashion Nova Settles Web Accessibility Lawsuit for $5.15 Million DevFeed: [Fashion Nova Settles Web Accessibility Lawsuit for $5.15 Million]() Original publisher: [Read original article]() Author: CJ Published: 2025-08-13T12:45:00Z Content type: news Language: en Sources: [Blog-Main]() Topics: [Accessibility](), [digital accessibility](), [Website](), [Web Content Accessibility Guidelines](), [alt text](), [screen]() Tags: [accessibility](), [accessibility-guidelines](), [alt-text](), [civil-rights](), [human-interest](), [industry-news](), [law](), [lawsuits-settlement](), [web-accessibility](), [web-content-accessibility-guidelines](), [website]() ### AI overview Fashion Nova agreed to pay $5.15 million in a class-action settlement involving alleged web accessibility barriers. Eligible legally blind individuals who attempted to access the retailer's website during the applicable period may receive up to $4,000 per household, and the company agreed to improve the site's accessibility while denying wrongdoing. ### Source excerpt Fashion Nova LLC will send checks for up to $4,000 to individuals with vision disabilities who were unable to use the retailer's website using screen reading software (screen readers). ## Accessibility by Design: Preparing K-12 Schools for What's Next DevFeed: [Accessibility by Design: Preparing K-12 Schools for What's Next]() Original publisher: [Read original article]() Author: Cynthia Curry Published: 2025-07-30T17:51:46Z Content type: article Language: en Sources: [WebAIM Blog]() Topics: [Accessibility](), [digital accessibility](), [Web Content Accessibility Guidelines](), [Web](), [Website]() Tags: [accessibility](), [context](), [digital-accessibility](), [digital-platforms](), [implementation](), [organization](), [standards](), [uncategorized](), [web](), [web-content-accessibility-guidelines]() ### AI overview This article explains why delivering digital accessibility in K-12 education requires strategic planning and cross-organizational commitment. It connects existing obligations to provide accessible instructional materials with the shift from print to digital learning, arguing that implementation must be adapted to each organization's priorities, practices, policies, and context. ### Source excerpt Delivering web and digital accessibility in any environment requires strategic planning and cross-organizational commitment. While the goal (ensuring that websites and digital platforms do not present barriers to individuals with disabilities) and the standards (the Web Content Accessibility Guidelines) remain constant, implementation must be tailored to each organization's needs and context. For K-12 educational agencies, [...] ## Cognitive Load and Web Accessibility: Quick Tips for Clearer Content DevFeed: [Cognitive Load and Web Accessibility: Quick Tips for Clearer Content]() Original publisher: [Read original article]() Author: Marissa Published: 2025-07-24T19:45:00Z Content type: tutorial Language: en Sources: [Blog-Main]() Topics: [Accessibility](), [Web Accessibility (a11y)](), [Web Content Accessibility Guidelines](), [Website](), [Users](), [User interface design]() Tags: [accessibility](), [accessibility-guidelines](), [accessibility-ux](), [autism](), [charts](), [cognitive-load](), [form](), [layout](), [navigation](), [people-with-disabilities](), [quick-tips](), [tips](), [wcag](), [web-accessibility](), [web-content-accessibility-guidelines]() ### AI overview This article explains how cognitive load affects web accessibility, particularly for people with cognitive and learning disabilities. It recommends simplifying complex content, using consistent layouts and navigation, and following the Understandable principle of WCAG. ### Source excerpt The Web Content Accessibility Guidelines (WCAG) is designed to improve experiences for all users with disabilities. That includes people who have cognitive disabilities and learning disabilities -- but those users are often left out of the discussion. ## Why WCAG Conformance Doesn't Mean "Perfectly Accessible" DevFeed: [Why WCAG Conformance Doesn't Mean "Perfectly Accessible"]() Original publisher: [Read original article]() Author: Jordan Published: 2025-07-23T12:45:00Z Content type: article Language: en Sources: [Blog-Main]() Topics: [Web Content Accessibility Guidelines](), [Accessibility](), [Web Accessibility (a11y)](), [Web](), [alt text](), [Users]() Tags: [accessibility](), [accessibility-guidelines](), [accessibility-ux](), [accessible](), [alt-text](), [cause](), [content](), [lawsuit](), [markup](), [speech](), [tables](), [wcag](), [web-accessibility](), [web-content-accessibility-guidelines]() ### AI overview The article explains that WCAG conformance, including Level AA, is a valuable goal but does not guarantee a perfectly accessible experience. Pass-or-fail criteria can be met while websites still create barriers through poor alt text, difficult captions, incomprehensible table presentation, or layout shifts caused by slow page speeds. ### Source excerpt The Web Content Accessibility Guidelines (WCAG) are an excellent set of standards, and WCAG conformance is achievable -- regardless of the size of your website, the complexity of its features, or any other factors. ## Missouri's Web Accessibility Standard: What Businesses Should Know DevFeed: [Missouri's Web Accessibility Standard: What Businesses Should Know]() Original publisher: [Read original article]() Author: Gary Published: 2025-07-15T10:45:00Z Content type: article Language: en Sources: [Blog-Main]() Topics: [Accessibility](), [Web Accessibility (a11y)](), [Web Content Accessibility Guidelines](), [Requirements](), [web applications]() Tags: [accessibility](), [accessibility-guidelines](), [accessibility-requirements](), [compliance](), [digital-accessibility](), [wcag](), [web-accessibility](), [web-content-accessibility-guidelines](), [websites]() ### AI overview This article explains Missouri's Web Accessibility Standard, including its basis in Section 508 and WCAG 2.1. It describes how the standard applies to state agencies and may affect contractors, while noting that Title III of the ADA applies to places of public accommodation, including websites. ### Source excerpt Read the official website of the state of Missouri, and you'll find a fairly standard web accessibility policy -- with one curveball: ## Accessibility Tests in Compose - Name, Role, Value DevFeed: [Accessibility Tests in Compose - Name, Role, Value]() Original publisher: [Read original article]() Author: Eevis Panula Published: 2024-06-19T03:57:03.684000Z Content type: tutorial Language: en Sources: [Eevis Blog]() Topics: [Jetpack Compose](), [Accessibility](), [Testing](), [Web Content Accessibility Guidelines](), [Mobile]() Tags: [accessibility](), [accessibility-guidelines](), [compose](), [mobile](), [tests](), [wcag](), [web-content-accessibility-guidelines]() ### AI overview A tutorial on testing accessibility in Jetpack Compose. It explains how to verify the accessible name, role, and value of custom components, including a switch, radio button group, and clickable row, in relation to the WCAG "Name, Role, Value" criterion. ### Source excerpt When writing tests for your app, you should also consider testing for accessibility-related things. And I get it; it can be challenging to know where to start. So, I decided to write this blog post about how to test some accessibility aspects. In this post, we will add some accessibility-related tests for three custom components constructed with the help of clickable, selectable, and toggleable modifiers. These components were built in a blog post I wrote: Improving Android Accessibility with Modifiers in Jetpack Compose. What Are We Testing? The tests we're writing verify that the components have names, roles, and values. But where does this group come from? The background is that Web Content Accessibility Guidelines (WCAG) has a success criterion, "Name, Role, Value", which ensures that every element has a programmatically determinable name and role. Also, states, properties, and values that users can change are programmatically changeable. And now, if you wonder why I'm mentioning something named "Web," the WCAG is also used to determine the minimum level of accessibility for mobile apps as well, despite the name. Name, in this case, means the accessible name--so, the textual representation of the element. It can be, for example, a button's text, an icon button's content description, a label for a switch, or similar. It's what anyone using a screen reader hears. Voice access users use it to activate interactive elements. Role, on the other hand, is the role of the element. It can be, for example, a button - which tells the user that, hey, this is a button, and it should behave as a button. A role is a promise of how things should work, so if you add a role, be sure to add the correct interactions as well. However, roles are used less on Android than on the web. Value can refer to an element's state, property, or value. The exact thing is different per element. For example, with a checkbox, the value tells if it is checked, or with an accordion, it's the state that ## Celebrating Global Accessibility Awareness Day DevFeed: [Celebrating Global Accessibility Awareness Day]() Original publisher: [Read original article]() Author: schalk-neethling Published: 2023-05-18T00:00:00Z Content type: article Language: en Sources: [MDN Blog]() Topics: [Accessibility](), [Web Content Accessibility Guidelines](), [Web](), [Documentation]() Tags: [accessibility](), [aria](), [awareness](), [css](), [docs](), [global](), [html](), [tools](), [web](), [web-content-accessibility-guidelines]() ### AI overview This MDN article celebrates Global Accessibility Awareness Day by sharing guidance and resources for making websites more accessible. It emphasizes using the Web Content Accessibility Guidelines, consulting accessibility guidance in MDN Web Docs, using HTML semantics appropriately, applying ARIA carefully, and considering keyboard navigation, screen readers, and color contrast. ### Source excerpt In celebration of Global Accessibility Awareness Day in 2023, we share some tools and guidelines to help you make the web more accessible. ## The future of design systems is accessible DevFeed: [The future of design systems is accessible]() Original publisher: [Read original article]() Author: Carly Ayres Published: 2023-05-09T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [digital accessibility](), [Web Content Accessibility Guidelines](), [Accessibility]() Tags: [accessibility](), [accessibility-best-practices](), [design](), [design-systems](), [digital-accessibility](), [series](), [web-content-accessibility-guidelines]() ### AI overview The article discusses how design systems can make accessibility a core priority. It describes their role in applying accessibility guidance consistently, documenting best practices, testing components, and propagating improvements across product ecosystems. ### Source excerpt In the third part of our series, we talk to design system and accessibility experts about making inclusive systems a top priority. Previously, we covered complexity and automation. ## What is WAI? The Web Accessibility Initiative DevFeed: [What is WAI? The Web Accessibility Initiative]() Original publisher: [Read original article]() Author: Ilknur Eren Published: 2022-07-18T00:00:00Z Content type: article Language: en Sources: [The A11Y Project]() Topics: [Web Accessibility (a11y)](), [Web](), [Web Content Accessibility Guidelines](), [Accessibility](), [aria](), [FIRST](), [Internet](), [browsers](), [User interface design](), [image slider]() Tags: [accessibility](), [applications](), [aria](), [browsers](), [community](), [content](), [development](), [education](), [evaluation](), [internet](), [standards](), [support](), [tools](), [web](), [web-accessibility](), [web-content-accessibility-guidelines]() ### AI overview This article explains the Web Accessibility Initiative (WAI), a W3C initiative launched in 1997 to improve Web accessibility for people with disabilities. It describes W3C's role in developing Web standards, WAI's accessibility guidelines and resources, and its contributions to WCAG and WAI-ARIA. ### 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 ## Fixing contrast issues, on your own site and elsewhere DevFeed: [Fixing contrast issues, on your own site and elsewhere]() Original publisher: [Read original article]() Author: Kilian Valkhof Published: 2021-06-07T00:00:00Z Content type: article Language: en Sources: [The A11Y Project]() Topics: [Accessibility](), [Web Content Accessibility Guidelines](), [Web](), [User interface design]() Tags: [accessibility](), [article](), [design](), [developer](), [tools](), [web](), [web-content-accessibility-guidelines]() ### AI overview This article explains how insufficient text contrast creates widespread accessibility problems on websites. It introduces contrast ratios, describes WCAG thresholds for regular and large text, illustrates how visually similar colors can produce different audit results, and recommends using design plugins and accessibility checkers to identify contrast issues. ### 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 ## Alternate text and automation DevFeed: [Alternate text and automation]() Original publisher: [Read original article]() Author: Eric Bailey Published: 2021-03-23T00:00:00Z Content type: article Language: en Sources: [The A11Y Project]() Topics: [alt text](), [Accessibility](), [Web Content Accessibility Guidelines](), [Content Management System](), [Machine learning](), [Automation](), [WordPress]() Tags: [accessibility](), [alt-text](), [automation](), [code](), [computer-vision](), [machine-learning](), [web-content-accessibility-guidelines](), [wordpress]() ### AI overview The article explains that effective alt text helps people using assistive technology understand images and is required as part of WCAG. Although machine learning and computer vision can automate image descriptions in content management systems, automated descriptions may be inaccurate or incomplete, so human review remains necessary. ### Source excerpt Alternate (alt) text help people who use assistive technology understand images, and are a core part of the Web Content Accessibility Guidelines (WCAG). They require a human's input to be effective. To create alternate text, you add an alt attribute to an image that clearly and concisely describes what it is depicting: A bowl of tomato soup and a grilled cheese sandwich. Assistive technology such as a screen reader will read the text provided inside the alt attribute's opening and closing quotes. It may sound something like: Image. A bowl of tomato soup and a grilled cheese sandwich. This allows a person to know an image is present, and what the image's content contains. With this context, someone using assistive technology can understand the image's purpose the same way someone who is not using assistive technology would. It's up to the person writing the code to add an alt attribute. It's also up to them to look at the image they're using and write an accurate description. Many Content Management Systems (CMS) allow the people who use them to include alt text by writing it in a dedicated input field. WordPress' alt text input field for uploaded images. Automation Technologies such as machine learning and computer vision allow us to guess at what an image is based on its arrangements of pixels. For example, we might show a computer hundreds of thousands of photos of fire hydrants to train it to understand what configurations of pixels look "fire hydrant-ish." The idea is that you can take these technologies and apply them to a CMS or other publishing system. The publishing system would ideally then be able to automatically apply alternate text to any image uploaded by an author. The problem is that automated image description is not a perfect science. Many of these automated detection technologies are still new and unsophisticated. This means there's a good chance they haven't been taught what the image you [Next page]()