# W3C Published articles for W3C. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Support the well-known change password URL with Appwrite Auth DevFeed: [Support the well-known change password URL with Appwrite Auth]() Original publisher: [Read original article]() Author: Atharva Deosthale Published: 2026-09-16T00:00:00Z Content type: tutorial Language: en Sources: [Appwrite Blog]() Topics: [passwords](), [Appwrite](), [Application Security](), [web applications](), [W3C]() Tags: [bitwarden](), [deployment](), [passwords](), [security](), [tutorial](), [tutorials](), [w3c]() ### AI overview This tutorial shows how to support the well-known change password URL in a TanStack Start app using Appwrite Auth. It explains the redirect, the change-password form for signed-out visitors, autocomplete hints, and deployment to Appwrite Sites. ### Source excerpt Password managers open /.well-known/change-password when they find a leaked or weak password. Add the redirect and a change password page backed by Appwrite Auth. ## OpenTelemetry proposes environment variables for context propagation across processes DevFeed: [OpenTelemetry proposes environment variables for context propagation across processes]() Original publisher: [Read original article]() Author: OpenTelemetry Authors; Docs CC BY Published: 2026-09-11T11:01:22Z Content type: article Language: en Sources: [Blog on OpenTelemetry]() Topics: [context](), [tracing](), [OpenTelemetry](), [Processes](), [CI/CD](), [data-processing]() Tags: [ci-cd](), [data-processing](), [environment-variables](), [opentelemetry](), [processes](), [spans](), [tracing](), [w3c]() ### AI overview The OpenTelemetry Specification has a release candidate for using environment variables to carry trace context and baggage between processes. The article explains how this can connect spans across workflow runners, shells, build tools, test processes, and similar workloads when protocol headers or message metadata are unavailable, and requests feedback before the specification becomes Stable. ### Source excerpt A trace does not always cross a network boundary. A workflow runner starts a shell, the shell launches a build tool, and the build tool starts test processes. Batch and data-processing systems create similar chains of child processes. Without a shared way to pass trace information across these boundaries, spans from each process can end up in separate traces. If context propagation is new to you, it is the mechanism that carries information from one service or process to the next. For tracing, this includes the trace and span identifiers that let new spans join the same trace. It can also carry baggage: application-defined key-value pairs that are passed to downstream work. ## Ebb, Meet Flow: Intrinsic Design in a Nutshell DevFeed: [Ebb, Meet Flow: Intrinsic Design in a Nutshell]() Original publisher: [Read original article]() Author: L. Jeffrey Zeldman Published: 2026-08-18T17:24:50Z Content type: opinion Language: en Sources: [Jeffrey Zeldman]() Topics: [Responsive Design](), [web design](), [Front end](), [web-standards]() Tags: [authoring](), [best-practices](), [css](), [design](), [essentials](), [responsive](), [responsive-design](), [responsive-web-design](), [rwd](), [standards](), [state-of-the-web](), [the-essentials](), [the-profession](), [type](), [typography](), [usability](), [user-experience](), [ux](), [w3c](), [web-design](), [web-design-history](), [web-standards](), [webdesign](), [webtype]() ### AI overview This article explains intrinsic or fluid responsive design: define type scales for small and large screens, then let the browser interpolate between them according to viewport width. It connects the approach to earlier ideas about designing for the web's natural ebb and flow and to the development of Responsive Web Design through improved web standards and browser support. ### Source excerpt In 2020, the gifted makers of websites at Clearleft shared methods to achieve fluid responsive design. "Utopian" web design was (and still is) their half-kidding name for this approach, which Apple's Jen Simmons, working indendently, called "intrinsic design." Instead of chasing an ever-changing number of fixed breakpoints, utopian or intrinsic design follows the web's intrinsic [...] The post Ebb, Meet Flow: Intrinsic Design in a Nutshell appeared first on Jeffrey Zeldman Presents. ## RFC 9998: Report from the IAB/W3C Workshop on Age-Based Restrictions on Content Access DevFeed: [RFC 9998: Report from the IAB/W3C Workshop on Age-Based Restrictions on Content Access]() Original publisher: [Read original article]() Published: 2026-07-03T00:00:00Z Content type: article Language: fr Sources: [Blog de Stéphane Bortzmeyer]() Topics: [Internet](), [W3C](), [Internet Engineering Task Force (IETF)]() Tags: [architecture](), [article](), [ietf](), [internet](), [report](), [rfc](), [w3c]() ### AI overview This article discusses RFC 9998, the report of an IAB/W3C workshop on age-based restrictions for access to Internet services. It describes the workshop's focus on technical approaches, architecture, privacy, decentralization, and the potential consequences of age-verification systems. ### Source excerpt En octobre 2025, l'IAB et le W3C ont organisé un atelier (https://datatracker.ietf.org/group/agews/about/) à Londres sur la restriction d'accès à des services Internet en fonction de l'âge. Ce RFC est le compte-rendu de l'atelier. En tant que compte-rendu, il n'exprime donc pas une position officielle de l'IAB. ## You don't need to pick one: how Sentry and OpenTelemetry work together DevFeed: [You don't need to pick one: how Sentry and OpenTelemetry work together]() Original publisher: [Read original article]() Author: Lazar Nikolov Published: 2026-05-27T00:00:00Z Content type: tutorial Language: en Sources: [Sentry Blog]() Topics: [OpenTelemetry](), [telemetry](), [tracing](), [Traces](), [context](), [Instrumentation](), [React](), [SDKs]() Tags: [frontend](), [instrumentation](), [opentelemetry](), [sentry](), [telemetry](), [traces](), [tracing](), [w3c]() ### AI overview This article explains how to combine Sentry and OpenTelemetry in a web application. It recommends keeping OpenTelemetry for backend instrumentation, using the Sentry SDK on the frontend for browser context and application features, and exporting backend traces and logs to Sentry through OTLP directly or through an OpenTelemetry Collector. Sentry's OTLP ingest supports traces and logs, but not metrics at the time described. ### Source excerpt Use Sentry on the frontend, keep OpenTelemetry on the backend, and choose direct OTLP or Collector forwarding for OTLP events. ## 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. ## 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 ## WebAuthn, FIDO2, and CTAP: Concepts and Components of Passwordless Authentication DevFeed: [WebAuthn, FIDO2, and CTAP: Concepts and Components of Passwordless Authentication]() Original publisher: [Read original article]() Author: sakshyam.shah@goteleport.com (Sakshyam Shah) Published: 2022-07-07T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [WebAuthn](), [Authentication](), [public key](), [browsers](), [Security](), [W3C]() Tags: [authentication](), [browsers](), [protocol](), [public-key](), [security](), [w3c](), [web]() ### AI overview This tutorial explains WebAuthn as a public-key authentication API for web browsers. It introduces the relationship between WebAuthn, FIDO2, the W3C specification, and CTAP, and describes the components required for passwordless authentication. ### Source excerpt This post introduces basic concepts and details related to WebAuthn. ## 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 Web Authentication (WebAuthn) DevFeed: [W3C Web Authentication (WebAuthn)]() Original publisher: [Read original article]() Author: Stian Thorgersen Published: 2019-03-06T00:00:00Z Content type: article Language: en Sources: [Keycloak Blog]() Topics: [WebAuthn](), [Authentication](), [public key](), [Keycloak](), [browser](), [Java]() Tags: [authentication](), [idm](), [java](), [kerberos](), [keycloak](), [ldap](), [openid-connect](), [public-key](), [saml](), [security](), [sso](), [w3c](), [web-authentication]() ### AI overview The article explains that WebAuthn became an official W3C web standard and describes its use of public-key credentials instead of shared secrets. It covers phishing resistance, browser and device support, two-factor and passwordless authentication, and planned WebAuthn integration in Keycloak. ### Source excerpt W3C Web Authentication (WebAuthn) was recently made an official web standard. This is a great step towards making a safer and simpler authentication experience for users. Where traditional authentication, such as password and OTP, rely on having shared secrets between the user and the web application, this is not the case with WebAuthn. WebAuthn uses public key-based credentials resulting in the web application not having access to the users secrets anymore. The keys are also unique per web application which eliminates the risk of phishing attacks. WebAuthn provides a standard protocol for web applications to authenticate via a number of devices through a relatively simple challenge/response. All major browser vendors now have support for WebAuthn and FIDO2, where FIDO2 is the specification that enables the browser to communicate with different hardware devices. WebAuthn can be used both as a two factor mechanism as well as enable passwordless authentication. There are already an healthy amount of devices that can be used together with WebAuthn. There are a number of security keys like YubiKey, ThinC and Titan. A lot of new laptops also come with built-in fingerprint scanners, and it Android also recently made it possible to use the fingerprint scanners on Android 7+ devices with WebAuthn. We are of course planning on bringing WebAuthn support to Keycloak in the near future. The team behind webauthn4j has been hard at work greating a quality Java library for WebAuthn and will hopefully soon have an extension to Keycloak ready. We will first focus on two-factor authentication with WebAuth and as part of this we will bring a number of improvements to Keycloak around two-factor authentication. For more details check the design document. Later, we will also bring the passwordless experience to Keycloak. This will also introduce Keycloak to the identity first login flows. By asking for the users identity first Keycloak can provide smarter decisions on how to authenticate ## Shaping the Future of Payments in the Browser DevFeed: [Shaping the Future of Payments in the Browser]() Original publisher: [Read original article]() Author: Krystian Czesak Published: 2018-09-04T19:32:00Z Content type: article Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [API](), [browser](), [Shopify](), [JavaScript](), [Chrome](), [Web](), [modern web development]() Tags: [api](), [browser](), [checkout](), [chrome](), [community](), [contribute](), [data](), [experimentation](), [javascript](), [payments](), [shopify](), [w3c]() ### AI overview Shopify describes an experiment evaluating the Payment Request API, a JavaScript API for native browser payments that simplifies checkout forms and the checkout experience. The article explains Shopify's participation in the W3C Web Payments Working Group and defines success metrics for assessing whether Payment Request is market ready, including checkout completion rate and a faster, better purchase experience. ### Source excerpt At Shopify, the leading multi-channel commerce platform that powers over 600,000 businesses in approximately 175 countries, we aim at making commerce better for everyone. This sometimes means investing in new technologies and giving back what we learned to the community, especially if it's a technology we think will ## Statement Objecting To EME as a W3C Recommendation DevFeed: [Statement Objecting To EME as a W3C Recommendation]() Original publisher: [Read original article]() Author: James Pitts Published: 2017-08-21T15:59:58Z Content type: opinion Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Web](), [Accessibility](), [Security](), [Open Source]() Tags: [accessibility](), [ethereum](), [organizational](), [security](), [standards](), [statement](), [w3c]() ### AI overview The Ethereum Foundation publishes its formal objection to the W3C's proposed Encrypted Media Extensions recommendation. It argues that EME and the Content Decryption Module implementations it enables could reduce accessibility, limit internet freedom, undermine security research, and weaken trust among users and developers. ### Source excerpt The Foundation believes Encrypted Media Extensions (EME) should not be published as a W3C Recommendation, and we are now making public the formal objection the Ethereum Foundation submitted to the W3C opposing the recommendation of EME. As a member of the W3C, the Ethereum Foundation contributes to the standards-making process and... ## Understanding WebDriver, Selenium, Marionette, and Browser Automation DevFeed: [Understanding WebDriver, Selenium, Marionette, and Browser Automation]() Original publisher: [Read original article]() Author: Maja Frydrychowicz Published: 2016-07-12T04:00:00Z Content type: article Language: en Sources: [Mozilla Automation]() Topics: [webDriver](), [Browser Automation](), [Selenium](), [Testing](), [Firefox](), [HTTP](), [JSON](), [Mozilla](), [JavaScript](), [Open Source]() Tags: [automation](), [browser](), [browser-ui](), [browsers](), [client-driver](), [firefox](), [foss](), [geckodriver](), [harness](), [http](), [javascript](), [json](), [marionette](), [mozilla](), [open-source](), [payload](), [request](), [responses](), [selenium](), [w3c](), [web](), [webdriver]() ### AI overview An explanatory article untangles the terminology around Marionette, Selenium, WebDriver, FirefoxDriver, and geckodriver. It explains the W3C WebDriver Specification and how its browser-agnostic protocol uses JSON over HTTP to send commands and receive responses for browser automation and testing. ### Source excerpt I define WebDriver, W3C WebDriver, Selenium, geckodriver, FirefoxDriver, Marionette harness/runner/client/driver and more. ## 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). ## Target Joins the W3C DevFeed: [Target Joins the W3C]() Original publisher: [Read original article]() Author: Target Brands, Inc Published: 2014-10-15T05:00:00Z Content type: release Language: en Sources: [Target]() Topics: [Web](), [Internet of things](), [Internet](), [coding-community]() Tags: [internet-of-things](), [location-based](), [open-source](), [standards](), [w3c](), [web](), [web-services]() ### AI overview Target announced its membership in the World Wide Web Consortium (W3C) and described plans to collaborate on web services, location-based content distribution, and the Internet of Things for retail-related technology. ### Source excerpt Tuesday, October 14th 2015, Target affirmed its commitment to technology and leadership in the retail space by joining the World Wide Web Consortium (W3C). As a company that cares about delivering great experiences for customers, we realize those experiences are now steeped in technology. One way Target can have a significant impact on shaping technology is open engagement with other companies and organizations at the heart of emerging development - the W3C enables us to do just that. So you joined - now what? There are so many areas of technology important to retail and associated businesses. Initially, we're interested in engaging with tech leaders, businesses, and organizations on web services, location-based content distribution (iBeacons, smart stores, etc.), and the Internet of Things. Through open dialogue and collaborative work in the W3C, we seek to push these areas of technology forward to enable new and better experiences for our customers. More to come soon! This is just the beginning. As an organization we will be engaging with the developer community in new and different ways, proposing ideas on the technologies that matter to us, and providing feedback of our progress. Now let's get to work! Target Joins the W3C was originally published by Target Brands, Inc at target tech on October 15, 2014. ## Introducing HTML Inspector DevFeed: [Introducing HTML Inspector]() Original publisher: [Read original article]() Published: 2013-06-11T15:22:52Z Content type: tutorial Language: en Sources: [Philip Walton]() Topics: [HTML](), [Code quality](), [JavaScript](), [Testing](), [browser](), [Document Object Model (DOM)](), [W3C](), [jQuery]() Tags: [browser](), [code-quality](), [html](), [javascript](), [testing](), [w3c]() ### AI overview The article introduces HTML Inspector, a customizable and extensible JavaScript tool that runs in the browser to check HTML markup. It explains how the tool traverses the DOM, applies rules, reports errors, and differs from the stricter, non-extensible W3C Validator. ### Source excerpt HTML Inspector is a code quality tool to help you and your team write better markup. It's written in JavaScript and runs in the browser, so testing your HTML has never been easier.