## Problem/motivation Parent: #3586433+s _**THIS ISSUE IS RESERVED FOR MEARRA (KATI) - PING KRISTEN IN DRUPAL SLACK YOU WANT TO WORK ON THIS AND AREN'T KATI :smile:**_ _**THIS ISSUE WAS GENERATED WITH GROK AND NEEDS HUMAN REVIEW BEFORE PROCEEDING.**_ This is the first-batch area **#2**. This is an **area audit**, not a confirmed bug. Run the checks below on the Overview dashboard and file each confirmed finding as its own follow-up (one WCAG success criterion per issue). Do not change code from reading the template or from AI review alone. CCC has had keyboard/DOM work and some automated announce tests on other screens. **No one has done a human screen-reader pass** on this page. ## What this page is `/admin/config/ai/context/overview` is the CCC onboarding dashboard: - Welcome heading and short explanation - **Show this overview page** checkbox (users with *Administer AI Context* only). Change saves over AJAX; unchecking redirects to the context items list - **Getting Started** steps (copy changes if published items or agent settings exist) - **Quick Links** to items, add item, general settings, and agents - **Documentation** links that open in a new tab, with visually-hidden “(opens in new tab)” text The Drupal page title is the `h1`. The welcome heading in the template is an `h2`, then section `h3`s. That heading order is expected. ## Scope **In scope** - Landmarks, heading order, lists, and link names - Keyboard tab order and visible focus - New-tab documentation links (announce “opens in new tab”; `target="_blank"` plus `rel="noopener noreferrer"`) - The overview checkbox: label, description, keyboard use, and what happens when it is unchecked (redirect to `/items`) - Reflow at 200% zoom (the three sections are a CSS grid) - Contrast, forced colours, and target size on links/checkbox - Screen-reader pass of the welcome text, Getting Started list, Quick Links, and Documentation list **Out of scope for this child** - Context item listing, add/edit form, and per-agent form - Extensions and scope settings (separate first-batch children) - Redesigning Getting Started copy - Re-checking tooltip/icon work from [#3586302](https://git.drupalcode.org/project/ai_context/-/work_items/3586302) (that is on the listing, not this page) The empty Getting Started state (“There are no published context items”) is enough. If the site already has items or agent settings, note which state you saw. You do not need to create sample content. ## Test environment Use Drupal CMS 2.1+, Gin admin theme, and ai_context `1.0.x`. Record the rest when you file findings. See CCC project page for [installation instructions](https://www.drupal.org/project/ai_context#install-testing-steps). | Item | Value | |------|-------| | Drupal CMS | [version] | | Theme | Gin | | CCC / `ai_context` | `1.0.x` | | Browser | [e.g. Chrome 139] | | OS | [e.g. macOS 15 / Windows 11] | | AT | NVDA + Chrome **or** VoiceOver + Safari | | Viewport | desktop (~1280) and a narrow width | | Color mode | light and dark if the theme supports it | | Tool | `@axe-core/playwright` (note versions) | ## Steps 1. Log in as a user who can administer CCC (`admin` / `admin` is fine on the local DDEV site). 2. Open `/admin/config/ai/context/overview`. If you get 403, enable **Show overview page** at `/admin/config/ai/context/settings/general`. 3. Run axe on the page (WCAG 2.2 AA tags: `wcag2a`, `wcag2aa`, `wcag21aa`, `wcag22aa`) in light and dark if available. 4. Keyboard-only: tab through local tasks, the checkbox and Save, Getting Started, Quick Links, and Documentation. Confirm a visible focus ring and a sensible order. 5. Screen reader: read the page. Confirm the welcome `h2` / section `h3`s, that lists are announced as lists, that Quick Links make sense from the link text alone, and that each Documentation link includes “opens in new tab”. 6. Zoom to 200% (and 400% if the three columns feel cramped). Confirm the sections stack and nothing is clipped or off-screen. 7. Optional: uncheck **Show this overview page** (or use Save). You should land on `/admin/config/ai/context/items`. Re-enable the setting under **Settings → General** before you continue. Do not leave it disabled. ## How to file findings Each confirmed issue gets its own ticket. Use the field block from [Accessibility Bug Reporting Best Practices](https://mgifford.github.io/ACCESSIBILITY.md/examples/ACCESSIBILITY_BUG_REPORTING_BEST_PRACTICES.html): Bug ID, URL, selector, WCAG SC, tool + rule ID, severity, HTML snippet, steps, and the same scan command used to find it. Prefix follow-up titles with `[Accessibility]` and relate them to this issue and to #3586433. Do not file `incomplete` / needs-review axe results as bugs until a human confirms them. Do not file from template reading or AI review alone. ## Remaining tasks - [ ] Axe scan on this page (light; dark if the theme supports it) - [ ] Keyboard-only walk - [ ] Screen-reader pass (NVDA+Chrome or VoiceOver+Safari) - [ ] 200% zoom (400% if reflow looks doubtful) - [ ] Forced-colours / Windows High Contrast if you can - [ ] File one-SC follow-ups for confirmed findings - [ ] Comment here with environment, which Getting Started state you saw, and “no findings” if the page is clean ## AI disclosure - [x] AI assisted issue