Edited with a lot more resources and ways to get involved if you actually wanna get involved.
Hey non-disabled #Linux folk, sure would be fantastic if everyone pitched in on helping the blind and sighted allies making Linux more accessible to disabled users rather than warning us about the end of Windows 10, like we don't already know. Telling us something we already know doesn't help us switch to Linux because while you're lecturing us, Linux still has accessibility issues in the underlying infrastructures.
To start, Here’s a small, impactful thing you can do for now. There are bigger needs but making a fully accessible place one can research and compare distros would be a start. This website is linked to a lot. It’s inaccessible to screen magnifier users because the test is coded in such a way where elements appear behind other elements. All the links in the navigation area are empty and need labels. Making the quiz screen reader friendly by having regular web elements for questions such as radio buttons and other HTML elements without enabling an accessibility mode would be a fantastic start. https://distrochooser.de/
Here's some background on the recent state of Linux accessibility, and a project you can contribute to.
https://blogs.gnome.org/a11y/2023/10/27/a-new-accessibility-architecture-for-modern-free-desktops/
You can help the Fedora team make their KDE spin more accessible than it already is. https://fedoraproject.org/kde/
You can join their core accessibility group, https://discussion.fedoraproject.org/tag/dei-team
Learn about the state of modern Linux accessibility. Video. https://www.youtube.com/watch?v=w9psDfEFf9c
Make more repositories, wiki's, websites, like Linux Access ORG, of accessible mainstream distros and other flavors/spins. Make accessibility guides. Do what big tech does for accessibility but do it better than them.
Help contribute to sites like https://linuxaccess.org/
Gnome's accessibility breakdown... ish. It's old but still valid for most. https://blogs.gnome.org/a11y/2023/10/27/a-new-accessibility-architecture-for-modern-free-desktops/
and contribute to projects such as Access Kit. https://accesskit.dev/
Lastly, there are a ton of blind mailing lists out there for linux. Read what they have to say. Here's just one of them, this thread provides more. https://inbox.the-brannons.com/blinux/CAO2sX30cKU4i_Nsskitw5gLeYjwjswfMRphf5krmjMH1DK69Cw@mail.gmail.com/#r
@WeirdWriter I'm trying to work out where the issues are based on your edit, but I'm having some trouble.
I'm seeing labels with checkbox elements nested inside them for answers in the regular test mode (despite there also being a custom span for visual effect), for example, and the WAVE evaluator claims that these are correctly associated.
I'm also not quite sure what 'the navigation area' refers to - I thought you meant the menu on the left where you can navigate between questions, but according to Firefox's (accessibility) tree those all seem to be hyperlinks with recognized label texts.
Am I looking in the right place, or am I missing something?
@WeirdWriter From what I can tell, adaptive mode increases the contrast and font size; markup-wise, it changes the form elements so that the label is attached to the checkbox input through a for= reference, rather than nesting the checkbox inside of the label.
Both approaches should be valid and equivalent to connect the two elements, but I wonder now if some screenreaders handle these cases differently somehow.
(If I can find the time, I'll try setting up a screenreader to see what it makes of it...)
@joepie91 Im on On mobile but I would suggest NVDA
@joepie91 On both desktop and mobile screen readers, every link after the home page URL is empty. It doesn’t have labels. I would love to know what things change when someone uses the adaptive mode for the quiz. https://distrochooser.de/?vim=true