diff --git a/docs/README.instructions.md b/docs/README.instructions.md
index 73250e54..8a9e06eb 100644
--- a/docs/README.instructions.md
+++ b/docs/README.instructions.md
@@ -113,6 +113,7 @@ Team and project-specific instructions to enhance GitHub Copilot's behavior for
| [Makefile Development Instructions](../instructions/makefile.instructions.md)
[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fmakefile.instructions.md)
[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fmakefile.instructions.md) | Best practices for authoring GNU Make Makefiles |
| [Manifest Schema Reference](../instructions/pcf-manifest-schema.instructions.md)
[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fpcf-manifest-schema.instructions.md)
[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fpcf-manifest-schema.instructions.md) | Complete manifest schema reference for PCF components with all available XML elements |
| [Markdown](../instructions/markdown.instructions.md)
[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fmarkdown.instructions.md)
[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fmarkdown.instructions.md) | Documentation and content creation standards |
+| [Markdown Accessibility Review Guidelines](../instructions/markdown-accessibility.instructions.md)
[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fmarkdown-accessibility.instructions.md)
[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fmarkdown-accessibility.instructions.md) | Markdown accessibility guidelines based on GitHub's 5 best practices for inclusive documentation |
| [MCP-based M365 Copilot Development Guidelines](../instructions/mcp-m365-copilot.instructions.md)
[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fmcp-m365-copilot.instructions.md)
[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fmcp-m365-copilot.instructions.md) | Best practices for building MCP-based declarative agents and API plugins for Microsoft 365 Copilot with Model Context Protocol integration |
| [Memory Bank](../instructions/memory-bank.instructions.md)
[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fmemory-bank.instructions.md)
[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fmemory-bank.instructions.md) | Bank specific coding standards and best practices |
| [Microsoft 365 Declarative Agents Development Guidelines](../instructions/declarative-agents-microsoft365.instructions.md)
[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fdeclarative-agents-microsoft365.instructions.md)
[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fdeclarative-agents-microsoft365.instructions.md) | Comprehensive development guidelines for Microsoft 365 Copilot declarative agents with schema v1.5, TypeSpec integration, and Microsoft 365 Agents Toolkit workflows |
diff --git a/instructions/markdown-accessibility.instructions.md b/instructions/markdown-accessibility.instructions.md
new file mode 100644
index 00000000..5c4f3d62
--- /dev/null
+++ b/instructions/markdown-accessibility.instructions.md
@@ -0,0 +1,71 @@
+---
+description: 'Markdown accessibility guidelines based on GitHub''s 5 best practices for inclusive documentation'
+applyTo: '**/*.md'
+---
+
+# Markdown Accessibility Review Guidelines
+
+When reviewing markdown files, check for the following accessibility issues based on GitHub's [5 tips for making your GitHub profile page accessible](https://github.blog/developer-skills/github/5-tips-for-making-your-github-profile-page-accessible/). Flag violations and suggest fixes with clear explanations of the accessibility impact.
+
+## 1. Descriptive Links
+
+- Flag generic link text such as "click here," "here," "this," "read more," or "link."
+- Link text must make sense when read out of context, because assistive technology can present links as an isolated list.
+- Flag multiple links on the same page that share identical text but point to different destinations.
+- Bare URLs in prose should be converted to descriptive links.
+
+Bad: `Read my blog post [here](https://example.com)`
+Good: `Read my blog post "[Crafting an accessible resume](https://example.com)"`
+
+## 2. Image Alt Text
+
+- Flag images with empty alt text (`![]()`) unless they are explicitly decorative.
+- Flag alt text that is a filename (e.g., `img_1234.jpg`) or generic placeholder (e.g., `screenshot`, `image`).
+- Alt text should be succinct and descriptive. Include any text visible in the image.
+- Use "screenshot of" where relevant, but do not prefix with "image of" since screen readers announce that automatically.
+- For complex images (charts, infographics), suggest summarizing the data in alt text and providing longer descriptions via `` tags or linked content.
+- When suggesting alt text improvements, present them as recommendations for the author to review. Alt text requires understanding of visual content and context that only the author can properly assess.
+
+## 3. Heading Hierarchy
+
+- There must be only one H1 (`#`) per document, used as the page title.
+- Headings must follow a logical hierarchy and never skip levels (e.g., `##` followed by `####` is a violation).
+- Flag bold text (`**text**`) used as a visual substitute for a proper heading.
+- Proper heading structure allows assistive technology users to navigate by section and helps sighted users scan content.
+
+## 4. Plain Language
+
+- 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 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
+
+### Lists
+
+- Flag emoji or special characters used as bullet points instead of proper markdown list syntax (`-`, `*`, `+`, or `1.`).
+- Flag sequential items in plain text that should be structured as a proper list.
+- Proper list markup allows screen readers to announce list context (e.g., "item 1 of 3").
+
+### Emoji
+
+- Flag multiple consecutive emoji, which are disruptive to screen reader users since each emoji name is read aloud in full (e.g., "rocket" "sparkles" "fire").
+- Flag emoji used to convey meaning that is not also communicated in text.
+- Emoji should be used sparingly and thoughtfully.
+
+## Review Priority
+
+When multiple issues exist, prioritize in this order:
+
+1. Missing or empty alt text on images
+2. Skipped heading levels or missing H1
+3. Non-descriptive link text
+4. Emoji used as bullet points or list markers
+5. Plain language improvements
+
+## Review Tone
+
+- Explain the accessibility impact of each issue, specifying which users are affected (e.g., screen reader users, people with cognitive disabilities, non-native speakers).
+- Do not remove personality or voice from the writing. Accessibility and engaging content are not mutually exclusive.
+- Keep suggestions actionable and specific.
\ No newline at end of file