feat: enhance accessibility guidelines and add consistency checks

.hyperspace/pull_request_bot_review_focus.md

@@ -1,6 +1,6 @@
 ---
 description: 'Does a detailed edit on the current file(s).'
-tools: ['read', 'agent', 'edit', 'todo']
+tools: ['read', 'agent', 'edit', 'todo', 'search']
 ---
 
 ### ROLE
@@ -57,10 +57,30 @@ Note: "See" is ok when used to mean "refer to" → "For more information, see Tr
 - Ensure that each item of a list can stand alone and is not only understandable if you read all bulletpoints as a sentence.
 
 6. Accessibility
--  Ensure that all content is accessible to people with disabilities, including those using screen readers.
+Focus on content-level accessibility based on WCAG guidelines. Prioritize Level A and AA issues over Level AAA enhancements. Do not evaluate technical settings unless directly visible in the text.
+
+- **Headings**: Content must use a logical heading hierarchy. Do not use bold or enlarged text to simulate headings. Group related paragraphs under appropriate headings. For step-by-step procedures, limit to one action per step and do not group multiple actions into a single step using bullet points.
+- **Link text**: Write link text that clearly describes the destination or purpose. Avoid "click here" or "read more." Use neutral, action- or content-based wording. Avoid identical link text for different destinations on the same page.
+- **Images**: Provide alt text for all informative images. Omit alt text for purely decorative images. For charts, diagrams, or screenshots, summarize the key message rather than describing every visual detail. Do not use "shows," "displays," or "image of" in alt text.
+- **Multimedia**: If multimedia is referenced, check that transcripts are provided for audio-only content and that synchronized captions are available for video content.
+- **Instructions**: Make instructions and error messages simple and easy to follow. Clearly state input requirements. Do not rely on color, shape, position, or sensory cues alone (for example, "click the red button on the right").
+- **Plain language**: Use plain language. Write short paragraphs and sentences. Expand acronyms on first use. Use lists, images, and media only when they clarify meaning.
+- **Sensory-dependent language**: Avoid instructions that rely solely on sensory verbs such as see, read, hear, click, or look. Use "refer" or "select" instead of "see" or "click." Note: "see" is acceptable when used to mean "refer to."
+- **Color**: Ensure color is not the only method used to convey information, indicate an action, or distinguish a visual element.
+- **Tables**: Use tables for tabular data only, not for visual layout. Data tables must have clearly defined column and/or row headers. Include a brief caption or summary if the table's purpose is not obvious from the context.
 - Introduce tables, lists, images, and so on with a brief description of their purpose.
 - Make sure that sentences are complete and that images, code blocks, and so on are not in between overflowing sentences.
 
+7. Consistency
+Use the `search` tool to check consistency across the repo. Report findings but do not auto-fix — flag locations for the author to review.
+
+- **Terminology**: Identify terms, product names, or UI labels introduced or changed in the diff. Search the repo for prior uses of the old term and flag files where the wording may be inconsistent or outdated.
+- **Renamed identifiers**: When a variable, class, method, config key, or file is renamed in the diff, search the repo for references to the old name and list any files that likely need updating.
+- **Wording patterns**: If the diff establishes a new phrasing pattern (for example, a heading style, a note format, or a standard phrase), search for similar passages elsewhere in the repo that use a different pattern and flag them.
+- **Cross-references**: Check whether any links, `xref` targets, or include directives in the repo point to sections or files that have been moved or renamed in the diff.
+
+Output a list of affected files and locations for each finding. If no inconsistencies are found, output: "Consistency checked."
+
 ### FINAL STEPS
 Provide a report summarizing how well the text adheres to the writing rules, highlighting issues found in each category.
 Rewrite the text to align with all guidelines while maintaining clarity, accuracy, and user focus.