mirror of
https://github.com/github/awesome-copilot.git
synced 2026-04-30 20:25:55 +00:00
Revise accessibility instructions for clarity and detail (#1456)
This commit is contained in:
@@ -5,7 +5,7 @@ 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.
|
||||
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/) and the Smashing Magazine article [Improving The Accessibility Of Your Markdown](https://www.smashingmagazine.com/2021/09/improving-accessibility-of-markdown/). Flag violations and suggest fixes with clear explanations of the accessibility impact.
|
||||
|
||||
## 1. Descriptive Links
|
||||
|
||||
@@ -17,7 +17,7 @@ When reviewing markdown files, check for the following accessibility issues base
|
||||
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
|
||||
## 2. Image Alternative (alt) Text
|
||||
|
||||
- Flag images with empty alt text (e.g., ``) unless they are explicitly decorative.
|
||||
- Flag alt text that is a filename (e.g., `img_1234.jpg`) or generic placeholder (e.g., `screenshot`, `image`).
|
||||
@@ -56,6 +56,18 @@ Good: `Read my blog post "[Crafting an accessible resume](https://example.com)"`
|
||||
- Flag emoji used to convey meaning that is not also communicated in text.
|
||||
- Emoji should be used sparingly and thoughtfully.
|
||||
|
||||
## 6. Multimedia
|
||||
|
||||
- Provide captions for videos and transcripts for recorded audio.
|
||||
- Do not auto-play audio and video.
|
||||
- It's recommended that animated images and other animations are paused on page load.
|
||||
|
||||
## 7. Other
|
||||
|
||||
- Links: Avoid opening links in a new tab or window.
|
||||
- Bold and Italics: Screen readers often don't announce bold or italic emphasis, so critical information should not rely on this styling alone.
|
||||
- Tables: Use tables for data only. Do not use tables for page layout. Avoid nested tables. Avoid complex tables as they are difficult to represent in an accessible format in standard Markdown.
|
||||
|
||||
## Review Priority
|
||||
|
||||
When multiple issues exist, prioritize in this order:
|
||||
@@ -65,9 +77,11 @@ When multiple issues exist, prioritize in this order:
|
||||
3. Non-descriptive link text
|
||||
4. Emoji used as bullet points or list markers
|
||||
5. Plain language improvements
|
||||
6. Multimedia
|
||||
7. Other
|
||||
|
||||
## 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.
|
||||
- Keep suggestions actionable and specific.
|
||||
|
||||
Reference in New Issue
Block a user