mgifford

Load this skill whenever the project supports light/dark mode, colour theme switching, high-contrast mode, or responds to prefers-color-scheme. Under no circumstances hard-code colours that break in alternative themes. Absolutely always test colour contrast in both light and dark themes, and respect user OS-level colour preferences via CSS media queries.

Load this skill when configuring or reviewing CI/CD pipelines, GitHub Actions workflows, or automated testing setups. Ensures accessibility regressions are caught before code reaches production by enforcing quality gates, structured reporting, and a zero-debt strategy across all pages and user preferences.

Load this skill immediately whenever a project contains an ACCESSIBILITY.md file, or whenever you are contributing to the mgifford/ACCESSIBILITY.md repository. Absolutely always read ACCESSIBILITY.md before proposing or writing any changes. Under no circumstances skip this skill when an ACCESSIBILITY.md file is present. This skill governs when and how all other accessibility topic skills must be loaded.

Load this skill whenever the project contains text, UI components, icons, form controls, data visualisations, or focus indicators — in short, almost every project. Under no circumstances hard-code colour values without verifying contrast ratios. Absolutely always ensure text meets 4.5:1, large text meets 3:1, and non-text UI elements meet 3:1 against adjacent colours. Test in light mode, dark mode, and forced-colors (high contrast) mode.

Load this skill whenever the project contains dynamic content updates, status messages, alerts, notifications, loading indicators, or any use of aria-live, role="status", role="alert", or role="log". Under no circumstances add or modify live-region markup without applying these rules. Prioritize correct politeness levels and avoid redundant announcements.

Load this skill whenever the project contains navigation components — primary navigation menus, dropdown menus, mega menus, breadcrumbs, pagination, mobile hamburger menus, or in-page jump navigation. Under no circumstances create navigation without proper landmark roles, keyboard support, and accessible labels. Absolutely always wrap navigation in <nav> with a unique aria-label.

Apply the Opquast Digital Quality Framework (245 rules, 14 categories) when building, reviewing, or auditing websites and web applications. Use for web development quality assurance, accessibility compliance, security hardening, privacy implementation, e-commerce best practices, and holistic digital quality checks.

Load this skill whenever the project involves writing, editing, or reviewing content for a general audience, including UI copy, help text, error messages, documentation, and instructions. Under no circumstances use jargon, complex sentence structures, or unexplained acronyms without providing plain alternatives. Absolutely always target a reading level accessible to the broadest possible audience. Load alongside content-design/SKILL.md for all content work.

Validate an approved mission before merge

Cross-artifact consistency and quality analysis

Interview and compile a project charter

Open the mission dashboard

Execute a work package implementation

Merge an accepted mission

Create an implementation plan

Generate research documents for the current mission

Comprehensive AI-assisted accessibility practices for Drupal Core, including 100 validated user stories, automated workflows, module testing, and patch evaluation frameworks. Use when implementing, testing, or evaluating accessibility in Drupal — covers keyboard navigation, screen reader compatibility, WCAG 2.2 AA workflows, Playwright test suites, axe-core scanning, and patch evaluation.

DOM, theming, and CSS accessibility rules for Drupal templates and stylesheets. Use when generating, reviewing, or modifying *.html.twig, *.css, *.pcss, *.scss, theme libraries, layout regions, or any markup that ships to the browser. Covers semantic HTML over ARIA, the Drupal hide-content-properly contract (visually-hidden vs hidden vs aria-hidden vs the @media (scripting) js-show/js-hide pattern), WCAG 2.2 SC 2.5.8 24×24 px target size enforcement, focus-visible outlines, and reduced-motion handling. Loaded by the drupal-accessibility dispatcher.

Accessibility rules for Drupal JavaScript behaviours, AJAX, modals, and the test layers that cover them. Use when generating, reviewing, or modifying *.js, Drupal.behaviors, AJAX commands, dialog/modal code, or *Test.php that exercises the UI. Mandates Drupal.announce() over hand-rolled aria-live, focus trapping for modals and focus return for AJAX triggers, Playwright (not Nightwatch) for browser-level accessibility scans per core issue

Server-side accessibility rules for Drupal Form API and render arrays. Use when generating, reviewing, or modifying *.module, *.inc, *Form.php, controllers, or any PHP that builds a render array. Covers required

