quill accessible-dialogs.instructions.md

Accessibility rules for dialogs in QUILL, a wxPython desktop application. They focus on making dialog windows usable with screen readers, keyboards, mice, and different visual needs.

In plain words
What is it for?
Building or reviewing modal windows, setting default and Escape actions, managing focus, labeling controls, and checking the project's accessibility tests.
Why use it?
They provide consistent focus, naming, button, keyboard, contrast, and error behavior so dialogs are understandable and do not trap users.

Instructions file for GitHub Copilot

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/community-access/quill/accessible-dialogs
Clone the repo
git clone --depth 1 https://github.com/Community-Access/quill

Made for: GitHub Copilot.

Per session 4,512 This file is loaded in full into every session.
When invoked 4,512 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.04512 $0.04512
Opus 5 $0.02256 $0.02256
Sonnet 5 $0.00902 $0.00902
Haiku 4.5 $0.00451 $0.00451

Measured 3d ago against content hash 1dc7f4a43a2a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

quill accessible-dialogs.instructions.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.github/instructions/accessible-dialogs.instructions.md · 350 lines

How it starts

The opening of the file, as written. The whole thing — 350 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Accessible Dialog Patterns (wxPython, screen-reader-first)

These rules govern every dialog and modal surface in QUILL's wxPython UI. They go beyond keyboard navigation: a dialog is only "done" when a blind keyboard user, a low-vision user, and a sighted mouse user each get an equally clear, predictable experience.

Authoritative sources these rules are grounded in:

  • wxWidgets/wxPython Phoenix dialog, sizer, and validator overviews (wx.Dialog, wx.StdDialogButtonSizer, CreateButtonSizer, SetAffirmativeId, SetEscapeId, SetDefault, wx.Accessible).
  • WCAG 2.2 success criteria: 1.4.3/1.4.11 (contrast), 1.4.10 (reflow), 1.4.12 (text spacing), 2.1.2 (no keyboard trap), 2.4.3 (focus order), 2.4.7 (focus visible), 2.4.11 (focus not obscured), 3.3.1/3.3.2/3.3.3 (error identification, labels, suggestions), 4.1.2 (name/role/value).
  • QUILL's shared contract: apply_modal_ids(...) and show_modal_dialog(...) in quill/ui/dialog_contract.py, enforced by the DLG-3 / A11Y-4 guards (tests/unit/ui/test_dialog_inventory.py, tests/unit/ui/test_dialog_hardening_contract.py, quill/tools/dialog_button_contract.py).

When any rule below conflicts with QUILL's machine-enforced contract, the enforced contract wins. Otherwise, treat these as required. This file is the authoring companion to docs/qa/dialogs.md (manual regression map) and the DLG-3 dialog estate governance described in the repository Copilot instructions.


1. Surface choice (native-first)

Need Use Avoid
Confirm / yes-no / warning wx.MessageDialog / wx.RichMessageDialog Bespoke wx.Dialog
One choice from a list wx.SingleChoiceDialog Hand-rolled list dialog
Simple text entry wx.TextEntryDialog Custom panel plus button
File / folder selection wx.FileDialog / wx.DirDialog Custom browser
Color / font wx.ColourDialog / wx.FontDialog Custom picker
Long progress wx.ProgressDialog / wx.GenericProgressDialog Spinner with no name
Rich / multi-control form hardened wx.Dialog (only sanctioned bespoke base) Any non-wx modal surface

Read the full file on GitHub · 350 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 350 lines · 4,512 tokens per session scan A 1dc7f4a43a2a

Subscribe to this mod's changes

quill accessible-dialogs.instructions.md is an instructions file published in the GitHub repository Community-Access/quill (43 stars, last pushed 3d ago), licensed MIT. It adds 4,512 tokens to every session, about $0.0226 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,345 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens