Skip to main content


Here's a neat exploration of the curb cut effect for accessibility in @gnome - using accessibility tools to aid in testing automation! Has pros and cons identified in the article, but interesting nonetheless.

➡️ https://fedoramagazine.org/automation-through-accessibility/

#Fedora #Gnome #accessibility #a11y #Linux #OpenSource

in reply to Fedora Project (F40 is OUT)

@chernosktrainstation This is great but can we also talk about how Fedora ships with a broken screen reader by default?

#Fedora #Gnome #accessibility #a11y #Linux #OpenSource #wayland

This entry was edited (2 weeks ago)
in reply to JWF :fedora: :redhat:

1. Install Fedora.
2. Turn on the screen reader.
3. Attempt to control it using the keyboard.
This entry was edited (2 weeks ago)
in reply to Aral Balkan

@aral @chernosktrainstation I'm chatting with the Fedora A11y working group about it. It comes as a bit of a surprise because there is a lot of enablement work happening around accessibility. The FOSDEM demo I linked previously showed Orca either working out of the box or not working on different desktop environments of Fedora. Fedora Workstation was a working environment in the demo.

Going to keep digging into this. The toots have been shared with the right folks.

in reply to JWF :fedora: :redhat:

@jwf @chernosktrainstation Thank you. There’s is work underway in GNOME currently that will hopefully eventually fix this. But hopefully there will be an internal review and a policy enacted so that whatever resulted in the decision to ship Fedora with Wayland by default with a broken screen reader can be avoided in the future. Appreciate your help :)