feat(adventure): add The Accessibility Nightmare

[offon-data-refresh]

create: The Accessibility Nightmare

Auto-synced from the challenges repo.

Source: https://github.com/off-on-dev/open-source-challenges/tree/main/adventures/accessibility-nightmare

Levels in this PR: beginner

---

Before merging

• Check the contributor: block in src/data/adventures/accessibility-nightmare/adventure.yaml. It is synced from
  docs/index.yaml in the challenges repo; add it by hand only if the sync log says none was found.

  contributor:
    name: "Full Name"
    url: "https://example.com"
    about: "One sentence bio."

• Confirm month: is correct for the planned release
• Set community_category_id: in src/data/adventures/accessibility-nightmare/adventure.yaml (look up at https://community.offon.dev/categories.json) - [ ] Update rewards.deadline: from TODO to ISO 8601 (e.g. 2026-07-01T23:59:00+01:00)
• Review meta_description: in adventure.yaml — auto-generated from the first level summary; refine to cover all levels in one technical sentence (max 160 chars)
• Review topics: on each level, auto-set to all adventure tags, refine to level-specific subset if needed
• Update discussion_url: in each level once the Discourse threads are created
• Update discussionUrl in each *-posts.json stub

Manual steps (only if needed)

• If a level's architecture_diagram SVG was not auto-fetched (check the sync logs for a warning), add the SVG manually to src/assets/diagrams/ and add architecture_diagram: <file>.svg to that level in adventure.yaml - [ ] If a level has an architecture_diagram but no diagram_alt, add diagram_alt: to that level in adventure.yaml with a one-sentence description of the diagram - [ ] Run node scripts/refresh-leaderboard.mjs after community_category_id is set
• Run node scripts/refresh-discussions.mjs after discussionUrl values are set

Routes & sitemap

Routes are generated from adventure.yaml by the Astro content collection
at build time (getStaticPaths) — there is nothing to regenerate or commit.
The leaderboard registry derives from adventure.yaml at runtime via buildAdventureCategories() in refresh-leaderboard.mjs -- nothing to hand-maintain.

Checks

npm run sync && npm run build && npm run test:e2e

[github-actions]

PR Preview Action v1.8.1
Preview removed because the pull request was closed.
2026-09-08 08:19 UTC