Worked example · Website owners and developers · Reviewed October 27, 2026

We loaded the public skill below through 9octopus and applied it to this sample input. The output is shown so you can inspect the result and repeat the task. Your agent’s output may differ.

What you need

A connected agent with terminal access, Node.js/npx, Playwright CLI, and an installed browser. The agent needs permission to inspect and edit the sample HTML. A chat-only client without browser tools cannot run this check.

Choose your agent’s setup guide, connect it to 9octopus, and finish OAuth sign-in before trying the prompt.

Skill used

playwright — source revision used

The source link pins the instructions used for this example. Catalog availability can change; find currently available skills for this task.

Example input

A sample newsletter form: visible text says “Email address”, but it is not a label. The Subscribe control is a clickable div. Check whether someone can identify the field and complete the form with a keyboard.

Open the original sample form · Try the corrected form

Try this prompt

Find a public skill for checking a signup form in a real browser. Load the best fit and confirm its exact version. Inspect the sample form’s accessible names and keyboard navigation, fix confirmed issues, and repeat the same checks. Keep the report limited to what you tested.

Public task recommendations use OpenAI for semantic matching. Keep secrets and private repository contents out of discovery queries; provide the working material directly to your agent under your normal access controls.

Ask your agent to search the public catalog, check the selected skill’s source and prerequisites, and confirm its version before continuing. If the source revision above is unavailable, review the suggested alternative before applying it. A new search may return different matches.

How we worked through it

  1. Inspect the browser snapshot: the input appears as an unnamed textbox and Subscribe appears as a generic element.
  2. Press Tab through the form. The email input receives focus, but the clickable div is skipped.
  3. Associate a label with the email input and replace the clickable div with a native submit button. Repeat the keyboard interaction in the browser.

Example output

Finding 1 — Email field has no accessible name.
Fix: associate <label for="email"> with <input id="email">.

Finding 2 — Subscribe cannot receive keyboard focus.
Fix: use <button type="submit">Subscribe</button>.

Retest: the snapshot exposes textbox “Email address” and button “Subscribe”.
Tab reaches Subscribe; Enter displays “Demo complete. No email was sent or saved.”
Download example output

What we checked

  • Before: browser snapshot showed an unnamed textbox and a generic Subscribe element.
  • Before: Tab moved from the input to the page body, skipping Subscribe.
  • After: the labeled textbox and native button appeared in the snapshot; Tab reached the button and Enter updated the status message.

What this example does not establish

This is a deliberately small sample, not a customer incident or a full accessibility audit. We checked accessible names and keyboard operation in Chromium. Screen-reader behavior and broader WCAG conformance still need separate review. No real subscription or email service is connected.

Explore another worked example or connect your agent to try your own task.