Mastodon 🐘

RealZeroHeads-up if you who care about people that are blind or use screen readers (software tools that read text from the screen for you) in general:I occasionally see people use "fancy looking" text, here's a great example attached.To someone that can read it, this clearly reads "free art raffles" followed by a heart and some icons.Google's "Talkback" screen reader reads it as "Heart. Hermitian conjugate matrix."So: the heart and the name of the last icon. None of the text that is, actually, symbols, not text.Different screen readers handle this differently, but this can happen.So, if you want to treat people fairly, don't use "fancy" over "working".Sadly, the whole user profile looks like this.This is intended as well-meant info, no rant! ♥️<a href="https://social.tchncs.de/tags/Accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#Accessibility</a> <a href="https://social.tchncs.de/tags/ScreenReaders" class="mention hashtag" rel="nofollow noopener" target="_blank">#ScreenReaders</a>

ChronocideQuestion for those who use <a href="https://sunny.garden/tags/screenreaders" class="mention hashtag" rel="nofollow noopener" target="_blank">#screenreaders</a> (specifically <a href="https://sunny.garden/tags/nvda" class="mention hashtag" rel="nofollow noopener" target="_blank">#nvda</a> with Firefox). How do you get the screenreader to announce the Firefox developer tools? All I seem to get is "Developer Tools frame, Inspector Panel frame, Markup View frame" and no announcement of the actual HTML displayed in the Inspector panel.Navigating with the keyboard (arrow keys) doesn't announce anything either, nor does NVDA + arrow keys.Retoots would be appreciated!<a href="https://sunny.garden/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#webdev</a> <a href="https://sunny.garden/tags/accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#accessibility</a>

Darling Davie 🏳️‍🌈Still playing with GNOME 48, and notice that orca doesn't realize the items on the top bar, including time and battery state, Are not refreshed, in the screen reader, until orca is cycled off and on. I don't think this issue is particular to <a href="https://queer.cool/tags/debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#debian</a> but, maybe, someone running a different distro can confirm. <a href="https://queer.cool/tags/gnu" class="mention hashtag" rel="nofollow noopener" target="_blank">#gnu</a> <a href="https://queer.cool/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://queer.cool/tags/accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#accessibility</a> <a href="https://queer.cool/tags/screenreaders" class="mention hashtag" rel="nofollow noopener" target="_blank">#screenreaders</a> <a href="https://queer.cool/tags/gnomedesktop" class="mention hashtag" rel="nofollow noopener" target="_blank">#gnomedesktop</a>

D.Hamlin.MusicWhy is this a problem? Sounds like a great <a href="https://dragonscave.space/tags/accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#accessibility</a> improvement if you ask me.<a href="https://www.xda-developers.com/windows-update-broke-print-to-pdf/" rel="nofollow noopener" translate="no" target="_blank">https://www.xda-developers.com/windows-update-broke-print-to-pdf/</a><a href="https://dragonscave.space/tags/Blind" class="mention hashtag" rel="nofollow noopener" target="_blank">#Blind</a> <a href="https://dragonscave.space/tags/ScreenReaders" class="mention hashtag" rel="nofollow noopener" target="_blank">#ScreenReaders</a> <a href="https://dragonscave.space/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a>

FlorianAlways fun to read <a href="https://cupoftea.social/tags/hackerNews" class="mention hashtag" rel="nofollow noopener" target="_blank">#hackerNews</a> and their rather ... let's call it ... qualitatively exceedingly disappointing mentality towards <a href="https://cupoftea.social/tags/accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#accessibility</a> (stroopwafel to the dutchies who see what i did there). But some points do make me think to what degree, say, <a href="https://cupoftea.social/tags/screenReaders" class="mention hashtag" rel="nofollow noopener" target="_blank">#screenReaders</a> could be innovating more. One thing that stuck by me was a comment on an article regarding the use of "click here" that basically suggested some kind of heuristic for, say, reading the entire line of text when that's encountered, rather than the link text. Another one could be including the previous sibling's accessible name on unlabeled form fields which I ...think? JAWS might already be doing? Like obviously these should be toggleable to not screw up audits but I think after 30 years we can safely say people often can't be forked to learn <a href="https://cupoftea.social/tags/HTML" class="mention hashtag" rel="nofollow noopener" target="_blank">#HTML</a> basics and it might make some things smoother?

