A11 / Access
Start with the surface you need.
A11 access begins with a clear use case, an accountable owner, and an explicit boundary around the work to be inspected or built.
Access principleA11 / 07
Clear
scope.
Clear owner.
Access brief
Describe the work, not a vague account tier.
This local brief records intent in the browser only. It does not submit data, create an account, grant access, or imply admission to a connected environment.
Review boundary
Access should increase clarity, not authority by accident.
Requests are framed so intended capability, data, permissions, and owner decision are visible before any connected environment is considered.
- State the intended product surface.
- Name the accountable owner.
- Describe sensitive data without sending secrets.
- Separate exploration from execution authority.
Before you request access