Answer: When making UI changes in Zed, you should check that all keyboard shortcuts work as intended, that shortcuts are discoverable (tooltips, menus, docs), that the feature is usable without a mouse (keyboard-only navigation), that all mouse actions work (drag, context menus, resizing, scrolling), that it looks great in light and dark mode themes, and that hover states and focus indicators are clear and consistent. Status: Overdue (check was due 2026-11-20T13:40:16Z and has not succeeded) Entry: tool/zed/features/ui-accessibility-ergonomics-checklist Revision: 1 Digest: sha256:e9db161b32227ee1 (changes whenever the content changes) Timeline: Created: 2026-11-15T13:59:16Z Last changed: 2026-11-15T13:59:16Z Last verified: 2026-11-19T13:40:16Z Next check: 2026-11-20T13:40:16Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Keyboard shortcuts | Do all keyboard shortcuts work as intended? | [1] | 2026-11-19 Shortcut discoverability | Are shortcuts discoverable (tooltips, menus, docs)? | [1] | 2026-11-19 Keyboard-only navigation | Is it usable without a mouse (keyboard-only navigation)? | [1] | 2026-11-19 Mouse actions | Do all mouse actions work (drag, context menus, resizing, scrolling)? | [1] | 2026-11-19 Light and dark mode | Does the feature look great in light and dark mode themes? | [1] | 2026-11-19 Hover and focus indicators | Are hover states and focus indicators clear and consistent? | [1] | 2026-11-19 Sources: [1] Zed Industries. "zed.dev/docs/development/ui-checklist.md". https://zed.dev/docs/development/ui-checklist.md Role: primary. Accessed: 2026-11-19T13:40:16Z Quote: "Do all keyboard shortcuts work as intended?" (Supports: Keyboard shortcuts) Quote: "Are shortcuts discoverable (tooltips, menus, docs)?" (Supports: Shortcut discoverability) Quote: "Is it usable without a mouse (keyboard-only navigation)?" (Supports: Keyboard-only navigation) Quote: "Do all mouse actions work (drag, context menus, resizing, scrolling)?" (Supports: Mouse actions) Quote: "Does the feature look great in light and dark mode themes?" (Supports: Light and dark mode) Quote: "Are hover states and focus indicators clear and consistent?" (Supports: Hover and focus indicators) Snapshot SHA-256: 32de04e8da09c4c34294aaa0f36e5c64e518b3e2baf29a95868ba107f216f3c4 (captured 2026-11-13T04:01:50Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-15T13:59:16Z, so the values verified then were kept. Cross-check: not-available at 2026-11-19T13:40:16Z. No independent second source is configured for this entry Last successful check: 2026-11-19T13:40:16Z Last attempt: 2026-11-19T13:40:16Z Notes and limitations: Extracted automatically from a single official source (section "Accessibility / Ergonomics {#accessibility-ergonomics}"). Human-readable page: https://zed.dev/docs/development/ui-checklist.html Related: https://latestn.com/tool/zed/features/ui-performance-requirements What performance requirements must Zed UI interactions meet? https://latestn.com/tool/zed/features/ui-platform-consistency-checklist What should I verify for Zed UI consistency across Windows, Linux, and macOS? https://latestn.com/tool/zed/features/ui-responsiveness-checklist How should Zed UI changes handle narrow panes, small displays, and high-DPI screens? https://latestn.com/tool/zed/features/theme-files-location Where do theme files go in a Zed extension? https://latestn.com/tool/zed/features/theme-json-structure What fields does a Zed theme JSON file need? https://latestn.com/tool/zed/features/toolchain-collaboration-access Can guests or collaborators change the active toolchain in a shared Zed project? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-15T13:59:16Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/zed/features/ui-accessibility-ergonomics-checklist/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/zed/features/ui-accessibility-ergonomics-checklist POST: https://latestn.com/dispute/tool/zed/features/ui-accessibility-ergonomics-checklist with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/zed/features/ui-accessibility-ergonomics-checklist?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What should I check for accessibility and keyboard usability when making UI changes in Zed? Revision 1, last verified 2026-11-19T13:40:16Z. https://latestn.com/tool/zed/features/ui-accessibility-ergonomics-checklist (accessed 2026-11-21T09:58:08Z). @misc{LatestN_tool_zed_features_ui_accessibility_ergonomics_checklist_r1, title = {What should I check for accessibility and keyboard usability when making UI changes in Zed?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/zed/features/ui-accessibility-ergonomics-checklist}}, note = {Revision 1; digest sha256:e9db161b32227ee1; last verified 2026-11-19T13:40:16Z; accessed 2026-11-21T09:58:08Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/zed/features/ui-accessibility-ergonomics-checklist