Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

×

+ - Ask Slashdot: How to handle unfixed Linux accessibility bugs?

Submitted by dotancohen
dotancohen (1015143) writes "It is commonly said that open source software is preferable because if you need something changed, you can change it yourself. Well, I am not an Xorg developer and I cannot maintain a separate Xorg fork. Xorg version 1.13.1 introduced a bug which breaks the "Sticky Keys" accessibility option. Thus, handicapped users who rely on the feature cannot use Xorg-based systems with the affected versions and are stuck on older software versions. Though all pre-bug Linux distros are soon scheduled for retirement, there seems to be no fix in sight. Should disabled users stick with outdated, vulnerable, and unsupported Linux distros or should we move to OS-X / Windows? The prospect of changing my OS, applications, and practices due to such an ostensibly small issue is frightening.

Note that we are not discussing "I don't like change" but rather "this unintentional change is incompatible with my physical disability". Thus this is not a case of every change breaks someone's workflow."
This discussion was created for logged-in users only, but now has been archived. No new comments can be posted.

Ask Slashdot: How to handle unfixed Linux accessibility bugs?

Comments Filter:

Who goeth a-borrowing goeth a-sorrowing. -- Thomas Tusser

Working...