#web-standards — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #web-standards, aggregated by home.social.
-
🍺 (the return of) Tables, Tequila and Beer
scope attribute is largely redundant
#a11y #html #webStandardshttps://html5accessibility.com/stuff/2020/12/22/the-return-of-tables-tequila-and-beer/
-
🍺 (the return of) Tables, Tequila and Beer
scope attribute is largely redundant
#a11y #html #webStandardshttps://html5accessibility.com/stuff/2020/12/22/the-return-of-tables-tequila-and-beer/
-
🍺 (the return of) Tables, Tequila and Beer
scope attribute is largely redundant
#a11y #html #webStandardshttps://html5accessibility.com/stuff/2020/12/22/the-return-of-tables-tequila-and-beer/
-
🍺 (the return of) Tables, Tequila and Beer
scope attribute is largely redundant
#a11y #html #webStandardshttps://html5accessibility.com/stuff/2020/12/22/the-return-of-tables-tequila-and-beer/
-
🍺 (the return of) Tables, Tequila and Beer
scope attribute is largely redundant
#a11y #html #webStandardshttps://html5accessibility.com/stuff/2020/12/22/the-return-of-tables-tequila-and-beer/
-
The Security Interest Group has published the first draft of a Group Note titled W3C Standards Vulnerability Disclosure & Handling Process and Policy. This document defines how to report suspected security vulnerabilities in W3C standards and specifications (technical reports), so that issues can be triaged, confirmed, and resolved through the appropriate W3C processes.
https://www.w3.org/news/2026/group-note-draft-w3c-standards-vulnerability-disclosure-handling-process-and-policy/
#WebStandards #SecurityVulnerability -
The Security Interest Group has published the first draft of a Group Note titled W3C Standards Vulnerability Disclosure & Handling Process and Policy. This document defines how to report suspected security vulnerabilities in W3C standards and specifications (technical reports), so that issues can be triaged, confirmed, and resolved through the appropriate W3C processes.
https://www.w3.org/news/2026/group-note-draft-w3c-standards-vulnerability-disclosure-handling-process-and-policy/
#WebStandards #SecurityVulnerability -
The Security Interest Group has published the first draft of a Group Note titled W3C Standards Vulnerability Disclosure & Handling Process and Policy. This document defines how to report suspected security vulnerabilities in W3C standards and specifications (technical reports), so that issues can be triaged, confirmed, and resolved through the appropriate W3C processes.
https://www.w3.org/news/2026/group-note-draft-w3c-standards-vulnerability-disclosure-handling-process-and-policy/
#WebStandards #SecurityVulnerability -
The Security Interest Group has published the first draft of a Group Note titled W3C Standards Vulnerability Disclosure & Handling Process and Policy. This document defines how to report suspected security vulnerabilities in W3C standards and specifications (technical reports), so that issues can be triaged, confirmed, and resolved through the appropriate W3C processes.
https://www.w3.org/news/2026/group-note-draft-w3c-standards-vulnerability-disclosure-handling-process-and-policy/
#WebStandards #SecurityVulnerability -
The Security Interest Group has published the first draft of a Group Note titled W3C Standards Vulnerability Disclosure & Handling Process and Policy. This document defines how to report suspected security vulnerabilities in W3C standards and specifications (technical reports), so that issues can be triaged, confirmed, and resolved through the appropriate W3C processes.
https://www.w3.org/news/2026/group-note-draft-w3c-standards-vulnerability-disclosure-handling-process-and-policy/
#WebStandards #SecurityVulnerability -
The Pointer Events Working Group is pleased to publish Pointer Events Level 3 as a W3C Recommendation. The features in this specification extend or modify those found in Pointer Events, a W3C Recommendation that describes events and related interfaces for handling hardware-agnostic pointer input from devices including a mouse, pen, or touchscreen.
https://www.w3.org/news/2026/pointer-events-level-3-is-now-a-w3c-recommendation/
#PointerEvents #WebStandards -
The Pointer Events Working Group is pleased to publish Pointer Events Level 3 as a W3C Recommendation. The features in this specification extend or modify those found in Pointer Events, a W3C Recommendation that describes events and related interfaces for handling hardware-agnostic pointer input from devices including a mouse, pen, or touchscreen.
https://www.w3.org/news/2026/pointer-events-level-3-is-now-a-w3c-recommendation/
#PointerEvents #WebStandards -
The Pointer Events Working Group is pleased to publish Pointer Events Level 3 as a W3C Recommendation. The features in this specification extend or modify those found in Pointer Events, a W3C Recommendation that describes events and related interfaces for handling hardware-agnostic pointer input from devices including a mouse, pen, or touchscreen.
https://www.w3.org/news/2026/pointer-events-level-3-is-now-a-w3c-recommendation/
#PointerEvents #WebStandards -
The Pointer Events Working Group is pleased to publish Pointer Events Level 3 as a W3C Recommendation. The features in this specification extend or modify those found in Pointer Events, a W3C Recommendation that describes events and related interfaces for handling hardware-agnostic pointer input from devices including a mouse, pen, or touchscreen.
https://www.w3.org/news/2026/pointer-events-level-3-is-now-a-w3c-recommendation/
#PointerEvents #WebStandards -
The Pointer Events Working Group is pleased to publish Pointer Events Level 3 as a W3C Recommendation. The features in this specification extend or modify those found in Pointer Events, a W3C Recommendation that describes events and related interfaces for handling hardware-agnostic pointer input from devices including a mouse, pen, or touchscreen.
https://www.w3.org/news/2026/pointer-events-level-3-is-now-a-w3c-recommendation/
#PointerEvents #WebStandards -
Pointer Events Level 3 is now a #W3C Recommendation: https://www.w3.org/TR/2026/REC-pointerevents3-20260630/
This revision includes new features: altitudeAngle, azimuthAngle, pointerrawupdate event, associated coalesced events, and built-in predicted events.
-
Pointer Events Level 3 is now a #W3C Recommendation: https://www.w3.org/TR/2026/REC-pointerevents3-20260630/
This revision includes new features: altitudeAngle, azimuthAngle, pointerrawupdate event, associated coalesced events, and built-in predicted events.
-
Pointer Events Level 3 is now a #W3C Recommendation: https://www.w3.org/TR/2026/REC-pointerevents3-20260630/
This revision includes new features: altitudeAngle, azimuthAngle, pointerrawupdate event, associated coalesced events, and built-in predicted events.
-
Pointer Events Level 3 is now a #W3C Recommendation: https://www.w3.org/TR/2026/REC-pointerevents3-20260630/
This revision includes new features: altitudeAngle, azimuthAngle, pointerrawupdate event, associated coalesced events, and built-in predicted events.
-
Pointer Events Level 3 is now a #W3C Recommendation: https://www.w3.org/TR/2026/REC-pointerevents3-20260630/
This revision includes new features: altitudeAngle, azimuthAngle, pointerrawupdate event, associated coalesced events, and built-in predicted events.
-
Why sponsor TPAC 2026?
TPAC plays a key role in helping W3C coordinate solutions to technical challenges that extend across working group boundaries. Sponsors can:
✣ Amplify brand visibility and industry leadership
✣ Strengthen relationships and build new ones
✣ Demonstrate commitment to open web standards and the open web
✣ Showcase innovationSee more about sponsoring TPAC 2026 in Dublin, Ireland from 26 to 30 October at:
https://www.w3.org/news-events/tpac/2026/sponsorship/#packages
#SponsorW3C #WebStandards -
Why sponsor TPAC 2026?
TPAC plays a key role in helping W3C coordinate solutions to technical challenges that extend across working group boundaries. Sponsors can:
✣ Amplify brand visibility and industry leadership
✣ Strengthen relationships and build new ones
✣ Demonstrate commitment to open web standards and the open web
✣ Showcase innovationSee more about sponsoring TPAC 2026 in Dublin, Ireland from 26 to 30 October at:
https://www.w3.org/news-events/tpac/2026/sponsorship/#packages
#SponsorW3C #WebStandards -
Why sponsor TPAC 2026?
TPAC plays a key role in helping W3C coordinate solutions to technical challenges that extend across working group boundaries. Sponsors can:
✣ Amplify brand visibility and industry leadership
✣ Strengthen relationships and build new ones
✣ Demonstrate commitment to open web standards and the open web
✣ Showcase innovationSee more about sponsoring TPAC 2026 in Dublin, Ireland from 26 to 30 October at:
https://www.w3.org/news-events/tpac/2026/sponsorship/#packages
#SponsorW3C #WebStandards -
Why sponsor TPAC 2026?
TPAC plays a key role in helping W3C coordinate solutions to technical challenges that extend across working group boundaries. Sponsors can:
✣ Amplify brand visibility and industry leadership
✣ Strengthen relationships and build new ones
✣ Demonstrate commitment to open web standards and the open web
✣ Showcase innovationSee more about sponsoring TPAC 2026 in Dublin, Ireland from 26 to 30 October at:
https://www.w3.org/news-events/tpac/2026/sponsorship/#packages
#SponsorW3C #WebStandards -
Why sponsor TPAC 2026?
TPAC plays a key role in helping W3C coordinate solutions to technical challenges that extend across working group boundaries. Sponsors can:
✣ Amplify brand visibility and industry leadership
✣ Strengthen relationships and build new ones
✣ Demonstrate commitment to open web standards and the open web
✣ Showcase innovationSee more about sponsoring TPAC 2026 in Dublin, Ireland from 26 to 30 October at:
https://www.w3.org/news-events/tpac/2026/sponsorship/#packages
#SponsorW3C #WebStandards -
👉🏽 output: HTML's native live region element by @scottohara
https://www.scottohara.me/blog/2019/07/10/the-output-element.html
-
👉🏽 output: HTML's native live region element by @scottohara
https://www.scottohara.me/blog/2019/07/10/the-output-element.html
-
👉🏽 output: HTML's native live region element by @scottohara
https://www.scottohara.me/blog/2019/07/10/the-output-element.html
-
👉🏽 output: HTML's native live region element by @scottohara
https://www.scottohara.me/blog/2019/07/10/the-output-element.html
-
👉🏽 output: HTML's native live region element by @scottohara
https://www.scottohara.me/blog/2019/07/10/the-output-element.html
-
⌨️Does this work for you?
https://codepen.io/stevef/pen/VYPWoqJ
Expected behaviour: the characters remaining "<output> text" is announced when a screen reader user pauses input into the <textarea>
-
⌨️Does this work for you?
https://codepen.io/stevef/pen/VYPWoqJ
Expected behaviour: the characters remaining "<output> text" is announced when a screen reader user pauses input into the <textarea>
-
⌨️Does this work for you?
https://codepen.io/stevef/pen/VYPWoqJ
Expected behaviour: the characters remaining "<output> text" is announced when a screen reader user pauses input into the <textarea>
-
⌨️Does this work for you?
https://codepen.io/stevef/pen/VYPWoqJ
Expected behaviour: the characters remaining "<output> text" is announced when a screen reader user pauses input into the <textarea>
-
⌨️Does this work for you?
https://codepen.io/stevef/pen/VYPWoqJ
Expected behaviour: the characters remaining "<output> text" is announced when a screen reader user pauses input into the <textarea>
-
Sharing this not because it’s about AI/LLMs but because it’s solid advice and the recommendations work equally well for *people* coding web applications (funny that, almost like these things were made by people for people or something).
TL;DR: Use web and platform standards; don’t reinvent the wheel.
-
Sharing this not because it’s about AI/LLMs but because it’s solid advice and the recommendations work equally well for *people* coding web applications (funny that, almost like these things were made by people for people or something).
TL;DR: Use web and platform standards; don’t reinvent the wheel.
-
Sharing this not because it’s about AI/LLMs but because it’s solid advice and the recommendations work equally well for *people* coding web applications (funny that, almost like these things were made by people for people or something).
TL;DR: Use web and platform standards; don’t reinvent the wheel.
-
Sharing this not because it’s about AI/LLMs but because it’s solid advice and the recommendations work equally well for *people* coding web applications (funny that, almost like these things were made by people for people or something).
TL;DR: Use web and platform standards; don’t reinvent the wheel.
-
Sharing this not because it’s about AI/LLMs but because it’s solid advice and the recommendations work equally well for *people* coding web applications (funny that, almost like these things were made by people for people or something).
TL;DR: Use web and platform standards; don’t reinvent the wheel.
-
#Development #Findings
What’s missing from SVG · Styling external SVGs is the top request https://ilo.im/16e0tv_____
#SVG #WebStandards #Design #WebDesign #WebDev #Frontend -
#Development #Findings
What’s missing from SVG · Styling external SVGs is the top request https://ilo.im/16e0tv_____
#SVG #WebStandards #Design #WebDesign #WebDev #Frontend -
#Development #Findings
What’s missing from SVG · Styling external SVGs is the top request https://ilo.im/16e0tv_____
#SVG #WebStandards #Design #WebDesign #WebDev #Frontend -
#Development #Findings
What’s missing from SVG · Styling external SVGs is the top request https://ilo.im/16e0tv_____
#SVG #WebStandards #Design #WebDesign #WebDev #Frontend -
"Web Standards at the Web Engines Hackfest" @igalia's @bkardell and @Meyerweb chatted with W3C interim CEO @dontcallmeDOM about Web Standards, the W3C, and the larger web ecosystem
"..the right place to bring the right people around the table to change online shared ecosystem in a way that...hopefully improves the world in the sense that these values are what we think is needed to make that ecosystem thriving and positive for end users "
https://www.igalia.com/chats/episode-100
#WebStandards -
"Web Standards at the Web Engines Hackfest" @igalia's @bkardell and @Meyerweb chatted with W3C interim CEO @dontcallmeDOM about Web Standards, the W3C, and the larger web ecosystem
"..the right place to bring the right people around the table to change online shared ecosystem in a way that...hopefully improves the world in the sense that these values are what we think is needed to make that ecosystem thriving and positive for end users "
https://www.igalia.com/chats/episode-100
#WebStandards -
"Web Standards at the Web Engines Hackfest" @igalia's @bkardell and @Meyerweb chatted with W3C interim CEO @dontcallmeDOM about Web Standards, the W3C, and the larger web ecosystem
"..the right place to bring the right people around the table to change online shared ecosystem in a way that...hopefully improves the world in the sense that these values are what we think is needed to make that ecosystem thriving and positive for end users "
https://www.igalia.com/chats/episode-100
#WebStandards -
"Web Standards at the Web Engines Hackfest" @igalia's @bkardell and @Meyerweb chatted with W3C interim CEO @dontcallmeDOM about Web Standards, the W3C, and the larger web ecosystem
"..the right place to bring the right people around the table to change online shared ecosystem in a way that...hopefully improves the world in the sense that these values are what we think is needed to make that ecosystem thriving and positive for end users "
https://www.igalia.com/chats/episode-100
#WebStandards -
"Web Standards at the Web Engines Hackfest" @igalia's @bkardell and @Meyerweb chatted with W3C interim CEO @dontcallmeDOM about Web Standards, the W3C, and the larger web ecosystem
"..the right place to bring the right people around the table to change online shared ecosystem in a way that...hopefully improves the world in the sense that these values are what we think is needed to make that ecosystem thriving and positive for end users "
https://www.igalia.com/chats/episode-100
#WebStandards
