content-design

Review web content for plain language, heading order, and link text.

39|2|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/mgifford/accessibility-skills --skill content-design-mgifford
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: content-design
Source: https://github.com/mgifford/accessibility-skills/tree/main/skills/content-design
Command: npx skills add https://github.com/mgifford/accessibility-skills --skill content-design-mgifford

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Web content often fails accessibility standards, creating barriers for people with cognitive, visual, and language differences. This guide helps ensure copy is clear, well-structured, and usable by the broadest audience.

Core Features & Use Cases

  • Enforces plain language and concise wording to improve readability.
  • Promotes a logical heading hierarchy and descriptive, context-rich link text.
  • Provides guidance for writing labels, error messages, headings, and instructions across web pages.

Quick Start

Paste your web content draft and ask for a plain-language accessibility review.

Frequently Asked Questions about content-design

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

FAQPage Schema
How do I write web content that meets accessibility standards?

Accessible web content requires plain language, logical heading hierarchy, and meaningful link text to ensure readability for users with cognitive, visual, and language differences. Applying structured writing during drafting or editing ensures your copy is usable by the broadest audience.

What is the best way to review headings and link text for web accessibility?

Reviewing headings and link text for web accessibility involves checking for logical heading order and context-rich descriptive links. Enforcing structured writing ensures labels and error messages remain clear and readable across all web pages and documents.

How do I write plain language error messages and instructions for websites?

Writing plain language error messages requires concise wording and clear instructions. By enforcing structured writing and readability checks during editing, you ensure labels and error messages are accessible and easily understood by all users.

Does plain language writing help with web content readability?

Plain language writing significantly improves web content readability by enforcing concise wording and clear structure. This approach ensures your copy, headings, and labels are accessible to people with cognitive, visual, and language differences.

Can I use this to review existing web copy for accessibility barriers?

You can review existing web copy for accessibility barriers by pasting your draft content for a plain-language accessibility review. This process checks headings, labels, and link text to enforce readability and logical structure across documents.

Why does my web content fail accessibility standards for headings and links?

Web content fails accessibility standards when headings lack logical order and link text is not descriptive or context-rich. Enforcing plain language and structured writing during editing ensures your copy meets readability requirements for users with diverse needs.