EaseWeb accessibility

Accessibility requirements for an interactive component or screen that is about to be designed or built: menus, dialogs, carousels, tabs, forms, drag and drop, custom controls, cards, tables, charts, animation, and the wireframes, mockups and prototypes for them. 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 an 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 also returns a version that keeps what the user wanted and passes, and one sentence that explains the change.

Checks the contrast of colours, a palette or design tokens for use 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.

Searches 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 terms, with EN 301 549 and Section 508 in English or JIS X 8341-3 in Japanese. Topics with no guide yet come back as "in progress". For a finding, a complaint, a failing check or a question that names a problem.

The full guide as Markdown, the same guide 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). Takes a guide slug, as listed in find_fix and before_building results.

The test plan for something that has been built or fixed. For a guide (by slug) or a component (by query) returns the pass criteria, the checks an 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. An agent or automation can’t establish the person’s checks.