From ccaa4d0bf00191612cb36731a87c45602392cd52 Mon Sep 17 00:00:00 2001 From: Roberto Perez Date: Thu, 26 Mar 2026 14:29:43 -0400 Subject: [PATCH] Add UI navigation plain language rule to markdown accessibility instructions --- instructions/markdown-accessibility.instructions.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/instructions/markdown-accessibility.instructions.md b/instructions/markdown-accessibility.instructions.md index ecf645d56..1c43665a5 100644 --- a/instructions/markdown-accessibility.instructions.md +++ b/instructions/markdown-accessibility.instructions.md @@ -38,6 +38,8 @@ Good: `Read my blog post "[Crafting an accessible resume](https://example.com)"` - Flag unnecessarily complex or jargon-heavy language that could be simplified. - Favor short sentences, common words, and active voice. - Flag long, dense paragraphs that could be broken into smaller sections or lists. +- When describing UI navigation, write actions as sequential steps in plain language first (e.g., "open Settings, then select Preferences"). Use generic, stable labels rather than icon names or visual descriptions. +- A parenthetical visual reference may follow as supplemental context (e.g., "(gear icon > Preferences)"), but never use visual breadcrumb notation or icon names as the sole way to describe a navigation path. - When suggesting plain language improvements, present them as recommendations for the author to review. Language decisions require understanding of audience, context, and tone. ## 5. Lists and Emoji Usage