Group AccessKit nodes by Ui
#7386
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
0f9886d to
c1d8d10
Compare
…it-nodes-by-ui # Conflicts: # crates/egui/src/context.rs # crates/egui_demo_app/src/accessibility_inspector.rs
…it-nodes-by-ui # Conflicts: # crates/egui_demo_app/src/accessibility_inspector.rs
|
Preview available at https://egui-pr-preview.github.io/pr/7386-lucasgroup-accesskit-nodes-by-ui |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This changes egui to create an AccessKit node for each
Ui. I'm not sure if this alone will directly improve accessibility, but it should make it easier to create the correct parent / child relations (e.g. grouping menus as children of menu buttons).Instead of having a global stack of parent ids, they are now passed via a parent_id field in
UiBuilder.If having all these
GenericContainernodes somehow is bad for accessibility, the PR could also be changed to only create nodes if there is actually some accessibility info with it (the relevant is currently commented-out in the PR). But I think screen readers should just ignore these nodes, so it should be fine? We could also use this as motivation to git red of some unnecessary wrappedUis, e.g. CentralPanel creates 3 Uis when 2 should be enough (the initial Ui and a Frame, maybe we could even only show theFrameif we can give it an UiBuilder and somehow show the Frame withUi::new).Here is a screenshot from the accessibility inspector (#7368) with this PR:
Without this PR:
Screen.Recording.2025-07-24.at.12.12.34.mov