#webstandards

13 posts · Last used Jul 31

The CSS Working Group has published a First Public Working Draft of CSS Linked Parameters Module Level 1. This spec introduces a way to pass CSS values into linked resources, such as SVG images, so that they can be used as CSS custom environment variables in the destination resource. This allows easy reuse of "templated" SVG images, which can be adapted to a site’s theme color, etc. easily, without having to modify the source SVG. https://www.w3.org/news/2026/first-public-working-draft-css-linked-parameters-module-level-1/#CSS #SVG #WebStandards
4
0
9
0
The W3C Team proposes advancing Web Authentication: An API for accessing Public Key Credentials Level 3 to W3C Recommendation. This specification was published by the Web Authentication Working Group as a Candidate Recommendation Snapshot on 26 May 2026. It defines an API enabling the creation and use of strong, attested, scoped, public key-based credentials by web applications, for the purpose of strongly authenticating users. https://www.w3.org/news/2026/proposed-advancement-of-webauthn-3-to-w3c-recommendation/#WebAuthn #WebStandards
10
1
11
0
W3C Invites Implementations of EPUB 3.4, EPUB Reading Systems 3.4 and EPUB Accessibility 1. EPUB® 3 defines a distribution and interchange format for digital publications and documents. EPUB Reading Systems 3.4: This specification defines the conformance requirements for EPUB 3 reading systems. EPUB Accessibility 1.2: This specification specifies content conformance requirements for verifying the accessibility of EPUB® Publications. https://www.w3.org/news/2026/w3c-invites-implementations-of-epub-3-4-epub-reading-systems-3-4-and-epub-accessibility-1-2/#EPUB #a11y #WebStandards
2
0
10
0
The Accessibility Guidelines Working Group has published WCAG Evaluation Methodology (WCAG-EM) 2.0 as a Group Note. This document describes a methodology with a step-by-step process to evaluate how well digital products conform to Web Content Accessibility Guidelines (WCAG) 2. https://www.w3.org/news/2026/group-note-wcag-evaluation-methodology-wcag-em-2-0/#a11y #WebStandards
5
0
15
0
🚀 #dokieli ( https://dokie.li/ ) is a web-based #decentralized article #publishing and #annotation #application and browser extension, built as an #opensource ( https://git.dokie.li/ ) project using #webstandards. dokieli enables individuals and communities to publish, share, and annotate articles using their preferred identities and storage, and you are always free to switch to another application and take your content with you.
12
0
15
0
On the W3C blog: "CSS animations, human rights, and big accessibility at the AB Web Meetup" by @hdv@front-end.social Hidde noted that in early July the @ab@w3c.social held a F2F in Rotterdam 🇳🇱 and organized a get-together with the local developer community. This “Web Meetup” featured three talks looking at web standards in different ways as well as time for the speakers, AB, and the community to mingle. Read more at: https://www.w3.org/blog/2026/css-animations-human-rights-and-big-accessibility-at-the-ab-web-meetup/#WebStandards #CommunityMeetup
24
0
16
1
The @w3c@w3c.social "Standards Vulnerability Disclosure & Handling Process Policy" document explains how to responsibly report #security vulnerabilities in W3C specifications. It defines the process for reporting, acknowledging, verifying, resolving, and disclosing security issues in #WebStandards #GroupNoteDraft ▶️ https://www.w3.org/TR/security-disclosure/ We appreciate researchers helping keep the Web secure by reporting issues in W3C specifications. Feedback welcome: https://github.com/w3c/security-disclosure/issues
4
0
7
0
At the Brussels seminar on Human Rights and ICT Standardization, W3C contributed to the discussion on how human-rights principles can enter technical work while design choices are still open. The post connects Ethical Web Principles, accessibility, horizontal review, threat and harm modeling, and the practical cost of participation: making assumptions, impacts, and responsibilities visible before they become infrastructure. https://www.w3.org/blog/2026/human-rights-and-ict-standardization-what-is-w3c-doing-about-this/#HumanRights #ICTStandardization #WebStandards
5
0
9
0
W3C is pleased to be included in the Forbes Accessibility 200 list for 2026 - along with 18 of our Members - in recognition of the impact @wai@w3c.social has had on the world. We want to thank everyone who contributes to work on Accessibility at W3C. We are grateful to @forbes@flipboard.com and the experts on the advisory panel for recognizing the importance and impact of our work. https://www.forbes.com/companies/w3c-world-wide-web-consortium/?list=accessibility #ForbesAccessibility200 #WebStandards
14
0
19
1
The Linked Web Storage Working Group has published the following four First Public Working Drafts: LWS 1.0 Authentication Suite: OpenID Connect, LWS 1.0 Authentication Suite: SAML 2.0, LWS 1.0 Authentication Suite, and LWS 1.0 Authentication Suite. These enable LWS applications to integrate with OpenID providers, with SAML 2.0 identity providers and clients that are able to sign their own identity tokens. Learn more at: https://www.w3.org/news/2026/first-public-working-drafts-for-the-linked-web-storage-lws-1-0-authentication-suite/#WebStandards #LinkedWebStorage
10
0
10
0
The JSON-LD Working Group published a First Public Working Draft of CBOR-LD 1.0. This spec defines CBOR-LD 1.0, a CBOR-based format to serialize Linked Data. The encoding is designed to leverage the existing JSON-LD ecosystem, which is deployed on hundreds of millions of systems today, to provide a compact serialization format for those seeking efficient encoding schemes for Linked Data. https://www.w3.org/news/2026/first-public-working-draft-cbor-ld-1-0/#WebStandards #LinkedData
8
1
11
0
You've seen all posts