Have there been any reports of the Tab interaction navigating strangely using NVDA? Our accessibility specialist did a full test on a course we built in Evolve and had some navigation issues with it. However, I remember reading some older posts that discussed NVDA having issues with navigation.
Hi @RobinS I haven’t come across that issue myself during accessibility testing. It’s always tricky to resolve issues with one particular reader if the component works well with the others. NVDA can be a bit unreliable in that regard. They do provide updates pretty regularly so hopefully it will be resolved by an update further down the line.
Cheers-Sam
@RobinS when I re-worked the accessibility on the Tab component a couple of years ago I set it up as per the Example of Tabs with Manual Activation in the W3C WAI APG - and we’ve had it audited as being fully accessible to WCAG Level AA since then.
So I would think it’s more likely to be an issue with NVDA (which is definitely the most buggy of all the screenreaders) rather than an issue with the Tab component itself.
That said, if your accessibility specialist has any concrete examples of where it’s not marked up correctly for accessibility then of course please feel free to share with us!
The only thing I could think that could upset it is maybe using streaming video within the tab content… as the streaming video player is third-party code we have very little control over how accessible it might be.
Thanks Sam and Matt for your replies. I have about a page-long description of what she encountered. Is there a way I could send this to you to get your take on it? I can cut/paste it in here if that is preferred. We appreciate your help!
Typically an accessibility report would state what actually needs to be done to remediate the issue; if there’s anything like that in there then yes it would be very helpful to see.
If it’s only one page send it through anyway and we’ll take a look.
Should also mention we are currently going through an annual re-audit of Evolve’s accessibility so it may well be that comes back with some advice on this. Obviously it passed the audit last year and we haven’t made any changes to the accessibility of this component since then… but it’s entirely possible they missed something subtle last time!
Thanks! How do I send it through to you? Post it here? I think this was more of a “here’s the trouble I had navigating this” rather than how to remediate.
1 Like