Wcag22 Css Lint

io.github.jmshinhwaPublished by GitHub account jmshinhwav1.0.4Updated Oct 24, 2026

Reads your stylesheet and names the success criterion each rule breaks, including the three WCAG 2.2

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

Lints a stylesheet for WCAG 2.2 accessibility issues and names the success criterion each rule breaks.

What you can do
This local MCP server reads a stylesheet and reports accessibility problems, naming the WCAG success criterion that each offending rule breaks. It covers the WCAG 2.2 criteria, including the three new ones added in that version. It runs as a local process over stdio, so the assistant can call it while working on CSS.
When to use it
Useful when auditing or refactoring CSS for accessibility compliance and you want the assistant to point at specific rules and the criteria they violate. Worth adding if your workflow already involves WCAG 2.2 conformance checks on stylesheets.
Requirements
Runs locally as an npm package started with npx, so Node.js and npx must be available on the machine. No authentication, environment variables, or headers are declared. Desktop only; not available as a web executable.
Before you install
The registry description and README are sparse: the README only mentions VS Code themes by the same publisher and does not document the linting tools or their inputs. No credentials are requested, but confirm what files it reads before pointing it at a codebase.

Installation

In SourceWeft

  1. Open Wcag22 Css Lint in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

readystack-themes

Made by ReadyStack · free calculators and templates at getreadystack.com VS Code themes by ReadyStack

Source: README.md at commit ee1c884

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v1.0.4LatestSep 19, 2026
  2. v1.0.2Sep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.