#Focus resource
10 messages · Page 1 of 1 (latest)
Ping @open sierra ❤️
Focus doesn't make sense to use with bevy_ui since it's only meant for keyboard focus and bevy_ui doesn't have that concept. It's meant for UIs with keyboard and gamepad focus to sync that state with the accessibility API and doesn't do anything else (I.e. it doesn't set hover state or anything.)
So I need to create my own UI plugin that lets me draw keyboard focus to UI elements?
Because if you're deafblind, like me, purely audio or visual games don't really work; I need something to interact with using my keyboard and braille display. I thought the purpose of integrating accesskit into Bevy was facilitating that?
At the moment, Bevy apps are screen reader-inaccessible with all cursor types apart from the touch cursor using JAWS, as far as I can tell.
bevy_ui is incomplete and lacks any keyboard features at the moment (no text input) so there is nothing for the accessibility API to plug in to.
Ah, got it. Is there already something in Bevy that the accessibility API can plug in to, or is that still a bit down the road at this time?
There's a minimal implementation of node labels, although it's not great
Okay. Where should I start if I want to help? I'm new to Bevy and looking at the source code of bevy::ui::widget::Label didn't really tell me much about its implementation, but I'm an experienced rustacean and very experienced when it comes to screen reader accessibility.
@open sierra had been leading that effort, although @smoky arrow has been helping too 🙂 The main thing that we need is a central design. #ui-dev is probably a better spot for this conversation though, so others can follow along