Repository navigation
Pin the experiment's tab order and focus outlines - #41
Merged
Merged
Conversation
The browser harness checked focus behavior after actions but not the initial keyboard path or the visible focus indicator. Walk ten Tab stops, assert the expected controls and require a solid 2px outline on each. Add a backward Tab assertion inside the inspector dialog.
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
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.
Follow-up to #37: the browser harness verified focus after actions but not the initial keyboard path or the visible focus indicator.
What changed
solid 2pxoutline on every stop.CONTRIBUTING.mdanddocs/EXPERIMENT.md.Verification
npm run test:browser— exit 0 in Chrome 157; tab order and outlines passnpm run check— exit 0, 145 unit tests, 5 integration tests, package and bundle checksBoundary
This is a DOM regression check, not a screen-reader or manual visual review. Issue #16 remains open for a named screen reader and outside report.