MastodonTech.de

🧿🪬🍄🌈🎮💻🚲🥓🎃💀🏴🛻🇺🇸> <a href="https://mastodon.social/tags/Firefox" class="mention hashtag" rel="nofollow noopener" target="_blank">#Firefox</a> has long lagged behind <a href="https://mastodon.social/tags/Chrome" class="mention hashtag" rel="nofollow noopener" target="_blank">#Chrome</a> in adopting new <a href="https://mastodon.social/tags/webStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#webStandards</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">#browser</a> is finally getting a feature Chrome has offered for years.<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">https://www.neowin.net/news/better-late-than-never-firefox-is-finally-getting-a-feature-chrome-users-have-had-for-years/</a><a href="https://mastodon.social/tags/webGPU" class="mention hashtag" rel="nofollow noopener" target="_blank">#webGPU</a> <a href="https://mastodon.social/tags/webDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#webDev</a> <a href="https://mastodon.social/tags/browsers" class="mention hashtag" rel="nofollow noopener" target="_blank">#browsers</a> <a href="https://mastodon.social/tags/mozilla" class="mention hashtag" rel="nofollow noopener" target="_blank">#mozilla</a>

Timo TijhofWhen 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: <a href="https://en.wikipedia.org/wiki/Template:Cleanup" rel="nofollow noopener" translate="no" target="_blank">https://en.wikipedia.org/wiki/Template:Cleanup</a><a href="https://fosstodon.org/tags/css" class="mention hashtag" rel="nofollow noopener" target="_blank">#css</a> <a href="https://fosstodon.org/tags/WebDesign" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebDesign</a> <a href="https://fosstodon.org/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebStandards</a> <a href="https://fosstodon.org/tags/mathstodon" class="mention hashtag" rel="nofollow noopener" target="_blank">#mathstodon</a>

Holger HellingerWenn „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.“<a href="https://hellinger.wtf/tags/Barrieren" class="mention hashtag" rel="nofollow noopener" target="_blank">#Barrieren</a> <a href="https://hellinger.wtf/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebStandards</a>

Steve FaulknerMeanwhile the discussion on defining "view"rumbles on: 52 comments · 137 repliesI have largely stayed out of it as I have other more pressing shit to do. 🖖🏽<a href="https://mastodon.social/tags/WCAG" class="mention hashtag" rel="nofollow noopener" target="_blank">#WCAG</a> <a href="https://mastodon.social/tags/a11y" class="mention hashtag" rel="nofollow noopener" target="_blank">#a11y</a> <a href="https://mastodon.social/tags/webStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#webStandards</a> <a href="https://mastodon.social/tags/endless" class="mention hashtag" rel="nofollow noopener" target="_blank">#endless</a><a href="https://github.com/w3c/wcag3/discussions/286" rel="nofollow noopener" translate="no" target="_blank">https://github.com/w3c/wcag3/discussions/286</a>

Steve FaulknerInterview with Lola Odelola <a href="https://mastodon.social/@lolaodelola" class="u-url mention" rel="nofollow noopener" target="_blank">@lolaodelola</a> "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)"<a href="https://mastodon.social/tags/ARIA" class="mention hashtag" rel="nofollow noopener" target="_blank">#ARIA</a> <a href="https://mastodon.social/tags/AT" class="mention hashtag" rel="nofollow noopener" target="_blank">#AT</a> <a href="https://mastodon.social/tags/a11y" class="mention hashtag" rel="nofollow noopener" target="_blank">#a11y</a> <a href="https://mastodon.social/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebStandards</a><a href="https://tetralogical.com/blog/2025/07/02/interview-with-lola-odelola/" rel="nofollow noopener" translate="no" target="_blank">https://tetralogical.com/blog/2025/07/02/interview-with-lola-odelola/</a>

