AccessKit Node
Re-export is Confusing with Bevy's Node
#16235
Labels
A-Accessibility
A problem that prevents users with disabilities from using Bevy
C-Code-Quality
A section of code that is hard to understand or change
D-Trivial
Nice and easy! A great choice to get started with Bevy
S-Needs-Design
This issue requires design work to think about how it would best be accomplished
Milestone
Bevy version
main
/0.15 RCDescription
The
bevy_a11y
re-exports AccessKit'sNode
, but that can be confusing sincebevy_ui
also defines aNode
. Since #16234, there is now a way to use AccessKit without importingaccesskit::Node
. Now that it is optional, we should reconsider the way Bevy re-exports AccessKit. For example, only re-exportingRole
.Context
This was raised by @alice-i-cecile in this Discord message.
The text was updated successfully, but these errors were encountered: