Enhancement in Accessibility Best Practices Skill

Open
#124 0 comments 0 reactions 2 assignees View on GitHub

@GerganaKremenska is already working on this.

Since Aug 11, 2026.

Assessment

This issue has not been assessed yet.

Description

Why are you proposing this feature?

The ui5-best-practices-accessibility plugin already does a great job providing grounded, UI5-specific guidance through its reference files. The existing set — labeling.md, keyboard.md, landmark.md, invisible-message.md and others — gives coding agents concrete Wrong/Correct code pairs to draw on when explaining accessibility findings.

While working with the plugin, I noticed that several WCAG areas commonly encountered in UI5/Fiori development do not yet have a corresponding reference file. I wanted to raise this as a question for the team: would adding reference files for these areas meaningfully improve the quality and precision of agent-generated guidance?

Areas that appear to have no reference coverage today

Area Gap
State and Value Communication No reference for valueState/valueStateText, required field pairing, disabled control naming
Color, Contrast, and Adaptive Display No reference for color-only status controls, OverflowToolbarLayoutData priority, dialog contentHeight, CSS theme variable usage, or focus ring suppression
Reflow and Text Adaptability No reference for table demandPopin/minScreenWidth, column importance, wrapping="false" in fixed containers, fixed pixel dimensions, or CSS rem vs px usage
Error Prevention and Recovery No reference for valueStateText correction guidance, confirmation dialogs before destructive actions, or focus management on confirmation dialogs
Predictable Behaviour and Input No reference for selection-change cascade without an Apply step, liveChange opening dialogs before user acts, autocomplete on personal-data fields, or gesture handlers without keyboard alternatives
How should a possible solution look like?

No response

Are there alternative approaches?

No response

Any further information you would like to share?

I have drafted content for all 5 files in the format of the existing references. I'm happy to share them as a starting point if the team thinks this direction is worth exploring.

Dominant language
JavaScript
Stars
35
Forks
10
Avg merge
2h 28m
Merged PRs (30d)
7

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from UI5/plugins-coding-agents

All issues in UI5/plugins-coding-agents

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.