Accessibility assertions, and note where they do and do not reach.
ctx.enable_accesskit() makes role, label, disabled, hidden, toggle state
and numeric value directly assertable, and tab-order tests are the
cheapest real accessibility guarantee available — press Tab, assert
focus lands where it should, including wraparound. But AccessKit has no
web adapter; it is listed as planned. So this is a native-build
guarantee that we rely on to keep the web build honest by construction,
not something assertable in-page. Worth knowing before someone promises
screen-reader support on the web.
Checked against main @ faec848. Context: accesskit and web_screen_reader are deliberately switched off in crates/gridwright-studio/Cargo.toml, with a comment saying why — nothing a screen reader can use exists behind a canvas of painted shapes yet, and turning them on would claim a story the studio does not have. Tracked as work, not as a decision against it.
Source: TODO.md line 2977 — Interface › Testing the interface
Accessibility assertions, and note where they do and do not reach.
ctx.enable_accesskit()makes role, label, disabled, hidden, toggle stateand numeric value directly assertable, and tab-order tests are the
cheapest real accessibility guarantee available — press
Tab, assertfocus lands where it should, including wraparound. But AccessKit has no
web adapter; it is listed as planned. So this is a native-build
guarantee that we rely on to keep the web build honest by construction,
not something assertable in-page. Worth knowing before someone promises
screen-reader support on the web.
Checked against
main@faec848. Context:accesskitandweb_screen_readerare deliberately switched off incrates/gridwright-studio/Cargo.toml, with a comment saying why — nothing a screen reader can use exists behind a canvas of painted shapes yet, and turning them on would claim a story the studio does not have. Tracked as work, not as a decision against it.Source:
TODO.mdline 2977 — Interface › Testing the interface