SwarmCraft
Help and referenceGuide

Docs

Accessibility and keyboard shortcuts

Use SwarmCraft with standard browser and VS Code navigation patterns, and keep the workflow operable without depending on pointer-only interaction.

Accessibility and keyboard shortcuts

Use standard browser and VS Code keyboard patterns across SwarmCraft. Report a workflow that requires pointer input as an accessibility defect.

Browser and docs guidance

On the public docs surface, start with the normal browser patterns first:

  • use the skip link to jump to main content
  • use standard link and heading navigation
  • zoom the page when you need larger content
  • collapse or open the docs navigation on smaller screens
  • use the search field and result links without leaving the keyboard

The current page is identified in the docs rail. Article headings provide screen-reader landmarks, and contextual continuation links follow the article rather than an implied global sequence.

VS Code guidance

Inside VS Code, the SwarmCraft extension follows editor conventions where possible. That means you should prefer:

  • the Activity Bar for opening the extension view
  • the Command Palette for SwarmCraft commands
  • the Explorer for revealing linked packet files
  • normal keyboard navigation through tree items and context menus

Helpful commands to remember

  • SwarmCraft: Sign In
  • SwarmCraft: Choose Repo
  • SwarmCraft: Move to Doing
  • SwarmCraft: Copy SwarmCraft Command
  • SwarmCraft: Sync Packet

The Command Palette is the keyboard fallback when a tree context menu is awkward. After opening a packet, use normal editor, terminal, source-control, and accessible-view commands supplied by VS Code and the selected AI extension.

Board and dialog guidance

Use board cards and explicit movement controls when drag-and-drop is not suitable. Keep focus inside an open dialog until it closes, then confirm focus returns to a useful control. Status, error, and progress meaning must not depend on color alone.

If keyboard or screen-reader use fails

Record the route or VS Code command, control label, input method, expected focus or announcement, and actual result. Include browser, operating system, VS Code, and assistive-technology versions without sharing private project content. Check Troubleshoot SwarmCraft, then contact support if the issue remains.

The terminal outcome for this reference is an operable keyboard and screen-reader path. Return to the guide for the task you were completing once the blocked interaction works.