Hi all, I’m looking into using the article indicator extension but was wondering the implications for accessibility. I’ve seen some threads on other components requesting info on why they may have failed an accessibility audit - hoping someone might have some info!
I’m guessing it could be failing the “avoid repetition” principle - because it reads out the article title in the button in the indicator, then you hear it again when you get to the article title itself. But I might be misunderstanding the principle - one is a button and the other a title after all.
I’ve tested using NVDA and added an ARIA label and it seems to work very well so far.
1 Like
Hi @LaurynS - that particular extension is currently marked as ‘Not accessible’ - if memory serves I think it had to do with how it affected navigating the page via the keyboard (but not 100% sure on that) - we would definitely not recommend including it in its current form.
Cheers-Sam
@LaurynS & @Sam_Cook_Evolve_PO there’s definitely an issue at the moment with it not being keyboard-accessible (unless you’re using a screen reader).
That’s easily fixed - but I think there’s a wider issue of how to make it easy to actually get to if you’re navigating using the keyboard/screen reader.
It’s also arguably slightly pointless for screen reader users anyway since Jaws, VoiceOver etc. already have similar functionality built in (in that you can get them to list all headings on the page and use that list to navigate).
2 Likes