Lists Accessibility

[Ro-Matos]

Goal

Atribute semantics to Lists component to implement accessibility corretly.

1. Currently the List structure uses only div. Is necessary use <ul> and <li> to have semantic HTML.
   (Already reported in issue → Accessibility: Components | Lists #1489)

Context

In our accessibility specs developed by the design teams of APP Vivo, this cases have frequently documented. But the developers are not able to assign the all properties in the code.

Is possible to use "role=list" and "role=listItem" but this use don't atribute if the List is ordered or unordered. Another point is that more practical to devs if the semantic comes by default in the component.

Impact

Improvements and compliance with accessibility guidelines.

Discussion Questions

None

Additional considerations

No response

Do you have a visual proposal?

No response

[yceballost]

I'm unclear about the purpose of this discussion. If the issue has already been identified and included for resolution, why initiate a separate discussion? 🤔

Please feel free to contribute directly to issue #1489 if there's something specific you'd like to emphasize or ensure is considered during its resolution

[Ro-Matos]

I created the discussion because in another component there was a similar situation (buttons), your guidance was to create a discussion to prioritize it (as a OB request):

And this issue was despriorized

[yceballost]

Yes, but the discussions are to discuss whether or not to include it in Mística.

Once a discussion is finalised an issue is created which means that it is a task to be worked on in Mística because it is something that will be included.

If there is something that you want to prioritise from the backlog of issues, the best thing to do is to create a ticket in the OBVIVO jira to prioritise it among all the others.

[yceballost]

the de-prioritisation is because we work with OKRs every quarter, and the accessibility project has moved down a lot on the Q1 target list (because we have other projects with higher priority).

I don't know if you can see this link, but here are listed the OKRs of my team. (I can show you in private if you want)
https://confluence.tid.es/display/CTO/2024-Q1+Team+Objectives%2C+Initiatives+and+KPIs#id-2024Q1TeamObjectives,InitiativesandKPIs-DesignCore

The first okr is to work on the components that you have asked for from Vivo, which are these (sorted by priority):

Accessibility project is the 6!

When we finish with Vivo component list requests for Q1, we can work on more component that are listed in OBVIVO Jira but here your team will be able to prioritise whether to continue creating components or to prioritise improving accessibility.

I hope I have explained myself as well as possible!

[Ro-Matos]

My Jira access is still pending. I'll forward it to someone with access to include this accessibility issue as an OB prioritization.
Sorry and thanks Yayo!