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

There is yet another accessibility overlay vendor out there, though it makes no conformance guarantees. Nor security or privacy guarantees.

“#ARTY Could Get You Sued”
adrianroselli.com/2025/07/arty…

#accessibility #a11y #overlay

#ARTY Could Get You Sued

I can’t actually assert the ARTY overlay will result in a lawsuit, though there is a trend of overlays attracting lawsuits. Attorneys say overlays don’t protect from lawsuits, either.

^{Adrian Roselli}

Have you tried RIM? It's an accessible way to get technical support remotely. It's somewhat similar to JAWS tandem and NVDA remote, but has more features... It's currently free until July 18th, so if you've been wanting to try it out, now is the time!

pneumasolutions.com/from-now-t…

#Accessibility #A11y

"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…

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

Des associations s'attaquent à plusieurs enseignes de grande distribution, car leurs sites internet et leurs applications ne sont pas suffisamment accessibles aux personnes aveugles et malvoyantes.

^{Alice Kachaner (France Inter)}

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

FTC Catches up to #accessiBe

From the FTC on Friday: The Federal Trade Commission will require software provider accessiBe to pay $1 million to settle allegations that it misrepresented the ability of its AI-powered web accessibility tool to make any website compliant with the W…

^{Adrian Roselli}

Yeah, I had planned not to write any more of these since I had already gone after the big players. But this one poked me.

“#Accesstive Will Get You Sued”
adrianroselli.com/2025/07/acce…

#overlay #accessibility #a11y

#Accesstive Will Get You Sued

I can’t actually assert the Accesstive overlay will result in a lawsuit, though there is a trend of overlays attracting lawsuits. Attorneys say overlays don’t protect from lawsuits, either.

^{Adrian Roselli}

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

“Check / Uncheck all in a Table”
adrianroselli.com/2025/07/chec…

TL;DR: Unless you have user testing results saying otherwise, maybe put a check-all checkbox outside the table.

The rest of this thread has video examples…

[1/4]

#UX #HTML #accessibility #a11y

Check / Uncheck all in a Table

^{Adrian Roselli}

Interview with Lola Odelola @lolaodelola

"Lola Odelola is a force to be reckoned with. Which is why TetraLogical are delighted to sponsor her work on the W3C Technical Architecture Group (TAG)"

#ARIA #AT #a11y #WebStandards

tetralogical.com/blog/2025/07/…

Interview with Lola Odelola - TetraLogical

Lola Odelola is a force to be reckoned with. Which is why TetraLogical are delighted to sponsor her work on the W3C Technical Architecture Group (TAG).

^TetraLogical

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

Improve accessibility with event widgets in the month view (!576) · Merge requests · GNOME / gnome-calendar · GitLab

Calendar application for GNOME

^GitLab

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

Sponsor @TheEvilSkeleton on GitHub Sponsors

Support TheEvilSkeleton's open source work

^GitHub

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