The reason I'm suggesting this, is because if you are a small/medium instance with open registrations, and spammers find and abuse your instance, I imagine that other instances will limit/suspend your instance without hesitation, given how willing some were to limit/suspend the much larger mastodon.social.
But do note this comment on the PR:
“To give some context to people seeing this: this is an emergency feature backport from Glitch SOC to help mitigating an ongoing spam wave, this feature may not make it in a next release, or with significative changes.”
Edited to add: multiple people have rightly commented on the accessibility concerns with hCaptcha: hCaptcha is really really really bad for blind and visually impaired people.
Please have a look at this excellent reply for more details:
@michael Please, please do not do this under any circumstance, if you care about your instance being accessible to the #blind and visually impaired (hint, you should).
#HCaptcha is a horrible example of how not to implement a #captcha solution, forcing people to register their email address and store a cookie, as well as disable cross origin restrictions on their devices in order to pass validation.
There are much better alternatives, such as the no-hassle https://github.com/mCaptcha/mCaptcha, which does not need any user input other than checking a checkbox. Alternatively, use captchas that provide text versions, e.g. via solving a math question or at the very minimum, provide an audio version, knowing that it is not ideal for the hearing impaired.
@michael@donmelton It's incredibly sad that H-Captcha was chosen despite it's lack of #accessibility and despite having other accessible options that are as valid and as useful.
Question for folks who build #iOS or #android apps with #accessibility in mind. How do you design, build, and test functionality for switch controls? Have you purchased (seemingly overpriced) kit from the known accessible tech sellers? Rolled your own switch in some way? Any other suggestions?
Today is GAAD (Global Accessibility Awareness Day). I am sharing some foundational (typography, color, & spacing) accessibility design tips for everyone. Enjoy!
p.s. this goes without saying, add alt text to your images.
"With this latest update, screen reader or keyboard users can now move focus around the canvas, as well as between different menus and screens, to create, edit, and read out content (including file structure, shapes with text, stickies, tables, and image alt text)."
We’re back with Wacky Races on This is How We Roll! Watch a full play-through and also see how Will and Sarah play games together and what they do differently to overcome Will’s vision disabilities. This is how we roll!
📝 Website Issues: On the Relevance of Audience Size and Impact:
Website issues—relating to #conformance, #security, #accessibility, #performance, #content, others—are usually treated with a particular priority, but that priority may not always be understandable, and may also be off. On the perspective we obtain when we consider and chart #audience size and impact.
Today is #GAAD (Global Accessibility Awareness Day)! A year ago I started #365DaysIOSAccessibility. Life happens and I couldn't keep up with the challenge. But I'm very proud with my 232-day-streak on Twitter. These days I'm more active here and on LinkedIn. Will keep sharing them with you. And I'm intending to continue with the remaining 104 soon! Thanks for following the series and for all your support!
So the Chrome os Terminal app, where you interact with Crostini and such, got a big accessibility face lift recently! Now, while you type, ChromeVox isn't repeating every l e t t e r you type. Also, the terminal output is separated out into one element per line which you can just navigate like regular items. And clicking on a line puts you directly back into the text box to type another command. And yes, output is read automatically.
Ergo, GitHub is uniquely positioned to impact #disabled#DevEx on #GAAD and every day.
Please read my convo with Ed Summers to be impressed with GitHub's unified, strategic and organized effort for #accessibility, to learn about key cross-platform and Copilot updates, and to watch and simply be inspired by life and work of Paul Chiou. #GAAD2023
New font alert! Intel has open-sourced their new monospace font called IntelOne Mono. This font was designed with developers who have low vision, with the goal of making programming more accessible by making it easier to read and write code. Anyone can download the font for free from Github: https://github.com/intel/intel-one-mono #font#developers#accessibility#a11y#DX#IAmIntel
PSA: I am trying my best to write good image descriptions (alt text), but sometimes I really struggle to describe something. Especially because #FragMyBrain then has a black-out ... I am in the middle of a sentence and then I am lost for words - words that I have used just a few minutes ago. This mostly happens in English (my secondary language - with German being primary and Turkish tertiary). I then use a translation tool to find the best possible translation of a German term. So, sorry for sometimes having weird sounding texts.
But apart from that, here is my biggest problem with image descriptions: How do I describe a COLOR to a person born blind?
I think a person who lost their sight has a sense of color because they used to see them. But a person born blind? How do I do that?
This is a serious question. Really, it really bothers me because when I start writing things like "... the blossoms have pink tips ..." - I mean, what does a person born blind imagine/think what "pink" is?
Thus, my PSA: Any help on this topic, or any guideline how to describe or circumvent that in image descriptions is highly, highly appreciated. I really would not want to skip the color information because that is sometimes a very important one.
So, please 🙏 - if any of you has any suggestions, tips, ... I would be forever in your debt.
I love the new “Point and Speak” tool that was shown today. Voice-overing anything you can point at with your finger is awesome and a great example of accessible AR.
Kudos to the team and 🤟
This conversation between @johnvoorhees and David Niemeijer, the founder and CEO of AssistiveWare, about Personal Voice, Assistive Access, and why developers should incorporate Apple’s #accessibility features is detailed, nuanced, and is done from the disability first perspective.