skills.rest
Angusatgithub
AngusatgithubCOMMUNITY
Explore all skills by this author →
GitHub

accessible-content

Guide content creators in structuring readable, navigable, and inclusive user-facing text.

Updated Apr 13, 2026
Search Tags:#writing#accessibility#content#usability#structure#alt-text
One-click install
npx skills add https://github.com/Angusatgithub/Charmera --skill accessible-content-angusatgithub
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessible-content
Source: https://github.com/Angusatgithub/Charmera/tree/main/.github/skills/accessible-content
Command: npx skills add https://github.com/Angusatgithub/Charmera --skill accessible-content-angusatgithub

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that all written content in user interfaces is readable, meaningful, and accessible, enhancing usability for everyone.

Core Features & Use Cases

  • Content Clarity: Guides the creation of plain language, active voice, and specific wording to improve comprehension.
  • Structured Headings: Assists in organizing headings and page structure for screen reader navigation.
  • Form Accessibility: Provides best practices for labeling inputs, associating instructions, and indicating required fields.
  • Alt Text and Links: Advises on creating meaningful alt text for images and descriptive link texts.
  • Error Messaging: Guides writing clear, helpful error messages that enhance user correction and understanding.
  • Table Accessibility: Recommends proper markup for data tables with captions and scope attributes.
  • Content Review: Offers checklists for verifying accessibility compliance before publishing.

Quick Start

Use the accessible-content skill to review and improve your website content for better accessibility compliance.

Frequently Asked Questions about accessible-content

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

FAQPage Schema
How do I write accessible alt text and descriptive links for web content?▼

To write accessible alt text and links, use meaningful descriptions for images and clear link text that indicates purpose. This ensures content is readable and navigable for screen readers and diverse users.

What is the best way to structure headings for screen reader navigation?▼

Structuring headings for screen readers involves organizing page structure logically. Properly nested headings enhance screen reader navigation, ensuring user-facing text is readable and navigable for everyone.

How do I make form labels and error messages accessible?▼

Making form labels and error messages accessible requires associating instructions with inputs and indicating required fields. Clear, helpful error messages enhance user correction and improve overall form usability.

Can I use plain language to improve content clarity and usability?▼

Yes, you can use plain language and active voice to improve content clarity. Specific wording improves comprehension, ensuring user-facing text is readable, meaningful, and inclusive for diverse users.

What are the requirements for accessible data table markup?▼

Accessible data table markup requires proper captions and scope attributes. This structure ensures data tables are readable and navigable, enhancing usability for users relying on screen readers.

Do I need an accessibility checklist to review content before publishing?▼

Yes, you need an accessibility checklist to review content before publishing. Verifying accessibility compliance ensures user-facing text, labels, and structure are readable and inclusive for all users.

Related Skills

Explore More Content & Communication Skills→
Owl-ListenerOwl-Listener
234

accessible-content

Guide authors to write plain-language interface copy for WCAG-aligned accessibility.

Community
Advanced
metabasemetabase
48.6k

docs-review

Review documentation diffs for Metabase writing style compliance.

Official
Basic
phazurlabsphazurlabs
35

Accessibility & Inclusive Design

Convert accessibility requirements into WCAG 2.2 and ARIA implementation guidance.

Community
Advanced
hulusi-tunchulusi-tunc
3

plain-language-design

Rewrite and review UI copy for plain-language readability and jargon reduction.

Community
Intermediate