<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet href="/rss-style.xsl" type="text/xsl"?><rss version="2.0"><channel><title>w3c.wiki — independent encyclopedia of W3C web standards</title><description>Reference cards for HTML, CSS, JavaScript Web APIs, WCAG, ARIA, security, performance. Vendor-neutral. Not affiliated with the World Wide Web Consortium.</description><link>https://w3c.wiki/</link><language>en</language><copyright>Content licensed CC BY-SA 4.0; not affiliated with W3C.</copyright><ttl>1440</ttl><item><title>ARIA tabs pattern</title><link>https://w3c.wiki/aria/tabs/</link><guid isPermaLink="true">https://w3c.wiki/aria/tabs/</guid><description>The tabs pattern combines a tablist of tab controls with corresponding tabpanels. Choose between manual and automatic activation; both are spec-compliant but have different keyboard semantics.</description><pubDate>Tue, 28 Apr 2026 00:00:00 GMT</pubDate><category>aria</category><category>aria</category><category>tabs</category><category>tablist</category><category>tabpanel</category><author>Editorial team</author></item><item><title>CSS color-mix() and relative colour syntax</title><link>https://w3c.wiki/css/color-mix/</link><guid isPermaLink="true">https://w3c.wiki/css/color-mix/</guid><description>color-mix() interpolates between two colours in a chosen colour space, replacing pre-processor colour utilities. Combined with the relative colour syntax it removes most need for a JavaScript colour library.</description><pubDate>Tue, 28 Apr 2026 00:00:00 GMT</pubDate><category>css</category><category>css</category><category>color</category><category>color-mix</category><category>oklch</category><author>Editorial team</author></item><item><title>CSS scroll-driven animations</title><link>https://w3c.wiki/css/scroll-driven-animations/</link><guid isPermaLink="true">https://w3c.wiki/css/scroll-driven-animations/</guid><description>animation-timeline: scroll() and view() drive a CSS animation by scroll position rather than by time. Replaces a long history of IntersectionObserver + JavaScript animation code for parallax, progress bars, and reveal effects.</description><pubDate>Tue, 28 Apr 2026 00:00:00 GMT</pubDate><category>css</category><category>css</category><category>scroll</category><category>animation</category><category>timeline</category><author>Editorial team</author></item><item><title>CSS @supports — feature queries</title><link>https://w3c.wiki/css/supports/</link><guid isPermaLink="true">https://w3c.wiki/css/supports/</guid><description>@supports tests for CSS feature support at parse time, letting authors ship modern CSS to capable engines and a tested fallback to older ones. Replaces the @media (-webkit-...) hacks of 2010-era CSS.</description><pubDate>Tue, 28 Apr 2026 00:00:00 GMT</pubDate><category>css</category><category>css</category><category>supports</category><category>feature query</category><category>fallback</category><author>Editorial team</author></item><item><title>The HTML &lt;button&gt; element</title><link>https://w3c.wiki/html/button/</link><guid isPermaLink="true">https://w3c.wiki/html/button/</guid><description>&lt;button&gt; is the right element for any user-action affordance. Three type values, optional form integration, and the 2024 commandfor / command attributes for declarative popover and dialog control.</description><pubDate>Tue, 28 Apr 2026 00:00:00 GMT</pubDate><category>html</category><category>html</category><category>button</category><category>form</category><category>command</category><author>Editorial team</author></item><item><title>&lt;picture&gt;, srcset, and responsive images</title><link>https://w3c.wiki/html/picture/</link><guid isPermaLink="true">https://w3c.wiki/html/picture/</guid><description>&lt;picture&gt; with &lt;source&gt; and srcset selects the best image for the viewport, pixel density, and supported format. The replacement for the JavaScript-shimmed responsive-image patterns of 2014–2018.</description><pubDate>Tue, 28 Apr 2026 00:00:00 GMT</pubDate><category>html</category><category>html</category><category>picture</category><category>srcset</category><category>responsive images</category><category>performance</category><author>Editorial team</author></item><item><title>HTML &lt;table&gt; for data, with accessible headers</title><link>https://w3c.wiki/html/table/</link><guid isPermaLink="true">https://w3c.wiki/html/table/</guid><description>&lt;table&gt; is the right element for tabular data and only tabular data. Correct use of &lt;caption&gt;, &lt;thead&gt;, &lt;th scope&gt;, and &lt;td headers&gt; is the difference between an accessible table and a grid of unrelated cells.</description><pubDate>Tue, 28 Apr 2026 00:00:00 GMT</pubDate><category>html</category><category>html</category><category>table</category><category>accessibility</category><category>data</category><author>Editorial team</author></item><item><title>ResizeObserver: element-level layout reactivity</title><link>https://w3c.wiki/js/resize-observer/</link><guid isPermaLink="true">https://w3c.wiki/js/resize-observer/</guid><description>ResizeObserver fires a callback when an observed element&apos;s content-box, border-box, or device-pixel size changes. The right primitive for component-level responsive behaviour, replacing window-resize listeners.</description><pubDate>Tue, 28 Apr 2026 00:00:00 GMT</pubDate><category>js</category><category>javascript</category><category>resize observer</category><category>responsive</category><category>layout</category><author>Editorial team</author></item><item><title>structuredClone() and the structured-clone algorithm</title><link>https://w3c.wiki/js/structured-clone/</link><guid isPermaLink="true">https://w3c.wiki/js/structured-clone/</guid><description>structuredClone() deep-copies almost any object, including Maps, Sets, ArrayBuffers, and cyclic graphs, in one platform-native call. Replaces the JSON.parse(JSON.stringify(x)) idiom and most third-party clone libraries.</description><pubDate>Tue, 28 Apr 2026 00:00:00 GMT</pubDate><category>js</category><category>javascript</category><category>structured clone</category><category>deep copy</category><category>transfer</category><author>Editorial team</author></item><item><title>Core Web Vitals: LCP, INP, CLS</title><link>https://w3c.wiki/perf/core-web-vitals/</link><guid isPermaLink="true">https://w3c.wiki/perf/core-web-vitals/</guid><description>Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift are the three field-measured metrics Google uses for the Page Experience signal. Targets: 2.5s, 200ms, 0.1.</description><pubDate>Tue, 28 Apr 2026 00:00:00 GMT</pubDate><category>perf</category><category>performance</category><category>core web vitals</category><category>lcp</category><category>inp</category><category>cls</category><author>Editorial team</author></item><item><title>Subresource Integrity (SRI)</title><link>https://w3c.wiki/security/subresource-integrity/</link><guid isPermaLink="true">https://w3c.wiki/security/subresource-integrity/</guid><description>SRI protects pages from compromised CDNs by pinning the cryptographic hash of an external script or stylesheet. The browser refuses to execute a resource whose hash does not match the integrity attribute.</description><pubDate>Tue, 28 Apr 2026 00:00:00 GMT</pubDate><category>security</category><category>security</category><category>sri</category><category>integrity</category><category>cdn</category><category>supply chain</category><author>Editorial team</author></item><item><title>WCAG 1.3.1 Info and Relationships</title><link>https://w3c.wiki/wcag/2.2/a/1.3.1</link><guid isPermaLink="true">https://w3c.wiki/wcag/2.2/a/1.3.1</guid><description>Information, structure, and relationships conveyed through presentation must also be programmatically determinable. The criterion that powers headings, lists, table headers, and form-label association.</description><pubDate>Tue, 28 Apr 2026 00:00:00 GMT</pubDate><category>wcag</category><category>wcag</category><category>structure</category><category>relationships</category><category>semantics</category><category>accessibility</category><author>Editorial team</author></item><item><title>WCAG 1.4.11 Non-text Contrast</title><link>https://w3c.wiki/wcag/2.2/aa/1.4.11</link><guid isPermaLink="true">https://w3c.wiki/wcag/2.2/aa/1.4.11</guid><description>User-interface components and graphical objects required to understand the content must have a contrast ratio of at least 3:1 against adjacent colours. Level AA; the criterion that catches under-styled focus rings, icon-only buttons, and chart strokes.</description><pubDate>Tue, 28 Apr 2026 00:00:00 GMT</pubDate><category>wcag</category><category>wcag</category><category>contrast</category><category>non-text</category><category>ui</category><category>accessibility</category><author>Editorial team</author></item><item><title>WCAG 2.1.1 Keyboard</title><link>https://w3c.wiki/wcag/2.2/a/2.1.1</link><guid isPermaLink="true">https://w3c.wiki/wcag/2.2/a/2.1.1</guid><description>Every functionality available with a pointer must also be available with the keyboard alone, without requiring specific timings for individual keystrokes. Level A; the foundation of every keyboard-accessible widget.</description><pubDate>Tue, 28 Apr 2026 00:00:00 GMT</pubDate><category>wcag</category><category>wcag</category><category>keyboard</category><category>accessibility</category><category>focus</category><author>Editorial team</author></item><item><title>WCAG 3.3.8 Accessible Authentication (Minimum)</title><link>https://w3c.wiki/wcag/2.2/aa/3.3.8</link><guid isPermaLink="true">https://w3c.wiki/wcag/2.2/aa/3.3.8</guid><description>Authentication must not depend solely on a cognitive function test (memorise, transcribe). New in WCAG 2.2 at Level AA. Affects password fields, captcha challenges, and SMS code transcription.</description><pubDate>Tue, 28 Apr 2026 00:00:00 GMT</pubDate><category>wcag</category><category>wcag</category><category>authentication</category><category>password</category><category>captcha</category><category>accessibility</category><author>Editorial team</author></item><item><title>ARIA states and properties</title><link>https://w3c.wiki/aria/states-and-properties/</link><guid isPermaLink="true">https://w3c.wiki/aria/states-and-properties/</guid><description>ARIA states (such as aria-checked) and properties (such as aria-label) carry the dynamic and static metadata of a widget. Authors of any non-native widget must update them as the user interacts.</description><pubDate>Mon, 27 Apr 2026 00:00:00 GMT</pubDate><category>aria</category><category>aria</category><category>state</category><category>property</category><category>accessibility</category><author>Editorial team</author></item><item><title>HTML &lt;form&gt; element and submission semantics</title><link>https://w3c.wiki/html/form/</link><guid isPermaLink="true">https://w3c.wiki/html/form/</guid><description>&lt;form&gt; wraps a set of controls and defines how they are submitted. Knowing the difference between native validation, the FormData API, and constraint validation prevents most form bugs.</description><pubDate>Mon, 27 Apr 2026 00:00:00 GMT</pubDate><category>html</category><category>html</category><category>form</category><category>validation</category><category>submission</category><author>Editorial team</author></item><item><title>ARIA landmark roles and structure</title><link>https://w3c.wiki/aria/landmarks/</link><guid isPermaLink="true">https://w3c.wiki/aria/landmarks/</guid><description>Landmark roles let assistive-technology users navigate a page by region: banner, main, navigation, complementary, contentinfo, search, form, region. Most have native HTML equivalents.</description><pubDate>Mon, 27 Apr 2026 00:00:00 GMT</pubDate><category>aria</category><category>aria</category><category>landmark</category><category>navigation</category><category>structure</category><author>Editorial team</author></item><item><title>ARIA roles: a vocabulary for assistive technology</title><link>https://w3c.wiki/aria/roles/</link><guid isPermaLink="true">https://w3c.wiki/aria/roles/</guid><description>ARIA roles describe what an element is to assistive technology. Native HTML elements come with implicit roles; ARIA lets authors declare a role explicitly for custom widgets.</description><pubDate>Mon, 27 Apr 2026 00:00:00 GMT</pubDate><category>aria</category><category>aria</category><category>role</category><category>accessibility</category><category>assistive technology</category><author>Editorial team</author></item><item><title>The HTML &lt;dialog&gt; element</title><link>https://w3c.wiki/html/dialog/</link><guid isPermaLink="true">https://w3c.wiki/html/dialog/</guid><description>&lt;dialog&gt; is the native HTML modal and non-modal dialog element. It manages focus trapping, the top layer, and inert background, replacing many ad-hoc modal libraries.</description><pubDate>Mon, 27 Apr 2026 00:00:00 GMT</pubDate><category>html</category><category>html</category><category>dialog</category><category>modal</category><category>accessibility</category><author>Editorial team</author></item><item><title>CSS color spaces and contrast</title><link>https://w3c.wiki/css/color-contrast/</link><guid isPermaLink="true">https://w3c.wiki/css/color-contrast/</guid><description>CSS Color 4 brings device-independent colour spaces (display-p3, lch, oklch) and the relative-colour syntax. Picking colours in a perceptually uniform space makes contrast tuning predictable.</description><pubDate>Mon, 27 Apr 2026 00:00:00 GMT</pubDate><category>css</category><category>css</category><category>color</category><category>contrast</category><category>lch</category><category>oklch</category><author>Editorial team</author></item><item><title>CSS layout primitives: flow, flex, grid, container</title><link>https://w3c.wiki/css/layout-primitives/</link><guid isPermaLink="true">https://w3c.wiki/css/layout-primitives/</guid><description>Modern CSS layout is built from four primitives: normal flow, flexbox, grid, and container queries. Knowing which to reach for is the largest determinant of layout quality.</description><pubDate>Mon, 27 Apr 2026 00:00:00 GMT</pubDate><category>css</category><category>css</category><category>layout</category><category>flexbox</category><category>grid</category><category>container queries</category><author>Editorial team</author></item><item><title>HTML semantic elements</title><link>https://w3c.wiki/html/semantic-elements/</link><guid isPermaLink="true">https://w3c.wiki/html/semantic-elements/</guid><description>HTML&apos;s semantic vocabulary — header, nav, main, article, section, aside, figure, footer — encodes structure that browsers, search engines, and assistive technology rely on.</description><pubDate>Mon, 27 Apr 2026 00:00:00 GMT</pubDate><category>html</category><category>html</category><category>semantic</category><category>structure</category><category>sectioning</category><author>Editorial team</author></item><item><title>Fetch API: requests, responses, streaming, and abort</title><link>https://w3c.wiki/js/fetch-api/</link><guid isPermaLink="true">https://w3c.wiki/js/fetch-api/</guid><description>Fetch is the modern HTTP client built into the platform. It exposes Request, Response, AbortSignal, ReadableStream, and FormData as primitives that compose with the rest of the platform.</description><pubDate>Mon, 27 Apr 2026 00:00:00 GMT</pubDate><category>js</category><category>fetch</category><category>http</category><category>abort</category><category>stream</category><author>Editorial team</author></item><item><title>Service workers: registration, lifecycle, fetch handling</title><link>https://w3c.wiki/js/service-worker/</link><guid isPermaLink="true">https://w3c.wiki/js/service-worker/</guid><description>A service worker is a programmable network proxy controlled by the page&apos;s origin. It enables offline, background sync, and push, but introduces a lifecycle that can outlive the page.</description><pubDate>Mon, 27 Apr 2026 00:00:00 GMT</pubDate><category>js</category><category>service worker</category><category>offline</category><category>cache</category><category>fetch</category><author>Editorial team</author></item><item><title>Web Components: custom-element lifecycle and slots</title><link>https://w3c.wiki/js/web-components-lifecycle/</link><guid isPermaLink="true">https://w3c.wiki/js/web-components-lifecycle/</guid><description>A custom element&apos;s lifecycle is defined by four user-agent callbacks plus three observable transitions. Knowing them is the difference between a robust component and one that leaks.</description><pubDate>Mon, 27 Apr 2026 00:00:00 GMT</pubDate><category>js</category><category>web components</category><category>custom elements</category><category>shadow dom</category><category>slots</category><author>Editorial team</author></item><item><title>WCAG 1.4.3 Contrast (Minimum)</title><link>https://w3c.wiki/wcag/2.2/aa/1.4.3</link><guid isPermaLink="true">https://w3c.wiki/wcag/2.2/aa/1.4.3</guid><description>Visual presentation of text and images of text must have a contrast ratio of at least 4.5:1, with documented exceptions for large text, incidental text, and logotypes.</description><pubDate>Mon, 27 Apr 2026 00:00:00 GMT</pubDate><category>wcag</category><category>wcag</category><category>contrast</category><category>accessibility</category><category>colour</category><category>luminance</category><author>Editorial team</author></item><item><title>WCAG 2.4.7 Focus Visible</title><link>https://w3c.wiki/wcag/2.2/aa/2.4.7</link><guid isPermaLink="true">https://w3c.wiki/wcag/2.2/aa/2.4.7</guid><description>Any keyboard-operable interface must show a visible indicator on the focused element. The indicator must be perceivable and reliable across keyboard, switch, and voice control inputs.</description><pubDate>Mon, 27 Apr 2026 00:00:00 GMT</pubDate><category>wcag</category><category>wcag</category><category>focus</category><category>keyboard</category><category>accessibility</category><author>Editorial team</author></item><item><title>CSS :has() — the parent selector</title><link>https://w3c.wiki/css/has-selector/</link><guid isPermaLink="true">https://w3c.wiki/css/has-selector/</guid><description>:has(...) matches an element if any of its descendants match the inner selector. The first general-purpose &apos;parent&apos; selector in CSS, with quadratic-time pitfalls if used carelessly.</description><pubDate>Mon, 27 Apr 2026 00:00:00 GMT</pubDate><category>css</category><category>css</category><category>has</category><category>selectors</category><category>parent selector</category><author>Editorial team</author></item><item><title>ARIA combobox pattern</title><link>https://w3c.wiki/aria/combobox/</link><guid isPermaLink="true">https://w3c.wiki/aria/combobox/</guid><description>The combobox pattern combines a single-line text input with a popup listbox, tree, grid, or dialog. The 1.2 spec requires aria-expanded, aria-controls, and either aria-activedescendant or focus-managed selection.</description><pubDate>Mon, 27 Apr 2026 00:00:00 GMT</pubDate><category>aria</category><category>aria</category><category>combobox</category><category>autocomplete</category><category>listbox</category><author>Editorial team</author></item><item><title>CSS @layer — explicit cascade layers</title><link>https://w3c.wiki/css/cascade-layers/</link><guid isPermaLink="true">https://w3c.wiki/css/cascade-layers/</guid><description>@layer creates named, ordered slots in the cascade so authors can predict which rule wins without specificity wars or !important escalation. The single largest improvement to cascade authoring since custom properties.</description><pubDate>Mon, 27 Apr 2026 00:00:00 GMT</pubDate><category>css</category><category>css</category><category>cascade</category><category>@layer</category><category>specificity</category><author>Editorial team</author></item><item><title>HTML &lt;details&gt; and &lt;summary&gt;</title><link>https://w3c.wiki/html/details/</link><guid isPermaLink="true">https://w3c.wiki/html/details/</guid><description>&lt;details&gt; is the native disclosure widget. The 2024 name attribute lets a group of &lt;details&gt; behave as an exclusive accordion. Replaces a long history of ad-hoc collapsible-panel JavaScript.</description><pubDate>Mon, 27 Apr 2026 00:00:00 GMT</pubDate><category>html</category><category>html</category><category>details</category><category>summary</category><category>disclosure</category><category>accordion</category><author>Editorial team</author></item><item><title>CSS View Transitions</title><link>https://w3c.wiki/css/view-transitions/</link><guid isPermaLink="true">https://w3c.wiki/css/view-transitions/</guid><description>View Transitions snapshot the page before and after a state change, then animate between the two snapshots. The single API turns &apos;navigation requires a SPA framework&apos; into &apos;add five lines of CSS&apos;.</description><pubDate>Mon, 27 Apr 2026 00:00:00 GMT</pubDate><category>css</category><category>css</category><category>view transitions</category><category>animation</category><category>navigation</category><author>Editorial team</author></item><item><title>AbortController and AbortSignal</title><link>https://w3c.wiki/js/abort-controller/</link><guid isPermaLink="true">https://w3c.wiki/js/abort-controller/</guid><description>AbortController is the platform&apos;s standard cancellation primitive. AbortSignal flows through fetch, addEventListener, streams, and most async platform APIs added since 2019.</description><pubDate>Mon, 27 Apr 2026 00:00:00 GMT</pubDate><category>js</category><category>javascript</category><category>abort</category><category>cancellation</category><category>fetch</category><author>Editorial team</author></item><item><title>IntersectionObserver: visibility-driven loading</title><link>https://w3c.wiki/js/intersection-observer/</link><guid isPermaLink="true">https://w3c.wiki/js/intersection-observer/</guid><description>IntersectionObserver fires a callback when a target element enters or leaves a viewport-relative root, with configurable thresholds. The right primitive for lazy-load, infinite-scroll, and sticky-state detection.</description><pubDate>Mon, 27 Apr 2026 00:00:00 GMT</pubDate><category>js</category><category>javascript</category><category>intersection observer</category><category>lazy load</category><category>performance</category><author>Editorial team</author></item><item><title>Content Security Policy: directives, nonces, and reporting</title><link>https://w3c.wiki/security/content-security-policy/</link><guid isPermaLink="true">https://w3c.wiki/security/content-security-policy/</guid><description>CSP is the response header that tells the browser which scripts, styles, frames, and connects are allowed to run. A correctly authored CSP eliminates whole classes of XSS attacks at the cost of a careful inventory of trusted sources.</description><pubDate>Mon, 27 Apr 2026 00:00:00 GMT</pubDate><category>security</category><category>security</category><category>csp</category><category>xss</category><category>nonce</category><category>header</category><author>Editorial team</author></item><item><title>The HTML &lt;input&gt; element and its types</title><link>https://w3c.wiki/html/input/</link><guid isPermaLink="true">https://w3c.wiki/html/input/</guid><description>&lt;input&gt; with its 22 type values is the most variable element in HTML. Each type carries different validation, keyboard, and platform UI semantics. Picking the right type is the difference between mobile autofill working or not.</description><pubDate>Mon, 27 Apr 2026 00:00:00 GMT</pubDate><category>html</category><category>html</category><category>input</category><category>form</category><category>validation</category><category>autocomplete</category><author>Editorial team</author></item><item><title>WCAG 4.1.2 Name, Role, Value</title><link>https://w3c.wiki/wcag/2.2/a/4.1.2</link><guid isPermaLink="true">https://w3c.wiki/wcag/2.2/a/4.1.2</guid><description>Every UI component built with markup must expose a programmatic name, role, and value, plus state changes via accessibility APIs. The single criterion that underpins every ARIA pattern.</description><pubDate>Mon, 27 Apr 2026 00:00:00 GMT</pubDate><category>wcag</category><category>wcag</category><category>name</category><category>role</category><category>value</category><category>aria</category><author>Editorial team</author></item><item><title>WCAG 2.5.8 Target Size (Minimum)</title><link>https://w3c.wiki/wcag/2.2/aa/2.5.8</link><guid isPermaLink="true">https://w3c.wiki/wcag/2.2/aa/2.5.8</guid><description>Pointer targets must be at least 24 by 24 CSS pixels, with documented exceptions for inline links, equivalent control alternatives, essential UIs, and user-agent default sizing. New in WCAG 2.2.</description><pubDate>Mon, 27 Apr 2026 00:00:00 GMT</pubDate><category>wcag</category><category>wcag</category><category>target size</category><category>tap target</category><category>pointer</category><category>accessibility</category><author>Editorial team</author></item><item><title>WCAG 2.5.7 Dragging Movements</title><link>https://w3c.wiki/wcag/2.2/aa/2.5.7</link><guid isPermaLink="true">https://w3c.wiki/wcag/2.2/aa/2.5.7</guid><description>Any drag-to-do interaction must have a single-pointer, non-drag alternative. New in WCAG 2.2 at Level AA. Reorderable lists, file uploads, and pan/zoom are the most common offenders.</description><pubDate>Mon, 27 Apr 2026 00:00:00 GMT</pubDate><category>wcag</category><category>wcag</category><category>drag</category><category>drop</category><category>pointer</category><category>accessibility</category><author>Editorial team</author></item></channel></rss>