🆕 blog! “What about using rel="share-url" to expose sharing intents?”
Let's say that you've visited a website and want to share it with your friends. At the bottom of the article is a list of popular sharing destinations - Facebook, BlueSky, LinkedIn, Telegram, Reddit, HackerNews etc.
You click the relevant icon and get taken to the site with the…
As the leading provider of accessibility training, Digital Access Training is proud to offer on-demand courses that make it easy for you to learn at your own time and convenience.
To elaborate on my hostility against WebKit: WebKit does nothing but get in my way whenever I work on literally any website.
When I rewrote nouveau's website in late 2023, it worked perfectly fine on Firefox (Gecko) and Chromium (Blink), but was broken on Epiphany/Safari (WebKit). The logo, which is an SVG, would not adapt to dark style, because, to this day, WebKit still does not support prefers-color-scheme in SVGs. So, as a workaround, instead of having one SVG file for both color schemes, we have one SVG file for light style, and one for dark style. Edit: This feature is currently considered nonstandard and is only written as a draft. WebKit behaves appropriately, see: estradiol.city/@ity/1150068605…
Another example: On my website, some elements are intentionally made to be unselectable using user-select: none;, such as the command-line decoration and the “Table of Contents” text, but on WebKit, these elements continue to be selectable because it does not properly support the user-select property. And no, using the vendor prefix is completely unacceptable, especially considering that it behaves differently.
Lastly, WebKit does not yet fully support the ::marker pseudo-element. This means, in my articles, numbered list items in the table of contents are completely wrong and don't represent the same numbers as headings.
Apple has consistently proved that they don't care about WebKit, because otherwise browsers like Safari and Epiphany would have worked as well as they do on Firefox and Chromium. There's absolutely no reason to force WebKit onto iOS and iPadOS if they're not even willing to invest in WebKit. Likewise, Apple employees working on WebKit should really stop calling themselves “WebKit evangelists” if their inferior engine regularly gets in developers’ way. So yes, WebKit sucks, and this is 100% on Apple. I don't care about being harsh. Apple is a multi-trillion dollar company, most of which came from exploiting people. The least they can do is invest in their projects.
For clarity, my hostility towards WebKit is purely targeted at Apple's lack of involvement with WebKit, not the browsers using it.
The ::marker CSS pseudo-element selects the marker box of a list item, which typically contains a bullet or number. It works on any element or pseudo-element set to display: list-item, such as the and elements.
That's not normative, that's descriptive of Firefox & Chromium behavior (the purpose of mdn is to be descriptive rather than normative, unlike the specifications themselves)
MDN even warns that "Respects color-scheme inherited from parent" is "non-standard" and to "Expect poor cross-browser support"
The feature itself is listed as "Full support" for Safari/WebKit on that site.
The feature is also considered "unfinished" by W3C, and W3C in the specification warns that
Information about a user can be used as an active fingerprinting vector. Analysis of impact pending, more information to be provided before spec is published. User agents and developers implementing this specification need to be aware of this vector and take it into consideration when deciding whether to use the feature. Specifically prefers-reduced-motion, prefers-color-scheme and prefers-reduced-data are currently of concern for exploitation.
W3C further comments on the specific feature that
[css-mediaqueries] Should prefers-color-scheme in SVG images be context-dependent? RESOLVED: Have prefered-color-scheme reflect 'color-scheme' on the embedding element in the embedding document, to the extent acceptable from security standpoint (pending security review)
I have no idea what policy WebKit has for standards, but the only standard it seems to violate is one that begins with this statement:
This is a public copy of the editors’ draft. It is provided for discussion only and may change at any moment. Its publication here does not imply endorsement of its contents by W3C. Don’t cite this document other than as work in progress.
So while it is certainly dumb that it has not been fixed yet, it feels a bit of a stretch to call it a violation of web standards, imo.
I wonder how difficult it is to fix, I've been meaning to try to get into WebKit stuff
As a developer, I try to make my software as accessible as possible for everyone. Unfortunately, I often lack a view from the user's perspective. I received a list from @dankeck with at least 10 suggestions for improvements, most of which I implemented in one night as if in a fever dream. The game is probably still a long way from being a screen reader user's dream, but I'm doing my best. Step by step! #webdev #a11y
If you have a FAQ on your site, please include anchor links for each entry.
In fact, if you are creating content on the web... please consider using anchor links for headings of all kinds, and anything else that people might want to link directly to. #grumble #web #webdev
The article emphasizes the importance of simplicity in web development, warning against over-engineering and excessive use of ARIA. It highlights that while ARIA can enhance accessibility, improper…
Question for those who use #screenreaders (specifically #nvda with Firefox). How do you get the screenreader to announce the Firefox developer tools? All I seem to get is "Developer Tools frame, Inspector Panel frame, Markup View frame" and no announcement of the actual HTML displayed in the Inspector panel.
Navigating with the keyboard (arrow keys) doesn't announce anything either, nor does NVDA + arrow keys.
Three strips of intersecting yellow and black “warning” tape. Accessibility isn’t an extra feature or a nice-to-have add-on. It’s a foundational requirement...
It's really bugging me that I need to replace a `<fieldset>` with a `div` prepped up with ARIA attributes because Chrome has a decade old layout bug. #webdev #a11y
Since yesterday, I have had an urge to play with CSS again, and it's the least practical time for it.
(Since work during the day and a brain that is currently saying no.)
There is a three-year-old article by Ryan Mulligan that has been living rent-free in my head for a while, and I recently applied it to a hobby project for the first time. I want to learn more about these techniques as I'm not fluent with them yet.
"Layout Breakouts with CSS Grid" featuring named template columns.
Just published a blog post tearing into hCaptcha’s so-called “accessibility” mode.
It’s not accessibility. It’s a cookie. And to get that cookie, you now have to submit your email and send a code via SMS to an U.S. phone number. It fails silently. It doesn’t confirm anything. You click “Confirm Code” and get “An error has occurred.” No cookie. No fallback. No support. And if you somehow get it? It’s a third-party cookie your browser probably blocks, and it expires. Then you get to do it all again.
Meanwhile, hCaptcha’s text-based challenge — the only mode that might actually work with a screen reader — isn’t tied to the cookie at all. It only shows up if the website owner specifically enables it. Most don’t. So even if you’re blind, even if you’re using assistive tech, you get the same unusable image grid as everyone else.
This isn’t accessibility. It’s exclusion wrapped in PR.
The blog post breaks it all down: how the cookie flow works (or doesn’t), why the system is broken by design, how developers got misled, and what real alternatives look like. If you care about accessible design or just want to understand how bad this gets, read it.
Lightweight open source Google reCaptcha alternative: ALTCHA leverages a proof-of-work mechanism to safeguard your website, APIs, and online services from spam and abuse. Unlike traditional solutions, ALTCHA is self-hosted, does not rely on cookies or fingerprinting, and ensures complete user privacy. It is fully compliant with GDPR, WCAG 2.2 AA-level, and the European Accessibility Act. github.com/altcha-org/altcha
FeedBagel helps you find and discover RSS feeds from any website. Search for RSS feeds by URL or browse our curated feed directory to follow your favorite blogs and news sites.
How do we translate web accessibility standards to command line applications? This is GitHub CLI's journey toward making terminal experiences for all developers.
Manufacturers who sell TVs in the UK & want the TV to run BBC iPlayer (BBC Public Service live/on-demand TV app) have to get their TVs certified by us. There's a large suite of tests & technical requirements - a colleague just pointed out to me that those docs are public:
TVs on UK sale now & marked with the iPlayer logo must support: * TLS 1.2+ * Mutual TLS (client certs) * HTTP/2+ * Service Workers & lots more...those just caught my eye
It used to be quite challenging to set the precedence of individual #CSS rules without a lot of headaches. (This encouraged the practice of authoring many small utility classes that do very little on their own.)
@geoff over at #CSS Tricks has written a definitive guide on using <details>, a number of possible use cases, and some of the trickier aspects of styling it and even animating the opening and closing states. I’ll be sure to refer to this the next time I do #WebDev on a <details>-based feature!
today is officially *THREE* weeks until the submission deadline for Good Internet magazine!
Good Internet launches in May 2025. it's a volunteer-run, not-for-profit print and digital quarterly magazine for personal website owners and those interested in using the internet as a means of self-expression, art, and recreation.
🔍 we're looking for 1,500-4,000 word articles about anything related to that!
if it relates to hobbies on "this side of the web," whether you call it the #smallweb or indieweb, we probably want to run it!
you can have your article as low-media (meaning only text and images) or interactive, where you code an entire webpage to help tell your story.
if you're interested in learning more, you can sign up for our email list for when we launch or you can check the submission guidelines @ goodinternetmagazine.com!
🤔HTML semantics: <abbr> theory versus abbreviation reality
"The HTML <abbr> element is deceptively familiar and attractive, its been around forever (1999) and thus people assume that it does what it does and does it well. Nothing much changed over the iterations of the abbr element definition over the years."
Don’t use the aria-label or aria-labelledby attributes on divs, spans, or other elements representing static/noninteractive text-level semantics, unless you’re also updating roles.
Many users prefer to use an RSS feed reader to stay up to date with the content on the websites they visit. But if you've enabled Cloudflare on your website, you're likely blocking these RSS users from accessing your website content without realizing it. openrss.org/blog/using-cloudfl… #RSS #CloudFlare #WebDev
