5 ms·

Looks great for those using Rust - however I do wonder how well this works, if at all, under screen readers and other accessible tech?

• Oxodao 11mo ago
  my #1 question each time I see a new UI framework
  • jacquesm 11mo ago
    "Let's get the volume first, then worry about accessibility" That's the typical answer to these questions. Unfortunately, unless you bake it in from day #1 that's not so simple to fix afterwards.
    • wiz21c 11mo ago
      at least I think egui has worked on that aspect...
    • anthony-eid 11mo ago
      Accessibility is apart of gpui roadmap.
      • pseudalopex 11mo ago
        > Unfortunately, unless you bake it in from day #1 that's not so simple to fix afterwards.
• jeroenhd 11mo ago
  Haven't tried running the code myself, but their API docs mention accessibility at least: https://longbridge.github.io/gpui-component/docs/components/list#accessibility https://longbridge.github.io/gpui-component/docs/components/... Assuming the docs are correct, the UI controls seem ARIA compliant as long as you bother implementing the necessary descriptions and labels.
• andrewl-hn 11mo ago
  Zed Editor (built on top of GPUI) is opaque to screen readers, so I wouldn't have high hopes.