Crimperman 🏳️‍🌈Two days ago I posted two toots. One about reasons to not round up at the checkout for charity and the second about being more <a href="https://hachyderm.io/tags/inclusive" class="mention hashtag" rel="nofollow noopener" target="_blank">#inclusive</a> for those with <a href="https://hachyderm.io/tags/ScreenReaders" class="mention hashtag" rel="nofollow noopener" target="_blank">#ScreenReaders</a> by using <a href="https://hachyderm.io/tags/CamelCase" class="mention hashtag" rel="nofollow noopener" target="_blank">#CamelCase</a> <a href="https://hachyderm.io/tags/Hashtags" class="mention hashtag" rel="nofollow noopener" target="_blank">#Hashtags</a> The first one got way more boosts and favourites than the second.It's nice that either got boosted but a bit of a shame that the inclusivity one didn't get as much reach. It would be nice if more people knew about the camel case thing.So if you could see your way clear to boosting the toot below I'd much appreciate it. <a href="https://hachyderm.io/@crimperman/114763457258104600" rel="nofollow noopener" translate="no" target="_blank">https://hachyderm.io/@crimperman/114763457258104600</a>

Crimperman 🏳️‍🌈TIL that formatting multi word <a href="https://hachyderm.io/tags/HashTags" class="mention hashtag" rel="nofollow noopener" target="_blank">#HashTags</a> in <a href="https://hachyderm.io/tags/CamelCase" class="mention hashtag" rel="nofollow noopener" target="_blank">#CamelCase</a> as opposed to lowercase allows <a href="https://hachyderm.io/tags/ScreenReaders" class="mention hashtag" rel="nofollow noopener" target="_blank">#ScreenReaders</a> and the like to read it as several words, not one or a series of letters. Thus it makes your toot more inclusive.<a href="https://hachyderm.io/tags/Accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#Accessibility</a> <a href="https://hachyderm.io/tags/FediTips" class="mention hashtag" rel="nofollow noopener" target="_blank">#FediTips</a>

Dan GeroThis is an old article from 2017, but I feel like it's anti-aging in a lot of ways, so I decided to share it here. It basically talks about how <a href="https://vocalounge.cafe/tags/NVDA" class="mention hashtag" rel="nofollow noopener" target="_blank">#NVDA</a> is the future of <a href="https://vocalounge.cafe/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a> <a href="https://vocalounge.cafe/tags/ScreenReaders" class="mention hashtag" rel="nofollow noopener" target="_blank">#ScreenReaders</a> for everyone. NVDA: Now More Than Ever! - The New Hofstader.com <a href="https://www.chrishofstader.com/nvda-now-more-than-ever/" rel="nofollow noopener" translate="no" target="_blank">https://www.chrishofstader.com/nvda-now-more-than-ever/</a> <a href="https://vocalounge.cafe/tags/Blind" class="mention hashtag" rel="nofollow noopener" target="_blank">#Blind</a> <a href="https://vocalounge.cafe/tags/accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#accessibility</a>

