One thing we would love to improve in #Mixxx is #ScreenReader support. Unfortunately we don't currently have any developers familiar with that kind of work. Is there anyone out there with experience in accessibility and QT who want to try to help? 👀
After a lengthy article about landmark elements, I wanted to do a short one about accessible hashtags. Turns out I'm not able to keep it short, because I started to create a comparison table. 🙃
My goal was to write some words about landmark elements, but it escalated quickly. I've created example websites, code snippets, screenshots and came up with cheeky headlines, ending up with with my longest article so far:
Suche nach einer Navigations-App. Google Maps möchte ich nicht nutzen, obwohl alles drin ist, was man haben möchte. Organic Maps, Maps.me und Magic Earth sind so voller Barrieren, dass sie nich zu gebrauchen sind. Ich mag nicht glauben, dass ein Smartphone ohne Google nicht barrierefrei navigieren kann.
@WestphalDenn
jetzt kommen wir der Sache schon ein wenig näher.
Du suchst also eine App für die #Fußgänger#Navigation, welche auch von einem #Screenreader gut ausgelesen werden kann.
Da bin ich leider nicht bewandert. Aber vielleicht kann dir ja das Fediverse helfen.
It used to be that in #Chrome, I could press Shift+F6 once a download had finished to reach it, and it would never disappear. Then, they switched it out for a dialog that popped up automatically when a download finished, but disappeared after a short number of seconds. Now, the dialog pops up, disappears after a short number of seconds, but tells me it doesn't have focus and that I should press Alt+Shift+A to get there before they hide it again. The endless cycle of shit is astounding.
"This dialog is not currently focused. Press Alt-Shift A to focus this dialog." is not a good #screenReader alert in any circumstances. It's particularly bad when the dialog in question may've disappeared by the time slower speech rate users hear the keystroke they need to press to reach it.
Was asked to 'add myself to a calendar' for a meeting, using a bloody awful site called 'when2meet' which isn't #ScreenReader accessible with #NVDA, so had to embarrassingly say 'do you think we could just arrange this meeting the conventional way? Here are some times I'm free, are there some times you're free?'
I hate this inaccessible web life we lead sometimes.
Which version is right for me? If you'd like to check out what is new in the next version of NVDA, then grab the 2024.1 beta. If you're happy staying on the stable version - grab 2023.3. #NVDA#NVDASr#ScreenReader
Me (On the phone trying to schedule something): Okay, let me open my calendar.
Presses Windows, types calendar, presses Enter
Okay, why isn't it launching? I just need to know what day that date is on!
Waits.
Outlook: Get everything in the new Outlook!
Me: Ah crap, close!
Me: Looks around to find where my calendar is I can arrow around.
Outlook: Calendar document. Application. tab Date selector. Tab Selected date January 24. TAB Go to previous month December. TAB Go to next month february Tab January 2024 table, December 31.
me: Oh thank goodness, there it is! In the old calendar app, it opened quick and landed in the calendar view where I could just arrow around the days. Like, it's almost enough to make me switch right to the Mac. Yeah it's buggy as crap with #accessibility, but the bugs at least stay the same; just about everything stays the same. So you just get slapped in the same place all the time instead of it changing spots every few months.
NVDA double release day! NVDA 2023.3.2 fixes the fix that wasn’t fully fixed in the first fix. Please do read the full announcement and download at: https://www.nvaccess.org/post/nvda-2023-3-2/
And to go with it, NVDA 2024.1 Beta 5 includes the fix from 2023.3.2, as well as documentation, logging and translation updates! Read more and download from: https://www.nvaccess.org/post/nvda-2024-1beta5/
Struggling with Ivory and VoiceOver today post-update. 🤦♀️ Is it just me, or are others facing the same issue? #Accessibility#Blind#Disability#ScreenReader 💻👀 Any tips or similar experiences out there?
For those on 2023.3 we have a security point release, NVDA 2023.3.1. We encourage all users to update to this stable release. Full info & download at: https://www.nvaccess.org/post/nvda-2023-3-1/
For those on the 2024.1 betas, we have a new one - 2024.1 Beta 4 includes the security patch above, plus more - read all the info and download from: https://www.nvaccess.org/post/nvda-2024-1beta4/
quick programming question, does anyone know how to fix the wx slider reporting the wrong values to nvda or other screenreaders. It appears to always report a higher value when pressing down and a lower value when pressing up, even if I set style to wx.SL_INVERSE. #programming#accessibility#screenreader#python#WxPython#gui
My writing family, or at least many of them sing the praises of Scrivener. Gosh, I'd love to join them in the wonders of scene organization etc, if only Scrivener for Windows were anything like usable with a #screenreader. It would be lovely if I had gotten an answer from #Scrivener people about this other than to paraphrase, we're small and not going to bother with you." Ah well, I'm a confirmed pantser anyway, so who needs this planning thing?
So, since it came up in a conversation, Element is still not okay when it comes to accessibility unfortunately. Are there any others that work well with a screen reader? Preferably with e2e support?
Do you use a screen reader? Whether you consider yourself a novice or an advanced JAWS user, we ask that you contribute to the future of web accessibility by taking the WebAIM Screen Reader Survey. Check out our latest blog: Take the WebAIM Survey https://blog.freedomscientific.com/take-the-webaim-survey/
Update on that weird text Hcaptcha from yesterday. I left the page alone for a while, came back to discover the whole thing had reset and I had to click the checkbox again to load the challenge, and then it just kinda... went straight through. I guess the answers I gave it were right? I honestly have no idea what happened. I wish I had a better answer than "fixed, bai" but that's all I've got. My guess to the presence of typos is that they're meant to throw off transformer models, but that's a UX choice worthy of an r/asshole design post IMO, especially if you're blind. That's extra brainpower you have to dedicate to fixing the typos in your head as you process the rest of the statement at the same time. It's one of those things where it makes you feel the insanity slowly creeping in from the edges. Not fun. In conclusion: fuck captchaas
This is the text challenge Hcaptcha has given me when I tried adding a discord bot to my server. Yes, the typose are directly copied from the captcha with no edits at all.
"Pleasе answеr the following question with a sіnglе word, number, or phrasе.
Select the most recent four figures of 47-0o6763249"
Does anybody know what this is asking me to input because I genuinely have no idea. I figured the answer is 3249, but I've gone through like 10 of these now with no luck.
There is one thing keeping me from switching to Firefox full time: the Chrome UI sounds extension. It makes a sound every time a new page loads or content updates. It's super helpful as a screen reader user when navigating very complex web apps. I tried repacking it for Firefox, but it won't run without some work. I'm looking at the sourcecode to see if I can make it work, but this is well outside my comfort zone. Anybody have resources for porting extensions from Chrome to Firefox?
I would like to hear from people using screen readers. Do you prefer the hashtags to be intermingled in the body of the message, or separately at the end?