Items tagged with: ScreenReader

Search

Items tagged with: ScreenReader


Recent datepicker experience:
1. Control is presented as three separate spin controls, supporting the Up/Down Arrow keys to increment and decrement the value as well as manual typing. But because they're not text inputs, I can't use the Left/Right Arrow keys to review what each separate one contains, only to move between day, month, and year.
2. I tab to year.
3. I press Down Arrow, and the value is set to 2075. I'm unclear how many use cases require the year to be frequently set to 2075, but I can't imagine it's many so this seems like a fairly ridiculous starting point.
4. I press Up Arrow, and the value gets set to 0001. The number of applications for which 0001 is a valid year is likewise vanishingly small.
5. I delete the 0001, at which point my #screenReader reports that the current value is "0". Also not a valid year.
6. Out of curiosity, I inspect the element to see which third-party component is being used to create this mess... only to find that it's a native `<input>` with `type="date"` and this is just how Google Chrome presents it.

A good reminder that #HTML is not always the most #accessible or user-friendly.

#accessibility #usability


So an update on Guide: I've exchanged some long emails with Andrew, the lead developer. He's open to dialogue, and moving the project in the right direction: well-scoped single tasks, more granular controls and permissions, etc. He doesn't strike me as an #AI maximalist can and should do everything all the time kind of guy. He's also investigating deeper screen reader interaction, to let AI just do the things we can't do that it's best at. I stand by my thoughts that the project isn't yet ready for prime time. But as someone else in the thread said, I don't think it should be written off entirely as yet another "AI will save us from inaccessibility" hype train. There is, in fact, something here if it gets polished and scoped a bit more. #blind#screenreader#a11y


Can you guess what I'm reading about from this nonsensical #screenReader output? I loaded the webpage myself and not even I understand. #accessibility

"
heading level 2 How it Works
Slides carousel 1 / 3 slide
out of slide 2 / 3 slide graphic How it works
out of slide 3 / 3 slide
out of slide 1 / 3 slide
out of slide 2 / 3 slide graphic How it works
out of slide 3 / 3 slide
out of slide 1 / 3 slide
out of slide 2 / 3 slide graphic How it works
out of slide 3 / 3 slide
out of slide button Previous slide
button Next slide
button current Go to slide 1
button Go to slide 2
button Go to slide 3
out of carousel link app-tutorial
link App Tutorial
heading level 2 No One Does it Alone...
"



Hello #Blind and #VisuallyImpaired community! 👋
I'm having trouble signing PDF documents with a digital certificate using my #screenreader (NVDA on Windows). I can do it in Adobe Reader but it's quite cumbersome and requires sighted assistance.
Does anyone have a more accessible workflow or software recommendation for signing PDFs with a digital certificate using the keyboard and a screen reader? Any tips or advice would be greatly appreciated!
Could you please #Boost this so it reaches more people? Thank you in advance! 🙏 #Accessibility #NVDA #PDF #DigitalSignature #AssistiveTechnology @NVAccess



Today I learned: If you use #Chrome and are annoyed by those "Sign in with Google" dialogs stealing keyboard focus on certain websites, you can disable it at the browser level.

