a2ui-project / a2ui-project/a2ui
Basic Catalog components not rendering accessibility attributes (was: Restaurant Finder example: accessibility of "Book Now")
- Dominant language
- TypeScript
- Stars
- 16.4k
- Forks
- 1.3k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 134
Description
The interface produced violates WCAG 2.4.6 by creating multiple "Book Now" buttons that perform different actions.
What should happen is something like this:
```html
Book Mott 32 Now
Book Now
Book Mott 32 Now
```
What's responsible for building "invisible" text of the interface? Is it the JSON (maybe the schema is incomplete), the composer, or better inference instructions?
Contributor guide
Research direction
The issue is about accessibility attributes not rendering in basic Catalog components, using a Restaurant Finder example. Look at the component responsible for generating the 'Book Now' button, likely in a catalog or button component file. Check the JSON schema for missing accessibility fields and the composer logic that builds the HTML. Test by rendering a catalog component and inspecting the output for aria-label or sr-only spans.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, html, typescript
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100