Name team-setting dialogs from visible headings
Screen readers announce Dialog without a purpose. Connect each settings dialog to its visible heading.
- Focused work estimate
- 1h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Accessible names · Composition
Estimated field mix
- Accessibility80%
- Frontend20%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
Fictional membership portal Juniper manages synthetic team settings. Use locally owned components and a local settings adapter.
Setup prerequisites
- Create synthetic settings forms and destructive-action stubs.
- Provide delayed success, rejection and removed-trigger cases.
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Dialog has a meaningful name
- Description excludes the entire form
- Heading IDs remain unique
Implementation constraints
- Use the owned primitive's naming API.
Verification to include
- Open two dialog types
- Mount repeated instances
Deliverables
- Dialog naming fix and checks
Rollout and recovery
Revert consumer composition if names collide.
Value of the work
For the engineer: Practice focus containment, dismissal and asynchronous feedback.
For the team: Inspect whether shared UI primitives protect users across many product flows.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.