Review image alt text, the descriptions read by screen readers, for unnecessary phrases and duplication of nearby text. Identify specific images to fix and make their descriptions concise while preserving information about what the images mean.
Use when reviewing rendered HTML, interactive components, or design-system patterns related to Avoid redundant image alternative text. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
Reviews image alternative text and revises wording that makes screen reader output unnecessarily verbose. It looks for introductory phrases such as “image of” or “photo of” in alt attributes, as well as descriptions that repeat adjacent text. It makes descriptions concise while conveying the image’s meaning. By examining rendered HTML, it identifies the specific elements that need attention and explains how to verify the changes.
Use it when reviewing a web page’s accessibility or checking whether images and captions repeat the same information when read aloud. It helps assess whether people using screen readers, software that reads screen content aloud, receive the information they need without unnecessary repetition or missing details.
alt text on this page and remove redundant wording.”Screen readers already announce that an element is an image, so alternative text does not need to repeat that information. Verify the revised result using browser accessibility tools or assistive technology.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.
The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 23, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Redundant alt text increases the verbosity for screen reader users without adding value, leading to a poorer user experience and slower navigation.
Scan image alt attributes for redundant phrases like 'image of', 'photo of', or text that duplicates surrounding content.
Remove redundant phrases from the alt attribute and ensure the text provides unique, descriptive information.
Explain why screen readers already announce 'graphic' or 'image', making phrases like 'image of' unnecessary and repetitive.
Review the rendered markup and interactive states that affect Avoid redundant image alternative text. Flag exact elements, roles, labels, focus behavior, or keyboard interactions that violate the rule, and note how to verify the fix with browser accessibility tooling or assistive tech.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/accessibility/image-redundant-alt
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create and review custom 404 pages that help visitors recover from broken or moved links through search and navigation. Check the rendered page and HTTP response so missing content returns a proper 404 status.
Audit or create a dedicated About page that explains a website’s purpose and identifies its people or organization. Review the rendered output and supporting information, including expertise and contact details, to find gaps.
Review and add automated accessibility checks for components, pages, and continuous integration workflows. Use axe-based tools to detect structural and attribute issues, while identifying checks that still need keyboard or screen reader testing.
Review sign-in, registration, multi-factor authentication, and account recovery for accessibility barriers. Find blocked paste, difficult code entry, and inaccessible backup methods, then suggest authentication paths that support password managers, autofill, or device approval.
Review form errors, success messages, and live updates so screen reader users receive important notifications. Check the HTML delivered to the browser, announcement settings, display duration, and dismissal controls, then identify specific elements that need changes.
Review HTML tables so screen reader users can understand how headers and data relate. Check header markup, table descriptions, and merged cells, then identify specific fixes and ways to verify them.