Website Testing Kit

Before you start

• Use a project, files or media you are authorized to inspect. Start with copies or a staging environment.
• Check the selected skill source, license, agent support and local dependencies before installing it.
• Agree on a small acceptance example and preserve the original input before changing anything.

Costs, licenses and data

Browser automation needs compatible local tools and an agent. Remote browser services are optional and may charge. The Vercel guideline entry has Unknown license metadata here; read its source and fetched guideline terms. No full accessibility certification is included.

See the example we checked

Empty, invalid, success and server-failure paths checked at three viewport sizes.

• Measured 375×700, 768×900 and 1440×900; no horizontal overflow.
• Tab order and visible 3px focus verified; Enter submits to a local test endpoint.
• Synthetic name retained after failure; email remained nonempty. No email delivery exists.

Check limits: One in-app browser; exact engine version unavailable. Email values are redacted in browser observations. No cross-browser, screen-reader or real delivery certification.

Try it on your computer

1. Download and extract the example into a new disposable folder. Read README.md and the source files.
2. With Python 3.10 or newer, run the command below from that folder. It uses the standard library; no API key, agent or package installation is needed for this check.
3. Open example-output/report.html or report.md and inspect result.json. The form and optional video-render instructions are in README.md.
4. For your own task, review the selected skills below, install one appropriate component through your agent, then adapt the brief to your project.

python check.py website-testing --source . --output example-output

8.2 KB · Original AI Craft Pad fixtures and code under MIT. The ZIP does not install external skills. Read it before running code. Existing files in example-output may be replaced.

Check the deliverable

• Actual viewport dimensions are recorded rather than inferred from an emulator setting.
• Keyboard focus is visible and controls work without a pointer.
• Normal, empty, invalid and failure states are covered with synthetic data.
• Visual baselines use the same environment and intentional changes are explained.
• The final delivered page is checked; an earlier local screenshot is not substituted.

Complete the checks below against the actual deliverable and preserve enough evidence for another person to repeat the important steps. Record the environment, source dates and anything that could not be checked. These components were selected from source documentation; this catalog has not executed them together as an integrated system.