Re:Blender 4.0
by robin_reala on Tuesday November 14, 2023 @09:37AM
(#38263774)
There’s so much more than that though. You need to build your own accessibility tree and hooks into the OS’s assistive tech infrastructure just for a start.
[ Parent
| on HN ]
Re:Blender 4.0
by doubled112 on Tuesday November 14, 2023 @09:45AM
(#38263860)
Is Blender accessible this way? Or is it, as they said, just an OpenGL surface with some widgets painted on?
My apologies for the word "just" doing a lot of work in that sentence.
https://devtalk.blender.org/t/blender-and-accessibility-for-...
> As a multi platform OpenGL app everything we draw is quite hidden from screen readers. Without cross-platform open source libraries available I can’t think of a feasible way of interacting with existing screen readers.
https://blender.stackexchange.com/questions/301899/blender-a...
Re:Blender 4.0
by dumbo-octopus on Tuesday November 14, 2023 @09:46AM
(#38263878)
Or you can just not do that, which is what Blender does.
To be fair, there's not all that much use in Blender for folks who cannot see a screen clearly.
Re:Blender 4.0
by robin_reala on Tuesday November 14, 2023 @09:52AM
(#38263943)
Assistive tech isn’t just screen readers. But yeah, Blender specifically is a visual design tool, I’ll give you that.
Re:Blender 4.0
by yjftsjthsd-h on Tuesday November 14, 2023 @10:27AM
(#38264418)
I know it's not just screen readers, but what a11y concerns would make sense for blender? It barely uses audio and what it does probably can be covered by external tooling. For visuals... the only things that occur are probably covered by Blender's UI scaling/zoom. But I could easily be forgetting something or ignorant.
Edit: Oops, somehow forgot input - but there again, I would natively expect most things to work via keyboard/mouse emulation, and beyond that you'd probably need custom integration, but it's got the Python hooks to facilitate that.
Re:Blender 4.0
by dumbo-octopus on Tuesday November 14, 2023 @10:37AM
(#38264576)
What comes to mind is someone with a tremor that is unable to use classic pointing devices and might have better luck using tab/arrow-key navigation to move through the buttons/menus/etc. From my cursory examination of the product I don't see much support for keyboard navigation, though as a professional tool I'm sure there's a plethora of keyboard shortcuts that one could learn.
Re:Blender 4.0
by yjftsjthsd-h on Tuesday November 14, 2023 @11:08AM
(#38265080)
Good point, I'd never noticed that before - menus seem fine once you get them open, but I can't find a way to open any menu without clicking, and ex. the preferences pane does seem completely impossible to navigate via keyboard. So yes, I agree that that appears a downside to their own toolkit.
Though I think all/pretty much all menu items can be accessed by pressing space and then typing the name of it. (If you use the setting space for command search.) There will be an auto completion list and it remembers the last action. So that is even better than what many other GUI applications do, where you have to search for ages in deeply nested menus for the action that you know how it is named, but don't know where the hell it is hidden. Quite frankly every program should have that feature.
Re:Blender 4.0
by dumbo-octopus on Tuesday November 14, 2023 @11:20AM
(#38265307)
FWIW you need to implement that yourself with basically any advanced enough toolkit. Even in HTML-land, any list widget worth it's salt is handling keystrokes itself.