create-website-build-kit 0.1.18 → 0.1.20

package/template/package.json

@@ -52,6 +52,7 @@
     "@astrojs/check": "^0.9.10",
     "@cloudflare/workers-types": "^5.20260815.1",
     "pa11y-ci": "^4.1.1",
+    "puppeteer": "^24.43.1",
     "sharp": "^0.35.3",
     "turndown": "^7.2.4",
     "typescript": "^6.0.3",

package/template/scripts/a11y-evidence.mjs

@@ -33,7 +33,7 @@ import { tmpdir } from 'node:os';
 import { join } from 'node:path';
 import { createRequire } from 'node:module';
 
-import { SCHEMES, configForScheme } from './lib/schemes.mjs';
+import { SCHEMES, assertForced, configForScheme } from './lib/schemes.mjs';
 
 const require = createRequire(import.meta.url);
 
@@ -103,10 +103,22 @@ const runScheme = (scheme) => {
   const file = join(tmp, `${scheme}.json`);
   writeFileSync(file, JSON.stringify(configForScheme(config, scheme), null, 2));
 
-  /* --config supplies the forced-scheme defaults either way; --sitemap only
-     replaces where the URL list comes from. */
+  /*
+   * --config supplies the forced-scheme defaults either way; --sitemap only
+   * replaces where the URL list comes from.
+   *
+   * ⚠ NO `--standard` HERE. That is a `pa11y` option, not a `pa11y-ci` one, and
+   *   passing it made the CLI exit immediately with `unknown option
+   *   '--standard'` — which this function reports as "pa11y-ci could not run.
+   *   Start the site first", pointing at the wrong problem entirely. So the
+   *   documented way to produce a pack against a DEPLOYED host had never once
+   *   worked; it was the form nobody ran, because the only excuse for not
+   *   testing this script was that it needed a deployment. The standard reaches
+   *   pa11y through `defaults.standard` in the config, which is where the
+   *   no-host form has always read it from.
+   */
   const args = host
-    ? ['pa11y-ci', '--config', file, '--sitemap', `${host}/sitemap-index.xml`, '--standard', standard, '--json']
+    ? ['pa11y-ci', '--config', file, '--sitemap', `${host}/sitemap-index.xml`, '--json']
     : ['pa11y-ci', '--config', file, '--json'];
 
   try {
@@ -130,6 +142,21 @@ const runScheme = (scheme) => {
   }
 };
 
+/*
+ * ⚠ THE SAME PROOF check-a11y MAKES, AND IT MATTERS MORE HERE. This file
+ *   writes a dated document stating which schemes were measured. Under the
+ *   flag that did nothing, that document was wrong in writing — an evidence
+ *   pack asserting a dark-palette pass that never happened. Refuse rather than
+ *   write it.
+ */
+for (const scheme of SCHEMES) {
+  const why = await assertForced(scheme);
+  if (why) {
+    console.error(`${RED}✗${RESET} ${why}\n`);
+    process.exit(1);
+  }
+}
+
 const passes = SCHEMES.map((scheme) => {
   const report = runScheme(scheme);
   const rows = Object.entries(report.results).map(([url, issues]) => ({

package/template/scripts/check-a11y.mjs

@@ -20,7 +20,7 @@ import { existsSync, mkdtempSync, readFileSync, writeFileSync } from 'node:fs';
 import { tmpdir } from 'node:os';
 import { join } from 'node:path';
 
-import { SCHEMES, configForScheme } from './lib/schemes.mjs';
+import { SCHEMES, assertForced, configForScheme } from './lib/schemes.mjs';
 
 const RESET = '\x1b[0m';
 const RED = '\x1b[31m';
@@ -51,6 +51,21 @@ if (!schemes.length) {
   process.exit(1);
 }
 
+/*
+ * ⚠ PROVE THE SCHEME FORCING WORKS BEFORE MEASURING ANYTHING. The previous
+ *   flag was one Chrome silently ignores, so this loop ran twice against the
+ *   machine's own palette and reported "clean in light and dark". Refusing here
+ *   costs one Chrome launch per scheme and is the only thing standing between
+ *   that sentence and the truth. See scripts/lib/schemes.mjs.
+ */
+for (const scheme of schemes) {
+  const why = await assertForced(scheme);
+  if (why) {
+    console.error(`${RED}✗${RESET} ${why}\n`);
+    process.exit(1);
+  }
+}
+
 const base = JSON.parse(readFileSync(CONFIG, 'utf8'));
 const urlCount = (base.urls ?? []).length;
 const dir = mkdtempSync(join(tmpdir(), 'a11y-'));