# WCAG Published articles for WCAG. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## WordPress Proposes Ipsum as a Minimal Default Theme for WordPress 7.2 DevFeed: [WordPress Proposes Ipsum as a Minimal Default Theme for WordPress 7.2]() Original publisher: [Read original article]() Author: Alex Harper Published: 2026-09-16T16:51:36Z Content type: news Language: en Sources: [Web Designer Depot]() Topics: [WordPress](), [WordPress themes and plugins](), [Website]() Tags: [accessibility](), [block-themes](), [cms](), [default-themes](), [full-site-editing](), [gutenberg](), [gutenberg-editor](), [ipsum](), [matt-mullenweg](), [news](), [news-web-development](), [release](), [twenty-twenty-seven](), [ux-design](), [wcag](), [web-design](), [web-development](), [website-design](), [wordpress](), [wordpress-7-2](), [wordpress-design](), [wordpress-themes]() ### AI overview WordPress has proposed Ipsum as the default theme for WordPress 7.2, replacing the year-based Twenty Something naming convention. The deliberately minimal theme is designed as a customizable blogging canvas, while the more expressive Mētis theme will remain separate and will not ship with the release. ### Source excerpt After 16 years, WordPress just killed one of its most recognizable traditions. The predictable "Twenty Something" default themes are history, and their replacement, Ipsum, signals a surprisingly different vision for what WordPress thinks a modern website should start with. ## 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 ## 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. ## 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). ## 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 ## Practical Methods for Improving Web Accessibility DevFeed: [Practical Methods for Improving Web Accessibility]() Original publisher: [Read original article]() Author: Tom Widerøe Published: 2016-06-13T11:19:07Z Content type: tutorial Language: en Sources: [Finn.no]() Topics: [Accessibility](), [User interface design](), [Mobile](), [browsers](), [navigation]() Tags: [accessibility](), [accessible](), [browsers](), [keyboard](), [mobile](), [navigation](), [test](), [wcag]() ### AI overview The article explains how FINN.no employees encouraged colleagues to prioritize accessibility through workshops, user testing, and automatic validation. It describes practical checks including page scaling, pinch zooming on mobile phones, a straw test for limited vision, and keyboard navigation. ### Source excerpt What to do when your colleagues don't make accessible products. When developing a website which affects the life of almost every person in Norway, accessibility should be a main priority. Norwegians who are not able to use FINN.no are unable to find a home without assistance. Accessibility considerations are too often an afterthought, and this can have profound effects. In the Spring of 2014, a small group of employees got together to find out how to make our colleagues care more about accessibility. After two years, the measures we think work best are workshops, user tests, and automatic validation. Workshops On a workshop we reveal accessibility issues and discuss how to solve them. At our workshops we demonstrate how FINN.no works for people with disabilities before we let the team members test it the same way themselves. People find this a lot more inspiring than memorising WCAG 2.0 recommendations and running automatic validations locally. How to test Scaling Pages The simplest thing to test for is page scalability, both for fonts and for the entire page. Most desktop browsers make it possible to scale both fonts and page no matter how poorly coded the pages are, but on mobile phones it's still quite common to lock page size to screen size. It must be possible to pinch zoom every page on mobile phones. The Straw Test Another simple method is to pretend that you are looking at the page through a straw. This simulates how the page will appear for partially sighted people who either have a limited field of vision or need to magnify the page to read it. This reveals relevant elements spaced too far apart in a way that will make it difficult to navigate the page. Keyboard Navigation Most pages are designed and coded with mouse click and touch screens in mind, and we easily forget about people with broken arms, motor disabilities, or other reasons for not being able to use a mouse. By navigating the page with only a keyboard, we test that focus on links and buttons a