aaronI woke up to a comment so smug, so perfectly soaked in gatekeeping and faux-righteous posturing, it earned its own blog post. You want freedom? You want GNU/Linux to mean something? Then maybe start by not telling disabled users to go fuck themselves with a smile. This commenter thought they were defending "software freedom." What they were really doing was kicking people out of the room. Dismissing accessibility. Mocking effort. Pretending that cruelty is some kind of rite of passage. They quoted Stallman like it was scripture, ignored real-world experience like it was noise, and wrapped it all in condescension dressed as virtue. I’ve spent over a decade in this ecosystem. Writing patches. Rebuilding broken stacks. Helping blind users boot systems upstream doesn’t even test. I didn’t "just install Arch and whine about the terminal." I lived in it. I survived it. I held it together when maintainers disappeared and no one else gave a damn. But apparently, because I didn’t call it GNU/Linux™ and because I dared to talk about how this OS chews people up and spits them out, I’m lazy. I’m weak. I should "get a dog." So I wrote a response. Line by line. No mercy. No euphemisms. This isn’t just about one comment. This is about every time someone’s been told they don’t belong because they couldn’t learn fast enough, code well enough, or survive long enough. It’s about everyone who was pushed out while the gatekeepers patted themselves on the back for "preserving the spirit of free software." You want a free system? Start by making it livable. Because freedom that demands you crawl bleeding through a broken bootloader isn’t freedom. It’s abandonment dressed in ideology. And if this kind of gatekeeping is your idea of community? You can keep it. <a href="https://fireborn.mataroa.blog/blog/you-dont-own-the-word-freedom-a-full-burn-response-to-the-gnulinux-comment-that-tried-to-gatekeep-me-off-my-own-machine/" rel="nofollow noopener" translate="no" target="_blank">https://fireborn.mataroa.blog/blog/you-dont-own-the-word-freedom-a-full-burn-response-to-the-gnulinux-comment-that-tried-to-gatekeep-me-off-my-own-machine/</a> <a href="https://dragonscave.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://dragonscave.space/tags/GNU" class="mention hashtag" rel="nofollow noopener" target="_blank">#GNU</a> <a href="https://dragonscave.space/tags/FOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FOSS</a> <a href="https://dragonscave.space/tags/Accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#Accessibility</a> <a href="https://dragonscave.space/tags/BlindTech" class="mention hashtag" rel="nofollow noopener" target="_blank">#BlindTech</a> <a href="https://dragonscave.space/tags/FreeSoftware" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeSoftware</a> <a href="https://dragonscave.space/tags/Gatekeeping" class="mention hashtag" rel="nofollow noopener" target="_blank">#Gatekeeping</a> <a href="https://dragonscave.space/tags/DisabilityInTech" class="mention hashtag" rel="nofollow noopener" target="_blank">#DisabilityInTech</a> <a href="https://dragonscave.space/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> <a href="https://dragonscave.space/tags/Orca" class="mention hashtag" rel="nofollow noopener" target="_blank">#Orca</a> <a href="https://dragonscave.space/tags/ScreenReaders" class="mention hashtag" rel="nofollow noopener" target="_blank">#ScreenReaders</a> <a href="https://dragonscave.space/tags/ArchLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#ArchLinux</a> <a href="https://dragonscave.space/tags/BurnItDown" class="mention hashtag" rel="nofollow noopener" target="_blank">#BurnItDown</a> <a href="https://dragonscave.space/tags/blogpost" class="mention hashtag" rel="nofollow noopener" target="_blank">#blogpost</a>

🇺🇸 🇺🇦 🇮🇱 🐧 🥦At work I've been making sure our client's site works correctly with JAWS. I learned that JAWS can be very expensive and that there are OTHER screen readers.People who USE screen readers: Is JAWS worth the money and worth being on <a href="https://mastodon.social/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a> for?Is Orca decent?What about the "multiplatform" System Access To Go? Does it do the job decently enough?<a href="https://mastodon.social/tags/AssistiveTechnology" class="mention hashtag" rel="nofollow noopener" target="_blank">#AssistiveTechnology</a> <a href="https://mastodon.social/tags/ScreenReaders" class="mention hashtag" rel="nofollow noopener" target="_blank">#ScreenReaders</a> <a href="https://mastodon.social/tags/JAWS" class="mention hashtag" rel="nofollow noopener" target="_blank">#JAWS</a> <a href="https://mastodon.social/tags/Orca" class="mention hashtag" rel="nofollow noopener" target="_blank">#Orca</a> <a href="https://mastodon.social/tags/VoiceOver" class="mention hashtag" rel="nofollow noopener" target="_blank">#VoiceOver</a> <a href="https://mastodon.social/tags/SystemAccessToGo" class="mention hashtag" rel="nofollow noopener" target="_blank">#SystemAccessToGo</a> #508

