Skip to content

Review a11y for design system and primitive Web Components #773

Description

@NoelDeMartin

As part of #769, a bunch of Web Components have been implemented that may not be completely accessible. In particular, these could be the Menu, Combobox, and Dialog components.

Before looking into this, though, we still have to consider whether we can use 3rd party components from Web Awesome or other libraries. If we do, maybe we can end up removing all the new functionality that has been implemented without an a11y review.

To clarify, the reason why these weren't implemented with full a11y support from the beginning is because doing that requires a lot more work. I preferred to get a basic version going, and once we decide whether we're using 3rd party components or not we can improve them.

Activity

  1. self-assigned this
    on May 29, 2026
  2. moved this from Backlog to Ready in SolidOS NLNet UIon May 29, 2026
  3. timea-solid commented on May 29, 2026

    @timea-solid
    Member

    What would be some suggested 3rd party web components to reuse? Can you share a link to a WebAwesome such component? So we have alternatives in the community?

  4. NoelDeMartin commented on May 29, 2026

    @NoelDeMartin
    MemberAuthor

    For the Dialog, we could look at <wa-dialog>, although I think the <dialog> element is pretty well supported nowadays and maybe we can get away with our own implementation.

    For the Menu, we could look at <wa-dropdown>, although I've done some tests with ARIA DevTools and I'm not completely sure it is accessible :(. However, I'm very skeptic that these components aren't accessible (it's one of the main points of Web Awesome), and talking with Gemini it seems like these aria roles are not "that important" as long as the focus management, roles, and labels are used properly... So I don't know, we need to spend a bit more time thinking about this one.

    And Combobox is probably the more troublesome, because <wa-combobox> is a paid component 😅. We could look at other 3rd party libraries, but I'm not familiar with any that works with web components. So maybe we need to do some more research here, or end up implementing it ourselves (their <wa-select> is open source, so we could look at it for inspiration).

  5. timea-solid commented on Jun 10, 2026

    @timea-solid
    Member

    As an update: we asked HAN Labs from NLnet to review profile-pane and also asked about Web Awesome components.

  6. moved this from Ready to In review in SolidOS NLNet UIon Jun 10, 2026
  7. timea-solid commented on Jun 22, 2026

    @timea-solid
    Member

    We will proceed with Web Awesome components.

  8. moved this from In review to In progress in SolidOS NLNet UIon Jun 22, 2026
  9. added 3 commits that reference this issue on Jun 23, 2026
  10. moved this from In progress to In review in SolidOS NLNet UIon Jun 24, 2026
  11. added a commit that references this issue on Jun 24, 2026
  12. moved this from In review to In progress in SolidOS NLNet UIon Jun 24, 2026
  13. moved this from In progress to In review in SolidOS NLNet UIon Jun 25, 2026
  14. moved this from In review to Ready in SolidOS NLNet UIon Jul 1, 2026
  15. closed this as completedby moving to Done in SolidOS NLNet UIon Sep 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions