Lmst

@eric I repeat: I'm not sure if you're allowed to do this.

Erik Kroes ✅ boosted:

I've referenced it enough that now it's all I can hear when I read it. Now you have to hear it too 🙉 https://ericwbailey.website/published/you-must-listen-to-rfc-2119/

"Scaled Accessibility: How Big Dutch Companies Manage Accessibility"

A keynote I gave at the Dutch accessibility conference NCDT. I presented my model for motivating and scaling accessibility.

Let me know what you think!
(I don't like watching recordings of myself)

https://www.ncdt.nl/programma/presentatie/35/scaled-accessibility-how-big-dutch-companies-manage-accessibility/

#accessibility #inclusivity #inclusiveDesign

@MostlyBlindGamer Don't give people ideas please

The web has given me something new to detest today. 🎁

It's like they took the experience of having no visible keyboard focus, and reinvented it for mouse-users. The creativity is impressive 😬

(Context. On a modern div-site, this makes everything seem interactive.)

#SurprisingHTML

a:hover, div:hover, p:hover, span:hover {
cursor: pointer;
}

@alastc Sadly, no.

The web is always surprising. Rarely in a good way 😬

reddit topic: google it! 🤬

google: here is a reddit topic for you

@jcsteh I restarted the browser and I think (🤞🏿) that worked.

Restore session (which I usually do when I start firefox) did show my own tabs and pages. So that gave me the impression I was on my own profile. But other things didn't come up. Now it's all back!

Firefox no longer suggests URLs when typing; I can only search.
My bookmarks are gone
My history is gone.

Help? Starting the day lost.

@alastc I think the only thing it did was make a developer feel good about themselves 😄

Wait what?

#SurprisingHTML

🌶️ Share your accessibility hot take!

🙋‍♂️ I don't like adjusting code for browser X, tool Y or version Z. I write the best code I can, and I can't control whatever happens with it. I'm an accessibility stoic.

Further testing clarifies a lot!

It's not jquery, it js on elements that are not focusable by keyboard by itself.

https://codepen.io/erikkroes/pen/EajdwQK

/cc @westbrook

@westbrook I'm not sure if keyboard API is technically the best name for it, but that's how I've learned to call it.
https://developer.mozilla.org/en-US/docs/Web/API/Keyboard_API

I've got a message saying that it might work on interactive items like buttons, but not on non-interactive items with a tabindex. So there might be something there

@westbrook A lot of tools might depend on keyboard accessibility like https://en.wikipedia.org/wiki/Switch_access

If you'd add a tabindex to the example-code, it might become reachable with a keyboard. But it's still not possible to trigger it.
It's pretty close to a guaranteed failure for https://www.w3.org/WAI/WCAG22/Understanding/keyboard.html

FYI, if you're using jQuery and write something like this.

❌ This will not trigger with a keyboard, screen reader or other software/device using the keyboard API.

🧠 Maybe avoid jQuery for this