Inautilo<a href="https://mastodon.social/tags/Development" class="mention hashtag" rel="nofollow noopener" target="_blank">#Development</a> <a href="https://mastodon.social/tags/Previews" class="mention hashtag" rel="nofollow noopener" target="_blank">#Previews</a> Kelp · A customizable UI library that needs no build step <a href="https://ilo.im/164ypi" rel="nofollow noopener" translate="no" target="_blank">https://ilo.im/164ypi</a>_____ <a href="https://mastodon.social/tags/Library" class="mention hashtag" rel="nofollow noopener" target="_blank">#Library</a> <a href="https://mastodon.social/tags/HTML" class="mention hashtag" rel="nofollow noopener" target="_blank">#HTML</a> <a href="https://mastodon.social/tags/CSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#CSS</a> <a href="https://mastodon.social/tags/WebComponents" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebComponents</a> <a href="https://mastodon.social/tags/CDN" class="mention hashtag" rel="nofollow noopener" target="_blank">#CDN</a> <a href="https://mastodon.social/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebStandards</a> <a href="https://mastodon.social/tags/WebDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebDev</a> <a href="https://mastodon.social/tags/Frontend" class="mention hashtag" rel="nofollow noopener" target="_blank">#Frontend</a>

vruzWeb'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">#compsci</a> <a href="https://mstdn.social/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#webdev</a> <a href="https://mstdn.social/tags/webstandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#webstandards</a> <a href="https://mstdn.social/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a>

vruzThe 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">#compsci</a> <a href="https://mstdn.social/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#webdev</a> <a href="https://mstdn.social/tags/webstandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#webstandards</a> <a href="https://mstdn.social/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a>

vruzWhy 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">#compsci</a> <a href="https://mstdn.social/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#webdev</a> <a href="https://mstdn.social/tags/wasm" class="mention hashtag" rel="nofollow noopener" target="_blank">#wasm</a> <a href="https://mstdn.social/tags/webstandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#webstandards</a>

Steve Faulkner🫡 Having had my head in an EAA assessment for the past month i missed this discussion until now <a href="https://mastodon.social/tags/WCAG" class="mention hashtag" rel="nofollow noopener" target="_blank">#WCAG</a> <a href="https://mastodon.social/tags/WCAG3" class="mention hashtag" rel="nofollow noopener" target="_blank">#WCAG3</a> <a href="https://mastodon.social/tags/a11y" class="mention hashtag" rel="nofollow noopener" target="_blank">#a11y</a> <a href="https://mastodon.social/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebStandards</a> Scheduling Approach Alternatives<a href="https://github.com/w3c/wcag3/discussions/322#" rel="nofollow noopener" translate="no" target="_blank">https://github.com/w3c/wcag3/discussions/322#</a>

