# Accessibility

> Accessibility is an Agent Skill for design published in the elastic/kibana repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Accessibility guidance for Kibana. Use this skill when working with or reviewing EUI components, resolving a11y-related (@elastic/eui) ESLint issues, and ensuring proper use of ARIA attributes, focus management, keyboard interactions, and accessible naming conventions.

- Skill name: `accessibility`
- Category: [Design](https://www.openparable.com/skill/design/1)
- Source: https://github.com/elastic/kibana/blob/HEAD/.agents/skills/accessibility/SKILL.md
- Repository: elastic/kibana (21,185 GitHub stars when collected)

## SKILL.md

# Kibana Accessibility

> Accessibility is part of writing the component, not a step that happens after lint complains. Open the matching guide in `references/components/index.md` **before** writing the JSX, and read `references/shared_principles.md` first.

## When to Use

- **Writing or refactoring an EUI component.** Open the matching guide from `references/components/index.md` and follow the canonical pattern (props, accessible names, focus, ids).
- **Fixing an `@elastic/eui/*` ESLint error.** Use `references/eslint.md` to jump from the rule id to the component guide that explains the canonical fix.
- **General a11y or non-EUI question.** Read `references/shared_principles.md`.

## References

Open only what you need:

- Standards, decision order, accessible naming, i18n, html ids, keyboard/focus, escalation: `references/shared_principles.md`
- Component guide topic table: `references/components/index.md`
- ESLint rule id → component guide (with manual-review notes): `references/eslint.md`

---

Source: https://www.openparable.com/skill/design/accessibility (OpenParable). Cite the canonical URL above.