Time to pencil it into your busy social calendars ... #id24 will take place on the 24 September 2026. Call for presentations will open in April ... but if you have an idea, or you'd like to help out as a guest host, get in touch!
inclusivedesign24.org/2026/
#a11y #accessibility #inclusiveDesign
In the final day of our Accessible Building Blocks series, we're sharing a video on how to design and build forms that everyone can fill in.
Watch the video here: youtu.be/hj6wCUyGx0o or with British Sign Language: youtu.be/WJGAVpdURGY
#AccessibleBuildingBlocks #Accessibility #AccessibleFormFields
Every year, we offer our speakers, guest hosts, and core team members the option to convert their little thank-you payment/honorarium into a charity donation. 1/
I’m just going to say as someone who lived in London for eleven years and is currently seriously considering going back precisely because of the far right theocratic fascism of Trump, that he’s talking out of his fucking asshole.
Save the date! Inclusive Design 24 returns on 25 September 2025 for 24 hours of talks about #accessibility and #InclusiveDesign. All streamed for free, no log in required. Here's our schedule for this year: inclusivedesign24.org/2025/schedule/ #id24
On the right-hand side of the image, the title reads “Accessibility training” in yellow font followed by “that works with delivery, not against it” in white font. The left-hand side has the TetraLogical logo in the top corner with the Knowledge icon below: two people, each made up of a circle for a head and a semicircle for a body. One is bright pink and the other bright purple, above them is a speech bubble with an orange spark of a shared idea inside
Accessibility training that works with your project delivery, not against it
Self-led courses to build confidence, consistency, and capability.
Ideal for onboarding, upskilling, and scaling.
tetralogical.com/services/tra...
#SustainableAccessibility #AccessibilityTraining #DigitalStrategy
We're happy to finally unveil the full schedule for the upcoming Inclusive Design 24 #id24 24 hour online event on the 25 September 2025 inclusivedesign24.org/2025/schedule/ #a11y #accessibility #inclusiveDesign
This sounds similar to a conversation I had recently 😂
A lot of #accessibility annotation kits rely on designers having a technical understanding of semantic roles, landmarks, autocomplete values etc. Lots of Frontend Devs don’t even understand that stuff. As a designer, you just need to be able to articulate the expected outcome for a user.
Screen reader HTML support tables
"With the addition of Gez Lemon to the editing team, work continues on expanding and improving the HTML and screen reader support information."
#HTML #screenReader #NVDA #JAWS #a11y
tetralogical.com/blog/2025/07...
These HTML support tables by @tetralogical.com are very, very good. tetralogical.com/blog/2025/07...
In 1994 the UK voted the widget inside a can of Guinness as Invention of the Year.
The Internet came second.
Yes, yes, I know that far more people were probably drinking Guinness than using the interwebs back in 1994, but c'mon... 😂
the popover attribute is just one ingredient in making accessible popups. It does a lot, but not everything you might need. that's on purpose.
Want to know more? Here you go:
www.scottohara.me/blog/2025/03...
Except you can’t add the link behaviour, not all of it. There are things in context menus and keyboard interactions that cannot be recreated.
Officer help someone stole my stealing machine
www.theverge.com/news/601195/...
There are four founding principles of TetraLogical:
Inclusive
Sustainable
Ethical
Original
This is at the heart of everything we do for our customers and how we invest in ourselves. Our Code of Ethics page details our commitments and how we meet them:
tetralogical.com/code-of-ethi...
Our Team. A screenshot from the TetraLogical website with the text "We're a boutique company with a whole lot of experience" above a row of headshots of the team. Below the photos, it says "We're an experienced team, with specialisms in many areas"
TetraLogical was founded 6 years ago by @tink.uk to focus on people and making sustainable change rather than just conformance.
In that time, we've achieved a lot, worked with companies across the globe and have grown the team into a 14-strong band of absolute experts in their specialities.
It’s very interesting but also very frustrating. If you haven’t listened already, you might enjoy @originstorypodcast.bsky.social which is co-presented by the author.
In other news, @tetralogical.com is 6 today! 🥳
And it's an absolute delight to be working with such a marvellous group of people:
tetralogical.com/about/team/
Logos for Alzheimer’s society Stepping Stones Save the children The Meeting Room Children’s Cancer and Leukaemia Group RISE Samaritans Kyra Women’s Project Guide Dogs Trussell Trust Winter Appeal Refugee Action
Over the years we've made 42 donations to 26 different charities.
This year we are donating to:
Alzheimer’s society
Stepping Stones
Save the Children
The Meeting Room
Children’s Cancer and Leukaemia Group
RISE
Samaritans
Kyra Women’s Project
Guide Dogs
Trussell Trust Winter Appeal
Refugee Action
As part of HTMHell's advent calendar, @tink.uk's article explores the risks of relying on AI-generated code for accessible web development.
AI tools can be helpful but they’re no substitute for expertise and critical thinking.
htmhell.dev/adventcalend...
#Accessibility #AccessibilityAI
I don’t always say that. But sometimes I do.
It depends.
It does, which is why I’d prefer the design pattern didn’t exist. But content order must be logical programmatically as well as visually.
The description approach has different issues, for example when searching for the text. There might be cases where one is better (or less worse) than the other.
Accessibility Unlocked!
This International Day of Persons with Disabilities, we’re excited to launch Accessibility Unlocked - a free six-day newsletter series designed to help you jumpstart your accessibility efforts.
My actual preference is to not use this design pattern at all. But we work with what is not what we’d like.
My preferred approach is to put the descriptor after the heading in the source order, then position it above with CSS. Flexbox and grid both make it easy enough to do. Add visually hidden text, such as “Tags: “, if the purpose of the descriptor is unclear.
