Craig Abbott

Haha! It makes me now think to raise another point, and that’s the word “accessible” often means different things to different people. I’ve worked with a few orgs who do accessibility well. As in, reasonable adjustments as part of DEI. But don’t do digital accessibility on websites or office docs.

Meet the team: Craig Abbott - TetraLogical Meet Craig Abbott, another friendly face supporting the charming Northern arm of TetraLogical. His home office comprises of several laptops, about 30 pairs of artfully arranged trainers, and two giant...

👷🏽 Meet @craigabbott.co.uk

"Meet Craig Abbott, another friendly face supporting the charming Northern arm of TetraLogical."

#accessibility #professional

tetralogical.com/blog/2025/08...

Oh… My… God! Stop the world, I want to get off!

Accessibility and inclusion are not the same. For example, you can have a WCAG 2.2 compliant sign-up form, but only offer two options to choose from for “gender”.

Can you think of any other examples?

#a11y #accessibility #inclusion

Yeah. The term itself isn’t exactly accessible is it 😅

I’m forever just pointing people at these! Though I would like it if they were tested more robustly with assistive tech.

Does your website have different language versions? Remember to translate your alternative text on images too.

It’s quite common to find hard coded English text descriptions for images. It’s a WCAG fail which can easily fly under the radar!

#accessibility #a11y

What? I didn’t say anything! 🤐

100% this! Also… non-conformant isn’t necessarily unusable. Though I’m not sure how much I’d want people to know that haha

The mind boggles!

Me too. You should put this on a T-shirt 😂

Haha. Yes, but that often just opens the door to more carnage! I’ve legit seen the following in a production service:

<Button as=“div” role=“button”>

😂

Yeah. It’s hard listening to people get dismissed as edge cases 😪

I blame React 😂

Oh man 100%! I mean, why use a button when you can use a span, an aria role, a tabindex and a tonne of CSS to achieve the same thing. Right? 😂

Good point! I have a habit of getting into the details too early 😂

Totally! 1 in 2 people in the UK develop a disability at some point. So “not yet disabled” is probably more accurate!

Yeah I think everybody always assumes it’s just screen readers users, and it’s so much more than that!

I like this attitude. You’re right there will always be a barrier for somebody. A robust feedback loop is always a winner!

Yeah. Kinda weird you can be compliant having never spoken to a single person with accessibility needs.

Yeah. I agree with this. I don’t get why WCAG requires heading levels to be correct programmatically but not visually.

Yeah. Once most people know a Div and a Span it’s just off to the races! 😂

Haha good point!

This is a really good one! I like the assumption mapping workshop in “Continuous Discovery Habits” by Theresa Torres. It’s good for helping weed some of these out.

What’s one thing you wish was more widely known about digital accessibility?

I’ll go first.

I wish more developers knew how to check elements for accessible names, roles and values.

#accessibility #a11y

Related to all of these! The new Donkey Kong is too round and cute. He’s lost all his attitude!

The back of a digital camera. The screen shows a zoomed in face of a little owl. It looks startled by something as it looks towards the top right of the frame.

Lovely fresh Sunday morning with a pop up hide and a camera. Hello Little Owl!

Haha, there’s a high probably it’s the same one! 😂

I don’t think we’re asking design tools to mimic implementation here. We’re just saying annotations should describe outcomes, rather than technical details like aria attributes etc, because that burden shouldn’t be on the designer.