Re: Add Findable Help

Hey folks,

> In addition, for Findable help it’s possible that the contact information
is not a navigation item because it’s text (e.g. a phone number) so that’s
why we need that language in the new criterion.


That's a fair point. I hadn't considered that. In that case yeah, I agree
with the suggested solution to this.

W

On Thu, Jun 18, 2020 at 3:00 PM Jonathan Avila <jon.avila@levelaccess.com>
wrote:

> Hi Alastair, I don’t think that distinction that moving a link from one
> nav group to another is not a fail of 3.2.3 is clear from reading the
> understanding documents and techniques – so if that is the case it might be
> good have to have an update that.  In addition, for Findable help it’s
> possible that the contact information is not a navigation item because it’s
> text (e.g. a phone number) so that’s why we need that language in the new
> criterion.
>
>
>
> Jonathan
>
>
>
> *From:* Alastair Campbell <acampbell@nomensa.com>
> *Sent:* Thursday, June 18, 2020 5:46 AM
> *To:* Detlev Fischer <detlev.fischer@testkreis.de>
> *Cc:* WCAG <w3c-wai-gl@w3.org>
> *Subject:* RE: Add Findable Help
>
>
>
> *CAUTION:* This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know
> the content is safe.
>
>
>
> > A standard link to help across pages I would consider part of the
> service navigation.
>
>
>
> Sure, and if the service navigation stays in the same order relative to
> other navigation mechanisms it would pass Consistent Navigation.
>
>
>
> However, if the help link moved from the service nav to the footer on some
> pages it would not fail Consistent Navigation, but we’d like it to fail
> this one.
>
>
>
> Cheers,
>
>
>
> -Alastair
>


-- 
*Wilco Fiers*
Axe for Web product owner - Co-facilitator WCAG-ACT - Chair ACT-R