Show more

I'm a bit of a retro gaming aficionado. After years of wanting one, I finally bought this!

Currently preparing the weekly links article, there will be a lot of accessibility and color accessibility ressources <3

You can get announcements of new accessibility publications, drafts for review, & other #W3C #WAI #accessibility news direct to your In Box – just subscribe to the new WAI Announcements e-mail list. #a11y #wcag
Info at:

I see people who do not practice accessibility again noting how inaccessible #a11y is to ‘outsiders’. A primer:

While having a lot of contrast is important for many aspects of accessible design, if everything has a lot of contrast, nothing has a lot of contrast.


I take some dark pleasure in citing accessibility issues on many client's "Diversity" pages. Oh, the irony.

Namor: Do not toot it!

*toots horn*

Doctor Doom: Fool! Doctor Doom toots as he pleases!

In choosing which designer or developer to hire, the one with a decent working knowledge of accessibility, wins out everytime. It's that important. All hiring managers should do the same.

‘Don't steal your user's focus outlines, you wouldn't steal their cursor either’ – #fronteers

THIS :-(

We “accessibility professionals” are ready to move on, but the level of understanding is so low, it’s just not
The reason why so many accessibility talks talk about the same simple things over and over is these mistakes are still sooo common :( #fronteers

It’s been one whole year since my book, Accessibility For Everyone, came out in paperback and ebook from A Book Apart.

Did you read it? Did it help you make more accessible websites? Please tell me you enjoyed it more than @gigapup did…

If you didn’t read it yet (or even want to read it again…!) you can always listen to the audiobook on Audible. The whole book takes less than an afternoon…

Today, I told 150 collegues that the best thing they can do for accessibility is to be more empathetic and think more inclusively.

It felt pretty good to say, too.

WAI-ARIA menus, and why you should generally avoid using them
The WAI-ARIA standard defines a number of related menu roles. However, in 99% of all cases, these should not be used. A bit of history In the mid 2000s, people were arguing over whether HTML4.01 or XHTML 1.x was the better standard. Both markup languages had in common that they hardly[...]
#ARIA #DontUse #menu #menubar #menuitem #menus

"Did you clear your cache?" will probably be my epitaph.

If you need to have your inputs and labels in a container to do something “fancy”* with the label (like overlaying the input and then shifting around once the user uses the field), you can use the following CSS to help users navigating the page by keyboard:

.wrapper:focus-within { outline: 2px solid currentColor; }

* I personally don’t like fancy stuff with forms, it breaks easily when JS doesn’t load and it is just not worth the hassle.

From a client: [site] enabled for screen readers if we have visually impaired candidates, etc.

This always amuses me. Accessibility covers a broad range of issues, but somehow, client’s never fail to make it only about blind folks.

Design & Dev Tip: If you are refreshing a clients website and they have an "accessibility" link in their footer, it is usually a good idea to, ya know—MAKE THE NEW SITE ACCESSIBLE!

Seriously, it is generally a good indication that the client will have accessibility concerns.

Show more

An open community for those interested in learning more about digital accessibility.