accessibility
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.mdbefore writing the JSX, and readreferences/shared_principles.mdfirst.
When to Use
- Writing or refactoring an EUI component. Open the matching guide from
references/components/index.mdand follow the canonical pattern (props, accessible names, focus, ids). - Fixing an
@elastic/eui/*ESLint error. Usereferences/eslint.mdto 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
More from elastic/kibana
codeql
Work with CodeQL in Kibana — write, test, and debug custom queries locally, fetch scan results from GitHub, and validate inline suppression comments. Use when writing or debugging CodeQL queries, running CodeQL unit tests, analyzing SARIF results, fetching scan results, or checking codeql suppression justifications.
1optimize-bundle-size
Reduce plugin `page load bundle size` and avoid unnecessary increases in `packages/kbn-optimizer/limits.yml`. Use when proactively optimizing bundles, investigating CI page-load overages, or reviewing PRs that change bundle limits.
1kibana-api
Shared utilities for interacting with a local Kibana instance. Provides auto-detection of Kibana URL and auth, and a kibana_curl wrapper.
1api-authz
Kibana API route authorization patterns. Use when configuring route security, working with requiredPrivileges, using authzResult for privilege-based branching, opting out of authorization, or naming custom privileges.
1ftr-testing
Deep reference for the Kibana Functional Test Runner (FTR). Use when reading, analyzing, debugging, or reviewing FTR tests, including config anatomy, services, page objects, loadTestFile patterns, data loading, tags, CI wiring, and common FTR idioms.
1validate-oas
Use when you need a quick VALID or NOT VALID result for a scoped Kibana OAS area, and first ensure the generated `oas_docs` inputs are up to date so validation runs against the current environment rather than stale snapshots.
1