ui5-best-practices-accessibility
This skill should be used when the user asks to audit, fix, check, review, or improve accessibility, a11y, ARIA, WCAG compliance, landmarks, labeling, heading levels, focus handling, keyboard navigation, keyboard shortcuts, screen reader support, invisible messaging, reading order, or touch / target size in UI5 application files (views, fragments, controllers). Also use when the user creates a new UI5 view, fragment, or controller and wants it to be accessible, or asks whether a specific control (Dialog, Table, Panel, etc.) meets accessibility requirements. Keywords: accessibility, a11y, ARIA, WCAG, screen reader, NVDA, JAWS, VoiceOver, landmark, landmarkInfo, accessibleRole, ariaLabelledBy, ariaDescribedBy, labelFor, tooltip, alt text, decorative, heading level, initialFocus, F6, fast nav, fastnavgroup, tabindex, CommandExecution, keyboard shortcut, InvisibleMessage, announce, reading order, reactiveAreaMode, target size.
Install
With your agent
Install OMGSkills skill "ui5/plugins-coding-agents:plugins/ui5/skills/ui5-best-practices-accessibility" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/UI5/plugins-coding-agents /tmp/plugins-coding-agents && ln -s /tmp/plugins-coding-agents/plugins/ui5/skills/ui5-best-practices-accessibility ~/.claude/skills/ui5-best-practices-accessibilityFrom README
Accessibility Review Accessibility in UI5 is incorporated in two levels: framework and application. This review supports what application developers must still provide explicitly to improve the accessibility of their application. Step 1 — Find the files If $ARGUMENTS lists specific files, review only those. Otherwise, discover all app source files automatically: If more than 15 files are found, use AskUserQuestion to let the user choose: Review everything (may take a moment) Focus on a specific folder or area Read each file in scope. Step 2 — Review Check the code against the eight topics below. For each topic where you find a gap, read the corresponding topic file before writing the fix — it contains the correct API pattern and wrong/correct examples.
More from this repo
fix-bootstrap-params
Used to fix HTML bootstrap parameter issues that UI5 linter reports but cannot auto-fix.
fix-component-async
Used to fix Component.js async configuration issues that UI5 linter reports but cannot auto-fix.
fix-control-renderer
Used to fix Control renderer issues that UI5 linter reports but cannot auto-fix.