fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

8.6K
active users

#WebStandards

2 posts1 participant0 posts today
Chris Alemany<p>You can see all the videos that have been uploaded so far on the <a href="https://socialbc.ca/tags/fedicon" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>fedicon</span></a> page here at spectra.video. <a href="https://socialbc.ca/tags/peertube" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>peertube</span></a></p><p><a href="https://spectra.video/c/fedicon_videos/videos" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">spectra.video/c/fedicon_videos</span><span class="invisible">/videos</span></a></p><p> <a href="https://socialbc.ca/tags/fediverse" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>fediverse</span></a> <a href="https://socialbc.ca/tags/mastodon" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>mastodon</span></a> <a href="https://socialbc.ca/tags/socialbc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>socialbc</span></a> <a href="https://socialbc.ca/tags/democracy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>democracy</span></a> <a href="https://socialbc.ca/tags/webstandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webstandards</span></a> <a href="https://socialbc.ca/tags/activitypub" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>activitypub</span></a> <a href="https://socialbc.ca/tags/community" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>community</span></a></p>
Chris Alemany<p>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 <a href="https://socialbc.ca/tags/fedicon" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>fedicon</span></a>.</p><p>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.</p><p>And yes, I am pretty sure we are in a Stanley Kubrick movie.<br><a href="https://socialbc.ca/tags/fediverse" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>fediverse</span></a> <a href="https://socialbc.ca/tags/mastodon" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>mastodon</span></a> <a href="https://socialbc.ca/tags/socialbc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>socialbc</span></a> <a href="https://socialbc.ca/tags/democracy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>democracy</span></a> <a href="https://socialbc.ca/tags/webstandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webstandards</span></a> <a href="https://socialbc.ca/tags/activitypub" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>activitypub</span></a> <a href="https://socialbc.ca/tags/community" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>community</span></a> <br><a href="https://spectra.video/w/p9nScG9XFX81iE89ufmWUM" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">spectra.video/w/p9nScG9XFX81iE</span><span class="invisible">89ufmWUM</span></a></p>
dokieli<p>🎉 Good news everyone!</p><p>We are extremely thankful and excited to be supported once again by <span class="h-card" translate="no"><a href="https://social.nlnet.nl/@nlnet" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>nlnet</span></a></span> to work on our roadmap ( <a href="https://dokie.li/docs#roadmap" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">dokie.li/docs#roadmap</span><span class="invisible"></span></a> ) as part of NGI Zero Commons Fund.</p><p>Read the announcement:</p><p><a href="https://nlnet.nl/news/2025/20250804-announcement-grants-CommonsFund.html" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">nlnet.nl/news/2025/20250804-an</span><span class="invisible">nouncement-grants-CommonsFund.html</span></a></p><p>The project:</p><p><a href="https://nlnet.nl/project/Dokieli-Collaborative/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">nlnet.nl/project/Dokieli-Colla</span><span class="invisible">borative/</span></a></p><p>This time we will focus on these tasks:</p><p>* End-to-end encryption<br>* Collaborative editing<br>* Code modularization<br>* Internationalization<br>* Browser extension improvements</p><p><a href="https://w3c.social/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSource</span></a> <a href="https://w3c.social/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebStandards</span></a> <a href="https://w3c.social/tags/i18n" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>i18n</span></a> <a href="https://w3c.social/tags/e2ee" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>e2ee</span></a></p>
DoctorG ♀️🏳️‍🌈<p>How to hide HTML element A from ScreenReader but let i be accessible to keyboard users?</p><p>Tools to check <a href="https://social.vivaldi.net/tags/Accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Accessibility</span></a> nag me, telling it is not allowed to use HTML like this:</p><p>&lt;a href="/" aria-hidden="true"&gt;Read more…&lt;/a&gt;</p><p>Solvable problem?</p><p><a href="https://social.vivaldi.net/tags/FollowerPower" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FollowerPower</span></a> <a href="https://social.vivaldi.net/tags/Accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Accessibility</span></a> <a href="https://social.vivaldi.net/tags/ARIA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ARIA</span></a> <a href="https://social.vivaldi.net/tags/WAI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WAI</span></a> <a href="https://social.vivaldi.net/tags/HTML" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HTML</span></a> <a href="https://social.vivaldi.net/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebStandards</span></a> <a href="https://social.vivaldi.net/tags/ScreenReader" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ScreenReader</span></a></p>
Aneesh Sathe<p><strong>The Small God of the&nbsp;Internet</strong></p><p>It was a small announcement on an innocuous page about “spring cleaning”. The herald, some guy with the kind of name that promised he was all yours. Four sentences you only find because you were already looking for a shortcuts through life. A paragraph, tidy as a folded handkerchief, explained that a certain popular reader of feeds was retiring in four months’ time. Somewhere in the draughty back alleys of the web, a small god cleared his throat. Once he had roared every morning in a thousand offices. Now, when people clicked for their daily liturgy, the sound he made was… domesticated.</p><p>He is called ArrEsEs by those who enjoy syllables. He wears a round orange halo with three neat ripples in it. Strictly speaking, this is an icon1, but gods are not strict about these things. He presides over the River of Posts, which is less picturesque than it sounds and runs through everyone’s house at once. His priests are librarians and tinkerers and persons who believe in putting things in order so they can be pleasantly disordered later. The temple benches are arranged in feeds. The chief sacrament is “Mark All As Read,” which is the kind of absolution that leaves you lighter and vaguely suspicious you’ve got away with something.</p><a href="https://aneeshsathe.com/wp-content/uploads/2025/08/image-from-rawpixel-id-2623752-jpeg.jpg" rel="nofollow noopener" target="_blank"></a>Guide for Constructing the Letter S from Mira Calligraphiae Monumenta or The Model Book of Calligraphy (15611596) by Georg Bocskay and Joris Hoefnagel. Original from The Getty. Digitally enhanced by rawpixel.<p>There was a time the great city-temples kept a candle lit for him right on their threshold. The Fox of Fire invited him in and called it Live Bookmarks.2 The moldable church, once a suit, then a car, then a journey, in typical style stamped “RSS” beside the address like a house number. The Explorer adopted the little orange beacon with the enthusiasm of someone who has been told there will be cake. The Singers built him a pew and handed out hymnals. You could walk into almost any shrine and find his votive lamp glowing: “The river comes this way.” Later, accountants, the men behind the man who was yours, discovered that candles are unmonetizable and, one by one, the lamps were tidied into drawers that say “More…”.</p><p>ArrEsEs has lineage. Long before he knocked on doors with a bundle of headlines, there was Old Mother Press, the iron-fingered goddess of moveable type, patron of ink that bites and paper that complains. Her creed was simple: get the word out. She marched letters into columns and columns into broadsides until villages woke up arguing the same argument.3<strong>* ArrEsEs is her great-grandchild—quick-footed, soft-spoken—who learned to carry the broadsheet to each door at once and wait politely on the mat. He still bears her family look: text in tidy rows, dates that mind their place, headlines that know how to stand up straight.</strong>**</p><p>Four months after <a href="https://blog.google/inside-google/company-announcements/a-second-spring-of-cleaning/" rel="nofollow noopener" target="_blank">the Announcement</a>, the big temple shut its doors with a soft click. The congregation wandered off in small, stubborn knots and started chapels in back rooms with unhelpful names like OGRP4. ArrEsEs took to traveling again, coat collar up, suitcase full of headlines, knocking on back doors at respectable intervals. “No hurry,” he would say, leaving the bundle on the step. “When you’re ready.” The larger gods of the Square ring bells until you come out in your slippers; this one waits with the patience of bread.</p><p>Like all small gods, he thrives on little rites. He smiles when you put his name plainly on your door: a link that says feed without a blush. He approves of bogrolls blogrolls, because they are how villages point at one another and remember they are villages. He warms to OPML, which is a pilgrim’s list people swap like seed packets. He’s indulgent about the details—/rss.xml, /atom.xml, /feed, he will answer to all of them—but he purrs (quietly; dignified creature) for a cleanly formed offering and a sensible update cadence5.</p><p>His miracles are modest and cannot be tallied on a quarterly slide. He brings things in the order they happened. He does silence properly. The river arrives in the morning with twenty-seven items; you read two, save three, and let the rest drift by with the calm certainty that rivers do not take offense. He remembers what you finished. He promises tomorrow will come with its own bundle, and if you happen to be away, he will keep the stack neat and not wedge a “You Might Also Like” leaflet between your socks.</p><p>These days, though, ArrEsEs is lean at the ribs. The big estates threw dams across his tributaries and called them platforms. Good water disappeared behind walls; the rest was coaxed into ornamental channels that loop the palace and reflect only the palace. Where streams once argued cheerfully, they now mutter through sluices and churn a Gloomwheel that turns and turns without making flour—an endless thumb-crank that insists there is more, and worse, if you’ll just keep scrolling. He can drink from it, but it leaves a taste of tin and yesterday’s news.</p><p>A god’s displeasure tells you more than his blessings. His is mild. If you hide the feed, he grows thin around the edges. If you build a house that is only a façade until seven JSters haul in the furniture, he coughs and brings you only the headline and a smell of varnish6. If you replace paragraphs with an endless corridor, he develops the kind of seasickness that keeps old sailors ashore. He does not smite. He sulks, which is worse, because you may not notice until you wonder where everyone went.</p><p>Still, belief has a way of pooling in low places. In the quiet hours, the little chapels hum: home pages with kettles on, personal sites that remember how to wave, gardeners who publish their lists of other gardeners. Somewhere, a reader you’ve never met presses a small, homely button that says subscribe. The god straightens, just a touch. He is gentler than his grandmother who rattled windows with every edition, but the family gift endures. If you invite him, tomorrow he will be there, on your step, with a bundle of fresh pages and a polite cough. You can let him in, or make tea first. He’ll wait. He always has.</p> <p class="">Heavily edited sloptraption.</p> <ol><li>He maintains it’s saffron, which is what halos say when they are trying to be practical ↩︎</li><li>The sort of feature named by a librarian, which is to say, both accurate and doomed. ↩︎</li><li>Not to be confused with the software that borrowed her title and a fair chunk of her patience. ↩︎</li><li>Old Google Reader People ↩︎</li><li> On festival days he will accept serif, sans-serif, or whatever the village printer has not yet thrown at a cat.<br> ↩︎</li><li>He can drink JSON when pressed; stew remains his preference. ↩︎</li></ol><p><a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://aneeshsathe.com/tag/ai/" target="_blank">#AI</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://aneeshsathe.com/tag/algorithmic-feeds/" target="_blank">#algorithmicFeeds</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://aneeshsathe.com/tag/blogging/" target="_blank">#blogging</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://aneeshsathe.com/tag/blogrolls/" target="_blank">#blogrolls</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://aneeshsathe.com/tag/discworld/" target="_blank">#Discworld</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://aneeshsathe.com/tag/doomscrolling/" target="_blank">#doomscrolling</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://aneeshsathe.com/tag/feed-readers/" target="_blank">#feedReaders</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://aneeshsathe.com/tag/google-reader/" target="_blank">#GoogleReader</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://aneeshsathe.com/tag/history/" target="_blank">#history</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://aneeshsathe.com/tag/indieweb/" target="_blank">#IndieWeb</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://aneeshsathe.com/tag/internet-folklore/" target="_blank">#internetFolklore</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://aneeshsathe.com/tag/open-web/" target="_blank">#openWeb</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://aneeshsathe.com/tag/opml/" target="_blank">#OPML</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://aneeshsathe.com/tag/personal-websites/" target="_blank">#personalWebsites</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://aneeshsathe.com/tag/philosophy/" target="_blank">#philosophy</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://aneeshsathe.com/tag/posse/" target="_blank">#POSSE</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://aneeshsathe.com/tag/printing-press/" target="_blank">#printingPress</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://aneeshsathe.com/tag/quiet-web/" target="_blank">#quietWeb</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://aneeshsathe.com/tag/rss/" target="_blank">#RSS</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://aneeshsathe.com/tag/small-gods/" target="_blank">#smallGods</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://aneeshsathe.com/tag/terry-pratchett/" target="_blank">#TerryPratchett</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://aneeshsathe.com/tag/web-standards/" target="_blank">#webStandards</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://aneeshsathe.com/tag/writing/" target="_blank">#writing</a></p>
Tantek Çelik<p>The Vision for W3C has been officially published as a ratified W3C Statement: <a class="" href="https://www.w3.org/TR/2025/STMT-w3c-vision-20250729/" rel="nofollow noopener" target="_blank">https://www.w3.org/TR/2025/STMT-w3c-vision-20250729/</a><br><br>As one of the editors, along with Chris Wilson (<a class="" href="https://cwilso.com" rel="nofollow noopener" target="_blank">@cwilso.com</a> <a class="" href="https://w3c.social/@c" rel="nofollow noopener" target="_blank">@c@w3c.social</a>), 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.<br><br>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).<br><br>The AB (<a class="" href="https://w3.org/wiki/AB" rel="nofollow noopener" target="_blank">@w3.org/wiki/AB</a> <a class="" href="https://w3c.social/@ab" rel="nofollow noopener" target="_blank">@ab@w3c.social</a>) has prioritized work on the Vision project for many years (<a class="" href="https://www.w3.org/wiki/AB/Vision" rel="nofollow noopener" target="_blank">https://www.w3.org/wiki/AB/Vision</a>), 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.<br><br><a class="" href="https://indieweb.social/tags/w3cVision" rel="nofollow noopener" target="_blank">#<span class="p-category">w3cVision</span></a> <a class="" href="https://indieweb.social/tags/VisionForW3C" rel="nofollow noopener" target="_blank">#<span class="p-category">VisionForW3C</span></a> <a class="" href="https://indieweb.social/tags/WorldWideWeb" rel="nofollow noopener" target="_blank">#<span class="p-category">WorldWideWeb</span></a> <a class="" href="https://indieweb.social/tags/W3C" rel="nofollow noopener" target="_blank">#<span class="p-category">W3C</span></a> (<a class="" href="https://w3.org" rel="nofollow noopener" target="_blank">@w3.org</a> <a class="" href="https://w3c.social/@w3c" rel="nofollow noopener" target="_blank">@w3c@w3c.social</a>)<br><a class="" href="https://indieweb.social/tags/openWeb" rel="nofollow noopener" target="_blank">#<span class="p-category">openWeb</span></a> <a class="" href="https://indieweb.social/tags/webStandards" rel="nofollow noopener" target="_blank">#<span class="p-category">webStandards</span></a><br><br>Previously:<br>* <a class="" href="https://tantek.com/2025/100/t1/vision-for-w3c-please-vote" rel="nofollow noopener" target="_blank">https://tantek.com/2025/100/t1/vision-for-w3c-please-vote</a><br><br>More posts:<br>* <a class="" href="https://www.w3.org/news/2025/vision-for-w3c-is-a-w3c-statement/" rel="nofollow noopener" target="_blank">https://www.w3.org/news/2025/vision-for-w3c-is-a-w3c-statement/</a><br>* <a class="" href="https://www.w3.org/blog/2025/vision-for-w3c-a-manifesto-for-our-operations-and-decision-making/" rel="nofollow noopener" target="_blank">https://www.w3.org/blog/2025/vision-for-w3c-a-manifesto-for-our-operations-and-decision-making/</a></p>
nemo™ 🇺🇦<p>🚨 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 ⚖️📉 <a href="https://mas.to/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebStandards</span></a> <a href="https://mas.to/tags/Privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Privacy</span></a> <a href="https://mas.to/tags/TechCompetition" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TechCompetition</span></a> <a href="https://mas.to/tags/W3C" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>W3C</span></a> <a href="https://mas.to/tags/Cookies" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Cookies</span></a> <a href="https://mas.to/tags/Google" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Google</span></a> <a href="https://www.theregister.com/2025/07/29/mow_w3c_cookie_complaint/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">theregister.com/2025/07/29/mow</span><span class="invisible">_w3c_cookie_complaint/</span></a><br><a href="https://mas.to/tags/newz" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>newz</span></a></p>
Alda Vigdís<p>And here I am with a spicy take on the &lt;hgroup&gt; HTML element of all things.</p><p>Is the &lt;hgroup&gt; element redundant and should we handle headings and subheadings differently instead of re-introducing the element?</p><p><a href="https://aldavigdis.dev/2025/07/25/taming-html-headings-subheadings-and-overlines/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">aldavigdis.dev/2025/07/25/tami</span><span class="invisible">ng-html-headings-subheadings-and-overlines/</span></a></p><p><a href="https://topspicy.social/tags/WebDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebDev</span></a> <a href="https://topspicy.social/tags/HTML" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HTML</span></a> <a href="https://topspicy.social/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebStandards</span></a></p>
Julie Blanc<p>📘 Just published: “Designing with Abstractions: CSS and the Case of Masonry Layouts”</p><p>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.</p><p>Appreciation to those participating in CSS WG debates and making this work visible.</p><p>→ <a href="https://journal.dampress.org/issues/design-et-abstractions/designing-with-abstractions-css-and-the-case-of-masonry-layouts" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">journal.dampress.org/issues/de</span><span class="invisible">sign-et-abstractions/designing-with-abstractions-css-and-the-case-of-masonry-layouts</span></a></p><p> <a href="https://mastodon.design/tags/CSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CSS</span></a> <a href="https://mastodon.design/tags/CSSWG" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CSSWG</span></a> <a href="https://mastodon.design/tags/w3c" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>w3c</span></a> <a href="https://mastodon.design/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebStandards</span></a></p>
🧿🪬🍄🌈🎮💻🚲🥓🎃💀🏴🛻🇺🇸<p>&gt; <a href="https://mastodon.social/tags/Firefox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Firefox</span></a> has long lagged behind <a href="https://mastodon.social/tags/Chrome" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Chrome</span></a> in adopting new <a href="https://mastodon.social/tags/webStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webStandards</span></a>, but loyal users now have something to celebrate as the <a href="https://mastodon.social/tags/browser" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>browser</span></a> is finally getting a feature Chrome has offered for years.</p><p><a href="https://www.neowin.net/news/better-late-than-never-firefox-is-finally-getting-a-feature-chrome-users-have-had-for-years/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">neowin.net/news/better-late-th</span><span class="invisible">an-never-firefox-is-finally-getting-a-feature-chrome-users-have-had-for-years/</span></a></p><p><a href="https://mastodon.social/tags/webGPU" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webGPU</span></a> <a href="https://mastodon.social/tags/webDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webDev</span></a> <a href="https://mastodon.social/tags/browsers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>browsers</span></a> <a href="https://mastodon.social/tags/mozilla" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>mozilla</span></a></p>
Timo Tijhof<p>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.</p><p>But, when you set a thick edge on one side, the thin 1px border gets squeezed into a slope, and won&#39;t reach the edge! And the sidebar forms a *trapezoid*!</p><p>This is most noticable on modern high-DPI screens. It is rather unsatisfying, and hard to unsee...</p><p>Example:<br /><a href="https://en.wikipedia.org/wiki/Template:Cleanup" target="_blank" rel="nofollow noopener" translate="no"><span class="invisible">https://</span><span class="ellipsis">en.wikipedia.org/wiki/Template</span><span class="invisible">:Cleanup</span></a></p><p><a href="https://fosstodon.org/tags/css" class="mention hashtag" rel="tag">#<span>css</span></a> <a href="https://fosstodon.org/tags/WebDesign" class="mention hashtag" rel="tag">#<span>WebDesign</span></a> <a href="https://fosstodon.org/tags/WebStandards" class="mention hashtag" rel="tag">#<span>WebStandards</span></a> <a href="https://fosstodon.org/tags/mathstodon" class="mention hashtag" rel="tag">#<span>mathstodon</span></a></p>
Holger Hellinger<p>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.</p><p>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.“</p><p><a href="https://hellinger.wtf/tags/Barrieren" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Barrieren</span></a> <a href="https://hellinger.wtf/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebStandards</span></a></p>
Steve Faulkner<p>Meanwhile the discussion on defining "view"rumbles on: 52 comments · 137 replies</p><p>I have largely stayed out of it as I have other more pressing shit to do. 🖖🏽</p><p><a href="https://mastodon.social/tags/WCAG" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WCAG</span></a> <a href="https://mastodon.social/tags/a11y" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>a11y</span></a> <a href="https://mastodon.social/tags/webStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webStandards</span></a> <a href="https://mastodon.social/tags/endless" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>endless</span></a></p><p><a href="https://github.com/w3c/wcag3/discussions/286" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/w3c/wcag3/discussio</span><span class="invisible">ns/286</span></a></p>
Steve Faulkner<p>Interview with Lola Odelola <span class="h-card" translate="no"><a href="https://mastodon.social/@lolaodelola" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>lolaodelola</span></a></span> </p><p>"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)"</p><p><a href="https://mastodon.social/tags/ARIA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ARIA</span></a> <a href="https://mastodon.social/tags/AT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AT</span></a> <a href="https://mastodon.social/tags/a11y" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>a11y</span></a> <a href="https://mastodon.social/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebStandards</span></a></p><p><a href="https://tetralogical.com/blog/2025/07/02/interview-with-lola-odelola/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">tetralogical.com/blog/2025/07/</span><span class="invisible">02/interview-with-lola-odelola/</span></a></p>
Inautilo<p><a href="https://mastodon.social/tags/Development" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Development</span></a> <a href="https://mastodon.social/tags/Previews" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Previews</span></a><br>Kelp · A customizable UI library that needs no build step <a href="https://ilo.im/164ypi" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">ilo.im/164ypi</span><span class="invisible"></span></a></p><p>_____<br><a href="https://mastodon.social/tags/Library" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Library</span></a> <a href="https://mastodon.social/tags/HTML" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HTML</span></a> <a href="https://mastodon.social/tags/CSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CSS</span></a> <a href="https://mastodon.social/tags/WebComponents" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebComponents</span></a> <a href="https://mastodon.social/tags/CDN" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CDN</span></a> <a href="https://mastodon.social/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebStandards</span></a> <a href="https://mastodon.social/tags/WebDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebDev</span></a> <a href="https://mastodon.social/tags/Frontend" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Frontend</span></a></p>
vruz<p>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. <a href="https://mstdn.social/tags/compsci" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>compsci</span></a> <a href="https://mstdn.social/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webdev</span></a> <a href="https://mstdn.social/tags/webstandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webstandards</span></a> <a href="https://mstdn.social/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>opensource</span></a></p>
vruz<p>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. <a href="https://mstdn.social/tags/compsci" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>compsci</span></a> <a href="https://mstdn.social/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webdev</span></a> <a href="https://mstdn.social/tags/webstandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webstandards</span></a> <a href="https://mstdn.social/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>opensource</span></a></p>
vruz<p>Why add yet another JS templating API when WASM + direct DOM access solves the root problem? Every language could build efficient UIs without the JS bottleneck. More universal than blessing one syntax. Think beyond JavaScript - imagine Rust components with zero overhead, Go templates that actually perform, or C# Blazor without the bridge tax. That's true platform evolution. <a href="https://mstdn.social/tags/compsci" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>compsci</span></a> <a href="https://mstdn.social/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webdev</span></a> <a href="https://mstdn.social/tags/wasm" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>wasm</span></a> <a href="https://mstdn.social/tags/webstandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webstandards</span></a></p>
Simeon.__proto__<p>What are your favorite blogs about the <a href="https://toot.cafe/tags/web" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>web</span></a>, <a href="https://toot.cafe/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webdev</span></a>, and <a href="https://toot.cafe/tags/webstandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webstandards</span></a>? </p><p>(sorry about the hashtags, trying to cast a wider net)</p>
Steve Faulkner<p>🫡 Having had my head in an EAA assessment for the past month i missed this discussion until now </p><p><a href="https://mastodon.social/tags/WCAG" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WCAG</span></a> <a href="https://mastodon.social/tags/WCAG3" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WCAG3</span></a> <a href="https://mastodon.social/tags/a11y" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>a11y</span></a> <a href="https://mastodon.social/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebStandards</span></a> </p><p>Scheduling Approach Alternatives</p><p><a href="https://github.com/w3c/wcag3/discussions/322#" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/w3c/wcag3/discussio</span><span class="invisible">ns/322#</span></a></p>