There are only 45 comments so far on the FTC settlement with #accessiBe and the last day to leave comments is Wednesday, 5 February:
https://www.regulations.gov/document/FTC-2025-0002-0001
I am leaving mine later today.
Context:
https://adrianroselli.com/2025/01/ftc-catches-up-to-accessibe.html
@mahryekuh @jscholes
I had not seen that thread, thanks. It doesn’t answer my question, though. And James has already spent a lot of time in that thread and in another forum explaining things in the last 24 hours so I hate to put him out again.
@mahryekuh @jscholes Not meant as criticism, I just don’t understand the use case.
@mahryekuh @jscholes
I am a bit confused why the headings would be hidden from sighted users (including sighted screen reader users).
If the content warrants a heading, then everyone would typically benefit.
If it’s only used to make regions navigable, then you risk arbitrary heading structures (and repeated navigation points when using heading *and* landmark navigation).
If that, then why not non-heading visually-hidden arbitrary plain text instead? You only need it for the accName.
Teen Vogue again showing popular press how to do journalism that challenges state abuse of power.
“ICE Watch Programs Can Protect Immigrants in Your Neighborhood — Here’s What to Know”
https://www.teenvogue.com/story/ice-watch-programs-immigrants-how-to-start
Chrome, as of 132, finally has keyboard support for scrolling containers:
https://adrianroselli.com/2022/06/keyboard-only-scrolling-areas.html#Update15
This assumes it doesn’t get rolled back again, as it has every other time it was deployed since 2018.
Silence from Safari.
A convo this morning about the .blog gTLD triggered memories of the 2012 new gTLD chaos (I blogged about it back then) and got me digging to see who ‘owns’ the registry:
https://www.iana.org/domains/root/db/blog.html
Knock Knock WhoIS There, LLC is owned by Matt Mullenweg:
https://ma.tt/2016/05/blog/
I am not a gTLD expert and don’t know the Mullenrisk here.
APCA is no longer part of WCAG3. You can still use it, but for conformance (legal, policy, etc.) reasons you will still need to follow WCAG2. It’s possible to satisfy both in most cases.
I wrote this advice for him in 2019 when inaccessible themes came up:
https://adrianroselli.com/2019/05/a-model-for-wordpress-accessibility.html
And that was after he did nothing with the information I gave him when he commented on my Gutenberg post mortem in 2018:
https://adrianroselli.com/2018/12/lessons-from-gutenberg.html#comment-121639
6 years and no movement.
Mullenweg has never cared about accessibility. He has never cared about the disability community. Frankly, he’s never cared about the WordPress community other than its value as free labor and marketing.
The tone-policing “just asking questions” BDFL is back and being as hostile to accessibility concerns as ever, trotting out the tired argument that art is the same as design.
I have a canned response for that absurd argument:
https://adrianroselli.com/2021/05/embracing-design-constraints.html
Mullenweg has always been dismissive of accessibility, even when he was still only a couple billion dollar company.
His hate-site post: https://twitter.com/photomatt/status/1875186207405334922
