darn it I wish I didn't like the 22 kHZ quality Eloquence so much, it's all I ever use. On iOS, I check the "higher quality" box. I need it and want it, it'll be a sad day when I'm forced to use 11 kHZ Eloquence. One reason I don't use JAWS much despite it having Split Braille. 22 kHZ Eloquence is the bomb, it's the beast, the bee's knees. It sounds so much better and not like an AM radio Eloquence (11 kHZ)

Today, we fined X for non-compliance with transparency obligations under the Digital Services Act (DSA).

We're holding X accountable for:
🔹Deceptive design of its ‘blue checkmark’
🔹Lack of transparency of its advertising repository
🔹Failure to provide access to public data for researchers

More information: link.europa.eu/bcmC87

So helping my wife make a 40 question google form. It looks like splitting questions in to sections is not accessible since you can't move the sections after they are added. Same for questions, I added them in the order we wanted but they are now in a random order and cannot figure out how to move them. I assume it is a drag and drop them. The shuffle order for questions checkbox settings has always been unchecked? Is there a better/more accessible platform for form creation out there?
in reply to Smojo

@Smojo @atopia @M see github.com/grote/Transportr/is… – wenn die Entwickler keine APKs bereitstellen, können wir dort auch keine abholen 🤷‍♂️

This year brought great improvements to #accessibility in GNOME, including:

• Accessibility from the start on the login screen
• Full accessibility of GNOME Web
• Tons of improvements to Calendar
• Screen reader integration for Notifications
• Configure #Orca screen reader from Settings
• GTK apps integrated w/Windows & macOS accessibility

Help us reach 1,500 #FriendsOfGNOME so we can focus on accessibility even more in 2026!

donate.gnome.org

#a11y #GNOME #FOSS #OpenSource #Linux

This entry was edited (3 weeks ago)

