drupal-a11y-patch-evallisted

# Drupal Accessibility Patch Evaluator Evaluate a Drupal accessibility patch end-to-end: reproduce the baseline failure, apply the patch, verify the fix, record manual/AT evidence, gate on a critic review, and produce an upstream-ready handoff. This skill governs one patch and one accessibility issue pattern per packet. **Use this when**: a Drupal accessibility patch needs independent evidence before being filed upstream. The skill parameterizes all environment paths — supply your machine-specific values at the start of each session. ## 1. When to Use / Required Inputs Before starting an evaluation session, the operator must supply: | Input | Notes | |---|---| | `RUNTIME_REPO_PATH` | Absolute path to the DDEV runtime clone. Do not use the source clone after Composer install mutates it. | | `DDEV_PROJECT` | DDEV project name (e.g. `drupal-core`). Machine-specific — do not hardcode in packets. | | `BASE_URL` | Full base URL including port (e.g. `http://DDEV_PROJECT.ddev.site:PORT`). Set as `DRUPAL_BASE_URL` for the evaluator. | | `PATCHES_DIR` | Path to the patches directory relative to the runtime clone root. | | `LEDGER_PATH` | Path to the TODO ledger (default: `docs/drupal-patch-evaluations/STATUS.md`). | | `PACKET_DIR` | Directory where packet files live (e.g. `docs/drupal-patch-evaluations/`). | Paths in the ledger are machine-specific; this skill parameterizes them. Never record absolute machine paths in the upstream handoff block or in Drupal.org issue content. ##