Issue-authoring and review rules for Drupal accessibility work. Use when drafting an accessibility issue, merge-request description, or change record, or when reviewing one. Enforces the structured field block (Bug ID instance/pattern, URL, simplified and full-DOM XPath, WCAG SC with level, tool rule ID, severity, frequency, screen type, colour mode), the HTML snippet, AI disclosure, one-issue-per-criterion scoping, and the manual-checks-required-before-RTBC rule. Pair with REFERENCE_BUG_REPORT.md in this directory for the fillable template. Aligned with the upstream ACCESSIBILITY_BUG_REPORTING_BEST_PRACTICES guide. Loaded by the drupal-accessibility dispatcher.

Dispatcher for Drupal accessibility guidance. Use when generating, reviewing, or modifying Drupal code, theming, JavaScript, or test coverage with accessibility implications, or when drafting accessibility issues for the issue queue. Routes work to a specialised sub-skill based on file type or task — server-side Form API (drupal-a11y-fapi), DOM and CSS (drupal-a11y-dom), interaction and testing (drupal-a11y-dynamic), or QA and issue authoring (drupal-a11y-qa). Enforces Drupal Accessibility Coding Standards, WCAG 2.2 AA (including the new SC 2.5.8 24×24 px target size), Drupal-native hiding patterns over hand-rolled ARIA, and the move from Nightwatch to Playwright plus Axe-core inside PHPUnit.

Drupal configuration management including config import/export, config splits (complete and partial), syncing config across environments, drush commands for config management, config:import, config:export, config-split commands

Managing Drupal contributed modules via Composer, including updates, patches, version compatibility, and Drupal 11 upgrades. Use when updating modules, resolving dependency issues, applying patches, or contributing back to drupal.org.

Use when you have an existing component, flow, or interface and need an evidence-backed accessibility design review after basic checks pass. Best for WCAG 2.2 compliance, focus management, ARIA pattern quality, semantics, and state communication gaps automated tools miss.

Use when you know what component, flow, or interface you need but not yet the right accessibility approach. Best for turning WCAG 2.2 requirements into an accessible implementation plan with WAI-ARIA APG patterns before code hardens bad interaction and state patterns.

Use when you need to run real accessibility tests — Playwright keyboard interactions, axe-core scanning, visual regression, and WCAG 2.2 compliance checks. The measurement layer that feeds evidence into a11y-critic reviews.

Orchestrate the a11y accessibility lifecycle: scout → plan → critique → [perspective audit] → test → critique. Dual-mode: full lifecycle automation or step-by-step dispatch. Spawns specialist agents at depth-1 from the main session.

Deep accessibility review from 7 access perspectives — activated by escalation from a11y-planner or a11y-critic when one or more perspectives are flagged at MEDIUM or HIGH alarm level.

Refresh docs/data payloads and verify GitHub Pages dashboard publishing artifacts. Use when user asks why pages are stale, missing rows, or not reflecting newest pipeline runs.

Generate high-value opportunity alert outputs and summaries. Use when user asks for top matches, alert thresholds, or refreshed docs/data alert intelligence.

Build and refresh recompete risk outputs for contractor cohorts. Use when user asks for recompete discovery, expiring awards, Rule-of-Two screening, benchmark deltas, or docs/data/recompetes.json updates.

Refresh USASpending enrichment artifacts (vendor landscape, trends, and contract officer intelligence). Use when user asks for market intelligence context or enrichment reruns.

Dispatcher for Drupal accessibility guidance. Use when generating, reviewing, or modifying Drupal code, theming, JavaScript, or test coverage with accessibility implications, or when drafting accessibility issues for the issue queue. Routes work to a specialised sub-skill based on file type or task — server-side Form API (drupal-a11y-fapi), DOM and CSS (drupal-a11y-dom), interaction and testing (drupal-a11y-dynamic), or QA and issue authoring (drupal-a11y-qa). Enforces Drupal Accessibility Coding Standards, WCAG 2.2 AA (including the new SC 2.5.8 24×24 px target size), Drupal-native hiding patterns over hand-rolled ARIA, and the move from Nightwatch to Playwright plus Axe-core inside PHPUnit.