# Web Accessibility Published articles for Web Accessibility. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Meta Just Launched an AI That Uses Websites for You. That Could Be a Big Deal for Web Designers DevFeed: [Meta Just Launched an AI That Uses Websites for You. That Could Be a Big Deal for Web Designers]() Original publisher: [Read original article]() Author: Noah Davis Published: 2026-09-09T15:12:00Z Content type: article Language: en Sources: [Web Designer Depot]() Topics: [AI Agent](), [User interface design](), [Artificial Intelligence](), [Accessibility](), [computer-use](), [Document Object Model (DOM)](), [Claude]() Tags: [accessibility](), [agentic-ai](), [ai](), [ai-agent](), [ai-agents](), [ai-automation](), [ai-tech](), [artificial-intelligence](), [browser](), [browser-agents](), [cloud](), [design](), [design-trends](), [forms](), [future-of-the-web](), [future-of-web-design](), [human-computer-interaction](), [meta](), [meta-muse](), [muse](), [muse-ai](), [ui-design](), [user-experience](), [ux](), [ux-design](), [visual-hierarchy](), [web-accessibility](), [web-design](), [web-development](), [website-design]() ### AI overview The article examines Meta's Muse personal AI agent and argues that web designers may need to design websites for both human visitors and agents acting on users' behalf. It highlights semantic structure, accessibility, predictable controls, and trust as important considerations. ### Source excerpt Your website's next visitor might not be human. Meta's new Muse agent can navigate sites, fill out forms and take action for you--and it could force web designers to rethink exactly who they're designing for. ## Test your custom elements and trust the results with Axe-core's support for ElementInternals DevFeed: [Test your custom elements and trust the results with Axe-core's support for ElementInternals]() Original publisher: [Read original article]() Author: Wilco Fiers Published: 2026-08-27T13:21:18Z Content type: article Language: en Sources: [Deque]() Topics: [Accessibility](), [axe-core](), [interoperability](), [Front end](), [browser](), [Angular](), [React](), [Vue.js](), [aria]() Tags: [a11y-for-developers](), [accessibility](), [angular](), [aria](), [axe-core](), [browser](), [compliance](), [frontend](), [interoperability](), [react](), [testing](), [vue](), [web-accessibility]() ### AI overview The article explains how custom elements and ElementInternals can standardize components across React, Angular, and Vue while allowing components to declare accessibility semantics. It highlights axe-core support for ElementInternals, enabling teams to test accessibility consistently across framework implementations and support compliance at enterprise scale. ### Source excerpt If you're a large enterprise organization with accessibility issues resulting from interoperability challenges, moving to ElementInternals is a savvy move. You can standardize, and safely test. And, with Axe-core now supporting ElementInternals, you can test those components and trust the results. The post Test your custom elements and trust the results with Axe-core's support for ElementInternals appeared first on Deque. ## 6 Best WordPress Plugins for Improving Website Accessibility in 2026 DevFeed: [6 Best WordPress Plugins for Improving Website Accessibility in 2026]() Original publisher: [Read original article]() Author: Eric Karkovack Published: 2026-08-25T17:09:45Z Content type: article Language: en Sources: [Speckyboy Design Magazine]() Topics: [Accessibility](), [WordPress themes and plugins](), [WordPress](), [alt text](), [Artificial Intelligence]() Tags: [accessibility](), [ai](), [alt-text](), [best-practices](), [content](), [features](), [images](), [learn](), [media](), [post](), [tools](), [web-accessibility](), [wordpress](), [wordpress-plugins]() ### AI overview A guide to six WordPress plugins that can help identify and improve website accessibility issues, including missing attributes, skip links, labels, contrast, and image descriptions. The article notes that automated results require manual verification. ### Source excerpt We have a fantastic collection of WordPress plugins and tools to help you overcome the challenges that come along with website accessibility. The post 6 Best WordPress Plugins for Improving Website Accessibility in 2026 appeared first on Speckyboy Design Magazine. ## Deque and Microsoft: Two decades of shaping the future of accessibility DevFeed: [Deque and Microsoft: Two decades of shaping the future of accessibility]() Original publisher: [Read original article]() Author: Preety Kumar Published: 2026-08-25T12:33:31Z Content type: article Language: en Sources: [Deque]() Topics: [Accessibility](), [Microsoft](), [software-development](), [Artificial Intelligence](), [AI Development](), [Human-Computer Interaction and Visualization]() Tags: [accessibility](), [accessibility-tools](), [ai](), [axe-core](), [company-news-and-updates](), [development](), [digital-experiences](), [human-computer-interaction](), [microsoft](), [partnership](), [software-development](), [web-accessibility]() ### AI overview Deque and Microsoft's nearly two-decade accessibility partnership is presented as a collaboration focused on embedding accessibility throughout software development. The article discusses how AI-assisted development, regulation, and digital accessibility are converging, and argues that accessibility should be considered from the first prompt. It also highlights the disability community's expertise in human-computer interaction as technically important for building more robust and reliable AI systems. ### Source excerpt What started nearly two decades ago as conversations between two people passionate about improving accessibility across Microsoft's digital experiences has grown into a lasting partnership built on shared learning, mutual respect, and a common belief that accessibility should be built into every stage of software development. The post Deque and Microsoft: Two decades of shaping the future of accessibility 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. ## Why digital accessibility is a strategic priority for HSBC DevFeed: [Why digital accessibility is a strategic priority for HSBC]() Original publisher: [Read original article]() Author: Deque Systems Published: 2026-07-28T11:03:51Z Content type: article Language: en Sources: [Deque]() Topics: [digital accessibility](), [Accessibility]() Tags: [accessibility](), [accessibility-best-practices](), [banking](), [business](), [compliance](), [customer](), [customer-trust](), [design](), [digital-accessibility](), [digital-experiences](), [digital-products](), [financial-services](), [strategy](), [web-accessibility]() ### AI overview This article explains why digital accessibility is a strategic priority for HSBC and financial-services organizations. It connects accessible online banking with customer trust, stronger relationships, more inclusive digital experiences, and long-term business value. ### Source excerpt Mali Fernando, Group Head of Digital Experience and Accessibility at HSBC, discusses the role of digital accessibility in creating better banking experiences, strengthening customer relationships, and supporting long-term business success. The post Why digital accessibility is a strategic priority for HSBC appeared first on Deque. ## 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. ## 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 [...] ## 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. ## ARIA Isn't A Solution for Every Digital Accessibility Issue DevFeed: [ARIA Isn't A Solution for Every Digital Accessibility Issue]() Original publisher: [Read original article]() Author: Sarah Published: 2025-10-20T19:45:00Z Content type: tutorial Language: en Sources: [Blog-Main]() Topics: [Accessibility](), [aria](), [digital accessibility](), [Web Accessibility (a11y)](), [HTML](), [Web Development]() Tags: [accessibility](), [accessibility-guidelines](), [aria](), [developer](), [developers](), [digital-accessibility](), [html](), [semantic](), [web-accessibility]() ### AI overview The article explains that WAI-ARIA is not a universal solution for digital accessibility. It describes evidence associating ARIA usage with more detected accessibility errors while noting that correlation does not prove causation, and recommends using semantic HTML instead when appropriate. ### Source excerpt Many digital accessibility initiatives fail -- or, at least, they're less successful than they could be -- because they're assigned solely to a single developer or group of developers. Regardless of the size of your business or your industry, every person on your team needs to understand the importance of accessibility. That includes content creators, designers, and customer service representatives. ## 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). ## Minnesota Web Accessibility Laws: An Overview DevFeed: [Minnesota Web Accessibility Laws: An Overview]() Original publisher: [Read original article]() Author: Sarah Published: 2025-08-19T14:15:00Z Content type: article Language: en Sources: [Blog-Main]() Topics: [Web Accessibility (a11y)](), [digital accessibility](), [Accessibility](), [Web]() Tags: [accessibility](), [accessibility-requirements](), [compliance](), [digital-accessibility](), [government](), [lawsuits-settlement](), [legal](), [mobile](), [mobile-apps](), [web-accessibility](), [website]() ### AI overview This overview explains how Minnesota's Human Rights Act applies to digital accessibility, including websites, mobile apps, web-based documents, and other digital resources. It discusses disability protections and potential damages and penalties under amendments that took effect in 2024. ### Source excerpt In the United States, most digital accessibility lawsuits are filed in New York or California. That's because those states have laws that make the legal landscape more favorable for web accessibility plaintiffs. ## 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). ## Minnesota Lawsuit Reinforces ADA's Web Accessibility Requirements DevFeed: [Minnesota Lawsuit Reinforces ADA's Web Accessibility Requirements]() Original publisher: [Read original article]() Author: Sam Published: 2025-07-28T16:15:00Z Content type: opinion Language: en Sources: [Blog-Main]() Topics: [Web Accessibility (a11y)](), [Accessibility](), [Requirements]() Tags: [accessibility](), [accessibility-requirements](), [department-of-justice](), [government](), [lawsuit](), [web-accessibility]() ### AI overview The article examines Frost et al. v. Lion Brand Yarn Company, a Minnesota lawsuit in which the court rejected the argument that websites operating stores are not places of public accommodation under the ADA. It highlights alleged screen-reader incompatibilities and the potential damages available under the Minnesota Human Rights Act. ### Source excerpt Title III of the Americans with Disabilities Act (ADA) applies to websites, according to the Department of Justice (DOJ) and a number of major court decisions. But despite that well-established precedent, many businesses continue to argue that websites aren't places of public accommodation -- and therefore, they're not covered by the ADA. ## 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: ## Up and Coming ARIA DevFeed: [Up and Coming ARIA]() Original publisher: [Read original article]() Author: John Northup Published: 2025-05-30T18:19:41Z Content type: tutorial Language: en Sources: [WebAIM Blog]() Topics: [aria](), [Accessibility](), [Web Accessibility (a11y)](), [Web]() Tags: [accessibility](), [android](), [aria](), [browser](), [chrome](), [edge](), [firefox](), [ios](), [macos](), [safari](), [uncategorized](), [web](), [web-accessibility](), [windows](), [windows-11]() ### AI overview This article surveys emerging ARIA 1.3 features, including aria-errormessage, aria-description, aria-details, and aria-keyshortcuts. It explains their intended uses and reports varying support across browsers, screen readers, and operating systems tested in May 2025. ### Source excerpt If you work in web accessibility, you've probably spent a lot of time explaining and implementing the ARIA roles and attributes that have been around for years--things like aria-label, aria-labelledby, and role="dialog". But the ARIA landscape isn't static. In fact, recent ARIA specifications (especially ARIA 1.3) include a number of emerging and lesser-known features that [...] ## Announcing FigJam screen reader support DevFeed: [Announcing FigJam screen reader support]() Original publisher: [Read original article]() Author: Figma Published: 2023-05-16T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Web Accessibility (a11y)](), [Figma](), [User interface design](), [Icon font](), [aria]() Tags: [accessibility](), [alt-text](), [aria](), [collaboration](), [figma](), [release](), [ui](), [updates](), [web-accessibility]() ### AI overview Figma announces official screen reader support for FigJam after a beta period. The update enables screen reader and keyboard-only users to navigate the canvas, menus, and screens while creating, editing, and reading file structures, text shapes, stickies, tables, and image alt text. Some features, including cursor chat, voting, widgets, and freeform vector nodes, are not yet supported. ### Source excerpt We sat down with the accessibility team to talk about the journey from beta to official release and share tips for anyone who'd like to use these updates to make their FigJam files more accessible. ## 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 ## Reviewing a design for accessibility DevFeed: [Reviewing a design for accessibility]() Original publisher: [Read original article]() Author: Steve Barnett Published: 2021-08-14T00:00:00Z Content type: article Language: en Sources: [The A11Y Project]() Topics: [Accessibility](), [Web Accessibility (a11y)](), [Web Development](), [HTML](), [Forms]() Tags: [accessibility](), [article](), [forms](), [guide](), [web-accessibility]() ### AI overview This article presents an early design-review approach for identifying and addressing accessibility issues before development begins. It recommends explicitly annotating semantics and accessibility requirements, then checking page titles, heading structure, image text alternatives, link and button names, standard controls, form-element names, grouped controls, and error messages. ### 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