Tootfinder

Opt-in global Mastodon full text search. Join the index!

@aardrian@toot.cafe
2026-07-15 17:17:20

Tuesday 21 July, Durham-Raleigh #Accessibility MeetUp (online or IRL in Millersville) will talk about the book, “Digital Accessibility Ethics: #Disability Inclusion in All Things Tech” with @…

@matthiasott@mastodon.social
2026-08-08 11:58:30

A talk about #accessibility at #T3DD2026! 👏 Kai Grosz spreading the word that … a <div> is not a <button> 🎉
(😉 @…)

Kai Grosz on stage at TYPO3 Developer Days explaining the correct use of semantic HTML buttons for optimal accessibility.
@aardrian@toot.cafe
2026-07-10 16:09:31

Yet another #accessibility #overlay that introduces WCAG failures just by installing it.
Users might not be able to report an accessibility problem. Here, one field is unlabeled (4.1.2 / 1.3.1) and the other is labeled by its placeholder (1.4.3 / 3.3.2).
This one offered by Welcoming Web.

“Report An Accessibility Problem” form with a textarea preceded by the visible label “Please describe your accessibility problem”, which dev tools shows is not associated with the field, and then a text field with the label “Please enter your email”, and which is also not associated with the field (though the field has placeholder text).

WCAG Evaluation Methodology now covers more than web pages: #a11y #accessibility

@aardrian@toot.cafe
2026-09-16 02:28:51

RE: #a11y #accessibility

None of this is about one bad app or one flawed feature. It’s a pattern. The whole industry builds accessibility for one disability at a time, and multiply disabled people fall through the gap between features. When VoiceOver turns off touch accommodations, that’s not a bug. It’s the whole model, made visible.
@flbergerdev@mastodontech.de
2026-07-03 19:19:38

In 2021, we discarded #Moodle after evaluation, and went on to develop @… as an #LMS with #accessibility

Selfie of the autor in the auditorium of the MoodleMoot D-A-CH conference at ETH Zürich.