In the address bar, type or paste in "chrome://settings/content/federatedIdentityApi" (without the quotes. You should land on the "Third-party sign-in" Settings page.

On that page, there'll be two radio buttons: "Sites can show sign-in prompts from identity services", and "Block sign-in prompts from identity services". Set it to the second one, and you should find that the problematic dialogs are no longer present.

#accessibility #screenReader


Tried the free edition of the #ZDSR#screenreader because I was curious. I will say that for my use-case, if #ZDSR was fully documented in English, it competes a lot more directly with #nvda than #jaws does, runs fine in a virtual machine, and has a bunch of stuff built in that I use NVDA addons for. If it had an English website I'd probably grab a copy for the entirely reasonable price. But I'm not willing to purchase through translation.


The app for the TP-Link Deco mesh system is nice and #screenreader#accessible if you're in the market for a router. More than can be said for Linksys Velop. Amplifi was okay, but the TP-Link app is actually better, at least on #IOS with #voiceover. I haven't had the system for long enough to give a review, other than that setup was quick and all the apps joined without issue. Also the default DHCP settings are weird. Who wants to start at 192.168.68.1? Changing it isn't obvious. First you have to change the lan address. Then it will change the gateway for you as part of that. Only then can you change the DHCP allocation. And even then it wants to start allocating at 192.168.0.1. That's too weird for me when the router lives at 192.168.1.1. And even after fiddling, it's still randomly assigning devices in 192.168.2. and 192.168.3.. But at least it let me reserve the devices that I need to be static. I probably have to go somewhere and do something incomprehensible with netmasks, but whatever. It's fine. #a11y


Does anyone have the #eloquence 6.1 dlls with Korean and Japanese support? I can't use 6.6 in this context because it needs to be portable and so I can't register the dll files. #nvda#screenreader#a11y Maybe @Tamasg perhaps?


So the primary thing I've learned from trying out the Ducky One #mechanical#keyboard is just how much lag my previous keyboards (a codekeyboard and a razer) were adding. I use a #screenreader, so I'm deeply aware of the audio lag from headphones and the audio subsystem, and configure things to reduce that as much as I can. I also knew bluetooth can introduce lag. But on picking up the Ducky...wow! A few ms can really matter! My system feels faster than it's ever felt before. Even if I wind up returning this, now I know that keyboard refresh rate is a thing I care about. Also, the inductive switches feel really nice and clicky to press, but are reasonably quiet for those around me.


Hey, #MechanicalKeyboard people! I just got myself a #Ducky One X wireless mechanical keyboard. As a #screenreader user who finds myself constantly running out of keyboard shortcuts, multi-level actuation sounded really exciting to me. Unfortunately, the browser-based programmer at duckyhub.io is entirely inaccessible. Apparently it uses a standard called #QMK or something? I don't build mechanical keyboards; I use them because I love the feedback, so I'm not deep enough into the hobby to know much about this. A browser-based programmer gave me hope that programming would be #accessible, but at least with the official website, that hope turned out to be false. So before I return this thing, do these standards mean there might be other software I can try to program the keyboard, to see if it's more accessible for me? #a11y#keyboard


Does anyone know if #LibreWolf or any other privacy focused #firefox forks keep #screenreader and other #accessibility features? Sadly, most of these projects seem to consider accessibility an unneeded feature that ads bloat and security issues and just strip it out completely, so I don't have high hopes. This just seems to be the latest one getting popular after the recent #firefox issues. #a11y


What's the state of #matrix, #xmpp and #IRC as far as #screenReader -accessible clients are concerned? Desktop (Windows, Mac) and mobile (iOS, Android).

Hoping for some input, please feel free to boost. As far as I know:

Matrix does not have a lightweight, fully accessible client for desktop, but one could be modified, such as #gomuks. On mobile, Element has scrolling issues, which is unacceptable for large rooms.

XMPP has accessible desktop clients (I used to run #Adium on the Mac), also #WeeChat. No idea about mobile.

IRC is perhaps the one which everything supports on desktop, from #MirandaIM through Weechat to the old Freedom Chat, which I could probably rewrite if I had to. Also not sure about mobile, but it would definitely need push notifications, because we can't expect people to stay constantly online on the go. #a11y #accessibility



Been playing with a video/article concept as of late with the working title"What you see is NOT what you get", pertaining to making things #accessible to fully #blind users.
A lot of #accessibility issues are easy to visualize: a missing ramp in front of a building, bad contrast, missing captions etc. but #screenReader accessibility is a lot more nebulous because there's actually not that much reading of the screen happening. I can't "point" at a screen reader accessibility issue because it happens behind the curtain, in the land of metadata, APIs and standards, rarely on the actual screen, which also makes it more difficult to "visualize" for devs. hrmm.


Our In-Process blog is out! Featuring:
- Update on NVDA 2025.1
- Planning for CSUN
- What's on the web
- Reading paragraphs in Braille

And bonus history of the Pilcrow! (Ok I was interested)

nvaccess.org/post/in-process-2…

#NVDA #NVDAsr #ScreenReader #Blog #News #Newsletter #Typography #CSUNATC



Also, the silly voice acting and humorous sound effects are almost worth the price of admission all on their own. Tip for #screenreader players: press zed to advance. The game does tell you that, but it tells you just one screen too late. When it's showing a picture, pressing enter will activate one of the menu options like pause or save or whatever, instead of advancing. Pressing the letter z will always advance. I don't actually know if that's just a standard #renpy thing I didn't know and never needed before in other games? It would make sense; in Infocom and other z-machine parser games, "z" is the standard "do nothing and wait" shortcut. So it might be a standard shortcut I just didn't know. But anyway, if you're stuck on advancing past the second thing after new game, z is what you need.


Spent a couple hours playing the visual novel Pizza Game. If you're the kind of person who finds bad My Immortal style #fanfic funny, this will work for you. It's fully #screenreader#accessible in the standard #renpy way, but also has descriptions of the visual jokes; the developer spent time thinking about #A11y, and it didn't just happen thanks to the engine. store.steampowered.com/app/710710/Pizza_Game/#visualnovel


Adding meaningful alt-text is not only important for everyone using a screenreader and an essential #inclusion and #accessibility requirement. Alt-text is also searchable and used by filters. People who prefer to filter certain people and topics for mental health and other reasons can't filter memes or images without it. Please use alt-text and cw generously 🙏

Added bonus: with added alt-text you can find images in your own posts with "from:me" and people are more likely to boost your posts.

#screenreader #fediverse #Mastodon



This is a long shot I know, but I know there were versions of the iOS Siri voices floating around for NVDA at one point. Does anyone have up to date addons of these voices somewhere and would be willing to share? If so, please feel free to reply or dm if you don't wish it to be public. #Windows #accessibility #screenreader #NVDASR #TTS



@Lukáš Tyrychtr @Jure Repinc @Gregarious I would be interested to know how do you guys use the @Dino #XMPP messaging app with a #screenReader? When I launch it it opens one of my recent conversations. Input box has the focus. I can't figure out how to use the keyboard to navigate to the incoming chat, to the toolbar, to the menu and similar. I can use ctrl+tab to cycle through open conversations. I am using version 0.4.4.


Be wary when adding additional context only for #screenReader users. An example:

Say you're working on an e-commerce site, and some products have two prices to show how great a sale discount is. The before and after is made visually apparent via some aspect of text formatting, and you want to make it explicit for screen reader users too.

The first step is to ask if this is necessary. If a user encounters two consecutive prices and one is lower than the other, they may intuitively understand what's going on without any explicit signposting, and can verify how much they're gonna pay during the checkout process. Only your users can provide this verdict.

If it's determined that some additional context is helpful, you could format it as something like: "Was $14.99, now $8.99" (optionally swapping the prices). It's short and punchy in braille and speech, perfectly descriptive of the situation at hand, and mirrors how it may be spoken out loud on an ad.

Resist the temptation to go further than this. You do not need to say "original price: $14.99, current sale price: $8.99". This is much longer and more verbose, while adding nothing. It also implies that you think screen reader users need to be told what a price is and explained the concept of a sale, even though you're not doing so for other audiences.

You also don't need to spell out the word "dollars", format the price in words, repeat the product name, and so on. If you find yourself with screen-reader-only text like: "The current price of 500 Grams of Premium Oolong Tea was fourteen dollars and ninety-nine cents, and is now on sale for eight dollars and ninety-nine cents", it has gone way too far.

In short: Set out to identify the problems that actually need solving, and only solve those problems.

#accessibility


In-Process is out - featuring news on NVDA 2024.4.2, our new add-on survey, a very successful SPEVI 2025 conference, and a User's guide: What to do if your add-on breaks?

Read the full issue now at:
nvaccess.org/post/in-process-2…

and remember, you can now subscribe to receive In-Process via email at: eepurl.com/iuVyjo

#NVDA #NVDAsr #Blog #News #Newsletter #WhatsOn #ScreenReader #Accessibility



If you're a #blind user, you should really consider #Kagi for web search. Especially if you pay for chat GPT pro, you can subscribe to Kagi instead for cheaper and get more features. But even if you don't want AI, the search page is #accessible, fast, and light-weight. And unlike other big tech companies (Microsoft and Google) Kagi still offers a cheaper plan with no AI if you don't want it. Also, because they downrank websites with ads, the more accessible results tend to be at the top. Kagi also lets you block domains from your results. So I got rid of inaccessible stuff like instagram and pinterest, and downranked YouTube, because those results aren't usually #screenreader accessible. While I don't agree with many of the opinions of the @kagihq founder (especially his decision to do business with Yandex for image search), I still feel like using Kagi is more ethical than dealing with Google or Bing, and that these are reasonable differences of opinion that reasonable people can have, not just another clownishly evil tech company. I also find the idea that if you're a paying customer, that somehow guarantees the business will treat you better, really strange. I pay a lot to my ISP and they still treat me like dirt! Kagi will almost certainly sell out at some point. But for the moment, it's where it's at for search: www.kagi.com/


For anyone following this, it looks like my answer is #readeck. The interface is #accessible, it does full text search, it archives pages, it has a browser extension, it works with #miniflux, it does the same kind of read/unread tracking that I wanted from #goodlinks, and it plays well with the rest of my things. Thanks so much to @readeck for making sure to build an interface that is fully #screenreader accessible. The only thing I'm lacking is an #IOS app. And the ability to share some labels publicly would also be neat. But otherwise, Readeck is perfect for my use-case. If you're a #blind person who wants a demo account to test it out and see if it works for you without going through all the bother of installation and set-up, send me a direct message. #a11y


The Release Candidate of NVDA 2024.4.2 is now available for testing. We encourage all users to download this RC and provide feedback.

Read more and download from: nvaccess.org/post/nvda-2024-4-…

This is a patch release to fix bugs with braille devices and reading math in Chromium. Fixed bug with with reading math in Chromium Browsers (Chrome, Edge). Humanware Brailliant BI 40X devices running firmware version 2.4 now work as expected.

#NVDA #NVDAsr #ScreenReader #Release #PreRelease #Update #Update



So is it just not possible to play #Forza horizon anymore? I restarted, and now can't set a route to get past the opening, no matter what I do. #a11y#audiogames#screenreader


@matt@toot.cafe Random question about screenreaders: Is typing every single occurrence of a hyperlinked word as a hyperlink (instead of e.g. just the first) annoying?

E.g. is

This compares [A] vs. [B].
While [A] offers better performance,
[B] uses less memory.

more annoying to listen to than
This compares [A] vs. [B].
While A offers better performance,
B uses less memory.

? Thank you!!
(if anyone else has experience with a #screenreader, please do tune in!!)


#Screenreader users: in a timed online exam, how would you expect to interact with something telling you the amount of time left?

I think having it regularly announce the time remaining is an obviously bad idea. If you know that it's labelled "Time remaining", would you just search for that text in the page when you want to check the time?

#accessibility #screenreader #VoiceOver #JAWS #NVDA


Dear friends, #screenreader users, #blind users and #accessibility professionals in particular.
Are you using chat over traditional email as provided by #DeltaChat / #DeltaLab / #ArcaneChat?
I like it uses traditional email infrastructure, is federated, supports end to end encryption, rich content including audio / voice messages. I have even recognized @adb has implemented screen reader accessibility specific features into the android app.
However I have quickly tried electron based app on linux with orca screen reader, exchanged a few messages back and fort between two of my personal accounts using the DeltaChat app and thunderbird and I haven't found the user experience verry appealing. I can't understand how to effectivelly navigate in the list of conversations and list of messages.
Therefore I would be interested to hear a few comments from people knowing this platform better. How accessible is it on different platforms?
On the desktop is the electron based app a prefered choice?
Also some other questions. For the best experience, do I need a new email address or can I use my existing self-hosted one I have already configured in thunderbird?
Ffeel free to point me to a FAQ, some up to date introductory documentation if you think my questions don't make much sense please.


I'm looking at setting up #Prometheus for monitoring my newly set up Proxmox host and the things running on it.

Has anyone done this with a #ScreenReader?

I've had to use #Grafana dashboards in the past and it wasn't great, since I couldn't get the data to show in tabular form.