Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
UL access-ability and classes
See original GitHub issueI’ve noticed something odd about one of the accessibility opportunities…
On a webpage I’m testing, I get the warning of:
List items (<li>) are not contained within <ul> or <ol> parent elements.
However, when looking at said list, they do have a parent
- element… But, it’s
<ul class="categoryName"
We’ve sectioned this list to only appear on product pages of that category - Is there a major reason why Lighthouse doesn’t accept UL parent elements with classes assigned to them? Does this cause a genuine problem for TTS services, or perhaps this is a bug?
Thanks-
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:10 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Please reopen
@jimitndiaye as explained above axe flags any list where the
roleis other thanlist, if you believe this is a mistake, could you please file an issue with a reproducible page in axe-core? We will adopt whatever they consider to be the a11y best practice here.Given that there’s an MDN example very similar to your markup. I’m inclined to agree that should be handled better. Maybe that can help support the case over there.