xoron :verified:File encryption with a browser.I've been exploring the <a href="https://infosec.exchange/tags/WebCryptoAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebCryptoAPI</a> and I'm impressed!When combined with the <a href="https://infosec.exchange/tags/FileSystemAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#FileSystemAPI</a>, it offers a seemingly secure way to <a href="https://infosec.exchange/tags/encrypt" class="mention hashtag" rel="nofollow noopener" target="_blank">#encrypt</a> and <a href="https://infosec.exchange/tags/store" class="mention hashtag" rel="nofollow noopener" target="_blank">#store</a> files directly on your device. Think <a href="https://infosec.exchange/tags/localstorage" class="mention hashtag" rel="nofollow noopener" target="_blank">#localstorage</a>, but with <a href="https://infosec.exchange/tags/encryption" class="mention hashtag" rel="nofollow noopener" target="_blank">#encryption</a>!I know <a href="https://infosec.exchange/tags/webapps" class="mention hashtag" rel="nofollow noopener" target="_blank">#webapps</a> can have <a href="https://infosec.exchange/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</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">#OpenSourced</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">#selfhosted</a> on <a href="https://infosec.exchange/tags/GitHubPages" class="mention hashtag" rel="nofollow noopener" target="_blank">#GitHubPages</a>.Live Demo: <a href="https://dim.positive-intentions.com/?path=/story/usefs--encrypted-demo" rel="nofollow noopener" translate="no" target="_blank">https://dim.positive-intentions.com/?path=/story/usefs--encrypted-demo</a>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">https://github.com/positive-intentions/dim/blob/staging/src/stories/05-Hooks-useFS.stories.js</a>Hook Code: <a href="https://github.com/positive-intentions/dim/blob/staging/src/hooks/useFS.js" rel="nofollow noopener" translate="no" target="_blank">https://github.com/positive-intentions/dim/blob/staging/src/hooks/useFS.js</a>IMPORTANT NOTES (PLEASE READ!): * This is NOT a product. It's for <a href="https://infosec.exchange/tags/testing" class="mention hashtag" rel="nofollow noopener" target="_blank">#testing</a> and <a href="https://infosec.exchange/tags/demonstration" class="mention hashtag" rel="nofollow noopener" target="_blank">#demonstration</a> 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 <a href="https://infosec.exchange/tags/VeraCrypt" class="mention hashtag" rel="nofollow noopener" target="_blank">#VeraCrypt</a>. It's just a <a href="https://infosec.exchange/tags/proofofconcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#proofofconcept</a> to show what's possible with <a href="https://infosec.exchange/tags/browser" class="mention hashtag" rel="nofollow noopener" target="_blank">#browser</a> <a href="https://infosec.exchange/tags/APIs" class="mention hashtag" rel="nofollow noopener" target="_blank">#APIs</a>.<a href="https://infosec.exchange/tags/Encryption" class="mention hashtag" rel="nofollow noopener" target="_blank">#Encryption</a> <a href="https://infosec.exchange/tags/Cryptography" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cryptography</a> <a href="https://infosec.exchange/tags/JavaScript" class="mention hashtag" rel="nofollow noopener" target="_blank">#JavaScript</a> <a href="https://infosec.exchange/tags/Frontend" class="mention hashtag" rel="nofollow noopener" target="_blank">#Frontend</a> <a href="https://infosec.exchange/tags/Privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#Privacy</a> <a href="https://infosec.exchange/tags/Security" class="mention hashtag" rel="nofollow noopener" target="_blank">#Security</a> <a href="https://infosec.exchange/tags/WebDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebDevelopment</a> <a href="https://infosec.exchange/tags/Coding" class="mention hashtag" rel="nofollow noopener" target="_blank">#Coding</a> <a href="https://infosec.exchange/tags/Developer" class="mention hashtag" rel="nofollow noopener" target="_blank">#Developer</a> <a href="https://infosec.exchange/tags/Tech" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tech</a> <a href="https://infosec.exchange/tags/FOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FOSS</a> <a href="https://infosec.exchange/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> <a href="https://infosec.exchange/tags/GitHub" class="mention hashtag" rel="nofollow noopener" target="_blank">#GitHub</a> <a href="https://infosec.exchange/tags/MastodonDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#MastodonDev</a> <a href="https://infosec.exchange/tags/Programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#Programming</a> <a href="https://infosec.exchange/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebStandards</a> <a href="https://infosec.exchange/tags/FileSystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#FileSystem</a> <a href="https://infosec.exchange/tags/WebAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebAPI</a> <a href="https://infosec.exchange/tags/ProofOfConcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProofOfConcept</a>

Timo TijhofYou'd think Google, having launched schema.org, knows how to produce valid schema.org metadata and HTML5.YouTube: How about a `` 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: <a href="https://github.com/Ranchero-Software/NetNewsWire/issues/902#issuecomment-2990075755" rel="nofollow noopener" translate="no" target="_blank">https://github.com/Ranchero-Software/NetNewsWire/issues/902#issuecomment-2990075755</a><a href="https://fosstodon.org/tags/NetNewsWire" class="mention hashtag" rel="nofollow noopener" target="_blank">#NetNewsWire</a> <a href="https://fosstodon.org/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebStandards</a> <a href="https://fosstodon.org/tags/whatwg" class="mention hashtag" rel="nofollow noopener" target="_blank">#whatwg</a> <a href="https://fosstodon.org/tags/HTML5" class="mention hashtag" rel="nofollow noopener" target="_blank">#HTML5</a> <a href="https://fosstodon.org/tags/schemaorg" class="mention hashtag" rel="nofollow noopener" target="_blank">#schemaorg</a> <a href="https://fosstodon.org/tags/google" class="mention hashtag" rel="nofollow noopener" target="_blank">#google</a>

