spec 1 linked patterns checked
MDN: Graceful degradation
Defines graceful degradation as designing a modern experience that falls back to an experience that still delivers essential content and functionality in less capable browsers or environments.
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 |
|---|---|---|---|
| Graceful degradation | Choose graceful degradation when users stay on the same surface and the core task continues with fewer capabilities. | The baseline path can complete the same core task or the interface explicitly says why it cannot. | MDN defines graceful degradation as retaining essential functionality in older or less capable environments. |
Comparisons supported by this source
- Graceful degradation vs fallback path vs offline state vs service unavailable page
MDN defines graceful degradation as retaining essential content and functionality in less capable environments.
Evidence Role
This source is treated as spec evidence. Its value comes from the specific claims and setting described above.
Publisher: Mozilla. Last checked: .