Conversation

Notices

1. Aral Balkan (aral@mastodon.ar.al)'s status on Tuesday, 12-Mar-2024 04:41:28 JST Aral Balkan

   • Matt Campbell
   • Sonny
   • Florens Verschelde

   @nah @fvsch @sonny @matt No one is assuming bad faith on the part of the volunteers. The pressure is for the corporations who profit from GNOME. Take GNOME away tomorrow and what does Red Hat do? What does IBM do? What does Canonical do? They have millions. Can they afford to make GNOME accessible? Yes. Should they be ashamed it doesn’t have a working screen reader? Also yes.

   • Aral Balkan (aral@mastodon.ar.al)'s status on Tuesday, 12-Mar-2024 04:46:14 JST Aral Balkan

     in reply to

     • Matt Campbell
     • Sonny
     • Florens Verschelde

     @nah @fvsch @sonny @matt But here’s the thing: Wayland would never have been made the default if, say, fonts didn’t render correctly. Not having a functional screen reader is as big an issue for people who rely on screen readers. So at some point, someone at Canonical decided that it didn’t matter that people who use screen readers would be excluded. And so they should be ashamed.

     #a11y #canonical #wayland #orca #screenReaders #accessibility

   • Jeff Fortin T. (nekohayo@mastodon.social)'s status on Tuesday, 12-Mar-2024 16:11:32 JST Jeff Fortin T.

     in reply to

     • Matt Campbell
     • Sonny
     • Florens Verschelde

     @aral @nah @fvsch @sonny @matt

     Two GNOME cycles, when people are actively working on accessibility this year, is a long time.

     Before panicking, consider: a reason it's been targetted to GNOME 48 (a year from now) and not 47 is, devs are collectively aware that not everything is ready for this to happen in 47, and that it is reasonably likely that a11y would be working by 48.

     The cited link (!99) says pointblank it is a blocker.

   • Aral Balkan (aral@mastodon.ar.al)'s status on Tuesday, 12-Mar-2024 16:11:32 JST Aral Balkan

     in reply to

     • Matt Campbell
     • Sonny
     • Jeff Fortin T.
     • Florens Verschelde

     @nekohayo @nah @fvsch @sonny @matt No one is panicking. By default, the most popular Linux distributions already ship with a broken screen reader. There’s nothing to panic about because this isn’t some hypothetical about a future harm. The harm (shipping an operating system with a broken screen reader) occurred when the first Linux distribution shipped Wayland as default.

   • Aral Balkan (aral@mastodon.ar.al)'s status on Tuesday, 12-Mar-2024 16:15:08 JST Aral Balkan

     in reply to

     • Matt Campbell
     • Sonny
     • Jeff Fortin T.
     • Florens Verschelde

     @nekohayo @nah @fvsch @sonny @matt What I find disappointing is that instead of seeing this as a problem and taking steps to ensure it never happens again, I’m just seeing defensiveness that tells me that some folks still don’t understand that accessibility should be a showstopper not a nice to have. That culture needs to change. And a policy adopted so it never happens again.

   • lhp (lhp@mastodon.social)'s status on Tuesday, 12-Mar-2024 23:36:34 JST lhp

     in reply to

     • Matt Campbell
     • Sonny
     • Jeff Fortin T.
     • Florens Verschelde

     @aral @nekohayo @nah @fvsch @sonny @matt You literally were just told - multiple times - that people know the problem and care about it and that this change is not even in the next version precisely because people are aware of this and other problems. You were told there are active and funded efforts to imprve the linux accessibility stack. Isn't that exactly what you want? Your last message in this thread feels very dishonest. Maybe there is a miscommunication here?

   • Aral Balkan (aral@mastodon.ar.al)'s status on Tuesday, 12-Mar-2024 23:36:34 JST Aral Balkan

     in reply to

     • Matt Campbell
     • Sonny
     • Jeff Fortin T.
     • Florens Verschelde
     • lhp

     @lhp @nekohayo @nah @fvsch @sonny @matt Being told is one thing. Actions speak louder than words. Clearly the people who decided to make Wayland default before fixing the screen reader did not care about accessibility. It’s good that there are folks working on fixing the problem that do.

     Now go away with your “dishonest” bullshit.