Eric Eggert

Turns out I have more followers over on the @yatil@toot.cafe instance. So I’ll redirect from here and use that. (Instances are weird and complicated.)

Is this thing still on?

My speaking gigs in May: https://yatil.net/blog/may-2022-speaking-gigs

RT @anatudor@twitter.com
Oh, damn, this was terribly confusing!

I saw it grey, but checked, so I thought it was disabled AND checked, so no possibility of unchecking it (except from DevTools).

Turns out grey & checked look is actually unchecked. Pink is hover/ focus/ checked. Sigh...

RT @vavroom@twitter.com
A

RT @karlgroves@twitter.com
If you are in North America and don’t go to this, you are wrong https://twitter.com/a11yto/status/1027568907152965632

RT @A11yRules@twitter.com
Part 2 of my chat with @meyerweb@twitter.com is now available: https://a11yrules.com/podcast/e52-interview-with-eric-meyer-part-2/ Eric states that accessibility is a foundational principle of the web. I couldn't agree more. #a11y #podcast We also spoke about the famous focus {outline: 0;} thing :)

RT @patrick_h_lauke@twitter.com
@marcosc@twitter.com if you want to be technically accurate, too ;)

(otherwise people will start cargo-culting aria-label into all their form controls when it's not necessary)

RT @yellowled@twitter.com
iTerm 2 verwendet ab Version 3.2.0 Metal 2 als Renderer. https://gitlab.com/gnachman/iterm2/wikis/Metal-Renderer

RT @iamjolly@twitter.com
In today’s post on the @knowbility@twitter.com blog, @becka11y@twitter.com schools us (in the nicest of ways) about the new WCAG 2.1 guideline for non-text contrast. https://knowbility.org/blog/2018/WCAG21-1411Contrast/

Now go… Get your learning’ on! #WCAG21 #WCAG #A11Y

That’s a real contrast ratio of 1.6, it should be 4.5.

White on white has a contrast ratio of 1. Don’t do that. Use proper visible colors.
---
Shame on @getdock for hiding the unsubscribe link in their email. The link color is #70707a so passes minimum WCAG color contrast requirement at 4.9:1. BUT! They set opacity 0.36, so the thing is barely visible. This feels like a deceptive practice. #a11y
https://twitter.com/vavroom/status/1026816053706465281

If you lazy load forms/form elements on a page based on the viewport, screen reader or keyboard only users might have already skipped it when it comes into the viewport. Detect keyboard users and load all elements on the page (also important for headings!) immediately.

Also, @vavroom@twitter.com’s #sxsw2019 proposal is worth your upvote: https://panelpicker.sxsw.com/vote/89805

VOTE UP!
---
Accessible or SUX, It’s Your Choice!
My SXSW session with a hearty nod to @thebillygregory’s “some UX/SUX” is up for your vote at https://panelpicker.sxsw.com/vote/90410.

Let’s help developers and designers understand how accessibility isn’t an option. If it’s not accessible, then it SUX.
https://twitter.com/iamjolly/status/1026798114936643584

Unfortunately many would consider this as bad CSS and use a template language to add a class to the element. In reality it is just plain awesome.
---
Just used:

.form__row > div:first-child:not(:only-child) { }
https://twitter.com/Malarkey/status/1026597246450769921

“Hey can you please check if this custom shiny web component is accessible? It has a lot of buttons and functionality and stuff.”

Me: *hits tab key on keyboard*

(focus skips the whole component)

Me: *breathes in*

Me: “No, it’s not accessible at all.”

#ariaserious

… hmmm … Nationalists that get the nationalist part wrong…
---
I think we've reached the "so what if he colluded" phase
https://twitter.com/dailyexception/status/1026152809773842432