@EgorKotov@datasci.social2025-09-03 11:14:38
#Accessibility modelers using #r5r #rstats, check this GUI for playing around with R5 network. If many people find it useful, I would get signal if I should invest any more free time into it.
@EgorKotov@datasci.social2025-09-03 11:14:38
@mgorny@social.treehouse.systems2025-10-01 07:29:43
Honestly, #emoji and icons in #Unicode are a true horror.
Yeah, sure. It's great that you don't have to use <img/> anymore and you can just paste a random Unicode character. You can get graphics into fields where only text was originally intended (like bug summaries). Even better, you can now easily get cool colorful icons on terminal with almost no effort.
However, it is an #accessibility nightmare. People are now encoding *information* in random graphical symbols. Symbols that require huge fonts to render, or huge character tables to describe.
Yeah, a bare <img/> carrying information sucks. However, you can add a *meaningful* alt-text to the image, and accessibility tools can use that text to provide meaningful context. Like "bug fix".
However, emojis and icons are symbolic. The best you can get is some description like "hammer and wrench", so people can kinda figure out that it's probably a "bug fix". Or maybe it was a "maintenance task"? Or you'll get a "unknown character 0x1F6E0". And I'm sure people will surely enjoy cross-referencing a "legend" of such "unknown characters".
@aardrian@toot.cafe2025-10-06 16:55:52
@seeingwithsound@mas.to2025-07-17 20:28:23
@unchartedworlds@scicomm.xyz2025-10-04 11:07:59
Content warning: web access design, state of play
Excellent article from @…, including both an overview and illustrative examples.
As an occasional web-tinkerer, I couldn't fully understand the web design details like a professional would. But from the parallels with event organising, I can tell that the overall vibe is spot-on: don't treat access as an afterthought which can be tacked on later, build it in from day 1.
"If you don't know enough about disabled users to understand their needs: find out. Knowing enough about accessibility to know when to seek out specialist guidance, and to understand it when you get it, should be a core competency for standards engineers. ...
"Getting this right requires a bit more work up-front, but – just as it is with front-end development – ultimately saves potential years of clean-up work (or having to scrap projects after years of effort), as well as avoiding harming disabled users."
#access #design #standards #WebStandards #accessibility #a11y #disability #UX
@andycarolan@social.lol2025-07-22 15:21:31
I'm seeing some really awful, low effort "may be..." ALT text recently. Clearly generated by an automatic process rather than by a human.
Is bad* alt text worse than no alt text?
*completely incorrect, and misleading
#Accessibility #a11y
@matthiasott@mastodon.social2025-09-12 22:11:48
🎧 Listening (at 1.5x speed … 😅) to a wonderful conversation between two of my favourite people: @… navigating the world of web #accessibility with @…
@chrysn@chaos.social2025-09-17 05:05:15
Terminal users who use #accessibility tools, what is your take on emoji in console applications, especially compared to marker characters (eg. angular brackets for directions or hashes for comments) and to explicitly spelled out labels?
Does an "info" emoji render "ℹ️ Some information" (or a warning as in "⚠️ X went wrong") get across well for terminal assi…
@aardrian@toot.cafe2025-07-22 20:43:16
Reason #2608 I do not trust “AI” to generate captions or transcripts:
“Complete silence is always hallucinated as 'ترجمة نانسي قنقر' in Arabic which translates as 'Translation by Nancy Qunqar'”
More examples in replies.
#a11y #accessibility
@aardrian@toot.cafe2025-08-19 14:16:13
Unfortunately, standards work may be a function of who has the biggest platform for social media polls (that maybe pre-judge the outcome).
I’m hoping those who work in or near #accessibility can offer some feedback to more fundamental, not pre-judged, questions here:
@castarco@hachyderm.io2025-08-27 20:21:14
Geeky question: is anyone thinking or working on adapting #accessibility and #i18n #web standards to the impending avalanche of bad #AI translations that we'll have to deal with as users?
I'll be more specific, one example: I can prefer Spanish texts over English ones... as long as they are written by a human being and are not a terrible automated translation made by an AI, in which case I'd prefer to read the original English text. But... as of today, I have no way to specify that through my browser settings.