If you are interested in how the Fediverse really works and some of the key people making it happen, sit down with a coffee and check out one (or all!) of the presentations from #fedicon.

Mine was about my journey finding the Fediverse and eventually teaming up with folks to create socialbc.ca and what I learned along the way.

And yes, I am pretty sure we are in a Stanley Kubrick movie.
#fediverse #mastodon #socialbc #democracy #webstandards #activitypub #community
https://spectra.video/w/p9nScG9XFX81iE89ufmWUM

Good news everyone!

We are extremely thankful and excited to be supported once again by @nlnet to work on our roadmap ( https://dokie.li/docs#roadmap ) as part of NGI Zero Commons Fund.

Read the announcement:

https://nlnet.nl/news/2025/20250804-announcement-grants-CommonsFund.html

The project:

https://nlnet.nl/project/Dokieli-Collaborative/

This time we will focus on these tasks:

* End-to-end encryption
* Collaborative editing
* Code modularization
* Internationalization
* Browser extension improvements

How to hide HTML element A from ScreenReader but let i be accessible to keyboard users?

Tools to check #Accessibility nag me, telling it is not allowed to use HTML like this:

<a href="/" aria-hidden="true">Read more…</a>

Solvable problem?

The Vision for W3C has been officially published as a ratified W3C Statement: https://www.w3.org/TR/2025/STMT-w3c-vision-20250729/

As one of the editors, along with Chris Wilson (@cwilso.com @c@w3c.social), I’m both proud of this multi-year W3C Advisory Board (AB) effort, and grateful to everyone who contributed and gave feedback that helped improve the document.

Writing down and openly publishing our collective values and principles is an important step forward for W3C. We now have a shared reference to both guide our priorities and cite to help resolve differences in opinion (rather than having to appeal to authority).

The AB (@w3.org/wiki/AB @ab@w3c.social) has prioritized work on the Vision project for many years (https://www.w3.org/wiki/AB/Vision), and personally, co-leading this project during my time on the AB has been inspiring, challenging, and a source of many lessons learned. Lots more to share on all that. For now, happy to take a moment to celebrate this milestone.

#w3cVision #VisionForW3C #WorldWideWeb #W3C (@w3.org @w3c@w3c.social)
#openWeb #webStandards

Previously:
* https://tantek.com/2025/100/t1/vision-for-w3c-please-vote

More posts:
* https://www.w3.org/news/2025/vision-for-w3c-is-a-w3c-statement/
* https://www.w3.org/blog/2025/vision-for-w3c-a-manifesto-for-our-operations-and-decision-making/

Advocacy group Movement for an Open Web (MOW) files complaint with UK CMA against W3C's push to kill third-party cookies , accusing it of favoring Google and harming smaller publishers #WebStandards #Privacy #TechCompetition #W3C #Cookies #Google https://www.theregister.com/2025/07/29/mow_w3c_cookie_complaint/
#newz

And here I am with a spicy take on the <hgroup> HTML element of all things.

Is the <hgroup> element redundant and should we handle headings and subheadings differently instead of re-introducing the element?

https://aldavigdis.dev/2025/07/25/taming-html-headings-subheadings-and-overlines/

Just published: “Designing with Abstractions: CSS and the Case of Masonry Layouts”

This (academic) article explores CSS as both a technical system and a design object. It examines how this is shaped through negotiation between conceptual models, implementation constraints, and interface considerations, focusing on the Masonry layout debates.

Appreciation to those participating in CSS WG debates and making this work visible.

→ https://journal.dampress.org/issues/design-et-abstractions/designing-with-abstractions-css-and-the-case-of-masonry-layouts

When applying a thick border around an element in multiple colors, the corners meet at a 45-degree angle forming a diamond. That is established and seems reasonable.

But, when you set a thick edge on one side, the thin 1px border gets squeezed into a slope, and won't reach the edge! And the sidebar forms a *trapezoid*!

This is most noticable on modern high-DPI screens. It is rather unsatisfying, and hard to unsee...

Example:
https://en.wikipedia.org/wiki/Template:Cleanup

Wenn „Developer“ den Plain-Text-Teil einer E-Mail „vergessen“ und stattdessen den Rest für Dokumentation missbrauchen, sehen Menschen wie ich, die keine HTML-Mails lesen wollen, und Menschen, die darauf angewiesen sind, oft gar nichts mehr.

Ich merke das auch im Alltag: Vor 20 Jahren war es selbstverständlich, einen Plain-Text-Teil bereitzustellen. Heute denken viele nur noch: „Hat doch eh jeder HTML-Mails.“

Meanwhile the discussion on defining "view"rumbles on: 52 comments · 137 replies

I have largely stayed out of it as I have other more pressing shit to do.

#WCAG #a11y #webStandards #endless

https://github.com/w3c/wcag3/discussions/286

Interview with Lola Odelola @lolaodelola

"Lola Odelola is a force to be reckoned with. Which is why TetraLogical are delighted to sponsor her work on the W3C Technical Architecture Group (TAG)"

#ARIA #AT #a11y #WebStandards

https://tetralogical.com/blog/2025/07/02/interview-with-lola-odelola/

#Development #Previews
Kelp · A customizable UI library that needs no build step https://ilo.im/164ypi

_____
#Library #HTML #CSS #WebComponents #CDN #WebStandards #WebDev #Frontend

The Web's superpower is its openness. Native JS templating makes JS more ergonomic. Direct WASM→DOM makes the web more OPEN. Which better serves the platform's future? The web shouldn't privilege one language. True platform evolution means equal access to core capabilities for all languages. That's how we get the next generation of web innovation. #compsci #webdev #webstandards #opensource

What are your favorite blogs about the #web, #webdev, and #webstandards?

(sorry about the hashtags, trying to cast a wider net)

Having had my head in an EAA assessment for the past month i missed this discussion until now

#WCAG #WCAG3 #a11y #WebStandards

Scheduling Approach Alternatives

https://github.com/w3c/wcag3/discussions/322#

File encryption with a browser.

I've been exploring the #WebCryptoAPI and I'm impressed!

When combined with the #FileSystemAPI, it offers a seemingly secure way to #encrypt and #store files directly on your device. Think #localstorage, but with #encryption!

I know #webapps can have #security vulnerabilities since the code is served over the web, so I've #OpenSourced my demo! You can check it out, and it should even work if #selfhosted on #GitHubPages.

Live Demo: https://dim.positive-intentions.com/?path=/story/usefs--encrypted-demo

Demo Code: https://github.com/positive-intentions/dim/blob/staging/src/stories/05-Hooks-useFS.stories.js

Hook Code: https://github.com/positive-intentions/dim/blob/staging/src/hooks/useFS.js

IMPORTANT NOTES (PLEASE READ!):
* This is NOT a product. It's for #testing and #demonstration purposes only.
* It has NOT been reviewed or audited. Do NOT use for sensitive data.
* The "password encryption" currently uses a hardcoded password. This is for demonstration, not security.
* This is NOT meant to replace robust solutions like #VeraCrypt. It's just a #proofofconcept to show what's possible with #browser #APIs.

You'd think Google, having launched schema.org, knows how to produce valid schema.org metadata and HTML5.

YouTube: How about a `<span>` inside the head, and `<link rel=alternative>` inside the body?

HTML5 parsers:
Thanks, I'll take that span as your implied end of `<head>`, and raise you an implied start of `<body>`. Everything that follows is now part of the body.

Context:
https://github.com/Ranchero-Software/NetNewsWire/issues/902#issuecomment-2990075755