Skip to content
Back to skills

App Accessibility

ASecurity

Audit or implement keyboard, screen-reader, contrast, focus, and accessible Shopify app interactions.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 1, 2026
ai-agentsdocumentation

Works with

  • cli
  • mcp

Security analysis

A100/100

Scanned October 3, 2026

npx -y skills add khadinakbarlabs/shopify-app-builder --skill app-accessibility --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of App Accessibility?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for App Accessibility
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/khadinakbarlabs-app-accessibility/badge)](https://www.skillsdirectory.com/skills/khadinakbarlabs-app-accessibility)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: app-accessibility
description: "Audit or implement keyboard, screen-reader, contrast, focus, and accessible Shopify app interactions."
---

# Make the app usable for everyone

## Start here

Accessibility lets merchants use the app without a mouse or perfect vision.

First useful outcome: Complete the primary task using only the keyboard.
Ask only for missing information that changes this task. Inspect the existing project and use synthetic data before touching a merchant store. Explain the next action and its expected result in plain language; offer a recommended default with its tradeoff.

## Guided workflow

1. Identify the primary task, meaningful labels, headings, live feedback and error associations.
2. Use the installed Polaris component semantics; provide accessible names for icon-only actions and clear field help.
3. Test focus movement in dialogs, validation errors and route changes; honor reduced motion and zoom.
4. Combine automated checks with manual keyboard and screen-reader sampling, prioritizing blocked tasks.

## Check it worked

Record tested viewport, keyboard path and actual failures; test loading, empty, error and success states.
Report what was changed, what was tested, and what still needs account access or live verification. Do not claim production readiness or approval from generated code alone.

## If you get stuck

An automated zero-issue score is not full accessibility proof.
Give one safe next step and a redacted error example, not a list of speculative fixes.

## Safety and optional depth

Use only the user's selected project/accounts. Never read credential caches or request secrets in chat; the operator configures the application's approved secret store. Ask before live deployment, store mutations, billing, publication or paid runs unless that exact action is already authorized. No MCP service is required by this plugin.

For concrete examples in an existing project, read only the relevant section of [technical-guide.md](references/technical-guide.md). These retained v1.x examples are version-sensitive, not the default template. Verify SDKs, schema fields, CLI flags and platform rules with [official documentation](https://shopify.dev/docs/apps/build/app-home) before using them.

Example request: "Use app-accessibility to help me with this task. Explain each change and verify it before moving on."

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…