Notices by Eric Eggert (yatil@yatil.social)

@lichtscheu @svenja An meinem iPhone kann ich die Seitentaste drücken, die auch den Bildschirm sperrt. Der Warnton geht dann aus, die Meldung bleibt im Benachrichtungs-Center. Ich glaube so habe ich mein Android-Testtelefon auch ruhig gestellt.

Why use a simple language that is right there and immensely powerful and not dependent on the author of a document to do something specific, when you can also ask everyone to write new JS templates? 🤷♂️ https://mastodon.social/@jaffathecake/115135860889032008

Gotta say, it is very brave to show to severely lackluster examples as supposed “expert” guidance by Deque’s AI in the article. (Of course without image recognition, blind users have no way to determine this, as the alternative text of the sample images is bad, too.)

Modern browsers will announce the name of a focusable element that is aria-hidden. Using required in the accessible form can be problematic (and is not needed for screen readers as the example claims). (1/2)

And 4000 hours of 3000 people is about 0,075% of people’s time. But sure, even that little is too much for accessibility. 🤷♂️ 80 minutes per year per employee is too much!

https://www.deque.com/blog/how-to-eliminate-costly-rework-and-fix-accessibility-issues-early-with-expert-guidance-from-axe-assistant/ (2/2)

“Look how beautiful these clothes are looking on our naked emperor!!!”

“I reformatted your phone!” – “All my stuff is on there!” – Cheerful: “Not anymore!!”

So good!

> investment in AI data centres accounts for about half of all US economic growth in 2025

Bubble or not, bubble or not? It certainly feels like a bubble. https://wandering.shop/@cstross/114982328165405817

I have not read the books yet, but the show felt all-around interesting and well produced. I think especially the relation between humans and Murderbot felt realistic in how they needed time to accept it. Also all characters felt very fleshed out, for an ensemble cast with a short runtime a real feat. I’m looking forward very much to season 2 (and hope to read a good chunk of the novellas until then!)

Providing an LLMs.txt to allow “AI” to get to your content easier is like putting your keys under the doormat, only that the doormat has KEYS UNDER HERE written in large letters and a sign on you street points at your house, saying ROB ME.

There is not a single benefit for you or for users that search for your content when it is mangled through statistical text output machines.

(Also, if you “AI” can’t read the standardized HTML format for content, why does it even exist?)

@WeirdWriter I mean, if they really think your writing is “a goldmine of qualitative human experience”, they are probably happy to send you actual gold in exchange, right?

Also, I love the “AI is so intelligent, but it is not intelligent enough to read your texts!” angle.

What a knob.

@tagesschau Die Rechtsextremen sind es, die keine Verbindung zu denen haben, die mit beiden Beinen auf dem Boden des Grundgesetzes stehen. Nicht die Fußballer sind schuld, dass es keine Gemeinsamkeiten gibt, sondern die Neo-Nazis.

So eine Quatschmeldung.

@Fragglemuppet Apple Music – The App lets you buy stuff. It’s basically iTunes.

Apple Music – The Service is the Streaming service.

You do not need to subscribe to the service to buy music.

I appreciate making WCAG more approachable, but this will lead to failures. Calling it WCAG is misleading because you will likely not meet conformance when using these cards. I wished people helped others understanding the requirements instead of reinterpreting them.

https://www.figma.com/community/file/1409436654182046971/wcag-2-2-card-deck (2/2)

Some people are recommending the following “WCAG” card deck, so here is my warning:

Some of these cards are problematically simplified – as it is often the case with these projects. 1.1.1 as shown on the images leaves out a whole lot of other use cases like pure decoration, CAPTCHAs, and images in interactive controls. (1/2)

@sarajw @matuzo …in a PDF in an iframe.

The cardinal sin of the CSS carousels is not framing the problem correctly. This is done so often in design and development, it’s one of the biggest problem.

Don’t ask how to make [carousels] accessible, ask what an accessible experience would look like that has a similar functionality as [carousels].

Framing it with accessibility first in mind will reveal much better solutions for everyone that are almost automatically accessible, too.

I see something that looks like tabs.
I think “surely these are implemented as ARIA tablist but reload the whole UI”.
I am right.

Stop using role="tablist" if your page reloads.

FFS.

#accessbility #a11y

@tagesschau The fuck? Gestern schrubt ihr noch “Boohooo, wir haben viel zu wenig Auslastung and den Ladesäulen” und heute heißt es “Boohooo, die Ladeinfrastruktur muss ausgebaut werden”.

Macht eure Arbeit als Journalisten und guckt raus ob der Himmel blau ist oder nicht.

And, honestly, just putting Chrome in an alternative Alphabet bucket will do squat. It would need to be its own foundation with mandatory payments from Chromium browser manufacturers.

https://open-web-advocacy.org/blog/break-googles-search-monopoly-without-breaking-the-web/ (3/3)

OWA, now: “Oh, no, breaking Google’s monopoly can have side effects on other browsers! And the open web.”

Not seeing the monopoly building objectively and finding a holistic solution has broken the web. This was clear when OWA lobbied against Safari, and now they are trying to counterweight the damage that is done. Focusing on browsers instead of ecosystems was always deemed to fail. Divorcing Google from Chrome would have needed to be the first step, not an afterthought. (2/3)