# WAI Published articles for WAI. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How to Decide Whether an Image Needs Alt Text DevFeed: [How to Decide Whether an Image Needs Alt Text]() Original publisher: [Read original article]() Author: Adrian Roselli Published: 2026-10-09T16:02:23Z Content type: article Language: en Sources: [Adrian Roselli]() Topics: [Web Accessibility (a11y)](), [User interface design](), [UI/UX Design]() Tags: [accessibility](), [alt-text](), [html](), [image](), [rant](), [standards](), [wai](), [wcag](), [web]() ### AI overview The article argues that images in narrative content serve a purpose and should not be called decorative without examining that purpose. It offers questions about whether readers would notice an image's removal or replacement, then adapts the WAI alt text decision tree to guide alternatives for images that contain text, appear in controls, or contribute meaning. ### Source excerpt ...aren't a thing. Three hand-drawn lines curling together like an S or three skinny snakes trying to spoon. At least not as far as people are concerned. Yes, this is an absolutist take, but sometimes it's necessary to take the absolutist position to force someone to justify their own reasoning.... ## Evaluating a Success Criterion DevFeed: [Evaluating a Success Criterion]() Original publisher: [Read original article]() Author: Adrian Roselli Published: 2026-09-01T13:47:16Z Content type: article Language: en Sources: [Adrian Roselli]() Topics: [W3C](), [GitHub Issues](), [audit](), [Requirements](), [Pull Request](), [interface](), [GitHub](), [test]() Tags: [accessibility](), [audit](), [github](), [github-issues](), [pull-requests](), [requirements](), [standards](), [test](), [w3c](), [wai](), [wcag](), [web]() ### AI overview A practical process for evaluating WCAG Success Criteria when their intent or application is unclear. It recommends consulting current W3C normative and supporting documents, techniques, GitHub issues and pull requests, expert commentary, and testing outcomes. ### Source excerpt Sidney Paget illustration of Sherlock Holmes from Strand Magazine, December 1892, p.646, but I added papers from his March 1893 (p.281 of Strand Magazine) illustration and then two versions of the W3C logo to the front page. When performing a WCAG evaluation (or review or audit), it's easy to get... ## The 2.1.1 "specific timings" Clause DevFeed: [The 2.1.1 "specific timings" Clause]() Original publisher: [Read original article]() Author: Adrian Roselli Published: 2026-08-26T15:10:52Z Content type: opinion Language: en Sources: [Adrian Roselli]() Topics: [Web Accessibility (a11y)](), [W3C](), [User interface design]() Tags: [accessibility](), [keyboard](), [rant](), [standards](), [usability](), [ux](), [w3c](), [wai](), [wcag](), [web]() ### AI overview The article examines the specific-timings clause in WCAG Success Criterion 2.1.1, explaining that keyboard operation must not require precisely timed keystrokes except where the underlying function depends on the user's movement path. It argues that simplified WCAG interpretations often overlook this requirement and discusses a suspected violation involving Wayfair. ### Source excerpt Many simplified, intro, or "plain-English" WCAG re-interpretations frame Success Criterion 2.1.1 Keyboard as ensuring a control or widget or thing can be operated with a keyboard. Some go further and also ask you to consider keyboard-like devices. Very few (I counted 1 out of 10) pay attention to the part... ## Link + Popover Navigation DevFeed: [Link + Popover Navigation]() Original publisher: [Read original article]() Author: Adrian Roselli Published: 2026-07-09T13:05:04Z Content type: article Language: en Sources: [Adrian Roselli]() Topics: [Web Accessibility (a11y)](), [HTML](), [Web Development](), [CSS](), [aria](), [browser]() Tags: [accessibility](), [apis](), [aria](), [browser](), [css](), [html](), [javascript](), [keyboard](), [navigation](), [pattern](), [reading](), [semantics](), [standards](), [usability](), [ux](), [wai](), [wcag](), [web]() ### AI overview An accessibility-focused navigation pattern replaces ARIA or HTML disclosure widgets with native HTML popovers. The article covers semantic structure, CSS positioning, keyboard and assistive technology behavior, focus order, and the use of ARIA for button naming. ### Source excerpt This is a redress of my 2019 post Link + Disclosure Widget Navigation, except (as the title implies), I've modified it to use native HTML popovers instead of ARIA or HTML disclosure widgets. Popover has the benefit of using appropriate HTML structure and semantics while removing the need for scripting... ## W3C recognized on the 2026 Forbes Accessibility 200 list DevFeed: [W3C recognized on the 2026 Forbes Accessibility 200 list]() Original publisher: [Read original article]() Author: Seth Dobbs, W3C CEO and President Published: 2026-05-21T12:49:00Z Content type: release Language: en Sources: [W3C]() Topics: [Web Accessibility (a11y)](), [W3C](), [Web Content Accessibility Guidelines](), [Website]() Tags: [2026](), [accessibility](), [accessibility-guidelines](), [blogs](), [recognition](), [standards](), [w3c](), [wai](), [wcag](), [web-content-accessibility-guidelines]() ### AI overview W3C announces its inclusion in the 2026 Forbes Accessibility 200 list, recognizing the impact of its Web Accessibility Initiative. The article describes WAI's work on WCAG, accessibility resources, and the development of WCAG 3. ### Source excerpt The World Wide Web Consortium (W3C) is honored to be included in the Forbes Accessibility 200 list for 2026 in recognition of the impact that our Web Accessibility Initiative (WAI) has had on the world. ## Designing better target sizes DevFeed: [Designing better target sizes]() Original publisher: [Read original article]() Author: Ahmad Shadeed Published: 2024-01-10T00:00:00Z Content type: tutorial Language: en Sources: [Ahmad Shadeed]() Topics: [User interface design](), [Web Development](), [User Interfaces](), [input](), [Users](), [test](), [CSS]() Tags: [clickable](), [css](), [design](), [designing](), [guide](), [hit](), [size](), [tap](), [target](), [ui](), [users](), [wai](), [wcag]() ### AI overview An interactive guide to designing sufficiently large clickable and touch targets for web interfaces. It explains target-size terminology across input methods and discusses WCAG and platform recommendations, including 44-by-44 CSS pixels and minimum spacing requirements. ### Source excerpt An interactive guide on designing better target sizes on the web. ## 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)](), [aria](), [Web Content Accessibility Guidelines](), [browser](), [W3C](), [web-standards]() Tags: [accessibility](), [accessibility-guidelines](), [accessible](), [aria](), [assistive-technology](), [benchmark](), [guidance](), [guidelines](), [implementation](), [initiative](), [internet](), [research](), [resources](), [standards](), [support](), [the-web](), [w3c](), [wai](), [web-accessibility](), [white-house]() ### AI overview W3C's Web Accessibility Initiative (WAI), launched in 1997, brings together disability organizations, governments, and researchers to develop web accessibility standards, guidance, evaluation resources, education, and outreach. Its work addresses auditory, cognitive, neurological, physical, speech, and visual disabilities. The excerpt highlights WCAG, which sets web accessibility criteria under four principles--perceivable, operable, understandable, and robust--with A, AA, and AAA success levels; and WAI-ARIA, which guides accessible dynamic content and custom interface components, including ways to support assistive technology. WAI working groups develop guidelines, and interested people can participate. ### Source excerpt The Web Accessibility Initiative is W3C's effort to improve accessibility of the Web for people with disabilities. What is the World Wide Consortium? In order to know about the Web Accessibility Initiative, we must first talk about the World Wide Consortium, also known as W3C. Founded in 1994 and currently led by director Tim Berners-Lee and CEO Jeffrey Jaff, W3C is an international community where organizers develop international standards for the Web. As described by W3's website, "W3C's mission is to lead the Web to its full potential." Organizers from all around the world, involved in many different fields, join W3C to develop guidelines that ensure long-term growth for the Web. The Web Accessibility Initiative is one initiative that was launched by W3C. What is the Web Accessibility Initiative? The power of the Web is in its universality. Access by everyone regardless of disability is an essential aspect. Tim Berners-Lee, W3C Director and inventor of the World Wide Web W3C launched The Web Accessibility Initiative, (WAI), in 1997, with support from the White House. The Web Accessibility Initiative's main goal is to make the internet accessible for people with disabilities. WAI brings people from disability organizations, governments, and research labs from all around the world to develop guidelines and resources to make the Web accessible to people with disabilities. This includes: auditory, cognitive, neurological, physical, speech and visual disabilities. In short, WAI develops accessibility standards and offers implementation guidance. As described by W3C Website, WAI "pursues accessibility of the web through these primary activities": Ensuring that W3C standards support accessibility Developing accessibility guidelines for web content and applications, browsers, and authoring tools Developing resources to improve web accessibility evaluation processes and tools Supporting education and outreach on web accessibility Coordinating with research and development ## Introducing downshift 🏎 for React ⚛ DevFeed: [Introducing downshift 🏎 for React ⚛]() Original publisher: [Read original article]() Published: 2017-08-23T00:00:00Z Content type: release Language: en Sources: [Kent C. Dodds Blog]() Topics: [React](), [autocomplete](), [render](), [callback](), [API](), [implementation]() Tags: [accessible](), [api](), [autocomplete](), [callback](), [flexibility](), [implementation](), [react](), [render](), [rendering](), [wai]() ### AI overview An introduction to downshift, a React primitive for building accessible autocomplete, typeahead, dropdown, select, and combobox components. It explains downshift's render prop and controlled props patterns, which give developers control over rendering while simplifying the API and implementation. ### Source excerpt downshift 🏎 is the primitive you need to build simple, flexible, WAI-ARIA compliant React... ## Easy color contrast ratios DevFeed: [Easy color contrast ratios]() Original publisher: [Read original article]() Author: Lea Verou Published: 2012-10-14T00:00:00Z Content type: article Language: en Sources: [Lea Verou's blog]() Topics: [Web Accessibility (a11y)](), [CSS](), [Web Development](), [Algorithms](), [W3C]() Tags: [a11y](), [accessibility](), [algorithm](), [blog](), [browser](), [colors](), [contrast-ratio-com](), [css](), [releases](), [wai](), [wcag]() ### AI overview An accessibility-focused article examines WCAG color contrast ratios and explains why the author built a tool to evaluate CSS colors, including semi-transparent colors, more conveniently. ### Source excerpt I was always interested in accessibility, but I never had to comply with any guidelines before. At W3C, accessibility is considered very important, so everything we make needs to pass WCAG 2.0 AA level. Therefore, I found myself calculating color contrast ratios very frequently. It was a very enlightening experience. I used to think that WCAG-mandated contrast ratios were too restrictive and basically tried to force you to use black and white, a sentiment shared by many designers I've spoken to. Surprisingly, in practice, I found that in most cases they are very reasonable: When a color combination doesn't pass WCAG, it usually *is* hard to read. After all, the possible range for a contrast ratio is 1-21 but only ratios lower than 3 don't pass WCAG AA (4.5 if you have smaller, non-bold text). So, effectively 90% of combinations will pass (82.5% for smaller, non-bold text). There are plenty of tools out there for this. However, I found that my workflow for checking a contrast ratio with them was far from ideal. I had to convert my CSS colors to hex notation (which I don't often use myself anymore), check the contrast ratio, then adjust the colors as necessary, covert again etc. In addition, I had to adjust the lightness of the colors with a blindfold, without being able to see the difference my adjustments would make to the contrast ratio. When using semi-transparent colors, it was even worse: Since WCAG only describes an algorithm for opaque colors, all contrast tools only expect that. So, I had to calculate the resulting opaque colors after alpha blending had taken place. After doing that for a few days, I got so fed up that I decided to make my own tool. In addition, I discovered that there was no documented way of calculating the contrast ratio range that can be produced with a semi-transparent background, so I came up with an algorithm (after many successive failures to find the range intuitively), published it in the w3c-wai-ig mailing list and used the algorit