Notices by Eric Eggert (yatil@toot.cafe)

@SteveFaulkner @w3c For the EU, it doesn’t matter as the AAA criteria are not included anyway. And I assume that EN will happily hear that there will be a decade of WCAG vacuum to make their own rules in. Stopping the work on WCAG 2 is a bad idea, I would not be surprised if we got a WhatWG situation.

You know, if you find an accessibility issue on a website of an accessibility person, just inform them. It’s professional curtesy. Nobody is perfect, and we all make mistakes. Just be kind.

@SteveFaulkner So they will keep not defining what a visible focus is for the 15th year running. Bull.

I’m furious that it took two, TWO, CR phases for the WG to come to the realization that in an SC, which screams “hard to test”, (quote from the meeting minutes) “the survey seems to indicate that testability is the main issue”.

You could reasonably make a good SC or two or three out of it. If you wanted, but the WG does not want to put in the work. And now everybody is exhausted, so we agree to put it on the AAA shelf. Hooray. Great use of resources.

Moving Focus Appearance to AAA is the worst outcome. At least define very broad categories of what visible means and slide them in at AA. “A part of the focused component must have a 3:1 contrast compared to the unfocused component.” Urgh. So much wasted time in the community for an ineffective rule.

https://lists.w3.org/Archives/Public/w3c-wai-gl/2023JanMar/0309.html

WCAG 3 is still not a thing.

(The existing first Working Draft is many, many years away from a state when it can be relied on.)

#reminder

So many of the basic HTML/CSS questions regarding accessibility are easily answered by looking at the specification. Most of the stuff is well specified and the HTML standard in particular is pretty well written.

Maybe I need to do a “How to read specs” webinar/stream/video.

When I learned that a COVID infection is potentially damaging the brain, even with “mild symptoms” or when asymptomatic, it changed the risk level that I’m willing to take dramatically.

Most of my work and income is a result of using a brain, and I don’t have spares. It’s a one-use item, so I gotta protect it.

Accessibly overlay vendors (remember: overlays do not work) have produced a handy list of such tools: https://github.com/a11yedge/overlays/issues/1

The GitHub issue is titled “Review what existing overlays actually do“ and from my point of view, it’s somewhere between “nothing” and “harm”, with a sprinkle of normalizing ableism. Cool, cool. Cool.

(Via @aardrian)

Remember when in the early mobile web websites asked you to add them to your Home Screen, often with banners that obscured the content? It’s coming back, baby! Just with the option of also getting pinged by Notifications.

😐

https://webkit.org/blog/13878/web-push-for-web-apps-on-ios-and-ipados/

As decent as a standard WCAG is, and as much as policymakers love it, it has a reputation problem with developers and other stakeholders. Even mentioning is creates trepidation. This comment speaks volumes: https://dev.to/grahamthedev/comment/24p6j

Prepare to get ask by all sites to install their websites as apps 😩 (I understand that Web Push is an often requested feature, but I don’t like the nagging that comes with it. – Putting it behind a user action and only when installed as a web app is the right decision, IMHO.) https://front-end.social/@jensimmons/109875869667947701

This @tomscott video is just amazing.

https://youtu.be/jPhJbKBuNnA

Automated testing won’t solve web accessibility: https://yatil.net/blog/automated-testing-wont-solve-web-accessibility

Automated transcriptions are just on the cusp of being a no-brainer for everyone. I think once Whisper indicates speaker changes or can even identify speakers, the whole world of audio, especially from more niche sources, will be made more accessible for many people. https://zeppelin.flights/@jsnell/109831862214536170

Posting this again for no reason at all.

https://yatil.net/blog/wcag-3-is-not-ready-yet

I appreciate @alastc’s descriptions of how to meet Focus Appearance here. But it shows the complexity and added a few additional questions for me.

As always, the core concern here is not the easily testable cases. It is the a) amount of components and b) determining how many of them are non-obvious. I still think splitting it up into multiple SCs is the best approach, but I also don’t think it will happen. I updated my blog post:

https://yatil.net/blog/new-wcag-22-features-rated#update-7-february-2023 https://toot.cafe/@alastc/109823105020304108

As always impressed by @jsnell’s work on these Apple Report Card articles. Super detailed and it gives a nice feel for what the general “vibe” around Apple is. I would love to do something like this for web accessibility one day…

https://sixcolors.com/post/2023/02/apple-in-2022-the-six-colors-report-card/

Wow, I hope browsers let users disable view transitions… A full window/display animation like that can certainly be triggering.

CW for video and demo: large, swirling animation with depth effect.

https://toot.cafe/@jaffathecake@mastodon.social/109818467681971657

@freakazoid @alcinnz People made browser-based apps because it was easy to do. Had and has zero to do with speeds, indeed page weight has gone up and speeds down over the years. (And most use cases are better met by native apps for me. Better usability and platform integration. That’s important to me.)