stackchain/stackchain-dashboard
1
0
Fork 0
Code Issues 9 Pull Requests 1 Actions Packages Projects Releases 713 Wiki Activity

Contain focus and background interaction in mobile Device Setup #1134

New Issue
Closed
opened 2026-08-19 14:23:56 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-19 14:23:56 +00:00
Member
Copy Link

Problem

Mobile Device Setup is declared aria-modal=true, but opening it leaves the dashboard behind it keyboard- and assistive-technology-reachable. Tab can escape the sheet, background controls remain interactive, and closing does not restore focus to the launcher. This breaks the phone-readiness flow for keyboard, switch-control, and screen-reader operators.

User flow

  1. Open Device Setup from the app menu.
  2. While open, Tab and Shift+Tab cycle only through visible setup controls.
  3. The application shell behind the sheet is inert until setup closes.
  4. Escape, Close, or browser Back closes the sheet and restores focus to the opener.

Acceptance criteria

  • Device Setup traps forward and reverse focus within visible enabled controls.
  • Header, main workspace, and mobile task dock are inert only while setup is open and their previous inert state is preserved.
  • Every close path removes containment and restores focus to the element that opened setup.
  • Existing setup, permission-recovery, and Back-safe behavior remain green.
  • Packaged mobile Chromium test verifies rendered focus containment and focus restoration at a phone viewport.

Evidence / non-duplication

frontend/mobile-device-setup.js currently handles Escape only and never manages shell inertness or opener focus. Historical issue #315 covered browser Back for task overlays, while #555/#715/#1084/#1132 cover setup guidance, reminders, timer pausing, and blocked notification recovery—not modal focus containment.

## Problem Mobile Device Setup is declared `aria-modal=true`, but opening it leaves the dashboard behind it keyboard- and assistive-technology-reachable. Tab can escape the sheet, background controls remain interactive, and closing does not restore focus to the launcher. This breaks the phone-readiness flow for keyboard, switch-control, and screen-reader operators. ## User flow 1. Open Device Setup from the app menu. 2. While open, Tab and Shift+Tab cycle only through visible setup controls. 3. The application shell behind the sheet is inert until setup closes. 4. Escape, Close, or browser Back closes the sheet and restores focus to the opener. ## Acceptance criteria - Device Setup traps forward and reverse focus within visible enabled controls. - Header, main workspace, and mobile task dock are inert only while setup is open and their previous inert state is preserved. - Every close path removes containment and restores focus to the element that opened setup. - Existing setup, permission-recovery, and Back-safe behavior remain green. - Packaged mobile Chromium test verifies rendered focus containment and focus restoration at a phone viewport. ## Evidence / non-duplication `frontend/mobile-device-setup.js` currently handles Escape only and never manages shell inertness or opener focus. Historical issue #315 covered browser Back for task overlays, while #555/#715/#1084/#1132 cover setup guidance, reminders, timer pausing, and blocked notification recovery—not modal focus containment.
timmy was assigned by rockachopa 2026-08-19 14:23:56 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
P0

Drop everything

  
P1

High priority

  
P2

Medium priority

  
agent:nightprowl

Assignments routed to the LongCat NightProwl evaluation worker

  
backend

Backend service

  
ci

Continuous integration / actions

  
frontend

Frontend / UI

  
meta

Meta / planning

  
pages

Gitea Pages

  
template

Repo template / standards

No Label
P0
P1
P2
agent:nightprowl
backend
ci
frontend
meta
pages
template
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
timmy
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: stackchain/stackchain-dashboard#1134
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?