# W3C The World Wide Web Consortium (W3C) is an international public-interest nonprofit organization that develops open web standards. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## 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. ## How Do Committees Fail To Invent? DevFeed: [How Do Committees Fail To Invent?]() Original publisher: [Read original article]() Author: Alex Russell Published: 2025-08-11T00:00:00Z Content type: opinion Language: en Sources: [Alex Russell]() Topics: [Development](), [Web platform](), [W3C]() Tags: [bias](), [browsers](), [consensus](), [development](), [engineering](), [standards](), [web-platform](), [webdev]() ### AI overview The article applies Conway's Law to standards development organizations, arguing that a "fifth column" problem can arise when delegates conceal their intentions through objections or silence. It examines how open membership, veto-heavy rules, and poor information can obstruct progress in standards working groups and affect developers' perceptions of standards. ### Source excerpt Mel Conway's seminal paper "How Do Committees Invent?" (PDF) is commonly paraphrased as Conway's Law: Organizations which design systems are (broadly) constrained to produce designs which are copies of the communication structures of these organizations. This is deep organisational insight that engineering leaders ignore at their peril, and everyone who delivers code for a living benefits from a (re)read of "The Mythical Man-Month", available at fine retailers everywhere. Conway's Law is generally invoked to describe organisations working to solve well-defined problems, in which everyone is working towards a solution. But what if there are defectors? And what if they can prevent forward progress without paying any price? This problem is rarely analysed for the simple reason that such an organisation would be deranged. But what if that happened regularly? I was reminded of the possibility while chatting with a colleague joining a new (to them) Working Group at the W3C. The most cursed expressions of Conway's Law regularly occur in Standards Development Organisations (SDOs); specifically, when delegates refuse to communicate their true intentions, either through spurious objection or tactical silence. This special case is the fifth column problem. Contents How Does This Happen? Mayfly Half-Lives The Web Platform's Power Structure But Why? Problem Misstatements Closed For Business Survivorship Bias and The Problem of Big, Old Rooms Marketing Gridlock As Thoughtfulness When Is A "Consensus" Not Consensus? Defences Against Fifth Columns Expressed in Conwayist terms, the fifth column problem describes the way organisations mirror the miscommunication patterns of their participants when they fail to deliver designs of any sort. This pathology presents when the goal of the majority is antithetical to a small minority with a veto. Reticence of certain SDO participants to consider important problems is endemic, in part, due to open membership. Unlike corporate environments wh ## Third-Party Cookies, Single Sign-On, and the Limits of Browser Privacy Interventions DevFeed: [Third-Party Cookies, Single Sign-On, and the Limits of Browser Privacy Interventions]() Original publisher: [Read original article]() Author: Alex Russell Published: 2024-07-30T00:00:00Z Content type: opinion Language: en Sources: [Alex Russell]() Topics: [Cookies](), [Web](), [Single sign-on (SSO)](), [W3C](), [browsers](), [Google]() Tags: [browsers](), [cookies](), [google](), [identity](), [privacy](), [sso](), [w3c](), [web](), [webdev]() ### AI overview This commentary critiques the W3C Technical Architecture Group's response to Google's decision not to imminently remove third-party cookies. It argues that the response underplays both the limited benefits of cookie removal and the unresolved effects on Single Sign-On, sign-in flows, advertising, and user tracking. ### Source excerpt The W3C Technical Architecture Group1 is out with a blog post and an updated Finding regarding Google's recent announcement that it will not be imminently removing third-party cookies. The current TAG members are competent technologists who have a long history of nuanced advice that looks past the shouting to get at the technical bedrock of complex situations. The TAG also plays a uniquely helpful role in boiling down the guidance it issues into actionable principles that developers can easily follow. All of which makes these pronouncements seem like weak tea. To grok why, we need to walk through the threat model, look at the technology options, and try to understand the limits of technical interventions. Contents Unmasking The Problem Fire And Movement Finding A Way Forward But before that, I should stipulate my personal position on third-party cookies: they aren't great! They should be removed from browsers when replacements are good and ready, and Google's climbdown isn't helpful. That said, we have seen nothing of the hinted-at alternatives, so the jury's out on what the impact will be in practice.2 So why am I dissapointed in the TAG, given that my position is essentially what they wrote? Because it failed to acknowledge the limited and contingent upside of removing third-party cookies, or the thorny issues we're left with after they're gone. Unmasking The Problem So, what do third-party cookies do? And how do they relate to the privacy theat model? Like a lot of web technology, third-party cookies have both positive and negative uses. Owing to a historcal lack of platform-level identity APIs, they form the backbone of nearly every large Single Sign-On (SSO) system. Thankfully, replacements have been developed and are being iterated on. Unfortunately, some browsers have unilaterally removed them without developing such replacements, disrupting sign-in flows across the web, harming users and pushing businesses toward native mobile apps. That's bad, as native app ## Aria-Label is Not Always the Answer DevFeed: [Aria-Label is Not Always the Answer]() Original publisher: [Read original article]() Author: Eevis Panula Published: 2023-01-03T08:57:28.550000Z Content type: tutorial Language: en Sources: [Eevis Blog]() Topics: [Accessibility](), [aria](), [HTML](), [html elements](), [W3C]() Tags: [accessibility](), [accessible](), [aria](), [details](), [html](), [html-elements](), [w3c]() ### AI overview This tutorial explains that aria-label is not universally appropriate or consistently supported across HTML elements. It describes when to use aria-label, when aria-labelledby is preferable, and the element types where aria-label works consistently with assistive technologies. ### Source excerpt Okay, you've learned about accessibility and that there is sometimes a need to make, for example, the link text more descriptive for screen reader users. You've learned about the aria-label-attribute, and its powers. It's the answer to everything! I'm afraid I have to say that it is not. It doesn't work with all HTML elements. In this blog post, I'll dig a bit deeper into the aria-label-attribute, and its usage and limitations, and options. What Is aria-label? So, let's first talk about the specification and where to use it. W3C Recommendation for Accessible Rich Internet Applications (WAI-ARIA)-document defines aria-label as "a string value that labels the current element." You can use it to provide a recognizable name of the object if there is no visible text on the screen that could be used as the label. If there was, aria-labelledby should be used. The most important thing, and the reason I'm writing this article, is that developers should use it only with the following elements: interactive elements (such as links, buttons, inputs et cetera) Elements that have a landmark role Elements that have an ARIA-widget role img or iframe-elements Source: Short note about aria-label, aria-labelledby and aria-describedby by Léonie Watson. aria-label on these elements works consistently with assistive technologies. The support is inconsistent if you use it with any other tag, such as div or span. More about that in Aria-label and non-supported elements. Let's look into each one of these elements a bit more. Interactive Elements Interactive elements are tags intended for user interaction. It means, for example, button, a (when href-attribute is present), input , details and others. The main idea is that users can interact with them. Elements with Landmark Role Elements can have landmark roles either implicitly or explicitly. Having an implicit role means that some of the HTML elements have roles set to them natively. The explicit role, on the other hand, is set with role-att ## 2019 in Review DevFeed: [2019 in Review]() Original publisher: [Read original article]() Published: 2020-01-10T00:00:00Z Content type: opinion Language: en Sources: [Una Kravets]() Topics: [Development](), [Front end](), [Google](), [CSS](), [Material Design](), [W3C](), [color]() Tags: [color](), [css](), [developer](), [front-end-development](), [google](), [material-design](), [retrospective](), [w3c](), [year-in-review]() ### AI overview A personal retrospective covering 2019 travel, work, projects, content production, and professional contributions. The author discusses joining Google as a Developer Advocate for Material Design, producing podcasts and web series, publishing front-end development content, contributing to the W3C CSS Working Group, and launching CSS Houdini and Material-related projects. ### Source excerpt 2019 was a massive year for me. I like to reflect on the year and set some goals for the future. ## Quick Threat Model Links October 2019 DevFeed: [Quick Threat Model Links October 2019]() Original publisher: [Read original article]() Author: Adam Published: 2019-10-09T00:00:00Z Content type: article Language: en Sources: [Shostack & Friends Blog]() Topics: [Security](), [Kubernetes](), [W3C](), [Web]() Tags: [blog](), [kubernetes](), [security](), [w3c](), [web]() ### AI overview A roundup of threat-modeling resources published in October 2019, covering Kubernetes, serverless functions, managed attribution, web feature development, and medical devices. It also notes that some linked resources are no longer available and discloses advisory-board relationships with Continuum and Ntrepid. ### Source excerpt Just a few things for now ## Keycloak Community Newsletter #1 DevFeed: [Keycloak Community Newsletter #1]() Original publisher: [Read original article]() Author: Sébastien Blanc Published: 2019-04-01T00:00:00Z Content type: news Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [Authentication](), [WebAuthn](), [W3C](), [GitHub](), [Kubernetes]() Tags: [announcement](), [authentication](), [github](), [github-issues](), [idm](), [jwt](), [kerberos](), [keycloak](), [kubernetes](), [ldap](), [new-feature](), [news](), [openid-connect](), [pull-requests](), [saml](), [sso](), [w3c](), [web-authentication]() ### AI overview The first Keycloak Community Newsletter reviews community articles on JWT authentication with React, NodeJS, Kong, Kibana, and Kubernetes. It also covers Keycloak releases, planned feature design discussions, WebAuthn becoming a W3C Standard, conference talks, and opportunities to contribute. ### Source excerpt This is the very first "Keycloak Community Newsletter." The goal of this newsletter is to share news about the Keycloak project. News from the community Since the beginning of the year, the community has been really active. Each week several blog posts about Keycloak are published. Here is a short selection. Let's start with Philip Riecks who explains in this article how you can use Microprofile JWT Authentication with Keycloak and React. Ramandeep Singh has been blogging about Keycloak and NodeJS. Joshua Alfred Erney explains in this blog series how to integrate Keycloak and Kong, a popular API management platform. With Mohamed Aboullaite's blog post, you will learn how to secure your Kibana dashboards using Keycloak. Finally in this three-part article, the process of installing Keycloak on Kubernetes will become very clear. News from the project Keycloak 5.0.0 has been released and 6.0.0 is around the corner. From now on, new larger Keycloak's features will be openly discussed. For each new feature, a design document will be created and pushed to our Github repository as a simple MarkDown file. This strategy makes it easy for everyone to comment as well as contribute to the designs by opening Github issues and providing pull requests. We have already three documents open for discussion: W3C Web Authentication - Two-Factor Application-Initiated Actions Observerability News from the Identity Management World The big announcement, two weeks ago, was that WebAuthn became an official W3C Standard. This event is a milestone in the world of authentication and Identity Management. The goal of WebAuthn, according to Wikipedia is to: standardize an interface for public-key authentication of users to web-based applications and services. The Keycloak community is naturally really interested in this new standard. A design document is available and the community has even started to work on a prototype. Conferences / Webinars In March, the Javaland conference was held in Germany ## W3C Push API Crash Course DevFeed: [W3C Push API Crash Course]() Original publisher: [Read original article]() Author: Nick Comer (nicholas@zumba.com) Published: 2015-05-29T00:00:00Z Content type: tutorial Language: en Sources: [Zumba]() Topics: [Chrome](), [notifications](), [W3C](), [Google Chrome](), [API](), [Google]() Tags: [api](), [chrome](), [google-chrome](), [notifications](), [push-notifications](), [w3c]() ### AI overview A tutorial introducing push notifications in Google Chrome through the W3C Push API. ### Source excerpt Getting started with push notifications in Google Chrome ## Media Queries 4 and Responsive Design Beyond Browser Size DevFeed: [Media Queries 4 and Responsive Design Beyond Browser Size]() Original publisher: [Read original article]() Published: 2014-10-16T00:00:00Z Content type: article Language: en Sources: [Una Kravets]() Topics: [Media Queries](), [Responsive Design](), [web design](), [W3C](), [browser]() Tags: [browser](), [deprecated](), [design](), [responsive-design](), [w3c](), [web]() ### AI overview This article reviews media query capabilities, including media types and expressions for different devices, and argues that responsive design can account for factors beyond browser size, such as location, weather, and lighting. ### Source excerpt The Media Queries 4 spec brings insight to technological capabilities that are coming up soon (this is based on the Editor's Draft, October 10, 2014).