screen-reader

Audit heading hierarchy, landmark structure, and link text in HTML files.

Updated Aug 23, 2026

Search Tags:#accessibility #screen reader #web development #wcag #semantic html #aria

Ready to run

npx skills add https://github.com/lukeslp/accessibility-skills --skill screen-reader

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: screen-reader
Source: https://github.com/lukeslp/accessibility-skills/tree/main/plugins/accessibility/skills/screen-reader
Command: npx skills add https://github.com/lukeslp/accessibility-skills --skill screen-reader

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of making web content understandable and navigable for users who rely on screen readers, ensuring they can access information and interact with interfaces effectively.

Core Features & Use Cases

Semantic HTML Guidance: Promotes the correct use of HTML5 elements for structure.
ARIA Best Practices: Provides rules for using ARIA attributes as a supplement, not a replacement, for native HTML.
Dynamic Content Announcement: Ensures screen reader users are notified of real-time updates on a page.
Form Accessibility: Guides the creation of accessible forms with proper labels and error handling.
Use Case: When developing a complex web application with dynamic content updates and custom form elements, this Skill ensures that screen reader users receive the same information and can complete tasks as easily as sighted users.

Quick Start

Use the screen-reader skill to audit the heading structure of the file 'index.html'.

Frequently Asked Questions about screen-reader

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

FAQPage Schema

How do I make dynamic web content accessible to screen readers?▼

To make dynamic web content accessible to screen readers, implement ARIA live regions to announce real-time page updates, ensuring users receive the same information as sighted users.

What is the best way to audit heading hierarchy and landmark structure for web accessibility?▼

Auditing heading hierarchy and landmark structure for web accessibility involves running Python scripts that evaluate your HTML files to ensure semantic structure is correctly implemented for screen reader navigation.

When should I use ARIA roles instead of semantic HTML for screen reader compatibility?▼

ARIA roles should be used as a supplement, not a replacement, for semantic HTML to ensure screen reader compatibility, providing accessible names and states only when native HTML elements fall short.

How do I design accessible forms with proper labels and error handling for screen reader users?▼

Designing accessible forms for screen reader users requires attaching proper labels to inputs and implementing clear error handling so that validation issues are announced effectively.

Does this screen reader accessibility guidance work with standard HTML files?▼

Yes, this screen reader accessibility guidance works directly with standard HTML files, providing Python scripts to audit elements like heading structure and link text within your documents.

Why does my screen reader not announce real-time updates on my web page?▼

Your screen reader may not announce real-time updates because the web page lacks properly configured ARIA live regions, which are required to notify users of dynamic content changes.