## Summary Follow-up of #3586434. @kati.vera found this in her accessibility audit on #3586434 (finding F2). The **Content** field on the context item form uses the markdown editor from the AI module (MDXEditor). When the caret is in the editor, Tab and Shift+Tab do not move focus out of the editor. A keyboard-only user cannot get to the fields after **Content**, so they cannot complete the form. This fails WCAG 2.2 SC 2.1.2 No Keyboard Trap (Level A). The fix belongs in the AI module, in project/ai#3586814. That issue is open and has no milestone, and its MR (project/ai!372) is not merged, so CCC 1.0.0 will ship with this problem. The triage on #3586434 planned a known-issue note in the CCC 1.0.0 release notes. This issue also adds the note to the docs, because the docs stay after the release notes are gone. Today: * `README.md` and the Content section of `docs/features/context_items.md` do not mention the problem. * The 1.0.0 release issue #3586602 has no task for it. CCC adds the editor to every context item form (`AiContextItemForm` sets `data-mdxeditor` on the Content textarea). There is no setting to use a plain textarea. The triage on #3586434 planned this note for 1.0.0. Releases add no commits, so the docs change must merge before the 1.0.0 tag to be in 1.0.0. The code freeze is on 9 November 2026. ## Proposed resolution * [x] Add a top-level `docs/known-issues.md` page, and add it to the `mkdocs.yml` nav next to "Upgrade policy". First entry: the Content editor keyboard trap. Say what happens, who it affects, the workaround (press Escape, then Tab or Shift+Tab, or use Source mode), and link project/ai#3586814. * [x] Add one sentence to `README.md` and `docs/index.md` that links to the known issues page. Do not repeat known issues on other pages. * [ ] Add the same known issue to the 1.0.0 release notes when the release is created (#3586602). This is not part of the MR. Questions: 1. [x] Is there a keyboard method that leaves the editor today, for example the Source mode, or Escape and then Tab? If yes, document it as the workaround. If no, say that there is no keyboard workaround yet. **Yes.** Tested on 2026-10-24 in Chrome on macOS with key presses (no screen reader). In rich text mode, Tab inserts a tab character and Shift+Tab stays in the editor. Escape and then Tab moves focus to the next control, and Escape and then Shift+Tab moves it to the editor toolbar. In Source mode, Tab moves focus out of the editor. 2. [x] Do we also add a "Known issues" section to `README.md`, or only to the docs page and the release notes? **No.** One known issues page in the docs, with a link from `README.md` and `docs/index.md`. 3. [x] Do we want a CCC option that shows a plain textarea instead of the editor until project/ai#3586814 is fixed? If yes, that is a separate issue for 1.0.1. **No.** The keyboard workaround (Escape, then Tab, or Source mode) is enough until the AI module is fixed. ## Notes * When an AI release fixes project/ai#3586814, remove the entry from the known issues page in a new issue. #3586565 uses the same approach for the editor min-height workaround. ## Stakeholders * **Owner:** @kepol * @kati.vera: found the problem in the accessibility audit on #3586434 <details><summary>opus notes</summary> * Checked on 2026-10-24 with read-only GitLab calls and `git grep` on `origin/1.0.x` at `913c3c2`. That commit includes the README and docs update for 1.0.0 from #3586612, which merged on 2026-10-24. * No ai_context issue covers this note. Searches (open and closed): "known issue", "release notes", "1.0.0 release", "MDXEditor", "keyboard trap", "3586814". * `git grep -i -E "3586814|keyboard trap|known issue"` on `README.md` and `docs/` returns nothing. * project/ai#3586814 is open (`toBeTriaged`, no milestone, no MR). It also lists F3, F7 (Block type), F10 and F11 for the editor, so those need no CCC issue. * `src/Form/AiContextItemForm.php:348-353` sets `data-mdxeditor` on every context item form. There is no condition. * The triage said "Known issue in the CCC 1.0.0 release notes". Release notes are not a commit. If you want only the release-notes note, do not file this issue, and add the known issue when you write the 1.0.0 release notes. * The same triage planned F5 for 1.0.0, but #3586607 is on the 1.0.1 milestone. Check that this is still the plan. * The #3586434 description asks for each follow-up to be related to #3586433 too, so the quick actions include it. </details> > [!note] > Check the one that best describes your usage, or leave all unchecked if AI was not significantly used. > > * [ ] AI **Assisted Issue** \ > _Mainly written by a human; AI used for partial generation under full human supervision._ > > * [x] AI **Generated Issue** \ > _Mainly generated by AI, reviewed and approved by a human before this issue was created._