spec 1 linked patterns checked
MDN: Progressive enhancement
Defines progressive enhancement as starting with baseline content and functionality, then layering advanced capabilities while distinguishing it from graceful degradation.
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 distinguishes progressive enhancement from graceful degradation and describes their relationship. |
Comparisons supported by this source
- Graceful degradation vs fallback path vs offline state vs service unavailable page
MDN distinguishes progressive enhancement from graceful degradation while noting that the approaches can complement each other.
Evidence Role
This source is treated as spec evidence. Its value comes from the specific claims and setting described above.
Publisher: Mozilla. Last checked: .