Inautilo<a href="https://mastodon.social/tags/Development" class="mention hashtag" rel="nofollow noopener" target="_blank">#Development</a> <a href="https://mastodon.social/tags/Trends" class="mention hashtag" rel="nofollow noopener" target="_blank">#Trends</a> 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">https://ilo.im/164cfq</a>“Chrome’s days are numbered.” _____ <a href="https://mastodon.social/tags/OpenWeb" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenWeb</a> <a href="https://mastodon.social/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebStandards</a> <a href="https://mastodon.social/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#AI</a> <a href="https://mastodon.social/tags/AnswerEngine" class="mention hashtag" rel="nofollow noopener" target="_blank">#AnswerEngine</a> <a href="https://mastodon.social/tags/SearchEngine" class="mention hashtag" rel="nofollow noopener" target="_blank">#SearchEngine</a> <a href="https://mastodon.social/tags/Google" class="mention hashtag" rel="nofollow noopener" target="_blank">#Google</a> <a href="https://mastodon.social/tags/Chrome" class="mention hashtag" rel="nofollow noopener" target="_blank">#Chrome</a> <a href="https://mastodon.social/tags/Browser" class="mention hashtag" rel="nofollow noopener" target="_blank">#Browser</a> <a href="https://mastodon.social/tags/WebDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebDev</a> <a href="https://mastodon.social/tags/Frontend" class="mention hashtag" rel="nofollow noopener" target="_blank">#Frontend</a>

W3C DevelopersCongrats to editors Matt Garrish and <a href="https://w3c.social/@tzviya" class="u-url mention" rel="nofollow noopener" target="_blank">@tzviya</a> for the two newly published <a href="https://w3c.social/@w3c" class="u-url mention" rel="nofollow noopener" target="_blank">@w3c</a> <a href="https://w3c.social/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebStandards</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">#timetoadopt</a> ▶️ <a href="https://www.w3.org/TR/dpub-aria-1.1/" rel="nofollow noopener" translate="no" target="_blank">https://www.w3.org/TR/dpub-aria-1.1/</a> ▶️ <a href="https://www.w3.org/TR/dpub-aam-1.1/" rel="nofollow noopener" translate="no" target="_blank">https://www.w3.org/TR/dpub-aam-1.1/</a><a href="https://w3c.social/tags/ebooks" class="mention hashtag" rel="nofollow noopener" target="_blank">#ebooks</a> <a href="https://w3c.social/tags/accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#accessibility</a>

🧿🪬🍄🌈🎮💻🚲🥓🎃💀🏴🛻🇺🇸URLs should be able to include HTTP verbs and headers. 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. Leaving HTTP verbs and headers out of URLs was an arbitrary decision.<a href="https://mastodon.social/tags/web" class="mention hashtag" rel="nofollow noopener" target="_blank">#web</a> <a href="https://mastodon.social/tags/http" class="mention hashtag" rel="nofollow noopener" target="_blank">#http</a> <a href="https://mastodon.social/tags/hypermedia" class="mention hashtag" rel="nofollow noopener" target="_blank">#hypermedia</a> <a href="https://mastodon.social/tags/hateoas" class="mention hashtag" rel="nofollow noopener" target="_blank">#hateoas</a> <a href="https://mastodon.social/tags/webStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#webStandards</a> <a href="https://mastodon.social/tags/html" class="mention hashtag" rel="nofollow noopener" target="_blank">#html</a> <a href="https://mastodon.social/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#programming</a> <a href="https://mastodon.social/tags/networking" class="mention hashtag" rel="nofollow noopener" target="_blank">#networking</a>

