Linked by Thom Holwerda on Tue 4th Aug 2009 10:43 UTC
Permalink for comment 377166
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
More News »
Sponsored Links



Member since:
2005-07-06
It does support it and more to the point it has an accessibility framework that meets requirements on many levels. Whether it is compatible with Gnome and GTK applications is another matter, but that doesn't make it inaccessible.
Yes because CORBA is crap and some people need to pull their fingers out and get their D-Bus support up to scratch, but it's more an issue of application compatibility. It's more of an issue for AT-SPI and Gnome and their support of the various interfaces through D-Bus. The framework is there in Qt to support it. It's also nice when you have technology that allows you to magnify with a reasonable level of detail ;-). Just supporting AT-SPI doesn't mean you're accessible nor that your apps will use it.
Actually it does (the project has been around for three years), but it means that there are two separate interface systems - one over D-Bus which Qt uses and one over CORBA that Gnome uses. Naturally that makes compatibility difficult but is orthogonal to the issue of whether a desktop is 'accessible' or not.
Mind you though, talking about supposed accessibility deficiencies seems to be some sort of mental disease that people get themselves into. As I've said, accessibility matters little when you have no applications and no functionality that people want. I daresay that there are thousands of off-the-shelf and custom applications running in governments that don't use any accessibility framework whasoever even if it is there, so Gnome's accessibility support isn't helping to win customers and users there. There are a lot of barriers to overcome before getting excited about accessibility.
I don't. I care about applications. I care about a development platform that will get us those applications. I care about functionality. I care about what open source desktops do with respect to competing with Windows and OS X and getting there. The current status quo we have with 'enterprise' Linux desktop distributions has totally and utterly failed to address those issues, and as such, no one uses them and no one cares. Trying to box yourself into a niche with accessibility and regulations as cover for falling totally flat in other areas is just a bit.......sad.
Whether they're of any use to you is neither here nor there. If you don't have the features and applications then no one uses you regardless. That's what counts. It's become pretty clear that we've got total stagnation on that front. Expect the situation to get ever worse.
I'd advise you to do likewise. There is a bundle of reasons why I prefer one over the other, and it doesn't come down to blind faith and desperation when they fall short.