Two problems with #Hulu's "Choose your ad experience" ad breaks:
Every time one comes up, it turns the audio description track off, but without changing the controls. You have to turn it to 'normal audio' and then back again to get descriptions back. #accessibility
Nobody wants to 'choose' an ad. Nobody cares. Nobody has ever in their life thought "I'd like ads if I could pick 'em." Just play them in rotation. Don't make us wait extra time for the ad to start.
I appreciate the call for more public transit, but I do not find it safe or accessible. Since people don’t wear masks on public transit, and since most public transit seems to have shitty air circulation, I know it’s a plague vector. I’ve been walking or biking everywhere and haven’t been on a bus since 2020. I’ve seen so many obviously sick, unmasked people waiting in bus shelters, and I don’t want what they’ve got. I wish people gave a shit about protecting one another from getting sick. #PublicTransit#accessibility#MaskUp
Yesterday was Another day of working on #OpenWebUi for #accessibility. I had a few things I did. First, I made the chat more accessible by adding labels. Next, I added more headings. Finally, I fixed the mottle selection dropdown. It is finally labeled now. Today, I hope to fix some menus and remove icons that are causing issues for scree reader users. Want to see my progress? check out the github. https://github.com/tayarndt/open-webui
1/3 I tested some popular latest LLM UIs for accessibility with screen readers, including oobabooga text-generation-webui, Open WebUI (aka Ollama WebUI), GPT4All, LM Studio, Koboldcpp, and Llama.cpp server on Windows. The most accessible was Llama.cpp server, though it had the fewest features. Oobabooga was also good, except for the list box not announcing choices as you browse; however, you can check your selection afterward. #accessibility#LLM#AI
@emmecola For blind people like me, if AI solves a captcha it's a miracle, not a problem. Companies should rethink client-based human verification; captcha is a discriminatory message. If you -company- experience fraud, it's not my responsibility to tell you I'm a human. It's your responsibility to protect me SERVER side, not placing a guardian with the gun at the door who kicks me out if I'm blind, deaf or cognitive impaired, because I can't solve the quiz you implemented. #accessibility#a11y
Hey everyone. On Wednesday I learned that I successfully passed my #CPACC exam! That combined with my existing #WAS certification makes me a #CPWA now! This has been a long-standing dream and goal of mine and I am ecstatic to have finally accomplished this achievement! #accessibility
It shows how to create a graphical user interface with Windows.Forms (dotnet) in Powershell.
The update added the ability for the font to adapt to the user's font theme and size changes in Windows. It's silly, really: Windows.Forms should do that by itself. But it doesn't, so every programmer has to be aware and make it happen. #accessibility#ux
🤔 as a long time command line geek I love TUIs, but i hate how horrible they are for #accessibility I hate making a tool and knowing "wow, this is gonna be completely, absolutely, and totally miserable for any blind person"
FINALLY got my hands on a Windows machine at work to install and use JAWS and NVDA properly for testing, instead of doing it on a virtual machine inside my work Mac.
Gosh they're both so chatty on first start... For good reason, I know. NVDA was MUCH faster an install too.
It's unclear whether it passes wcag but from our research I think it's much clearer to mark optional fields as 'optional' than have asterisks or 'required' next to every field and have optional fields implied by the lack of them.
If you're asking for data, the default should be it's because it is required. This is part of GDPR
I noticed that #Obsidian is barely useable with keyboard navigation on iOS/iPadOS. The UI herarchy does not translate into accessible tab navigation. The deepest reachable UI element is the vault switcher menu. There is room for improvement.
On May 1, HHS released a final rule that updated Section 504, something disability advocates have been demanding for decades. This rule clarifies and strengthens civil rights protections against the constant healthcare discrimination disabled people experience. And on April 26 the Department issued a final rule regarding Section 1557 of the Affordable Care Act (ACA), which prohibits discrimination based on race, color, national origin, sex, age, or disability in covered health programs and activities. These final regulations are vital for improving the medical care and access to services people with disabilities receive, and this webinar will help highlight why.
"Love it or hate it, it’s hard to deny how easy (relatively speaking) it is in React to develop two apps with a single codebase. React Native has been around since about 2015, and if you’ve been in the accessibility space, you’ve probably heard some warnings to not use it due to a lack of accessibility customization or remediation paths."
I love that a multi-billion-dollar corporation like RedHat/IBM can ship an operating system with a broken screen reader in 2024 (it’s not just them, it’s true for basically every major Linux distribution today) and, when you point it out, the response is “it’s no one’s fault… it’s all free labour… it’s FOSS, man”. And then: oh, and this charity is paying for one person to work on accessibility support to be implemented now… Anyone else see how fucked up that is?
65% of vision impaired people are over 50 years of age, despite making up only 20% of the world's population.
Accessible technology benefits everyone. As we age vision impairment becomes more likely. NVDA's free and open-source technology ensures no one is unfairly disadvantaged because of their vision.
You can support NV Access providing accessible technology by donating:
Linux blind users, listen to this and let me know what you guess this actually is, and most importantly, what you think! I'm just gauging interest as this is still in its early infancy, and I was wondering if it was worth continuing. As you can infer, I'm already far enough to have a working yet incomplete prototype!
Hi #blind folks, especially software developers! I'm taking part in a #GitHub research meeting and I hope to raise as many #accessibility points as I can. I was told this fact is not at all confidential, so I may gather feedback.
Here's what I remember: multiline comments are inaccessible (eternal story); sometimes menu roles are used where they shouldn't be (watching repos, reactions etc.). Anything else that really bugs you at GitHub? Thanks!