Skip to main content


So @gnome is removing the x11 session, leaving just the Wayland one.

If this goes out before Orca, the GNOME screen reader, is fixed to work on Wayland, it will mean that people who rely on screen readers will have no way to use one on GNOME. And thus on the major Linux distributions.

So I’m hoping the plan is that this change will not land until GNOME has a working screen reader.

#accessibility #a11y #gnome #linux #openSource #foss #wayland #x11 #orca peoplemaking.games/@ailepet/11…

in reply to Aral Balkan

GNOME folks are well aware of the problems with Orca on Wayland, and actively working to fix them. There's even funding for this work, thanks to the Sovereign Tech Fund. I'm personally working on a new Wayland-native accessibility stack that aims to eventually replace AT-SPI and support sandboxed apps, but there are also efforts to fix problems in the existing stack in the short term. cc @sonny

Marco Zehe reshared this.

in reply to Matt Campbell

@matt @sonny That’s great. So will the x11 session not be removed until this work is done and there is a functional screen reader for Wayland then?
in reply to Aral Balkan

Well, I don't know if you've read that MR, but it's targeting GNOME 48, which leaves plenty of time to fix the accessibility issues.
in reply to Aral Balkan

It's the default because it's already quite functional, except for the problems you point out. Additionally, if you increase the number of users on Wayland, it is easier to identify problems and fix them. If it weren't the default, who even knows how long it would have taken us to identify that there were problems with Orca
in reply to Naiara -> naipotato@transfem.social

@nah @matt @sonny If the GNOME folks didn’t realise that Orca was broken before making Wayland the default that’s even worse. It would mean no one on the GNOME team is testing accessibility. If they knew and made it the default anyway, it just shows that accessibility is seen as not essential. So I’m actually not sure which is worse. And we can’t go back in time so hopefully lessons will be learned and this will remedied as soon as possible.
in reply to Aral Balkan

Ok, but I remind you that GNOME is not a company, it is a project created by a lot of volunteers. Everyone works on what they want/can, the idea is precisely that there are people who test Wayland and come to help and fix the problems

I think we all agree that accessibility is important, and we all want to create software that is inclusive enough for everyone... but we must also come down to reality, where as long as the problem can be worked around, a lot of ppl think that nothing needs to be fixed

Removing the possibility of workarounding and shoving problems in your face is a strategy to attract volunteers to help improve the software

Finally: public appeals where bad faith is assumed and the project is criticized as if it were a company with a team of full-time developers is a strategy to reduce people's motivation to work on things. You don't need to shit on GNOME for things to be fixed, but on the contrary, the strategy is to show up with proposals and willingness to improve the situation

in reply to Matt Campbell

Usable screen reader on Wayland is a hard requirement for dropping the X11 session. See gitlab.gnome.org/GNOME/gnome-s…

We are working on it.

This entry was edited (2 months ago)
in reply to Naiara -> naipotato@transfem.social

@nah @sonny @matt Accessibility is a human right. Drastic regressions to the accessibility of a system that disabled users rely on are a human right violation.

We can cut a lot of slack to volunteer contributors, but not “human right violations are permissible” amounts of slack.

Ultimately, it’s the responsibility of the project’s leadership (volunteer or not) to set norms like “we can only accept your contributions if they’re accessible”.

in reply to Florens Verschelde

@nah @sonny @matt As a norm, that’s not particularly new in open-source. I’ve contributed to several projects who only accept contributions that 1) align with project goals, 2) pass peer review and 3) pass multiple test suites.

That can definitely be a barrier to contribution. But there are also smaller hobbyist-focused toy projects with lax norms that people can contribute to, if strict norms are a deal-breaker.

in reply to Florens Verschelde

Privacy and security are equally important; however, people's solution here is for us to continue using X11 by default until the alternative is "perfect" and we can switch to it.