Georgiana BrummellI have been a computer user for over twenty years. Since 2017, I have seen Youtube, GMail, and Facebook, respectively, shut down their Mobile, Basic HTML, and Basic Mobile sites. These are not apps, but actual websites that were simple in design and extremely easy to use with screen readers. As a result, I have been forced to use clients (Youtube and GMail) or to leave sites entirely (Facebook). I tried alternatives, only to find that most of them had accessibility issues. Over my many years on the Internet, but especially within the last few, I've seen websites become more and more cluttered with visual elements, constant refreshes that caused trouble with NVDA (the screen reader I use), and advertisements in the middle of articles that made it very difficult to read them without pasting them into Notepad or using some kind of Reader View to cut the junk from the site. I've seen sites add captchas with no audio alternatives, so that they were completely useless, or contain loud audio as soon as I entered them, so that I couldn't hear what my screen reader was saying, or have forms with inaccessible elements that made it impossible for me to fill them out. And then, there was Dreamwidth. This site was, is, and I hope, always will be, 100% accessible, with no compromises ever. The developers truly care about their users and make the experience as positive as possible there. If you would like to keep a journal, or even write articles of any kind, make friends, join groups, and enjoy a slower pace, I strongly encourage you to try it. My own journal can be found here. Anyone may read and comment on public entries, whether or not he is a member.<a href="https://dandylover1.dreamwidth.org/" rel="nofollow noopener" translate="no" target="_blank">https://dandylover1.dreamwidth.org/</a><a href="https://someplace.social/tags/accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#accessibility</a> <a href="https://someplace.social/tags/blind" class="mention hashtag" rel="nofollow noopener" target="_blank">#blind</a> <a href="https://someplace.social/tags/Dreamwidth" class="mention hashtag" rel="nofollow noopener" target="_blank">#Dreamwidth</a> <a href="https://someplace.social/tags/friends" class="mention hashtag" rel="nofollow noopener" target="_blank">#friends</a> <a href="https://someplace.social/tags/journal" class="mention hashtag" rel="nofollow noopener" target="_blank">#journal</a> <a href="https://someplace.social/tags/NVDA" class="mention hashtag" rel="nofollow noopener" target="_blank">#NVDA</a> <a href="https://someplace.social/tags/ScreenReaders" class="mention hashtag" rel="nofollow noopener" target="_blank">#ScreenReaders</a>

Georgiana BrummellI thought that some of you might find this interesting, since so many in the Fediverse genuinely care about accessibility. Note: The description was taken from the Top Tech Tidbits newsletter. The second link is to the article itself.<a href="https://www.toptechtidbits.com/tidbits2025/06192025/index.html" rel="nofollow noopener" translate="no" target="_blank">https://www.toptechtidbits.com/tidbits2025/06192025/index.html</a>"This article provides an updated guide for enhancing the accessibility of social media posts, focusing on critical elements like alt text, fonts, hashtags, and content warnings. It emphasizes practical tips to create inclusive content that can be navigated by individuals using screen readers and other assistive technologies."<a href="https://a2i.co.uk/blog/accessible-social-media-content/" rel="nofollow noopener" translate="no" target="_blank">https://a2i.co.uk/blog/accessible-social-media-content/</a><a href="https://someplace.social/tags/accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#accessibility</a> <a href="https://someplace.social/tags/AltText" class="mention hashtag" rel="nofollow noopener" target="_blank">#AltText</a> <a href="https://someplace.social/tags/Android" class="mention hashtag" rel="nofollow noopener" target="_blank">#Android</a> <a href="https://someplace.social/tags/AssistiveTechnology" class="mention hashtag" rel="nofollow noopener" target="_blank">#AssistiveTechnology</a> <a href="https://someplace.social/tags/blind" class="mention hashtag" rel="nofollow noopener" target="_blank">#blind</a> <a href="https://someplace.social/tags/ContentWarnings" class="mention hashtag" rel="nofollow noopener" target="_blank">#ContentWarnings</a> <a href="https://someplace.social/tags/fonts" class="mention hashtag" rel="nofollow noopener" target="_blank">#fonts</a> <a href="https://someplace.social/tags/hashtags" class="mention hashtag" rel="nofollow noopener" target="_blank">#hashtags</a> <a href="https://someplace.social/tags/inclusion" class="mention hashtag" rel="nofollow noopener" target="_blank">#inclusion</a> <a href="https://someplace.social/tags/IOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#IOS</a> <a href="https://someplace.social/tags/NVDA" class="mention hashtag" rel="nofollow noopener" target="_blank">#NVDA</a> <a href="https://someplace.social/tags/posts" class="mention hashtag" rel="nofollow noopener" target="_blank">#posts</a> <a href="https://someplace.social/tags/ScreenReaders" class="mention hashtag" rel="nofollow noopener" target="_blank">#ScreenReaders</a> <a href="https://someplace.social/tags/SocialMedia" class="mention hashtag" rel="nofollow noopener" target="_blank">#SocialMedia</a> <a href="https://someplace.social/tags/Talkback" class="mention hashtag" rel="nofollow noopener" target="_blank">#Talkback</a> <a href="https://someplace.social/tags/technology" class="mention hashtag" rel="nofollow noopener" target="_blank">#technology</a> <a href="https://someplace.social/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a>

