| ▲ | rat9988 16 hours ago | ||||||||||||||||
You are dismissing again the answer you are getting. Why do you think it is lacking accessibility despite using a framework claiming " GPUI Kit ships 75+ documented components and primitives, WebAssembly support, AccessKit accessibility" | |||||||||||||||||
| ▲ | d1sxeyes 14 hours ago | parent | next [-] | ||||||||||||||||
To be clear, GPUI Kit is not the same as GPUI. I am not sure if Discord is using GPUI Kit, but accessibility natively is possible with either. It's reasonable to be concerned that Discord may not have focused on accessibility while rewriting. It's less reasonable to be concerned that it may be impossible to write accessible apps using GPUI, as that is now possible (https://github.com/zed-industries/zed/blob/main/crates/gpui/...) although this is a fairly recent addition. It's also less reasonable to assume that an app made with GPUI Kit will automatically be accessible. You still need to put effort into it. | |||||||||||||||||
| |||||||||||||||||
| ▲ | ethin 8 hours ago | parent | prev [-] | ||||||||||||||||
I'm not dismissing it, just uncertain how good it is. Quality over quantity and all that. You can have 75 or 100 or 200 UI components and some can be perfectly accessible while others might not be even things accesskit supports right now. Or Accesskit may only partially support a widget. As I've said downthread, I'm hoping that Discord using a UI toolkit like this will cause upstream effects with respect to Accesskit coverage, so we'll have to see when they start migrating people over to it. | |||||||||||||||||