upvote

points

by mort967 hours ago |
comments
upvoteby dblohm72 hours ago|
next
[-]
I'm not trying to troll here, asking seriously: are there any immediate-mode GUI APIs with good a11y?
reply
upvoteby net_7 hours ago|
prev|
[-]
I haven't worked on screen reader support, yet. Support for alternative text input is built into SDL. UI size scaling is a feature I plan on adding eventually.
reply
upvoteby doodlesdev6 hours ago|
parent|
[-]

   > I don't get why every language's community doesn't just do the same thing: roll an idiomatic UI lib on top of SDL.

   > I haven't worked on screen reader support, yet. Support for alternative text input is built into SDL. UI size scaling is a feature I plan on adding eventually.
Well, that's why :)

For most serious applications, accessibility isn't a second thought, it's a requirement and it's very hard to implement correctly.

reply
upvoteby net_6 hours ago|
parent|
[-]
So the solution is to build applications around less of a common base? I don't follow the logic, with respect to Zed. I get what you mean if there's a first-party UI solution in your language (e.g. Swift), but in that case you don't need an open-source UI library.
reply
upvoteby mort964 hours ago|
parent|
[-]
The solution, if you want a production ready GUI, is to use a GUI toolkit which already has decent accessibility support.

There aren't that many of those: .NET, AppKit/UIKit, SwiftUI, Qt, GTK, the web, wxWidgets (which is really just GTK/AppKit/.NET), probably a couple others. So you either use the native language of one of those toolkits, or you use bindings from your language to those toolkits.

reply