The change to Wayland is huge, and requires many improvements across multiple projects (many of which don't even belong to GNOME as such), so it's not exactly trivial. We need more people working on this, and therefore we need to raise the interest of potential contributors to iron out all the remaining rough edges.

As I said in a previous post: until Ubuntu put Wayland by default, many people were not even willing to work with Wayland. It's important to understand this: the world of free software moves by motivation. If you're a software user, and you have a problem with said software that you can work around... how much motivation do you have to improve said software? You'll probably continue working around the problem until you can't do it anymore, and only then you'll contribute to solving the problem once and for all.

Right now, the workaround is to continue in X11, even despite the security and privacy problems that this implies. Many people don't realize how insecure X11 is, and they minimize these problems. GNOME is aware of this, and made Wayland the default several versions ago, also because Wayland was already usable for many users. X11 was still available as a fallback in case Wayland wasn't ready for you yet.

The proposal now is to eliminate X11 once and for all, and to do so a goal has been set: GNOME 48 (which will not be released until March 2025). Blocking issues for this also began to be collected, the current state of Orca being one of them (see Sonny's post), and this has been 4 months now.

I must highlight that accessibility is a fundamental pillar within the development of GNOME, we seek to create a desktop that can be usable and accessible by everyone, without discrimination. However, I must also highlight that there are many more aspects to take into account in order to achieve this. It's not as simple as it seems to be, and at GNOME we always seek to achieve the best solution. Assuming bad faith and criticizing the project as openly as Aral does is not productive. Perhaps putting pressure will work in contexts such as governments or companies, but not in free software.


Usable screen reader on Wayland is a hard requirement for dropping the X11 session. See gitlab.gnome.org/GNOME/gnome-s…

We are working on it.


in reply to Naiara -> naipotato@transfem.social

@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.
in reply to Aral Balkan

@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

in reply to Aral Balkan

@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.

in reply to Jeff Fortin T.

@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.
in reply to Aral Balkan

@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.
in reply to Aral Balkan

@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?
in reply to 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.

in reply to Aral Balkan

If you're going to keep repeating your "righteous" indignation, misplaced IMO, please at least remove Sonny from the thread, as I tried to do (after adding him). He's already doing everything he can. The past can't be changed, and I think there's no use belaboring it.
in reply to Aral Balkan

No one is assuming bad faith on the part of the volunteers. The pressure is for the corporations who profit from GNOME.


When you talk about GNOME, you're talking about the entire project and all its contributors, not just the companies that benefit from it. Keep that in mind: public attacks can reduce the motivation of contributors (as has happened many times before)

in reply to Naiara -> naipotato@transfem.social

@nah @fvsch @sonny @matt I’m going to leave it at this: If I ran a large corporation that benefited from GNOME but didn’t want to support it financially or pay for it to be accessible, etc., I’d want any criticism of it to be seen as criticism of the poor, unpaid volunteers. It’s a great way for corporations to avoid criticism.
in reply to Aral Balkan

And I'll put it this way: if I work on a free software project for the benefit of the entire community, without earning anything from it, purely in my free time... and then someone decides to post criticizing the project from above to down about problems that I know and that both I and colleagues on the same project try to solve, without even helping... I really don't think it feels good to me.

I understand your point, but you also understand mine. If you want to attack companies, mention them directly, or criticize their products (for example, Ubuntu or RHEL). Attacking GNOME is useless in that case.

in reply to Naiara -> naipotato@transfem.social

@nah @sonny @matt I am personally extremely critical of this framing of the GNOME Project as having no responsibility and no accountability, on the basis of most of the work being done by volunteers. This does not fly for other NGOs, and should not be used as an argument here.

Maybe time for the GNOME Foundation board and team to step up and set some clear norms and expectations for digital accessibility, if they have not done so until now?

in reply to Florens Verschelde

@fvsch @nah @matt

I'm not sure why we keep arguing, I already explained that usable screen reader is a hard requirement for dropping the x11 session.

With that said I agree and we are working on it. The GNOME Foundation will need the means to its ambition so I hope we can count on your support then.

in reply to Sonny

@sonny @nah @matt It’s great to have your word that it’s a blocker, but that’s not correctly reflected in the MR you linked to (gitlab.gnome.org/GNOME/gnome-s…).

- The MR's metadata does not show it as blocked by another issue or MR, as far as I can tell?
- The comment you linked to says “potential blocker”, and the only response says it’s acceptable as a blocker *provided someone else commits to doing the work*. That is *not* a “hard requirement”, and probably requires an update.

in reply to Florens Verschelde

@fvsch @nah @sonny @matt How did we even get to this conversation? Gnome is not dropping x11 any time soon and there are no regressions. Gnome activily works towards accessibility and even has freeze breaks to correct accessibility regressions. Stop jumping the gun. :welp:
in reply to Myles Petersen

@Myles124 @nah @sonny @matt Well, you can read up in this conversation to find arguments stating that it’s regrettable if there are accessibility regressions but so is the life of this volunteer-led project.

I’ve argued against those arguments, and am happy that GNOME leadership also disagrees with those arguments. I’m hoping this also translates to written requirements and norms, both in this specific merge request and in the GNOME Foundation and Project's guidelines.

in reply to Florens Verschelde

@Myles124 @nah @sonny @matt Personally, I’m wondering about the GNOME Foundation and Project's norms for accessibility. I’m reading developer.gnome.org/hig/guidel… but that’s mostly guidance about improving an app’s accessibility, not stating norms that the GNOME Project must follow or strict requirements.
in reply to Florens Verschelde

@Myles124 @nah @sonny @matt Messaging from people involved in GNOME here and in the linked merge request has been mixed:

1. The MR author proposed blocking on this accessibility issue.
2. A reviewer replied that blocking on this issue is acceptable *provided someone else works on it*.
3. One contributor argued that accessibility is important but should not be treated as a strict requirement.
4. A GNOME Foundation director said it is a strict requirement.

in reply to Florens Verschelde

@Myles124 @nah @sonny @matt I’m glad that “strict requirement” is the word from the highest ranking person here. And to close this loop, given that there is a variety of expressed opinions from contributors, I’d love to see written documentation on:

- Who has the authority to make this call (especially since the GNOME website says that technical decisions are not managed by the Foundation)?
- What accessibility norms apply to GNOME releases.
- How those norms are applied.