Skip to content

fix: make frame controls keyboard-safe - #43

Open
ddebowczyk wants to merge 12 commits into
Jeshwin:mainfrom
ddebowczyk:fix/keyboard-control-semantics
Open

fix: make frame controls keyboard-safe#43
ddebowczyk wants to merge 12 commits into
Jeshwin:mainfrom
ddebowczyk:fix/keyboard-control-semantics

Conversation

@ddebowczyk

Copy link
Copy Markdown

Summary

  • make tab selection work through normal keyboard button activation
  • give compact controls accessible labels and expanded state
  • default Layman buttons to type=button so host forms do not submit
  • remove internal DOM IDs that could duplicate across views
  • cover focus, compact controls, reduced motion, form safety, and multi-view IDs

Verification

  • npm test
  • npm run lint
  • npm run build:lib
  • npm run typecheck:consumer
  • npm run typecheck:tauri-example
  • npm run check:package
  • npm pack --dry-run
  • markdownlint README.md docs/**/*.md
  • yq . .github/workflows/ci.yml
  • ast-grep outline on changed files
  • git diff --check

Follow-up to the controlled-view hardening stack; merge after PR #42.

@ddebowczyk
ddebowczyk force-pushed the fix/keyboard-control-semantics branch 2 times, most recently from 38aa937 to 05cc009 Compare August 12, 2026 13:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant