veganism.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Veganism Social is a welcoming space on the internet for vegans to connect and engage with the broader decentralized social media community.

Administered by:

Server stats:

296
active users

#screenreader

13 posts11 participants0 posts today

In-Process is out, featuring a hint on 2025.1 beta timing, details on the updated Basic Training for NVDA training module, our recent server updates, AND what you need to know about reading info in a command prompt. Read now: nvaccess.org/post/in-process-1

And don't forget to subscribe to get the next edition (AND notification when the beta comes out) via email: eepurl.com/iuVyjo

Screenshot of a "Command Prompt" window with the command:
"C:\echo I love NVDA!" above the text "I love NVDA!" and a new prompt "C:\" with the caret below that.
NV Access · In-Process 11th April 2025We are getting close to a beta for NVDA 2025.1. We are on track for 2025.1 Beta 1 to be released early next week. Please do subscribe to be notified by email as soon as it is available! In the mean…

Sometimes when I'm arrowing through the cells of an Excel spreadsheet with #NVDA, the #screenReader will stop reading the content and just say "selected" once before falling silent. It happens regardless of the scroll lock key state, and I have to move away from the Excel window and then back to continue navigating.

Does anyone have suggestions on what might be causing this and how to avoid it? #accessibility

Anybody out there that knows a little about Orca (linux screen reader ) ? I was wondering if there was a way to direct it's output to the terminal (or to a text document) ? I work with sighted users that do some testing and they have some difficulties understanding the TTS output.

#a11y#linux#Orca

I thought tick tock might be kind of accessible with a #screenreader but really think I'll stick to youtube. 2 things going through my hearing aids at the same time makes things tricky and I don't see how to stop the auto playing of videos when scrolling through on tick tock. live and learn though, that's what I always say. nothing ventured nothing gained.

Question for folks who use screen readers: what is your preferred way for someone to write individual letters? Example, spelling out the letters on a sign that do not add up to a real word.

I did alt text for a picture of signs that were badly made. When describing the text layout, I went with "Capital Letter space Capital Letter". How well does that work versus maybe "Capital Letter dash Capital Letter"? Or is there a better option?

Wollte Iceshrimp ausprobieren. Noch bevor ich mich auf iceshrimp.de registrieren konnte stellte ich schon ein paar unbenannte Schalter fest. Naja, ist Opensource und lässt sich ändern, also auf die Registrierungsseite gegangen.
Iceshrimp.de nutzt HCaptcha. Ok, dann eben kein Iceshrimp für mich. Diese Accessibilitycookies funktionieren bei mir so gut wie nie, ich muss einem Service dem ich nicht traue meine Mailadresse geben, was noch ein faktor ist, der gegen HCaptcha spricht. Audiocaptcha gibts auch nicht. Wann endlich Captcha-alternative? #DisabledAlltag #Blind #A11Y #ScreenReader

Is it normal that tabbing over a webpage only reads the clickable links with the #screenReader, or should I also be able to get to text and images? The page gets read in full when I don't do anything, but when I start to use tab I only get to the links. (I am remaking our webpage and used the Windows screen reader for the first time, please be patient 🙈 )

a story of chloe, bruce rockwell and a shoppingcenter out of a community space on the willowstreet

some lines may be typo'ed at Dramatize Me‬'s channel in #caption to read

shelter as shoulder
5:36 teer=tear down

bean=been
watt=what

5:57 cat fun=have fun

6:15 ditch=teach

07:03 denomination=demolation

mooed up=moved up

tsk=it's
happy=happen

9:28 you're in=ruin

youtube.com/watch?v=vVjiT_YGCA4

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.

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