One of its greatest flaws

Smart

I wish though that calling out someone as making bullshit statements wasn’t rebutted with “you’re being mean by calling out that I d ok not know what I’m talking about”

Shouting sounds fine to me.

Statement like that are bullshit and shouldn’t be made. Full stop.

thanks for posting that.

“If they (screen readers) wanted to”

I hate statements like this, as if the people making screen readers should be expected to find this sort of info that is not included in the a11y tree

It’s today again.

Automated WCAG Testing Is Grrreat! I’m a big fan of using automation in WCAG testing. I use bookmarklets, dev tools, browser features & reporting, and a pile of third-party products from assorted vendors. These save me time and effort,...

The Accessibility Conformance Testing (ACT) Task Force has published its rules, letting you filter automated rules:
www.w3.org/WAI/standard...

It’s only partial coverage of 31% of SCs:
adrianroselli.com/2025/04/auto...

Automation is good, but limited. Understand those limits.

#accessibility #a11y

would love for the family of input buttons type=button,submit,reset,image to be made obsolete

When your experience of the web has only been visual, it's really easy to say that the underlying code doesn't matter.

Initial prototype of a `<toolbar>` element is coming along. Largely piggybacks off the focusgroup code so it's actually quite simple to do.

Lots to discuss and tweak before it's finished but got to start somewhere.

2/2

(Important note: it is a draft, far from completed, and we have lots of work planned. Feedback is welcomed!)

The latest Working Draft of WCAG 3 is out today! w3.org/TR/wcag3/

In this version, we've:
- moved lots of requirements to “Developing” phase,
- wrote down how to test,
- mapped reqs to user needs (using DAF),
- split out 'applies when' and 'except when' to massively increase readability
1/2

“Shouldn’t”

there are UX challenges to solve with making sure users can effectively reach the different sections of parallel content (dialogs or not).

solvable, but not with truly "modal" dialogs. since that's in opposition to what "modal" means.

heh... fwiw i don't think any of the use cases that have been called out are a11y blackholes.

there are valid use cases for dialogs that are fully modal, and for non-modal dialogs (standard or popover) that need to be used in parallel with other content that may or may not be inert.

which is what a ctrl + f6 command to navigate between dialogs could be useful for - but then users need to be made aware that exists...

tldr; it's not as simple as it's being made out to be, which i understand may be due to limited characters per messages... i'm mean, i'm bored of typing now too

so in those cases, the only way one might know that other content exists outside of the dialog is to try and tab out of the dialog to find it...

but users shouldn't be able to tab out of dialogs...

from my experiences, this is the best method to ensure users will be consistently aware that a toast popup is rendered, since some screen readers (nvda for example) will constrain element navigation to the dialog - even modeless.

I appreciate linkedin continuously sending me emails that people are waiting for my response, because it means I’ll always have some email to delete when I open my inbox.

shooogar?

sugar?

DID YOU TAKE ERIC'S MEMORIES!?!?!

Just had to remind myself that 2024 was not last year

Pros/cons to that reminder….

lol. I know

As a matter of fact, no.

Looks like you’re trying to create an emoji face. Can clippy help you finish that?

A standardized in-page calendar would take care of one of the most difficult aspects of custom pickers and allow for more flexibility in their presentation.

Don’t need to make a standardized dual range picker popup if you can make a button to invoke a dialog with two calendars jn it.

Funny that, a control that behaves as a button but is not exposed as a button would make it so some AT didn’t know how to interact with it….

Whodathunk

also. 10 years ago.... yeesh....

this reminds me of when me, you and heydon were talking about exactly this, on twitter, back in 2016
www.scottohara.me/blog/2016/08...