EaseWeb accessibility

dev.easewebPublished by easeweb.devOfficial publisherv1.0.0Updated Oct 29, 2026

Accessibility guides for coding agents: fixes with working code, test steps, contrast checks. EN/JA

VerifiedStreamable HTTPWeb executableKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Free, no-login accessibility guide service that gives coding agents fixes with working code, test steps and colour contrast checks for UI work.

What you can do
  • Get guidance before building: send a UI request in the user's words and receive the applicable accessibility guides.
  • Search and read guides: find topics by words, component, tag, ARIA attribute or WCAG/EN 301 549/Section 508/JIS criterion, and fetch the full guide as Markdown with before and after code.
  • Check colours: evaluate foreground/background pairs, text size and weight, or non-text uses such as borders, icons and focus rings.
  • Plan verification: get pass criteria, checks the agent can run itself, and a short manual test script for people.
When to use it
Useful when an assistant designs, builds or changes interactive UI, picks colours or design tokens, or needs to explain and verify accessibility fixes. It suits teams that want WCAG, EN 301 549, Section 508 and JIS X 8341-3 oriented guidance in English or Japanese without an account.
Requirements
Remote streamable HTTP endpoint at easeweb.dev; no login, API keys, environment variables or headers are declared. Network access is required.
Before you install
The server states that automated checks and its tools never prove accessibility; manual keyboard and screen reader testing still has to be done by a person and should not be reported as complete. Requests describing UI work are sent to a third-party service.

Installation

In SourceWeft

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

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.easeweb%2Feaseweb/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "easeweb-accessibility": {
      "type": "http",
      "url": "https://easeweb.dev/mcp"
    }
  }
}

Tools

5

before_building

Before building: requirements and reference code

Call BEFORE designing or building any interactive component or screen: menus, dialogs, carousels, tabs, forms, drag and drop, custom controls, cards, tables, charts, animation. This includes wireframes, mockups and prototypes. Takes the request in the user’s own words and returns the guides that apply with the requirements to build in from the start (keys, roles and names, focus, what is announced), working reference code, and the checks split into what the agent can confirm and what a person must. When the request itself breaks a rule (autoplay with no pause, a placeholder as the only label, a div as a button, hover-only menus, removed focus outlines, disabled zoom), it returns a version that keeps what the user wanted and passes, plus one sentence to say to the user. Do not refuse such a request, and do not build the failing version quietly.

Parameterslimitlocalerequestrequired

find_fix

Find the fix for an accessibility problem

Search the Learn guides by words, component name, tag, ARIA attribute or WCAG number (1.4.3, SC 2.1.1, JIS 達成基準, EN 301 549 9.x). Returns for each matching topic: the problem, the fix in one line, how to test it, the guide link, and the criterion in WCAG, EN 301 549, Section 508 and JIS X 8341-3 terms. Topics with no guide yet come back as "in progress". Use it when a finding, a complaint, a failing check or a question names a problem.

Parameterslimitqueryrequiredlocale

get_guide

Get one guide as Markdown

The full guide as Markdown, the same as easeweb.dev/learn/<slug>.md: what happens, why it fails, who it affects, what automation misses, the Before and After code, how to verify, and the limits. Also returns the After code as plain text with its marks (recommended, not enough on its own, the rule of thumb behind it). Get the slug from find_fix or before_building.

Parametersslugrequiredlocale

test_steps

How to test a fix: agent checks and the person’s script

Call AFTER building or fixing something, and before telling the user it is done. For a guide (by slug) or a component (by query) returns the pass criteria, the checks the agent can run itself, the checks only a person can do (which keys to press and what should happen, as a two-minute script), the guide’s limits, and a Playwright regression test skeleton. Hand the person’s checks to the user as written; never report them as done.

Parametersslugquerylocale

check_palette

Check colour contrast for text and controls

Call when choosing or changing colours, a palette or design tokens, before they are used in a design or in code. Takes colour pairs (foreground and background, with text size in px and weight when the foreground is text, or use: "non-text" for control borders, icons and focus rings) or a set of named tokens, in hex, rgb() or hsl(). Returns each pair’s contrast ratio, pass or fail against WCAG 1.4.3 (text) and 1.4.11 (non-text) at AA or AAA, the nearest passing shade of the same hue, and the guides that apply. It checks values, not rendered pages: text over images, real focus states and forced colors stay with the audit.

Parameterslevelpairslocaletokens

Version history

1
  1. v1.0.0LatestOct 29, 2026

Score

83% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.