Georgiana BrummellI am copying this from a friend, because I can't share it the regular way. I have added a few extra tags so that both the blind and sighted community can be made aware of this wonderful project. "Broadfork, Boosted from <a class="u-url mention" href="https://mindly.social/@KuJoe" rel="nofollow noopener" target="_blank">@KuJoe</a>: For those of you on mobile (and desktop) who find it difficult to write alt text for images you upload, I’ve built a simple website to do it for you. It’s very basic right now, but it uses Google’s Gemini AI to write the alt text for images you upload. Current testing indicates I probably need to dial it back to make the alt text less detailed, but if you’d like to try it out and see if it works for you then feel free: <a href="https://alttexty.org/" rel="nofollow noopener" target="_blank">https://alttexty.org/</a> " <a class="hashtag" href="https://blob.cat/tag/alttext" rel="nofollow noopener" target="_blank">#AltText</a> <a class="hashtag" href="https://blob.cat/tag/android" rel="nofollow noopener" target="_blank">#Android</a> <a class="hashtag" href="https://blob.cat/tag/accessibility" rel="nofollow noopener" target="_blank">#Accessibility</a> <a class="hashtag" href="https://blob.cat/tag/accessibilitytesting" rel="nofollow noopener" target="_blank">#AccessibilityTesting</a> <a class="hashtag" href="https://blob.cat/tag/blind" rel="nofollow noopener" target="_blank">#blind</a> <a class="hashtag" href="https://blob.cat/tag/developers" rel="nofollow noopener" target="_blank">#developers</a> <a class="hashtag" href="https://blob.cat/tag/gemini" rel="nofollow noopener" target="_blank">#Gemini</a> <a class="hashtag" href="https://blob.cat/tag/googlegemini" rel="nofollow noopener" target="_blank">#GoogleGemini</a> <a class="hashtag" href="https://blob.cat/tag/ios" rel="nofollow noopener" target="_blank">#IOS</a> <a class="hashtag" href="https://blob.cat/tag/images" rel="nofollow noopener" target="_blank">#images</a> <a class="hashtag" href="https://blob.cat/tag/nvda" rel="nofollow noopener" target="_blank">#NVDA</a> <a class="hashtag" href="https://blob.cat/tag/screenreaders" rel="nofollow noopener" target="_blank">#ScreenReaders</a> <a class="hashtag" href="https://blob.cat/tag/talkback" rel="nofollow noopener" target="_blank">#Talkback</a> <a class="hashtag" href="https://blob.cat/tag/voiceover" rel="nofollow noopener" target="_blank">#Voiceover</a> <a class="hashtag" href="https://blob.cat/tag/windows" rel="nofollow noopener" target="_blank">#Windows</a>

Georgiana BrummellEvery time I go to the main Friendica site, I am reminded of why I joined Akkoma. They still have done nothing about accessibility. I know their team is very small, but some of these things shouldn't be that difficult to resolve. This site isn't perfect either, but it's a lot better with most things. Still, I mostly post to Reddit and Dreamwidth. The former is accessible with Reddit for Blind, and Luna for Reddit, and the latter is accessible with... Dreamwidth! Yes! A 100% accessible site can, and does, exist! Why it's so difficult for people to use semantic html and follow WCAG guidelines is beyond me. Likewise, why sites such as Facebook, GMail, and Youtube had perfectly working mobile versions (not apps, but websites) and then shut them down baffles me! <a class="hashtag" href="https://blob.cat/tag/accessibility" rel="nofollow noopener" target="_blank">#accessibility</a> <a class="hashtag" href="https://blob.cat/tag/akkoma" rel="nofollow noopener" target="_blank">#Akkoma</a> <a class="hashtag" href="https://blob.cat/tag/blind" rel="nofollow noopener" target="_blank">#blind</a> <a class="hashtag" href="https://blob.cat/tag/dreamwidth" rel="nofollow noopener" target="_blank">#Dreamwidth</a> <a class="hashtag" href="https://blob.cat/tag/facebook" rel="nofollow noopener" target="_blank">#Facebook</a> <a class="hashtag" href="https://blob.cat/tag/friendica" rel="nofollow noopener" target="_blank">#Friendica</a> <a class="hashtag" href="https://blob.cat/tag/nvda" rel="nofollow noopener" target="_blank">#NVDA</a> <a class="hashtag" href="https://blob.cat/tag/reddit" rel="nofollow noopener" target="_blank">#Reddit</a> <a class="hashtag" href="https://blob.cat/tag/screenreaders" rel="nofollow noopener" target="_blank">#ScreenReaders</a> <a class="hashtag" href="https://blob.cat/tag/youtube" rel="nofollow noopener" target="_blank">#Youtube</a>

