accessible-content

What problem does it solve?

Words are interface. Every label, every heading, every error message is a design decision. This skill ensures content works for screen readers, for people reading in a second language, for people under stress, and for people who just need things to be clear.

Core Features & Use Cases

• Plain Language First: Emphasizes readability by using short sentences, common words, active voice, and avoiding jargon unless necessary with plain explanations.
• Heading Structure: Ensures a single, descriptive H1 and a logical H1→H2→H3 hierarchy for screen reader navigation.
• Form Labels & Instructions: Requires visible labels, proper ARIA associations, required-field indications, format hints, and error accessibility.
• Alt Text: Provides guidance for informative, decorative, and functional images, with detailed alternative descriptions when needed.
• Link Text & Errors: Encourages descriptive link text and error messages that explain the problem and the fix.
• Tables & Data: Recommends captions, proper table headers, and accessible data layouts.
• Content Review: Verifies labels, headings, link text, and error messages for accessibility.
• Integration: Works with related skills such as cognitive-accessibility and inclusive-personas to ensure audience awareness.

Quick Start

Audit your interface copy now by applying plain-language rules to labels, headings, and error messages to improve readability.