Adrian Roselli

One hoopy frood who really knows where his towel is.

Searchable on tootfinder: https://tootfinder.ch/

Web-o-tron: https://adrianroselli.com/
RSS-o-tron: https://adrianroselli.com/feed

Public Key

npub1he7dskfxg8pr4h97kqeckp8qfug5rwwl5vhghh36n0fpk5lxrhxqtammdk

NIP-05 Address

aardrian_at_toot.cafe@momostr.pink

Profile Code

nprofile1qqstulxctynyrs36mjltqvutqnsy7y2ph806xt5tmcafh5sm20npmnqprpmhxue69uhhyetvv9ujumt0d4hhxarj9ecxjmntqyvhwumn8ghj7un9d3shjtnddakk7um5wgh8q6twdvhsen87rf

Publishing to

relay.momostr.pink

relay.primal.net

Author Public Key

npub1he7dskfxg8pr4h97kqeckp8qfug5rwwl5vhghh36n0fpk5lxrhxqtammdk

Show more details

Last Notes

2024-09-29 00:34:45

- reply

He probably quizzed her. I’m sure it was very formal and not at all made up.

2024-09-29 00:16:19

- reply

I made this argument in 2018 when Automattic had demonstrated it was a poor steward of the WordPress project:
https://adrianroselli.com/2018/12/lessons-from-gutenberg.html
Oh, I also documented how Matt Mullenweg is himself the cash-focused prototypical technbro, including all the misogyny, while he cloaks himself in the feel-goods of open source.
IOW, regardless of whatever WPEngine’s problem is, this take-my-ball-and-go-home man-child behavior is absolutely on brand for this guy.

2024-09-29 00:11:43

It is striking how much this quote from Automattic’s head hews so closely to Automattic’s decision to force #Gutenberg into #WordPress, without much consideration for #accessibility (for authors nor users) and with its corporate OSS contributions primarily around pushing the feature and failing to clean-up its own bugs & barriers.
“…giving our users a crappier experience so they can make more money.”
https://wordpress.org/news/2024/09/wp-engine/

2024-09-24 05:40:27

Hugs ok but $5.
#w3cTPAC
https://assets.toot.cafe/media_attachments/files/113/190/923/499/807/754/original/792b043b0ce910ae.jpg

2024-09-18 11:30:06

- reply

Which also makes the push to remove or obfuscate scroll bars (by the OS and developers) that much more insulting.
https://adrianroselli.com/2024/09/under-engineered-estimated-reading-time-feature.html

2024-09-12 20:03:13

Right now…
Chancey Fleet and Lauren Race
“Inclusive Methods for Co-Design Between Blind and Sighted Designers”:
https://www.youtube.com/watch?v=IoNp-QvZm_o&list=PLn7dsvRdQEfFompoGO_CE5z-_HjEdgVit
#id24

2024-09-10 15:26:15

- reply

So, not raising the dead kind of raising?

2024-09-10 15:26:15

- reply

So, not raising the dead kind of raising?

2024-08-23 12:37:57

“Smart” products have already demonstrated they are malware vectors and also part of the panopticon. Thanks to #Sonos we know they can be unintentionally remotely hobbled (versus when the corp means to to brick it).
But now they are shaking down existing and second-hand customers for new monthly fees:
• Peloton https://arstechnica.com/gadgets/2024/08/peloton-announces-95-used-equipment-activation-fee/
• Happiest Baby https://www.nytimes.com/2024/08/16/style/snoo-bassinet-smart-sleeper.html
• Anova https://www.theverge.com/2024/8/19/24223878/anova-sous-vide-kitchen-app-subscription
Validating why I buy daft products.

2024-08-16 21:22:09

- reply

Oh man there’s a browser!
I made a kawaii browser for one post and kawaii toast for another and this would have been so much easier (well, for the browser at least).

2024-08-12 13:15:05

When folks ask me “Is this [thing] accessible?” I often respond with questions. To save time in the future and maybe help those folks with their own due diligence, I gathered those questions in a post:
https://adrianroselli.com/2024/08/things-to-do-before-asking-is-this-accessible.html
#a11y #accessibility

2024-08-09 00:16:21

Keep your image alternative text brief, devoid of special characters, empty of URLs, and ideally in one language.
https://adrianroselli.com/2024/04/long-alt.html
The post goes into more detail.
#a11y #accessibility