if you want to build a secure system, you have to assume the dumbest (who isn't dumb, just not a nerd like you), most naive (who isn't naive, just doesn't know tech like you do), most helpless (who isn't helpless, just doesn't understand tech terms, especially in terrible documentation), most impatient (who isn't impatient, just doesn't want to study computers for 15 years) user and design your system around it.

Announcing the locations of the #LibreOffice Conferences in 2026 and 2027: blog.documentfoundation.org/bl…

The Most Unworkable Internet Law in the World: Quebec Opens the Door to Mandating Minimum French Content Quotas for User Generated Content on Social Media
michaelgeist.ca/2025/12/the-mo…

After reading about a major #Funkwhale instance shutting down, I'm wondering whether I should keep my podcast on open.audio.

blog.liberta.vip/libertadmin/i…

However, the idea of an audio app that uses #ActivityPub to be part of the #Fediverse is excellent.

Any suggestions on where to host a #podcast?

P. S. I just discovered @Castopod , an alternative to @funkwhale

I want to inspect which one is more stable, and if there are good servers as well. Feedback welcome!

This entry was edited (3 weeks ago)

Looking for guidance from my musician friends. I have a Komplete Kontrol A61 keyboard, and think it's far past time I learned to play this thing competently again. I also have a very friendly cat/raccoon/weasel/mythical creature hybrid whose species we aren't really sure of. Said catmonkeyweaselcoon likes to sit on things. As such, the keyboard is currently in its case to keep it from getting clogged with beige fur and litter. The case does a great job of keeping it litter-free, but also does a great job of keeping me from playing.

What do I need to keep this thing safe from our monkeybobcat creature? I see dust covers but our boy is 13 pounds dense, and I'm concerned the keys might get crushed over time. I don't think I want a case, because I'd like to leave it on the stand, though I'm open to a case if it somehow doubled as a stand/cover. Are there hard-shell dust covers? Stands with hard-shell covers that aren't huge? I just have a simple stand right now. Happy to upgrade it if that's the key but I'm having a hard time finding things that will work and figured I'd ask for pointers.

Zach Bennoui reshared this.

Actuellement confrontée à un site où :
Il y a un overlay accessibilité (oui ça commence mal).
Cet overlay crée un lien « aller au contenu ».
Ce lien ne mène nulle part.
Cet overlay m’oblige à naviguer dans toutes ses options à chaque fois avec Voice Over, même quand je ne l’ouvre pas.
Les boutons à l’intérieur sont des liens.
Ils ont une icône et un label, qui sont restitués à la suite par voice over.
Bref. Arrêtez.
#a11y #AccessibilitéNumérique #WebDev

Version 4 of ETI Eloquence for NVDA 64-bit has been released. In addition to fixing indexing issues and updating parts of the documentation, the major new feature in this release is dictionary updates.
From NVDA Settings, under the Eloquence dictionaries pane, users can now choose which dictionary they want and update it directly from GitHub. These updates pull the latest daily changes rather than the official monthly releases. The available options are the IBM TTS dictionaries and the Alternative IBM TTS dictionaries.
Note: to see the Eloquence dictionaries pane, ETI Eloquence must be selected before opening the NVDA Settings dialog.
github.com/fastfinge/eloquence…
@fastfinge

Zach Bennoui reshared this.

Do you use #eloquence on the 64-bit #nvda#screenreader? If so, a new release is available, and we could use your help! You can find out more info on the release page: github.com/fastfinge/eloquence_64/releases/tag/v4#blind#accessibility#a11y

reshared this

in reply to 🇨🇦Samuel Proulx🇨🇦

Ah... well: there is a translation workflow which will pull the translatable strings out of your add-on, put them somewhere for translators to translate, and then push the locale files back into your add-on. What I'm unsure about is whether they'd accept Eloquence as an add-on in that system.

The details are here:

github.com/nvaccess/mrconfig/b…

in reply to 🇨🇦Samuel Proulx🇨🇦

Indeed. Probably easiest to have people clone the repo, pull out the translatable strings into a file using an appropriate tool (or do that yourself and commit it), compile their own translated strings file, and contribute the textual and compiled versions in a PR.

Even though you're not using the add-on template, you can probably reuse the translation-related utilities from it.

github.com/nvaccess/addonTempl…

in reply to James Scholes

@jscholes Yes, this is the way. Unfortunately I only speak one language, so I can't generate a translation, and I can't switch my NVDA to another language to test the translation. So this work is going to have to fall on someone else, I think. I'm not confident enough in myself to release code I can't really test. I make enough silly mistakes as it is, because I'm not actually good at this and just do it anyway.
in reply to 🇨🇦Samuel Proulx🇨🇦

You don't really need to test the translations themselves; string selection happens via well trodden code paths inside NVDA. As long as the files end up in the right places (which are documented), it will work.

But I agree with your wider point about the rest of it. I would start by at least making sure the code is set up in the ways I described if it isn't already, because there'll be no translation at all without those bits. And then hope someone can come along to fill in the rest.

in reply to 🇨🇦Samuel Proulx🇨🇦

Don't tell anyone, but localisation is one reason I don't like working on software for the community. Not because I don't think it's critical; obviously people should have the thing available in their language.

But the common tools are just so... hacky. They feel like they were built with an order of priorities that went developer, translator, user, when I think user and translator should be considered as far more important.

As a result, the developer experience isn't actually that great—relying on magic global state and functions as it does—and translations can end up with anglicised word ordering because the English-speaking developers and tools get in the way.

in reply to James Scholes

@jscholes The trouble is, if you make it harder for developers, people like me will never do it at all. Not because we don't care, just because we're stupid and this is a hobby. In an ideal world, translators could somehow translate the text without requiring the developer to do anything but accept a pull request. Again, not because I don't think it's worth the effort, but just because I don't want to write code I can't test.

Does anyone know an accessible work time tracking piece of software or web service? And by that I do mean really accessible, not somewhat usable with tons of unlabeled controls and such nonsense. I personally don't, so inclined to craft something on my own, but before I just wanted to make sure it doesn't already exist. #Accessibility #Work #TimeTracking #Freelance

Now the question is: did Obersturmführer #Musk feed Grok with the data he stole with DOGE? 🤔

futurism.com/artificial-intell…

#musk
This entry was edited (3 weeks ago)
in reply to Gabriele Svelto

Also, you know what's funny? AI companies are ostensibly the root of these price increases - even though their demands are clearly unrealistic and overinflated - but their costs will also go up... and they're losing boatloads of money as it is. They're already financially strained, and we can only hope that increased costs are going to drive them into the ground faster.
This entry was edited (3 weeks ago)

Over the years, the most unwelcome thing (that I could still find amusing) to discover that as reflection of their respective domestic politics there's always an extant political sentiment even if it doesn't rise to the level of actual separatism, in Acheh, Riau islands, Sumatera, Southern Thailand, Indonesian Kalimantan even Mindanao, of using Malaysia as a discourse totem, the "what if we had joined that federation instead". Unwelcome because a lot of our diplomatic border disputes in this entire southeast asian region are basically frozen and no one really wants to heat them up, and the formation of Malaysia itself has always been treated as a something suspicious post-konfrontasi, that never really went away.

ANYWAY, tropical storm senyar got us all in the end. The floods weren't bad here comparatively but now we're dragged into the Sumatera-Java psychodrama as deaths continue to mount. #tootSEA #Malaysia #Indonesia