If anyone is going to TPAC, there is a session on extending ActivityPub to accommodate private groups https://www.w3.org/events/meetings/e94352d9-97c8-40ac-8518-535431f6b0b2/

If anyone is going to TPAC, there is a session on extending ActivityPub to accommodate private groups https://www.w3.org/events/meetings/e94352d9-97c8-40ac-8518-535431f6b0b2/
#Design #Outlooks
A different future for accessibility · Why the W3C is rebuilding its successful WCAG standard ilo.im/16h0w8 by Léonie Watson
_____
#Accessibility #Conformance #WCAG #WCAG2 #WCAG3 #W3C #WebDesign #Development #WebDev #Frontend
Are my colors in the acceptable contrast range?
#w3c #universaldesign #cvd #drsign #uxdesign #graphicdesign #contrast #wcag
Which encoding names epubcheck's XML parser rejects follows no rule, so I tested all 341 it knows. 770 test books in all, and epubveri reports the same message IDs on every one, bar two known differences.
None of the 562 books on my shelf changed.
Fewer repeats too: a file missing from the manifest is one error, not one per page.
Every change was checked against epubcheck 5.4.0 on more than 700 small test cases, finding for finding.
#W3C #publishing #DigitalPublishing #ebookdev #WebAssembly #accessibility
Every SVG element and attribute pair and every keyword went through both tools, tens of thousands of cases: same findings, two documented gaps aside. Two false reports are gone, e.g. fill-rule with spaces around it.
How We Want to Make WCAG Better, by @[email protected] (@[email protected]):
https://www.youtube.com/watch?v=tDvdzcbo_tU&ref=frontenddogma.com
Its CSS parser, styloria 0.12, follows the CSS Syntax draft W3C published on 1 Oct. Two CSS false positives are gone, and the same book now gives the same report on every run.
On my 544-book shelf: 18 s for all, epubcheck ~18 min.
Think you know WCAG 2.1.1? Adrian Roselli highlights the “specific timings” clause many simplified WCAG guides miss.
#Accessibility #DigitalAccessibility #WCAG #WCAG211 #A11y #WebAccessibility #UX #AccessibilityTesting #W3C
💬 No accessibility for old men – endless tour
I have found a new appetite for talking about #accessibility, #webStandards, #W3C, the #a11y industry, web accessibility history, #AI etc...
Readying my wardrobe for @w3c.bsky.social TPAC at the end of October wearing all @patrickhlauke.bsky.social
#Development #Explorations
Browsers situationship · When browsers agree but the spec doesn’t ilo.im/16gh09 by Rakhi Sharma
_____
#Spec #WebStandards #WebPlatform #Browsers #Interoperability #W3C #WHATWG #History #WebDev #Frontend
Mike [TM] Smith AKA Sideshowbarker – fireside
#w3c #standards #HTML #validation
Available now from wherever you eat your podcasts
Crafting WCAG 3 for More Accessible User Experiences, by @[email protected]:
Along the way I found and fixed four warnings or errors that epubcheck never gives, and one case where epubcheck skips a document, now filed upstream.
#Sigil #calibre #eBookFormatting #webassembly #W3C
WCAG Process for Assigning Levels, by @[email protected]:
https://alastairc.uk/blog/2026/09/wcag-leveling-process/?ref=frontenddogma.com
Le W3C vient de publier une mise à jour des traductions en français des WCAG 2.1 et 2.2, après des mois de travail du comité de traduction piloté par Access42.
Pourquoi cette mise à jour ? Et quels sont les principaux changements ? On vous dit tout !
Mike [TM] Smith AKA Sideshowbarker – fireside
now available on your podcast consumption platform