Notices by Eric Eggert (yatil@yatil.social), page 3

@kc Sehr cool!

NASA programmers: ”We distributed the program from the broken chip into different parts of Voyager and changed all the references to ensure that it all keeps working. We had one attempt at this.”

Web developers: “How am I supposed to remember to label my buttons and style focus states?? It’s just too hard!”

(Sorry, could not resist. 😂 I recognize the systematic problems around the education of web developers that are often trained to be one-trick ponies where the trick is a framework.)

If your links to WCAG Techniques or Understanding have a /TR/ in it, they are outdated, probably many, many, many years.

There are no redirects.

Outdated: https://www.w3.org/TR/WCAG20-TECHS/G83.html
Current: https://www.w3.org/WAI/WCAG22/Techniques/general/G83

(That said, notes were better marked in the old one. Someone should really take a look at this.)

IAAP wants disabled people, including photographers, to do work for free. And not even just for the course, the license is CC-Zero or CC-By which allows anyone to do anything with it.

IAAP charges for these courses. Do not submit your photos. Everyone, but especially people who are disadvantaged, have the right for fair and just compensation. Outrageous!

Link: https://www.linkedin.com/posts/international-association-of-accessibility-professionals_google-forms-sign-in-activity-7178058774023143426-eLR9

#a11y via @kc

Awesome, the neighboring state has cell broadcasting test day and because we don’t live in that state (but only a few kilometers away), I did not expect it at all.

That’s so scary!

@mia @matuzo User styles are great, but being able to say “never use font sizes smaller than 12px” is a killer feature for me. I wished other browsers had settings like that (and that these settings would expand: “Never use low contrast colors” and so on).

I would not be surprised if the exact demands towards the regulation was unclear and lawyers included PWAs just to be sure. Removing them so publicly might have been a way to get the regulators to say “we don’t consider PWAs as part of the browser” or “we give you a longer deadline”.

Testing out the edges of regulation is a weird fascination for me, so I would have loved to be in the room 😅

Apple Reverses Course on PWAs in EU https://512pixels.net/2024/03/apple-reverses-course-on-pwas-in-eu/

Yeah, sure gonna trust your conference where, according to the generated image, the “Registrratiion Open”.

I’m so tired of people not caring about their own stuff and making it mediocre by having half-assed “AI” involved.

So, this is why I don’t like people trying to “simplify” WCAG. Stark did it and I only looked at its 1.1.1 Non-Text Content page.

Several notes:
1. I don’t think this is much clearer than 1.1.1 itself. There is more fluff, but I don’t think it’s super useful
2. It calls the Success Criterion “Guideline” under the “What:” heading
3. It names transcripts/captions, which are only tangential to the SC at hand
4. No info that decorative images must be ignored

https://www.getstark.co/wcag-explained/perceivable/text-alternatives/non-text-content/

#a11y

“We should give the abusing party the benefit of the doubt” seems to be a common thought amongst the accessibility community. Which is of course why you would hire a prominent face in accessibility in the first place. “I can make them change” has been uttered in many abusive relationships, but it basically never happens.

#a11y #accessibility

@thomasfuchs Yes, exactly. Sometimes I want to say: Just give me access to your templates, I’ll rewrite them to proper HTML in two hours, fixing all issues. But that is also not useful, because it only fixes the symptoms.

It’s amazing that we used to write templates for online shops as one-person gigs no 10 years ago, but now making an accessibility change takes a team and a project manager.

Sure, technology got more complicated, but this is ridiculous!

The notion that we just need to reinvent WCAG to fix web accessibility is weird to me. I mean, there is lots to fix, but in the end, we need to make accessibility simpler and engaging. It must be so easy that the spec details don’t matter.

https://github.com/w3c/wcag3/discussions/33#discussioncomment-8112150

Making Braille cells cheap and abundant is something everyone should be working on. There was a concept that I saw a few months back that showed potential. It feels not even a difficult thing to do – but as long as there is no competition, there is no innovation. https://mastodon.social/@alexhall/111698222951198219

WCAG 2: Guidelines and Guardrails

A blog post about the two standards that are actually inside of WCAG 2.

https://yatil.net/blog/wcag-2-guidelines-and-guardrails

Well, this explains why cross-posting through micro.blog is not working anymore 😀

Gotta trim my feed!

@manton Maybe an error message in account/feeds would be useful when this happens. 😂

AIshittification

#enshittificationWithAI #enshittification #aishittification

The web was created with accessibility in mind, but in reality most stakeholders give as much shit as the general public about accessibility. Which is not a lot.

@baldur “We have to pretend this is surprising because we have largely enabled this unsustainable behavior.”

Why can’t Deutsche Post just let me know in an email in advance that there is a fee on the post I get from abroad?

They attempt to deliver once and ask you to have €9.38 on hand to pay for it. If you don't have the amount handy or take more than a minute to answer the door, they bring it to the nearest branch, where they keep it for a week and then return it.

Just let me pay online and deposit it in my letterbox. It’s not that hard.