Notices by Eric Eggert (yatil@yatil.social)

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)

Me, 4 years ago: “Breaking Safari which has no monopoly over the web is a bad idea, because it is the only remaining counter-weight to Google which literally controls most people’s browser, email, online documents storage, and phones.”

OWA: “LOL yeah, but Safari will get more investment because competition! Also there cannot be any side effects!”

(Competing browser engines have been possible on iOS in the EU for over a year now, there are zero.) (1/3)

*sigh* Gumroad now also works with DOGE. This is bad. Time for @joinsteady to support digital products, too. (Instead of only supporting subscriptions to content.)

https://www.wired.com/story/doge-department-of-veterans-affairs-ai/#:~:text=Lavingia%20is%20the%20CEO%20of%20Gumroad%2C%20a%20platform%20that%20helps%20creatives%20sell%20their%20work%20and%20takes%20a%20cut%20of%20each%20sale.

@tagesschau Bizarr.

So, this 77 × 22 × 22 mm electronic device got send to me in a box with the dimensions 153 × 78 × 60 mm which came in a parcel of 330 × 290 × 115 mm.

The parcel is 295 times the size of the item.
The box is 19 times the item. And filled with foam, because that’s what you do with all that air.

The parcel is 15 times the box.

I recognize some protection is needed, but this feels super excessive. Just put the box into an envelope. It’ll be fine.

@kc Dann halt nicht.

Deque says “AI” will help to “automate 100% of accessibility”. That’s bullshit.

The automated transcript of the talk where they say it cannot figure out that they talk about “axe” and writes “X” instead.

Oh, and instead of “Deque“, the transcript says “TC”.

100% of accessibility errors! “AI”! Sure.

(Also they chose to not afford human transcribers. A multi-million dollar company. Because f those disabled people.)

https://www.deque.com/axe-con/wp-content/uploads/2024/11/Ai-Media_46997_THE_STATE_OF_ACCESSIBILITY_FEB_25_2025_.txt

#a11y #accessibility

However, disabled people are limited in their human rights every day. Some less, some more. Your privilege to not see those discriminations does not overwrite their right to participate in an inclusive way. (2/2)

It’s always interesting to see who feels attacked when performative allyship is pointed out. Do I think people are on purpose performative? Maybe not always, maybe even rarely. But that’s a bias and people need to understand that.

When the people you want to be an ally for point out that your actions feel hollow and useless, then it is your place to listen and correct. It’s not their task to mitigate and put critique in a nice package.

Even well meaning peeps and orgs can do harm. Do better.

I think non-disabled people, even if they want to do the right thing, don’t know how all-encompassing disability discrimination is. They have the privilege to not encounter that discrimination every day. When it gets pointed out to them that they indeed could do things better or that there are societal issues, they see the loss of that privilege as a loss of a right. (1/2)

When the question is: headache from CO2 or from PM2.5 particles and Germany is like: YES!

I’m so glad I got these air filters.

@jscholes People over-explaining stuff to screen reader users is one of my pet peeves. “Should we write out this phone number as individual number words so that the screen reader does not announce it as a large number?” 😳

@Mela Ufff. Das geht gar nicht.

@Mela Möchte niemand verteidigen, aber im Ausgangs-/Gesuchposting hieß es, dass von Seiten der Referent*in abgesagt wurde und, dass Gebärdensprachdolmetscher*innen reserviert seien (aber nur für den Termin – was ein ganz anderes Verständnisproblem offenbart)… Also wohl keine “Ausladung”? https://www.linkedin.com/posts/katrin-n%C3%A4gele-0b3512256_wir-geben-noch-nicht-auf-unser-referent-activity-7282311181652877312-0XfY

I started writing a blog post… and then realized that I had already written that blog post. This happens more often than one would think.

https://yatil.net/blog/the-infuriating-inefficiency-of-accessibility-audits

Instead of “alt text” or “alt-text”, write “textual alternative for this/an image”.

You would be surprised how many people stumble over that bit of jargon.