techhub.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A hub primarily for passionate technologists, but everyone is welcome

Administered by:

Server stats:

4.7K
active users

#webstandards

1 post1 participant0 posts today
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'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" rel="nofollow noopener" translate="no" target="_blank"><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="nofollow noopener" target="_blank">#<span>css</span></a> <a href="https://fosstodon.org/tags/WebDesign" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebDesign</span></a> <a href="https://fosstodon.org/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebStandards</span></a> <a href="https://fosstodon.org/tags/mathstodon" class="mention hashtag" rel="nofollow noopener" target="_blank">#<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>
xoron :verified:<p>File encryption with a browser.</p><p>I've been exploring the <a href="https://infosec.exchange/tags/WebCryptoAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebCryptoAPI</span></a> and I'm impressed!</p><p>When combined with the <a href="https://infosec.exchange/tags/FileSystemAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FileSystemAPI</span></a>, it offers a seemingly secure way to <a href="https://infosec.exchange/tags/encrypt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>encrypt</span></a> and <a href="https://infosec.exchange/tags/store" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>store</span></a> files directly on your device. Think <a href="https://infosec.exchange/tags/localstorage" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>localstorage</span></a>, but with <a href="https://infosec.exchange/tags/encryption" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>encryption</span></a>!</p><p>I know <a href="https://infosec.exchange/tags/webapps" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webapps</span></a> can have <a href="https://infosec.exchange/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>security</span></a> vulnerabilities since the code is served over the web, so I've <a href="https://infosec.exchange/tags/OpenSourced" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSourced</span></a> my demo! You can check it out, and it should even work if <a href="https://infosec.exchange/tags/selfhosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>selfhosted</span></a> on <a href="https://infosec.exchange/tags/GitHubPages" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GitHubPages</span></a>.</p><p>Live Demo: <a href="https://dim.positive-intentions.com/?path=/story/usefs--encrypted-demo" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">dim.positive-intentions.com/?p</span><span class="invisible">ath=/story/usefs--encrypted-demo</span></a></p><p>Demo Code: <a href="https://github.com/positive-intentions/dim/blob/staging/src/stories/05-Hooks-useFS.stories.js" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/positive-intentions</span><span class="invisible">/dim/blob/staging/src/stories/05-Hooks-useFS.stories.js</span></a></p><p>Hook Code: <a href="https://github.com/positive-intentions/dim/blob/staging/src/hooks/useFS.js" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/positive-intentions</span><span class="invisible">/dim/blob/staging/src/hooks/useFS.js</span></a></p><p>IMPORTANT NOTES (PLEASE READ!):<br> * This is NOT a product. It's for <a href="https://infosec.exchange/tags/testing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>testing</span></a> and <a href="https://infosec.exchange/tags/demonstration" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>demonstration</span></a> purposes only.<br> * It has NOT been reviewed or audited. Do NOT use for sensitive data.<br> * The "password encryption" currently uses a hardcoded password. This is for demonstration, not security.<br> * This is NOT meant to replace robust solutions like <a href="https://infosec.exchange/tags/VeraCrypt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VeraCrypt</span></a>. It's just a <a href="https://infosec.exchange/tags/proofofconcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>proofofconcept</span></a> to show what's possible with <a href="https://infosec.exchange/tags/browser" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>browser</span></a> <a href="https://infosec.exchange/tags/APIs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>APIs</span></a>.</p><p><a href="https://infosec.exchange/tags/Encryption" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Encryption</span></a> <a href="https://infosec.exchange/tags/Cryptography" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Cryptography</span></a> <a href="https://infosec.exchange/tags/JavaScript" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>JavaScript</span></a> <a href="https://infosec.exchange/tags/Frontend" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Frontend</span></a> <a href="https://infosec.exchange/tags/Privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Privacy</span></a> <a href="https://infosec.exchange/tags/Security" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Security</span></a> <a href="https://infosec.exchange/tags/WebDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebDevelopment</span></a> <a href="https://infosec.exchange/tags/Coding" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Coding</span></a> <a href="https://infosec.exchange/tags/Developer" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Developer</span></a> <a href="https://infosec.exchange/tags/Tech" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Tech</span></a> <a href="https://infosec.exchange/tags/FOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FOSS</span></a> <a href="https://infosec.exchange/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSource</span></a> <a href="https://infosec.exchange/tags/GitHub" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GitHub</span></a> <a href="https://infosec.exchange/tags/MastodonDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MastodonDev</span></a> <a href="https://infosec.exchange/tags/Programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Programming</span></a> <a href="https://infosec.exchange/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebStandards</span></a> <a href="https://infosec.exchange/tags/FileSystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FileSystem</span></a> <a href="https://infosec.exchange/tags/WebAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebAPI</span></a> <a href="https://infosec.exchange/tags/ProofOfConcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ProofOfConcept</span></a></p>
Timo Tijhof<p>You'd think Google, having launched schema.org, knows how to produce valid schema.org metadata and HTML5.</p><p>YouTube: How about a `&lt;span&gt;` inside the head, and `&lt;link rel=alternative&gt;` inside the body?</p><p>HTML5 parsers:<br>Thanks, I'll take that span as your implied end of `&lt;head&gt;`, and raise you an implied start of `&lt;body&gt;`. Everything that follows is now part of the body.</p><p>Context:<br><a href="https://github.com/Ranchero-Software/NetNewsWire/issues/902#issuecomment-2990075755" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/Ranchero-Software/N</span><span class="invisible">etNewsWire/issues/902#issuecomment-2990075755</span></a></p><p><a href="https://fosstodon.org/tags/NetNewsWire" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NetNewsWire</span></a> <a href="https://fosstodon.org/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebStandards</span></a> <a href="https://fosstodon.org/tags/whatwg" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>whatwg</span></a> <a href="https://fosstodon.org/tags/HTML5" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HTML5</span></a> <a href="https://fosstodon.org/tags/schemaorg" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>schemaorg</span></a> <a href="https://fosstodon.org/tags/google" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>google</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/Trends" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Trends</span></a><br>The future of browsing the web · ”AI just broke the web that Google built.” <a href="https://ilo.im/164cfq" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">ilo.im/164cfq</span><span class="invisible"></span></a></p><p>“Chrome’s days are numbered.”<br>_____<br><a href="https://mastodon.social/tags/OpenWeb" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenWeb</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/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AI</span></a> <a href="https://mastodon.social/tags/AnswerEngine" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AnswerEngine</span></a> <a href="https://mastodon.social/tags/SearchEngine" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SearchEngine</span></a> <a href="https://mastodon.social/tags/Google" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Google</span></a> <a href="https://mastodon.social/tags/Chrome" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Chrome</span></a> <a href="https://mastodon.social/tags/Browser" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Browser</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>
dokieli<p><span class="h-card" translate="no"><a href="https://mstdn.social/@odd" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>odd</span></a></span> Thanks for checking it out!</p><p>For the most part, the solution has to do with the <a href="https://w3c.social/tags/webstandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webstandards</span></a> as opposed to specific implementations. So, when dokieli and a server can communicate over the same set of protocols and data formats, for instance, then the hosting or the software behind it is not an issue.</p><p>Yes, sharing involves a couple of areas: so, users with control access can give others access. Anyone can notify anyone (from their contacts for example) about the article.</p><p>- <span class="h-card" translate="no"><a href="https://w3c.social/@csarven" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>csarven</span></a></span></p>
W3C Developers<p>Congrats to editors Matt Garrish and <span class="h-card" translate="no"><a href="https://w3c.social/@tzviya" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>tzviya</span></a></span> for the two newly published <span class="h-card" translate="no"><a href="https://w3c.social/@w3c" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>w3c</span></a></span> <a href="https://w3c.social/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebStandards</span></a> "Digital Publishing WAI-ARIA Module 1.1 (DPUB-ARIA)" and "Digital Publishing Accessibility API Mappings 1.1 (DPUB-AAM)". <a href="https://w3c.social/tags/timetoadopt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>timetoadopt</span></a> </p><p>▶️ <a href="https://www.w3.org/TR/dpub-aria-1.1/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">w3.org/TR/dpub-aria-1.1/</span><span class="invisible"></span></a><br>▶️ <a href="https://www.w3.org/TR/dpub-aam-1.1/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">w3.org/TR/dpub-aam-1.1/</span><span class="invisible"></span></a></p><p><a href="https://w3c.social/tags/ebooks" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ebooks</span></a> <a href="https://w3c.social/tags/accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>accessibility</span></a></p>
🧿🪬🍄🌈🎮💻🚲🥓🎃💀🏴🛻🇺🇸<p>URLs should be able to include HTTP verbs and headers. </p><p>They say "URLs define the "what" not the "how"" but protocol prefixes, file extensions, and query parameters are part of the how and yet they all exist in the URL. </p><p>Leaving HTTP verbs and headers out of URLs was an arbitrary decision.</p><p><a href="https://mastodon.social/tags/web" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>web</span></a> <a href="https://mastodon.social/tags/http" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>http</span></a> <a href="https://mastodon.social/tags/hypermedia" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>hypermedia</span></a> <a href="https://mastodon.social/tags/hateoas" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>hateoas</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/html" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>html</span></a> <a href="https://mastodon.social/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>programming</span></a> <a href="https://mastodon.social/tags/networking" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>networking</span></a></p>
dokieli<p>🚀 <a href="https://w3c.social/tags/dokieli" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dokieli</span></a> ( <a href="https://dokie.li/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">dokie.li/</span><span class="invisible"></span></a> ) is a web-based <a href="https://w3c.social/tags/decentralized" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>decentralized</span></a> article <a href="https://w3c.social/tags/publishing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>publishing</span></a> and <a href="https://w3c.social/tags/annotation" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>annotation</span></a> <a href="https://w3c.social/tags/application" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>application</span></a> and browser extension, built as an <a href="https://w3c.social/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>opensource</span></a> ( <a href="https://git.dokie.li/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">git.dokie.li/</span><span class="invisible"></span></a> ) project using <a href="https://w3c.social/tags/webstandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webstandards</span></a>.</p><p>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.</p>
Yves Van Goethem :firefox:<p>Waow even the Ringmark test suit still exists!<br><a href="https://rng.io/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">rng.io/</span><span class="invisible"></span></a></p><p>With all the credits and background that led to the development of it: <a href="https://rng.io/about/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">rng.io/about/</span><span class="invisible"></span></a></p><p><a href="https://indieweb.social/tags/webstandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webstandards</span></a></p>
Yves Van Goethem :firefox:<p>Going down the Web Standardisation memory lane a bit.<br>I just found the OSS repo that we launched at SoundCloud to help browser vendors improve the Web Audio implementations across browsers 14 years ago 🤯<br>This was a short endevour but one we got a bit of support and contributions from great people at Microsoft, Google, Mozilla, W3C, Opera, Facebook, etc. <br><a href="https://github.com/soundcloud/areweplayingyet/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/soundcloud/arewepla</span><span class="invisible">yingyet/</span></a><br><a href="https://indieweb.social/tags/browser" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>browser</span></a> <a href="https://indieweb.social/tags/web" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>web</span></a> <a href="https://indieweb.social/tags/webstandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webstandards</span></a></p>
Steve Faulkner<p>ARIA/HTML relationship Severance</p><p>"You could use standard HTML controls without all that stinking DOM darkness and encapsulation fandango fucking up your relationships."</p><p><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/ARIA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ARIA</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/WebDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebDev</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://html5accessibility.com/stuff/2025/06/07/aria-html-relationship-severence/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">html5accessibility.com/stuff/2</span><span class="invisible">025/06/07/aria-html-relationship-severence/</span></a></p>