Search

Items tagged with: A11Y



The Orbit Player starts shipping July 21!
Order now first batch quantity are limited.
You can place your order online here:
orbitresearch.com/product/orbi…
Or call us at 888-606-7248 to order by phone.
#A11y #BrailleForAll #Inclusion #OrbitReaderQ20 #OrbitReaderQ40 #OrbitSpeak #OrbitSpeakPlus #OrbitPlayer



Can anyone recommend a modern body weight scale that is accessible, either via self-voicing, or bluetooth connection? If via self-voicing, anything that doesn't shout the measured weight so loud, that anyone within 500 feet can hear it? Anyone who has used these products in the past will most certainly be aware that the "blind equals deaf" stereotype that is clearly pervasive in the overwhelming majority of these products. I'm hoping there is something out there that does not make this assumption, and has a volume adjustment beyond mute and yell.
Thank you in advance for your suggestions.
#Body #Weight #Scale #health #blind #accessible #accessibility #A11Y #BlindDoesNotEqualDeaf


Donner votre avis pour faire progresser l’accessibilité numérique, ça vous tente ? 💬

Si vous êtes en situation de handicap, rejoignez notre panel de testeurs et testeuses !

En quoi ça consiste ? Vous allez sur un site web, vous naviguez dessus, vous nous dites ce que vous avez pensé.

Lors d'un échange individuel ou d'un atelier collectif, selon vos envies et disponibilités.

Vous recevez un bon d'achat d’au moins 20 € pour chaque activité réalisée.

a42.fr/volontaire

#a11y #handicap


Due to popular demand, our special offers for #NFB25 and #ACB2025 have been extended through July 20! Don’t miss your chance to grab amazing deals on Orbit’s Braille and other devices. orbitresearch.com/special-offe…
#A11y #BrailleForAll #OrbitSpeak #OrbitPlayer#OrbitReaderQ20#OrbitReaderQ40#Inclusion#OrbitSpeakPlus




"Leclerc, Carrefour, Auchan et Picard mis en demeure par des associations d'aveugles et de malvoyants pour leur sites"

"Contactées par France Inter, seules les enseignes Carrefour et Picard ont répondu à nos sollicitations. Carrefour se dit étonné de cette mise en demeure et déclare que son site marchand atteint un taux d’accessibilité de 71%. Le spécialiste des surgelés Picard revendique lui un niveau de 56%. Les deux entreprises affirment avoir engagé un plan d’amélioration sur plusieurs années."


Non mais alors là, pardon mais 🤣

Le seul taux attendu c'est 100%, en deça, ça ne signifie rien en tant que tel. On peut avoir 90% de conformité au RGAA et avoir un problème bloquant. Donc y'a pas à se vanter d'un taux sous 100%.

Ces entreprises sont au courant du problème depuis longtemps, c'est pas la découverte. On va pas pouvoir dire qu'elles ont un problème de moyen financier. Alors on arrête de se trouver des excuses hein.

#accessibilité #a11y #RGAA #validisme

radiofrance.fr/franceinter/pod…


Dear #disabled #gamers, for an introduction on #accessibility in #games I am looking for recent accessibility fails in games, especially AAA or otherwise famous games. If you are comfortable with me sharing your anecdotes on a talk (anonymized if you wish), let me know your stories. Which game do you wish to play but can't? Which studio promised a11y features but let you down in some way? #a11y


Hey everyone, #Linux Access appears to be live! This is a really fantastic resource for beginning Blind Linux users! linuxaccess.org/ #Accessibility #A11y


The overlay shill is not just a shill, but an overlay vendor itself.

It may have failed to disclose that when asking for, and engaging in, a “balanced” and “open” debate about overlays on LinkedIn.

Overlay vendors continue to be ethically dubious (at best).

#overlay #accessibility #a11y


What the fuck is it with #overlay companies and their apologists commenting on my blog?

I got two today (on the same post):
adrianroselli.com/2025/01/ftc-…

They are promoting their water-carrying shill-piece over on LinkedIn.

#accessibility #a11y


@Delta Chat Please stay awesome and original with your exclusive features and thanks for embracing #screenreader #a11y almost from the begining.





#a11y





We are excited to be a part of #NFB25 next week and to announce our new partnership with @nationsblind!

First time members can join Bookshare for 30% off our annual membership, and existing members can renew for 20% off. You can sign up and renew at our booth D14. See you at the convention next week!

#A11y #NFB #VI #Accessibility


I love this so much. It's pretty much a GUI for #tampermonkey, offering an easier way for #blind folks to find elements on a webpage and do things to them. Yes, you could do the same things directly by just writing JavaScript yourself. But this is much, much faster, and requires a bit less knowledge. It took me less than 30 seconds to turn all the story titles on fanfiction.net into headings. Labeling a button, or making other small changes would be just as fast. The typos and slightly incorrect English put me off at first; especially the word "blinds" for blind people felt weird and derogatory. apparently the author is from #Cameroon, though, so maybe that's standard there. stsolution2.org/WebAccessibilizer/#a11y#accessibility#screenreader