wall-e / DanielAre there any Hamburg based blind or visually impaired ux/ui designers, users or programmers on here?I'm not blind but have an academic background in human-computer interaction and have thought a lot about purpose-built ui/ux for screen readers during the past few weeks and would love to have some folx to bounce around ideas for better, "accessibility first" interface design.Any code which might result from these discussions would be free (in the GPL sense) and open-source of course!<a href="https://ioc.exchange/tags/ux" class="mention hashtag" rel="nofollow noopener" target="_blank">#ux</a> <a href="https://ioc.exchange/tags/ui" class="mention hashtag" rel="nofollow noopener" target="_blank">#ui</a> <a href="https://ioc.exchange/tags/accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#accessibility</a> <a href="https://ioc.exchange/tags/screenreaders" class="mention hashtag" rel="nofollow noopener" target="_blank">#screenreaders</a> <a href="https://ioc.exchange/tags/blindtech" class="mention hashtag" rel="nofollow noopener" target="_blank">#blindtech</a>

AydanI can't remember where/when I found them, maybe on fedi, but these two lists of how unicode characters are pronounced in JAWS or NVDA (two popular screen readers) are useful to think about when writing alt text or text intended for screen readers.<a href="https://stevefaulkner.github.io/symbols/SymbolsJAWS.html" rel="nofollow noopener" translate="no" target="_blank">https://stevefaulkner.github.io/symbols/SymbolsJAWS.html</a><a href="https://stevefaulkner.github.io/symbols/SymbolsNVDA.html" rel="nofollow noopener" translate="no" target="_blank">https://stevefaulkner.github.io/symbols/SymbolsNVDA.html</a><a href="https://aus.social/tags/screenReaders" class="mention hashtag" rel="nofollow noopener" target="_blank">#screenReaders</a> <a href="https://aus.social/tags/accessability" class="mention hashtag" rel="nofollow noopener" target="_blank">#accessability</a>

Frontend DogmaMake Screen Readers Talk With the ARIA Notify API, by <a href="https://tech.lgbt/@alex86" class="u-url mention" rel="nofollow noopener" target="_blank">@alex86</a>:<a href="https://www.oidaisdes.org/aria-notify-first-look.en/" rel="nofollow noopener" translate="no" target="_blank">https://www.oidaisdes.org/aria-notify-first-look.en/</a><a href="https://mas.to/tags/accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#accessibility</a> <a href="https://mas.to/tags/screenreaders" class="mention hashtag" rel="nofollow noopener" target="_blank">#screenreaders</a> <a href="https://mas.to/tags/aria" class="mention hashtag" rel="nofollow noopener" target="_blank">#aria</a> <a href="https://mas.to/tags/apis" class="mention hashtag" rel="nofollow noopener" target="_blank">#apis</a> <a href="https://mas.to/tags/javascript" class="mention hashtag" rel="nofollow noopener" target="_blank">#javascript</a>

🇨🇦Samuel Proulx🇨🇦 What screen readers do you use regularly on your Android device? I’m looking for an anecdotal idea of how popular alternative <a href="https://fed.interfree.ca/tags/screenreader" rel="nofollow noopener" class="hashtag" target="_blank">#screenreader</a> apps on <a href="https://fed.interfree.ca/tags/android" rel="nofollow noopener" class="hashtag" target="_blank">#android</a> really are. Please boost! Thanks so much for your help. <a href="https://fed.interfree.ca/tags/screenreaders" rel="nofollow noopener" class="hashtag" target="_blank">#screenreaders</a> <a href="https://fed.interfree.ca/tags/a11y" rel="nofollow noopener" class="hashtag" target="_blank">#a11y</a> <a href="https://fed.interfree.ca/tags/accessibility" rel="nofollow noopener" class="hashtag" target="_blank">#accessibility</a> <a href="https://fed.interfree.ca/tags/blind" rel="nofollow noopener" class="hashtag" target="_blank">#blind</a>

