Designers
DocsProAll the Possibles

Your first five minutes

An accessibility check that you can verify yourself. You will need the server connected and either a Figma link or any web address.

1. Check it is connected

Say:

Call the whoami tool from the Designers server.

You should see:

Plan: Free (daily caps per tool, 30 requests a minute; Pro adds site crawls, token matrices, scored reports and playbooks: https://designers.allthepossibles.com/#pro)

  check_contrast               11 of 60 used today, 49 left
  audit_page_accessibility     3 of 20 used today, 17 left
  heuristic_worksheet          2 of 20 used today, 18 left
  detect_design_slop           2 of 10 used today, 8 left

2. Check a colour pair

Say:

Check the contrast of #8a8a8a text on a white background at 16px.

You should see a result like this (the assistant may reword it, but the numbers are exact):

#8a8a8a on #ffffff  3.45:1  AA FAIL  (normal text)  APCA Lc 62.1
   APCA: enough for 24px regular or 16px bold; too low for body copy
   nearest passing: #767676 (4.54:1)

That is your assistant using a tool instead of guessing. #8a8a8a on white is 3.45 to 1, which fails the 4.5 to 1 needed for normal text, and the tool offers the nearest colour that passes.

3. Review a real design

In Figma, select the frame, right click, Copy/Paste as, Copy link to selection. Then say:

Use the accessibility_review prompt on this Figma link: <paste link>

If you have no Figma file, give it a live page instead:

Run audit_page_accessibility on https://example.com and tell me what to fix first.

For a live page you will see a list like this (this is the real output for our own homepage):

"All the Possibles: tools that check themselves before they ship": 12 headings, 0 images, 15 links, 3 buttons, 1 form controls
0 high, 1 medium, 1 low

MEDIUM 1.3.1 Info and Relationships: heading level jumps from h2 to h4
         e.g. <h4>
LOW    2.4.1 Bypass Blocks: no skip link at the top of a page with many links

Static HTML only. It does not render the page, so it cannot test colour contrast (use the contrast tool), focus order, keyboard traps, ARIA behaviour in script-built interfaces, captions, or reading order. Passing this audit does not mean a page is accessible; automated tools find roughly a third of WCAG failures.

What a good result looks like

Next

Try example requests for critique, copy, research and tracking, or say Start here. I have <what you have>.