progressive-enhancement SKILL.md skillA

progressive-enhancement from mgifford/accessibility-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add mgifford/accessibility-skills/progressive-enhancement@git:20261112.379cb95

Pins git:20261112.379cb95 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
mgifford/accessibility-skills
Path
skills/progressive-enhancement/SKILL.md
Versions recorded
3
Latest version
git:20261112.379cb95, committed Nov 12, 2026
First version recorded
Mar 31, 2026
Size
10,324 bytes
Repository stars
61
License
AGPL-3.0

Load this skill when building any web feature, reviewing architecture decisions, or evaluating JavaScript dependencies. Under no circumstances build features that break completely when JavaScript is unavailable or fails. Absolutely always start with semantic HTML, layer CSS enhancements, and add JavaScript as the final, optional layer. Prioritize resilience and universal access over cutting-edge features.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Progressive Enhancement Accessibility Skill

> **Canonical source**: `examples/PROGRESSIVE_ENHANCEMENT_BEST_PRACTICES.md` in `mgifford/ACCESSIBILITY.md`
> This skill is derived from that file. When in doubt, the example is authoritative.

Apply these rules when building any web feature or reviewing architecture decisions.

---

## Core Mandate

Start with a solid foundation that works for every user, then layer enhancements.
Every user — regardless of browser capability, network speed, assistive technology,
or JavaScript availability — must be able to access core content and complete core
tasks.

Progressive enhancement is also a sustainability practice. Pages that work without
JavaScript are dramatically lighter: fewer bytes transferred, less CPU spent on
parsing and executing scripts, and less energy consumed per page view. See
[SUSTAINABILITY.md](https://github.com/mgifford/SUSTAINABILITY.md) and the
[Web Sustainability Guidelines](https://www.w3.org/TR/web-sustainability-guidelines/).

---

## Severity Scale (this skill)

| Level | Meaning |
| --- | --- |
| **Critical** | Core content or task inaccessible without JS/CSS |
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_lwhadkuvyork5dui/9c4e8cadaf8c0c698fdd12bd04589a2f7fb78e92a606472c7a26b9992e99a9cf.json

Then /plugin install progressive-enhancement@markdownregistry-lwhadkuvyork5dui in Claude Code. It installs git:20261112.379cb95, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add mgifford/accessibility-skills/progressive-enhancement@sha256:9c4e8cadaf8c0c69

The line at the top of this page pins the label git:20261112.379cb95, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_lwhadkuvyork5dui.svg)](https://markdownregistry.com/a/art_lwhadkuvyork5dui)

1 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in mgifford/accessibility-skills/progressive-enhancement since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of progressive-enhancement from somewhere else? Ask it: where did my progressive-enhancement come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 3 versions of this file, between Mar 31, 2026 and Nov 12, 2026, about one every 113 days. Its first recorded version is graded C and its latest A.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20261112.379cb95 latest2026-11-12 379cb95 10,324 BA view · diff
git:20260331.f09d8892026-03-31 f09d889 9,666 BA view · diff
git:20260331.0b2aead2026-03-31 0b2aead 9,191 BC view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (10324 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

mgifford/accessibility-skills · 61 stars · license AGPL-3.0 · pushed 2026-11-12 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_lwhadkuvyork5dui
GET https://markdownregistry.com/api/v1/resolve?ref=mgifford/accessibility-skills/progressive-enhancement
GET https://markdownregistry.com/api/v1/blob/9c4e8cadaf8c0c698fdd12bd04589a2f7fb78e92a606472c7a26b9992e99a9cf

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from mgifford/accessibility-skills

AGENTS.md AGENTS.md file
mgifford/accessibility-skills · AGENTS.md
git:20261112.c9ebd5d · audit A · 61 stars
critic SKILL.md skill
mgifford/accessibility-skills · ai-workflows/critic/SKILL.md
git:20260717.54950ae · audit C · 61 stars
planner SKILL.md skill
mgifford/accessibility-skills · ai-workflows/planner/SKILL.md
git:20260717.3f6aae0 · audit C · 61 stars
accessibility-general SKILL.md skill
mgifford/accessibility-skills · skills/ACCESSIBILITY-general/SKILL.md · Load this skill immediately whenever a project contains an ACCESSIBILITY.md file, or whenever you are contributing to…
git:20261112.07bb00b · audit A · 61 stars
anchor-links SKILL.md skill
mgifford/accessibility-skills · skills/anchor-links/SKILL.md · Load this skill whenever the project contains in-page anchor links, skip links, fragment identifiers, or heading links…
git:20260722.125074b · audit A · 61 stars
aria-live-regions SKILL.md skill
mgifford/accessibility-skills · skills/aria-live-regions/SKILL.md · Load this skill whenever the project contains dynamic content updates, status messages, alerts, notifications, loading…
git:20260722.125074b · audit A · 61 stars
audio-video SKILL.md skill
mgifford/accessibility-skills · skills/audio-video/SKILL.md · Load this skill whenever the project contains audio or video content, media players, podcasts, video embeds, or any…
git:20260722.125074b · audit A · 61 stars
axe-rules SKILL.md skill
mgifford/accessibility-skills · skills/axe-rules/SKILL.md · Load this skill when configuring axe-core scans, reviewing automated accessibility test results, or writing tests that…
git:20260727.2f4d4d4 · audit A · 61 stars
behavioral-a11y SKILL.md skill
mgifford/accessibility-skills · skills/behavioral-a11y/SKILL.md · Load this skill when writing, reviewing, or interpreting behavioral accessibility automation — tests that manipulate a…
git:20260726.d7f226e · audit A · 61 stars
bug-reporting SKILL.md skill
mgifford/accessibility-skills · skills/bug-reporting/SKILL.md · Load this skill whenever you are filing, reviewing, or generating accessibility bug reports — whether from automated…
git:20261112.07bb00b · audit A · 61 stars
charts-graphs SKILL.md skill
mgifford/accessibility-skills · skills/charts-graphs/SKILL.md · Load this skill whenever the project contains charts, graphs, data visualizations, infographics, or any visual…
git:20260722.125074b · audit A · 61 stars
ci-cd SKILL.md skill
mgifford/accessibility-skills · skills/ci-cd/SKILL.md · Load this skill when configuring or reviewing CI/CD pipelines, GitHub Actions workflows, or automated testing setups…
git:20261112.c9ebd5d · audit A · 61 stars

Every file in mgifford/accessibility-skills

Browse by kind, by grade A, or by owner.