Continuing our volunteer effort to make GNOME Calendar fully accessible with a keyboard (see thread for context), we fixed a major bug that was causing the focus to disappear into the abyss when the user tried to tab into the month view in merge request !576. This means, as of this commit, events should now be completely functional and accessible within the month view. Additionally, the merge request changes the keyboard and focus behavior within the month view: Events can only be cycled using arrow buttons, the focus can't escape the month view with arrow buttons, and entering/exiting the month view can only be done with tab. These improvements will be available on GNOME 49.

#GNOME #Accessibility #a11y #GNOMECalendar #Calendar #FOSS #FreeSoftware #Linux


Happy Disability Pride Month everybody :)

During the past few weeks, there's been an overwhelming amount of progress with accessibility on GNOME Calendar:

Event widgets/popovers will convey to screen readers that they are toggle buttons. They will also convey of their states (whether they're pressed or not) and that they have a popover.

Calendar rows will convey to screen readers that they are check boxes, along with their states (whether they're checked or not). Additionally, they will no longer require a second press of a tab to get to the next row; one tab will be sufficient.

Month and year spin buttons are now capable of being interacted with using arrow up/down buttons. They will also convey to screen readers that they are spin buttons, along with their properties (current, minimum, and maximum values). The month spin button will also wrap, where going back a month from January will jump to December, and going to the next month from December will jump to January.

Events in the agenda view will convey to screen readers of their respective titles and descriptions.

Accessibility on Calendar has progressed to the point where I believe it's safe to say that, as of GNOME 49, Calendar will be usable exclusively with a keyboard, without significant usability friction!

There's still a lot of work to be done in regards to screen readers, for example conveying time appropriately and event descriptions. But really, just 6 months ago, we went from having absolutely no idea where to even begin with accessibility in Calendar — which has been an ongoing issue for literally a decade — to having something workable exclusively with a keyboard and screen reader! :3

Huge thanks to @nekohayo for coordinating the accessibility initiative, especially with keeping the accessibility meta issue updated; Georges Stavracas for single-handedly maintaining GNOME Calendar and reviewing all my merge requests; and @tyrylu for sharing feedback in regards to usability.

All my work so far has been unpaid and voluntary; hundreds of hours were put into developing and testing all the accessibility-related merge requests. I would really appreciate if you could spare a little bit of money to support my work, thank you 🩷

ko-fi.com/theevilskeleton
github.com/sponsors/TheEvilSke…

#Accessibility #a11y #DisabilityPrideMonth #GNOME #GNOMECalendar #GTK #GTK4 #Libadwaita #FreeSoftware #FOSS #OpenSource


Serious #accessibility question:

If I want to mark positive and negative outcomes in color, the "obvious" choice is of course to do that in green and red and have some form of textual fallback.

Now, Im of couse not getting rid of that fallback, but since there is usually a reason to mark things in color (it's much more obvious if you can see it!), so it would be nice to have a combination that is accessible to at least more people (nothing will work for everyone, it's about reaching 95% or 99%[1]), while still being intuitive for everyone else.

I've played around with green and orange before (yellow doesn't work, because it is super bright and I want to support both light and dark mode.)

Anyone any good ideas?

#a11y


Does the feature meet the standards for #accessibility? Is the documentation complete? No? THEN DON’T RELEASE THE FEATURE. Make these things release blockers, it’s literally that simple.

#linux #a11y


Disabled people and allies: We want accessibility in our software!

Developers: It's too hard, too expensive, *whine* (repeat for decades)

Most people I know: We don't want AI in our software!

Developers: We've gone to record lengths to shove AI into everything in less than a year. #a11y #Accessibility #AISucks


#a11y


Gestern mal Signal auf dem Desktop aufgemacht. Konnte mit NVDA nichts lesen und habs dann irgendwie geschafft, dass nicht mal mehr das Menü mit alt aufgeht. Es gab Zeiten, da konnte ich wenigstens meine Chats darüber lesen und beantworten. Dann eben kein Signal mehr für mich. #Signal #A11Y #DisabledAlltag #ScreenReader


#Linux #a11y question with a long self-indulgent preamble: I have been using #emacspeak in the #terminal on #MacOS as my “daily driver” for all writing/notetaking/ #orgmode scheduling/todo organizing for about a month now. I am super in love with it, transformational for this low-vision writer/teacher/editor/producer. (1/8)


interesting story: Today, while discussing VoiceOver commands with a colleague, I kept referring to it as "VoiceOver" (or "VO") + command. This royally confused them, coming from a non-accessibility background: They were not sure if the entire time I just meant for them to press that key while VoiceOver is running. This is an interesting nuance and something that's a holdover for me from the professional #A11Y industry, but clearly, we should nudge more articles to not reference the name of the screen reader but either use the word "modifier" or "SR-modifier" (with clear explanations to the meaning if documentation) or something that won't repeat the name with ambiguity.
#a11y




Question for Android users who use or used Samsung. What is the navigation gesture to go back? While talkback is on? I don't mean the three buttons that are the alternative, but the gestures that are by default, I think. I was asked. I'd be grateful if someone could answer this one. Thank you. #Android #A11Y #Talkback #Samsung