accessibility-writing

Create accessible documentation with plain language and structured headings.

1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/baphled/dotopencode --skill accessibility-writing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-writing
Source: https://github.com/baphled/dotopencode/tree/main/skills/accessibility-writing
Command: npx skills add https://github.com/baphled/dotopencode --skill accessibility-writing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of creating documentation and content that is understandable and usable by individuals with diverse needs, including those with visual impairments, cognitive disabilities, or who rely on assistive technologies.

Core Features & Use Cases

  • Clarity and Simplicity: Promotes plain language and avoids jargon.
  • Structured Content: Emphasizes logical heading hierarchies for better navigation.
  • Inclusive Language: Guides users on creating meaningful link text and providing descriptive alternatives for non-text elements.
  • Use Case: When writing a new user guide, this skill ensures that headings are correctly ordered, links are descriptive, and images have appropriate alt text, making the guide accessible to a wider audience.

Quick Start

Use the accessibility-writing skill to review the current draft of the README.md file for clarity and structure.

Frequently Asked Questions about accessibility-writing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write accessible documentation for users with disabilities?

Structure your content with a logical heading hierarchy to ensure accessible documentation. Proper heading order allows users relying on assistive technologies to navigate documents easily and understand the relationship between sections.

What is plain language and when should I use it for content creation?

Plain language is a writing approach that avoids jargon and promotes clarity and simplicity. Use it during content creation to make documentation understandable and usable by individuals with diverse cognitive needs and reading abilities.

How do I add descriptive context for non-text elements in documentation?

Add descriptive context for non-text elements by creating meaningful link text and providing descriptive alternatives for images. This inclusive content approach makes visual information accessible to users with visual impairments.

Can I use this approach to review an existing README.md file for clarity?

Yes, you can review an existing README.md file for clarity and structure using these accessibility principles. The process checks for correct heading order, descriptive links, and appropriate alt text to make the guide accessible.

What are the limitations of relying on plain language for accessible content?

Relying solely on plain language for accessible content is insufficient without logical structure. Accessible documentation also requires strict heading hierarchies and meaningful link text to be fully usable by assistive technologies.