spec 1 linked patterns checked
W3C: Geolocation
Defines the Geolocation API for retrieving device location with user consent, position options, position errors, permission checks, privacy considerations, and watch or clear-watch lifecycle.
Read with a purpose
What this source can teach
Use this source to check a technical or accessibility requirement against its exact wording and scope.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Location permission flow | Choose location permission flow when current device coordinates are the central interaction and the task needs permission timing, precision, grant or denial recovery, and location lifecycle states. | The native browser or OS prompt appears only after users understand why location is needed and choose a location-dependent action. | Supports consent, privacy, position options, error states, and watch lifecycle. |
Comparisons supported by this source
- Location permission flow vs permission request vs map view vs address entry vs privacy settings vs offline state
Supports geolocation consent, privacy considerations, position options, errors, and watch lifecycle.
Evidence Role
This source is treated as spec evidence. Its value comes from the specific claims and setting described above.
Publisher: World Wide Web Consortium. Last checked: .