Ensuring Accessibility and Quality Code in Web Projects Agent Skill

Quality assurance for web accessibility and usability, particularly for users with disabilities.

Context cost
2.7k tokensestimated from the bundle, loaded when it triggers
Bundle
2 files · 10.9 kBtext throughout, nothing executable
Licence
MITthe author’s own terms
Last change
—v0.5
Servers it uses
Noneruns standalone

What it does

Quality assurance for web accessibility and usability, particularly for users with disabilities. Use when involved in any web project.

What this skill changes about the agent has not been set out here as a list. Its SKILL.md, shown below, says it in the author’s own words.

accessibilitydesign
Filed under

Design & Media

The skill itself

A skill is instructions the model reads, so you can see what you are getting: below is the start of its SKILL.md. The front matter loads with every session, the body loads when the skill triggers, and the whole file comes with the install.

SKILL.md9.8 kB · preview
--- name: accessibility license: MIT metadata: author: conesible.de version: "0.5" ---
10# Ensuring Accessibility and Quality Code in Web Projects
11
12Building a web project with accessibility in mind from the very start is crucial, especially in contexts (like AI-driven development) where manual testing by humans is limited. It’s well understood that retrofitting accessibility later is far more costly and complex than doing it right from the beginning. Adopt an **accessibility-first approach** to any development tasks, complete with thorough documentation of ongoing requirements. Ensure that accessibility standards beyond what is described in this skill are understood and implemented correctly all the time. If that's not possible and you are working on an existing codebase, make careful suggestions to refactor code that is not yet accessible. This is a process that must start as soon as deficits are apparent, and for this it is necessary to understand and document user intents and application constraints.
13
14## Code Comments and WCAG References
15
16Add **code comments** liberally that explain implementations that are done specifically for accessibility. In those, explain this based on the WCAG 2.2 requirements of any level. Explain the **expected user flow** if relevant.
17
18## Use Semantic HTML and Proper Structure
19
20Start by using **semantic HTML** for all content and controls. Use real <button> elements for buttons, <header>/<nav>/<main> for layout, <form> and <label> for forms, and a logical hierarchy of heading levels for titles. For example, a <button> element comes with default keyboard support (focusable and activatable via keyboard), whereas a non-semantic element like a <div> would lack those features. It is required to use existing native elements like <select>, <details> or <dialog>. If there is no way of avoiding custom components (there usually isn't), follow established ARIA design patterns and **keyboard interaction models**. Use ARIA only if there is NO alternative, and in most cases, there is. If you do, document this choice and the reasoning behind it.
21
22Ensure the page is organized with clear **structure and landmarks**. Use HTML5 sectioning elements to delineate navigation, main content, forms, etc, to give users and yourself a clear understanding of how the content is structured. Always provide text equivalents for non-text media: include descriptive **alt text** for images, transcripts or captions for audio/video. If you can't reliably make those yourself, note a required and blocking task for another maintainer. Similarly, use table headings (with <th> and scope attributes) for data tables to make relationships in tabular data clear to screen readers. Avoid link texts like "here", "click" or "Continue Reading". If they are required visually, add a redundant way to receive their content (e.g. an interactive card) and remove those from the accessibility tree.
23
24## Design Accessible Components
25
26Each component’s HTML structure must reflect its semantics: use lists for menus or multi-option controls, use headings for titles, use fieldsets and legends for groups of form fields, etc. Maintain a consistent style for focus indicators (the outline or highlight when an element is focused) so that keyboard users can always see where focus is. **Keyboard accessibility** isn’t optional – ensure users can reach and operate every interactive element via keyboard alone (e.g., using Tab, Enter, space, arrow keys as appropriate). This may require adding tabindex ONLY for custom focusable elements and ONLY with negative values, and handling key events in scripts for custom widgets.
27
28Remember the WCAG rule for touch target sizes. Everything should be easily reachable. Mouse or gesture controls (like dragging) require an alternative.
This is a preview of SKILL.md. Download or install the skill to get the whole thing.
In the file
SKILL.md1,467 words
Files2
LicenceMIT
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈60
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
2,665
on trigger
The instruction body and 1 supporting file, read only when the skill fires.
1.4%
of a 200k window
Ten skills this size would take about 14% of the window before you open a file.
050k100k150k200k context window

2.7k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Middling. Fine to keep on in a project where you use it weekly, worth unloading in one where you never do.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

The procedure it runs

The procedure has not been set out here step by step. It is in the body of its SKILL.md: the start of it is shown above, and the whole file comes with the install.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

Its SKILL.md does not declare which tools it asks the agent for, so what it touches is whatever the instructions themselves ask for — read them before you install it.

What it asks for
Writes filesnot declared
Network accessnot declared

This SKILL.md carries no allowed-tools line, so neither is declared. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

2 files, 10.9 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • SKILL.md9.8 kB
  • LICENSE.txt1.1 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 2 files you can review in full before installing. The MIT licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

# Ensuring Accessibility and Quality Code in Web Projects · 2.7k tokens when loaded · macOS, Linux mkdir -p .claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/ensuring-accessibility-and-quality-code-in-web-pr/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/ensuring-accessibility-and-quality-code-in-web-pr" ] && { [ ! -e .claude/skills/ensuring-accessibility-and-quality-code-in-web-pr ] || { mv .claude/skills/ensuring-accessibility-and-quality-code-in-web-pr "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/ensuring-accessibility-and-quality-code-in-web-pr" .claude/skills/ && echo "Installed .claude/skills/ensuring-accessibility-and-quality-code-in-web-pr"
On Windows, or any OS with Node 20+
npx mcprush@latest skill add zolkyed/ensuring-accessibility-and-quality-code-in-web-pr

Windows PowerShell says 'running scripts is disabled on this system'? Run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither. Writes to .claude/skills/ensuring-accessibility-and-quality-code-in-web-pr/ in the current project. For every project instead, run mkdir -p ~/.claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/ensuring-accessibility-and-quality-code-in-web-pr/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/ensuring-accessibility-and-quality-code-in-web-pr" ] && { [ ! -e ~/.claude/skills/ensuring-accessibility-and-quality-code-in-web-pr ] || { mv ~/.claude/skills/ensuring-accessibility-and-quality-code-in-web-pr "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/ensuring-accessibility-and-quality-code-in-web-pr" ~/.claude/skills/ && echo "Installed ~/.claude/skills/ensuring-accessibility-and-quality-code-in-web-pr" (macOS, Linux) — or add --global to the npx line. The curl line replaces .claude/skills/ensuring-accessibility-and-quality-code-in-web-pr/ only after the download succeeds, so files left there by another skill of the same name, or by an older release, do not mix in. A copy already there is moved aside, not deleted, and the line prints where. It appears as accessibility in Gemini CLI, Codex, Copilot and Grok (its own name); Claude Code lists it by the folder name, ensuring-accessibility-and-quality-code-in-web-pr.

Which clients pick it up on their own

A skill is a folder of text. Most of these read a skills folder and pick it up without being told; the rest take the same folder another way — an upload in the app, a parameter on an API call — and then choose it by its description just the same.

Claude Code.claude/skills/
Claude DesktopCustomize › Skills
ChatGPTSkills › Create › Upload
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok Build.grok/skills/
Microsoft CopilotSkills › Upload a skill
PerplexityComputer › Skills › Upload a skill
DeepSeek Harness.dsh/skills/
Zed.agents/skills/
Devin Desktop.devin/skills/
Windsurf (legacy).windsurf/skills/
OpenAI Agents SDKInstructions or sandbox Skills
HTTP / APIa request parameter
This release
Version0.5
Publishedno release date on file
PriceFree
Referencezolkyed/ensuring-accessibility-and-quality-code-in-web-pr

Versions

v0.5 is what is on the shelf; no release here carries a date. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v0.5
  • No earlier releases have been published to the marketplace.
Pinning

The install command always fetches the release that is current the day you run it — v0.5 today — and cannot ask for an earlier one. The copy on your disk does not change until you run it again.

Reviews

—no reviews yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Sign in to review it

A review is tied to an account so it can be answered, edited and taken down by the person who wrote it.

Sign in
Who can post

Anybody with an account, one review each. It carries the version that was current when you wrote it, and the publisher may reply once.

Publisher
Servers0
Claim this skill