spec 1 linked patterns checked
W3C: Client-side scripting techniques for WCAG 2.0
Documents scripting techniques that should degrade gracefully when script is unsupported, including avoiding javascript URI dependencies and providing accessible scripted behavior.
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. | W3C scripting guidance includes graceful script failure when script is unsupported. |
Comparisons supported by this source
- Graceful degradation vs fallback path vs offline state vs service unavailable page
W3C scripting guidance documents graceful script failure when client-side script is unsupported.
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: .