WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: If default navigation is not keyboard accessible does an alternative access mean it still passes AA WCAG?

for

From: England, Kristina
Date: Jun 10, 2020 7:08AM

Reviewing the conforming alternative versions is a good starting point. However, usability of the alternative version is a huge factor. There's a virtual tour that has an alternative version that doesn't "pass" as they didn't fully understand what went into an alternative version (i.e., a knowledge of the various personas that would use that conforming version). They created a one pager that has load issues depending on the amount of videos you have and is generally exhausting to navigate as someone using keyboard only or someone with low vision (it has the heading and landmark structure for people using screen readers but, again, as a one pager, even that can be exhausting due to the length of the page). That same alternative version has gone out of sync with the non-conforming version so the only way to confirm it will stay in sync when a vendor is managing the conforming version is to cross your fingers and wait for nothing to go wrong with the conforming version. It's also extremely easy for a vendor to make a code change that impacts the conforming version and makes it non-conforming. Just some thoughts as it's actually pretty hard to ensure a conforming alternative version is kept equally effective and is maintained in the long run. Having tested alternative versions of products outside of virtual tours as well, I've yet to come across one that actually conforms (or if it does, continues to conform).

From: WebAIM-Forum < <EMAIL REMOVED> > on behalf of Patrick H. Lauke < <EMAIL REMOVED> >
Sent: Wednesday, June 10, 2020 8:43 AM
To: <EMAIL REMOVED> < <EMAIL REMOVED> >
Subject: Re: [WebAIM] If default navigation is not keyboard accessible does an alternative access mean it still passes AA WCAG?

[External Sender]

On 10/06/2020 13:36, Jim Byrne Accessible Web Design wrote:
> Hi,
>
> I reviewed a virtual tour and found that the tour was not inaccessible via keyboard. For example, the hotspots are invisible to keyboard and screen reader users. When a mouse hovers over the hotspots summary information is provided and when clicked the user is taken to a new area on the virtual tour.
>
> Apparently this can’t be fixed due to the technology used to create the tour. The default virtual tour is inaccessible and can’t be made accessible.
>
> They propose to provide an accessible alternative to the entire tour experience by creating accessible videos. Each area covered by the tour would be described in a video. The captions will fully describe all aspects of each area - both the commentary (i.e. the speech) and everything relevant that is on the screen.
>
> My question is. If the video is accessible but the default tour remains inaccessible does their virtual tour pass WCAG AA - assuming all other checkpoints are passed?

The video (provided it does indeed provide all the same
information/functionality) would act as a "conforming alternate version"
https://www.w3.org/TR/WCAG21/#dfn-conforming-alternate-version<https://www.w3.org/TR/WCAG21/#dfn-conforming-alternate-version> - so all
other things being equal, all points outlined there being satisfied, yes
that'd pass.

P
--
Patrick H. Lauke

https://www.splintered.co.uk/<https://www.splintered.co.uk> | https://github.com/patrickhlauke<https://github.com/patrickhlauke>
https://flickr.com/photos/redux/<https://flickr.com/photos/redux> | https://www.deviantart.com/redux<https://www.deviantart.com/redux>
twitter: @patrick_h_lauke | skype: patrick_h_lauke