dokieli🚀 <a href="https://w3c.social/tags/dokieli" class="mention hashtag" rel="nofollow noopener" target="_blank">#dokieli</a> ( <a href="https://dokie.li/" rel="nofollow noopener" translate="no" target="_blank">https://dokie.li/</a> ) is a web-based <a href="https://w3c.social/tags/decentralized" class="mention hashtag" rel="nofollow noopener" target="_blank">#decentralized</a> article <a href="https://w3c.social/tags/publishing" class="mention hashtag" rel="nofollow noopener" target="_blank">#publishing</a> and <a href="https://w3c.social/tags/annotation" class="mention hashtag" rel="nofollow noopener" target="_blank">#annotation</a> <a href="https://w3c.social/tags/application" class="mention hashtag" rel="nofollow noopener" target="_blank">#application</a> and browser extension, built as an <a href="https://w3c.social/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a> ( <a href="https://git.dokie.li/" rel="nofollow noopener" translate="no" target="_blank">https://git.dokie.li/</a> ) project using <a href="https://w3c.social/tags/webstandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#webstandards</a>.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.

Steve FaulknerARIA/HTML relationship Severance"You could use standard HTML controls without all that stinking DOM darkness and encapsulation fandango fucking up your relationships."<a href="https://mastodon.social/tags/HTML" class="mention hashtag" rel="nofollow noopener" target="_blank">#HTML</a> <a href="https://mastodon.social/tags/ARIA" class="mention hashtag" rel="nofollow noopener" target="_blank">#ARIA</a> <a href="https://mastodon.social/tags/a11y" class="mention hashtag" rel="nofollow noopener" target="_blank">#a11y</a> <a href="https://mastodon.social/tags/WebDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebDev</a> <a href="https://mastodon.social/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebStandards</a><a href="https://html5accessibility.com/stuff/2025/06/07/aria-html-relationship-severence/" rel="nofollow noopener" translate="no" target="_blank">https://html5accessibility.com/stuff/2025/06/07/aria-html-relationship-severence/</a>

Steve Faulkner🗿 the ARIA combobox role has gone through some changes during its specified life. It is worth reading about it in its latest incarnation in ARIA 1.3<a href="https://mastodon.social/tags/aria" class="mention hashtag" rel="nofollow noopener" target="_blank">#aria</a> <a href="https://mastodon.social/tags/a11y" class="mention hashtag" rel="nofollow noopener" target="_blank">#a11y</a> <a href="https://mastodon.social/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebStandards</a> <a href="https://w3c.github.io/aria/#combobox" rel="nofollow noopener" translate="no" target="_blank">https://w3c.github.io/aria/#combobox</a>

Web Accessibility InitiativeW3C Accessibility Specialist Daniel Montalvo will be at the Inclusive Africa Conference 3–5 June 2025. Daniel’s sessions are available free for remote participants: - 12.10pm (EAT), 3 June: Global Implementation of Accessibility - 2.40pm (EAT), 3 June: Roundtable on Developing Africa’s Digital Accessibility StandardRegistration: <a href="https://kutanaevents.com/events/inclusive_africa_conference" rel="nofollow noopener" translate="no" target="_blank">https://kutanaevents.com/events/inclusive_africa_conference</a><a href="https://w3c.social/tags/DigitalAccessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#DigitalAccessibility</a> <a href="https://w3c.social/tags/WAI" class="mention hashtag" rel="nofollow noopener" target="_blank">#WAI</a> <a href="https://w3c.social/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebStandards</a>

Steve FaulknerHow strict should the application of "2.5.3: Label in Name" be for languages other than English?<a href="https://mastodon.social/tags/a11y" class="mention hashtag" rel="nofollow noopener" target="_blank">#a11y</a> <a href="https://mastodon.social/tags/WCAG" class="mention hashtag" rel="nofollow noopener" target="_blank">#WCAG</a> <a href="https://mastodon.social/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebStandards</a><a href="https://github.com/w3c/wcag/discussions/4397" rel="nofollow noopener" translate="no" target="_blank">https://github.com/w3c/wcag/discussions/4397</a>

Frühere Suchanfragen

Suchoptionen

Verwaltet von:

Serverstatistik:

#webstandards