3 ms·

> trying to devalue their work by calling it games and toys. I'm sorry; that's not what I meant to do. I only meant that I know it's not reasonable to expect d

> trying to devalue their work by calling it games and toys. I'm sorry; that's not what I meant to do. I only meant that I know it's not reasonable to expect developers of games and other software that's just for fun to go out of their way to implement accessibility. But for any software that might be used in a job, for education, for interacting with a company or government agency, or even for communication in general, accessibility is really important. I know a blind guy who almost lost his job because he couldn't use a specific piece of inaccessible software; he only kept his job because the company found something entirely different for him to do. And yes, a lot of important software is not accessible. We need to change that. About AT-SPI and D-Bus, could you implement AT-SPI support as a plugin, so it's there for those who need it but doesn't add D-BUS as a hard dependency? That's what Qt does.

badsectoracula 9y ago
Oh i see, sorry about the misunderstanding then. > About AT-SPI and D-Bus, could you implement AT-SPI support as a plugin, so it's there for those who need it but doesn't add D-BUS as a hard dependency? That's what Qt does. I'll need to look into it, if i go into that route i'll most likely make it an optional build-time feature that is enabled by default if the relevant header files are found and try to load it dynamically instead of making it a plugin (the toolkit can be compiled as a static library to create self-contained executables). This is also what i'm doing with OpenGL support that may not always exist - the toolkit and application work, it just disables the OpenGL stuff. But this is something i'll check in the future, at the moment the toolkit is barely usable even by people with perfect sight :-P.
- mwcampbell 9y ago
  Sounds like a good solution. Thanks for taking the initiative to look into this already!

badsectoracula 9y ago

Oh i see, sorry about the misunderstanding then. > About AT-SPI and D-Bus, could you implement AT-SPI support as a plugin, so it's there for those who need it but doesn't add D-BUS as a hard dependency? That's what Qt does. I'll need to look into it, if i go into that route i'll most likely make it an optional build-time feature that is enabled by default if the relevant header files are found and try to load it dynamically instead of making it a plugin (the toolkit can be compiled as a static library to create self-contained executables). This is also what i'm doing with OpenGL support that may not always exist - the toolkit and application work, it just disables the OpenGL stuff. But this is something i'll check in the future, at the moment the toolkit is barely usable even by people with perfect sight :-P.

mwcampbell 9y ago
Sounds like a good solution. Thanks for taking the initiative to look into this already!