aaronJust published a blog post tearing into hCaptcha’s so-called “accessibility” mode.It’s not accessibility. It’s a cookie. And to get that cookie, you now have to submit your email and send a code via SMS to an U.S. phone number. It fails silently. It doesn’t confirm anything. You click “Confirm Code” and get “An error has occurred.” No cookie. No fallback. No support. And if you somehow get it? It’s a third-party cookie your browser probably blocks, and it expires. Then you get to do it all again.Meanwhile, hCaptcha’s text-based challenge — the only mode that might actually work with a screen reader — isn’t tied to the cookie at all. It only shows up if the website owner specifically enables it. Most don’t. So even if you’re blind, even if you’re using assistive tech, you get the same unusable image grid as everyone else.This isn’t accessibility. It’s exclusion wrapped in PR.The blog post breaks it all down: how the cookie flow works (or doesn’t), why the system is broken by design, how developers got misled, and what real alternatives look like. If you care about accessible design or just want to understand how bad this gets, read it.Link: <a href="https://fireborn.mataroa.blog/blog/hellcaptcha-accessibility-theater-at-its-worst/" rel="nofollow noopener" translate="no" target="_blank">https://fireborn.mataroa.blog/blog/hellcaptcha-accessibility-theater-at-its-worst/</a><a href="https://dragonscave.space/tags/Accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#Accessibility</a> <a href="https://dragonscave.space/tags/a11y" class="mention hashtag" rel="nofollow noopener" target="_blank">#a11y</a> <a href="https://dragonscave.space/tags/BlindTech" class="mention hashtag" rel="nofollow noopener" target="_blank">#BlindTech</a> <a href="https://dragonscave.space/tags/hCaptcha" class="mention hashtag" rel="nofollow noopener" target="_blank">#hCaptcha</a> <a href="https://dragonscave.space/tags/HellCaptcha" class="mention hashtag" rel="nofollow noopener" target="_blank">#HellCaptcha</a> <a href="https://dragonscave.space/tags/UX" class="mention hashtag" rel="nofollow noopener" target="_blank">#UX</a> <a href="https://dragonscave.space/tags/WebDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebDev</a> <a href="https://dragonscave.space/tags/ScreenReaders" class="mention hashtag" rel="nofollow noopener" target="_blank">#ScreenReaders</a> <a href="https://dragonscave.space/tags/Disability" class="mention hashtag" rel="nofollow noopener" target="_blank">#Disability</a> <a href="https://dragonscave.space/tags/TechRant" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechRant</a> <a href="https://dragonscave.space/tags/DevTools" class="mention hashtag" rel="nofollow noopener" target="_blank">#DevTools</a> <a href="https://dragonscave.space/tags/Ableism" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ableism</a> <a href="https://dragonscave.space/tags/Privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#Privacy</a> <a href="https://dragonscave.space/tags/FOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FOSS</a> <a href="https://dragonscave.space/tags/Inclusion" class="mention hashtag" rel="nofollow noopener" target="_blank">#Inclusion</a>

Sarah AThose having issues with the start menu not reading when searching for items please submit your comments here <a href="https://aka.ms/AAwefzf" rel="nofollow noopener" translate="no" target="_blank">https://aka.ms/AAwefzf</a> Thanks. <a href="https://glitchsoc.bg-presents.us/tags/Technology" class="mention hashtag" rel="nofollow noopener" target="_blank">#Technology</a> <a href="https://glitchsoc.bg-presents.us/tags/ScreenReaders" class="mention hashtag" rel="nofollow noopener" target="_blank">#ScreenReaders</a> <a href="https://glitchsoc.bg-presents.us/tags/NVDA" class="mention hashtag" rel="nofollow noopener" target="_blank">#NVDA</a>

Recent searches

Search options

Administered by:

Server stats:

#screenreaders