Review markdown files for accessibility issues and provide prioritized linting commands.
npx skills add https://github.com/dallay/opencode-docker --skill markdown-a11y
Please help me install this Agent Skill. Skill: markdown-a11y Source: https://github.com/dallay/opencode-docker/tree/main/config/skills/markdown-a11y Command: npx skills add https://github.com/dallay/opencode-docker --skill markdown-a11y
Ensures markdown documentation is readable and navigable for people using assistive technologies by identifying accessibility issues that are commonly overlooked in READMEs, docs, and profiles.
Review README.md for markdown accessibility and return a prioritized list of actionable fixes for images, headings, links, lists, emoji, and plain language.
High-intent search queries and answers about installing and using this skill.
To check markdown files for accessibility issues, review documentation pages and READMEs to enforce descriptive link text, meaningful image alt text, correct heading hierarchy, proper list markup, and restrained emoji use for screen reader compatibility.
Markdown accessibility problems that affect screen reader navigation include skipped heading levels, fake headings, generic link text like "here", missing image alt text, and improper list markup, all of which disrupt assistive technology navigation.
Fix heading hierarchy and missing alt text in documentation by identifying skipped heading levels and flagging filename-based or empty alt text, then replacing them with correct sequential markup and concise, meaningful image descriptions.
You can use markdownlint to enforce accessible heading and link standards by applying practical linting commands that validate descriptive link text, correct heading hierarchy, and proper list markup changes in your markdown files.
Excessive emoji use impacts markdown accessibility because screen readers announce every emoji, which disrupts the reading flow; flagging meaning-bearing emoji and rewriting with plain language ensures inclusive documentation.
The best way to audit a GitHub profile README for inclusive language is to review the markdown for screen reader compatibility, checking for descriptive links, proper list markup, and plain language rewrites to ensure accessible documentation.
Community-AccessAudit markdown documentation for WCAG accessibility compliance and generate a report.
HomericIntelligenceValidate markdown files for formatting, links, and style compliance using markdownlint-cli2.
ghalacticAnalyzes readability of technical content for accessibility and inclusive-language issues.
dodygAudit markdown files for WCAG accessibility violations with severity scores.
