- Issue created by @ryanrobinson_wlu
- Assigned to danrod
- 🇨🇦Canada danrod Ottawa
Thanks for reporting this @ryanrobinson_wlu , I'll look into fixing this later this weekend.
- 🇨🇦Canada danrod Ottawa
I am not sure if I will fix this, in terms of the accessibility tree, the top div will be ignored.
https://www.w3.org/WAI/ARIA/apg/patterns/landmarks/examples/general-prin...
https://dequeuniversity.com/rules/axe/4.3/region
I'm not sure if swapping the "div" tag with "section" and add the aria-label attribute will fix that, I'll have to do some tests with axe-core myself.
- Status changed to Needs work
12 months ago 10:41pm 18 December 2023 - Status changed to Active
11 months ago 1:09am 29 December 2023 - 🇨🇦Canada danrod Ottawa
I did some research on this issue and I found that there is a "region" role that is used to identify document areas the author deems significant. It is a generic landmark available to aid in navigation when none of the other landmark roles are appropriate.
I added the
role="region"
andaria-label="{{ 'Table Of Contents'|t }}"
attributes to the<div>
container and then I ran another accessibility test to the widget and It passed. Can be reviewed now. - Merge request !5Issue # 3408906 by danrod: Added role and aria-label attributes to the div... → (Merged) created by danrod
- Status changed to Needs review
11 months ago 1:21am 29 December 2023 - Status changed to RTBC
11 months ago 9:53pm 29 December 2023 - Status changed to Fixed
11 months ago 10:11pm 29 December 2023 Automatically closed - issue fixed for 2 weeks with no activity.