2024-08-08 11:46:28

A couple years ago Eric wrote about automatic captions and how filtering curse words is bad:
https://ericwbailey.website/published/swearing-and-automatic-captions/
Two examples just from today of folks being rightly frustrated:
• https://chaos.social/@gsuberland/112922780961277083
• https://elekk.xyz/@RC/112921572817888530
If you cannot bear you or your tools faithfully transcribing the words people say then you might be in the wrong business.
#accessibility #a11y

2024-08-07 12:25:58

Heydon reminds that the `<abbr>` element is mostly useless:
https://heydonworks.com/article/the-abbr-element/
I linked it from my post (where I show SR support, which is a bit odd) that says essentially same.

2024-08-02 19:39:07

- reply

And I filed an issue for the Chrome Developer Blog to make the version 127 announcement more than only 10% true:
https://issuetracker.google.com/issues/357082214
Ugh, this fucking company.

2024-08-02 19:23:26

- reply

Confirmation that this feature is not really in 127:
“Currently, 10% of users see it. By 128, 100% of users should expect keyboard focusable scrollers to be enabled by default.”
“Because we need to be a bit nimble as we do that ramp-up, we didn't put all of the nitty gritty details of that ramp schedule into the blog post. But it's true that some people will see this feature enabled in M127, potentially up to a majority of users.”
So Chrome’s claim was 90% wrong.
https://toot.cafe/@aardrian/112877345000799820

2024-08-02 11:23:11

- reply

If you read this from the Google Chrome Developer Blog, when do you expect this feature to be available?
Ref: https://developer.chrome.com/blog/new-in-chrome-127?hl=en#keyboard-focusable-scroll-containers
#accessibility #a11y
https://assets.toot.cafe/media_attachments/files/112/892/168/745/424/753/original/671122809e39337a.png
https://assets.toot.cafe/media_attachments/files/112/892/168/765/339/776/original/addb7b8591aa3026.png

2024-08-01 13:57:04

- reply

Updating this post with Chrome’s stutter-step release of this feature is becoming a part-time job:
https://adrianroselli.com/2022/06/keyboard-only-scrolling-areas.html#Update09

2024-08-01 13:31:21

- reply

I have filed a Chromium bug:
https://issues.chromium.org/issues/356827070
If anyone here knows someone on the Chrome team, probably let them know their latest attempt to make scrolling areas focusable is not working for everyone.
#a11y #accessibility

2024-07-31 20:31:58

Are you running Chrome 127 on Windows? I can use your help for a quick test.
1. Go to this URL:
https://cdpn.io/pen/debug/bGLrYBo
2. Zoom or resize so the table has a scrollbar at the bottom.
3. Without using your mouse, Tab to the table.
4. Use your arrow keys to scroll it left-right.
If it works, cool. If not, less cool. I have a case of someone where the keyboard scrollable containers feature added in Chrome 127 does not work.

2024-06-20 12:23:49

- reply

While I hate to pile on, it’s important to understand that the messge is from frustration with the ongoing and genuine harm that these kinds of barriers introduce.
It is valid to be angry and suggesting otherwise is dismissive of that community experience as a whole. That dismissiveness is part of the problem. Your lack of sympathy as well.
Historically, accessibility affordances only come after using this kind of advocacy. Which sucks.
@npub1p09…m5vl

2024-06-10 12:05:08

I made a YouTube & Vimeo web component (custom element):
https://adrianroselli.com/2024/06/youtube-and-vimeo-web-component.html
I even made a GitHub repo for `<youtube-vimeo-embed>`:
https://github.com/aardrian/youtube-vimeo-embed/
The code is perfect and has no errors of any kind whatsoever.
#a11y #accessibility #HTML

2024-06-06 13:21:42

“Maybe Don’t Name That Landmark”
https://adrianroselli.com/2024/06/maybe-dont-name-that-landmark.html
TL;DR: You probably don’t need to name that landmark. Even if you have two of the same landmark.
#a11y #accessibility

2024-05-08 00:07:56

“Digital Ocean” is a…

2024-04-12 15:55:45

- reply

From working with blind users, very annoying. URLs in particular are the worst. The extra crudt makes it very difficult to consume alt text in some cases given it is read as one string.