James Catt

Web guy. Photographer. Occasional tree-hugger.

[James Catt @CattJames]

If browser dev tools warned us about accessibility problems, we'd probably make a lot fewer of them. #a11y https://t.co/2kxNV7BvMQ

[James Catt @CattJames]

@HenryAllelujah @SportsNetLA Literally exactly what he complained about when he was with the Jays (and probably a factor in why they DFA'd him).

[James Catt @CattJames]

@hdv Not saying the SC should be dropped, but solving this at the browser level really is the ideal solution—give the user the ability to customize an indicator for their needs that can't be disabled/modified by authors.

[James Catt @CattJames]

Unbelievably, Bytes is as great as everyone says it is. Easily the best newsletter I receive. https://t.co/8txAaqchTK

[James Catt @CattJames]

@mmatuzo Signed up to the newsletter ages ago but just realized I haven't received one in some time. Are you still doing it?

[James Catt @CattJames]

@scottohara Had to laugh at the "OK, I think I’m done for now" heading at the end—because I had the same thought at the beginning as soon as you outlined how spotty the browser/screen reader support is.

Also wondering how the semantics play with something like Dragon NaturallySpeaking?

[James Catt @CattJames]

@twerske Thanks for the write-up. Question:

"inert gives developers the ability to remove an element from the tab order, and from the accessibility tree."

Does this mean that inert removes the element from the a11y tree? If so, can it be overridden with aria-hidden="false"?

[James Catt @CattJames]

@Alex_Panetta Excellent, informative coverage, free of nationalist bias—a rarity. Keep up the good work!

[James Catt @CattJames]

@JocoPolgar Great post, but the part about pseudo elements is inaccurate. In my testing, NVDA/JAWS/Voiceover/Talkback + Chrome/Edge/Firefox/Safari all announce ::before and ::after content. Only IE doesn't.

[James Catt @CattJames]

Loving the Monty Python-esque animation of solar-roof-crazed @elonmusk on this https://t.co/kgyP04Dz7a ...glad he's giving it his attention. #TeslaSolarRoof

[James Catt @CattJames]

@aaroniker_me @CodePen @greensock This is super cool, but but unfortunately it isn't accessible. Screen reader users are going to hear all three text blurbs smooshed together, and there's no way to confirm with a keyboard. #a11y

[James Catt @CattJames]

@sundress would love to get a Chrome dev's perspective if you have a few minutes: https://t.co/2kxNV7jUog #a11y #webdev

[James Catt @CattJames]

@floscholz can I ask why you removed the inline icons? https://t.co/f8fxasGgvR

[James Catt @CattJames]

@jaffathecake Oh look, a Googler trashing Edge. Color me surprised.

(just trolling, carry on :D)

[James Catt @CattJames]

Dave Rupert recently wrote a great post lamenting the fact that HTML doesn't actually live up to its promise of being accessible by default. Here's another issue for the pile: the HTML range input doesn't actually work for everyone. https://t.co/dWTtP97tQR

[James Catt @CattJames]

Learn how to create custom-styled HTML checkboxes that will work everywhere, for everyone https://t.co/iYBwWVai3U

[James Catt @CattJames]

@marcysutton @_marcusherrmann @FableTechLabs @vuejs In your experiment did you consider setting focus to an empty element immediately before the skip link? It effectively moves users to the top of the page the same way that navigating to a new (non-SPA) page would, but without revealing the skip link to sighted users.

[Sarah • @[email protected] @codingchaos]

New writing thing! Some tips for debugging semantic issues with complex interactive components.

"Talk to your kids about ARIA before it's too late." 😉

https://t.co/6sd1FKjzTQ

[James Catt @CattJames]

Be careful when publishing negative numbers on the web. Your users might be misinformed. https://t.co/rAIP6WzzFX

[James Catt @CattJames]

Why <details> is Not an Accordion https://t.co/dL6uDNge78