W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2018

Re: WCAG v2.1 for mobile website evaluation

From: Matt Elton <mattelton35@gmail.com>
Date: Fri, 17 Aug 2018 16:13:19 +0100
Message-ID: <CAKDfB0urF5P6a3D0bpXqJMwPKsKy-qgki0bAzkotscq-cm6G1w@mail.gmail.com>
To: "Subramanian, Poornima (PCL)" <psubramanian@hagroup.com>
Cc: Elizabeth Linnetz <elizabeth.linnetz@theprimacy.com>, "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Thank you very much. All your replies have been very helpful in providing
me with a fuller picture.

I have one more question (sorry for being greedy!). I've been told that it
is best to match certain desktop screen readers with browsers. For example,
IE with JAWS, NVDA with Firefox etc. With the newer desktop screen readers
(like JAWS 18) is this still important? If so, what desktop screen reader
would you use with Chrome?

Cheers,
Matt

On Fri, Aug 17, 2018 at 4:07 PM, Subramanian, Poornima (PCL) <
psubramanian@hagroup.com> wrote:

> That’s correct. Though the website is responsive, the user interface will
> have at least minimal change in terms of layout and presentation.
>
>
>
> For example, the visual label in desktop label can act as a hidden label
> in mobile view. And, the elements presented as show/hide elements in mobile
> view coded differently on desktop view.
>
>
>
> We initially test with Chrome mobile and desktop view to identify any
> change in the presentation on both views. This helps to a great extent to
> find out any missing labels, menu presentations, etc. to cover most of WCAG
> 2.0 guidelines.
>
> Then, testing with keyboard to ensure the elements are keyboard accessible
>
> Then, testing with both desktop (JAWS & NVDA) and mobile readers (VO,
> Talkback) to comply with full WCAG 2.0 standards.
>
>
>
> Best,
>
> Poornima.
>
>
>
> *From:* Elizabeth Linnetz [mailto:elizabeth.linnetz@theprimacy.com]
> *Sent:* Friday, August 17, 2018 10:23 AM
> *To:* Matt Elton <mattelton35@gmail.com>; w3c-wai-ig@w3.org
> *Subject:* RE: WCAG v2.1 for mobile website evaluation
>
>
>
> Hi Matt,
>
>
>
> You’ll find different issues on a mobile vs. desktop view – even if most
> of the elements are the same, frequently the menu renders differently on
> mobile vs. desktop.  Tabs may render as accordions and need to be tested,
> and other elements may change as well. You’ll want to make sure that
> anything hidden in mobile renders properly on desktop and remains hidden
> from screen readers.  VoiceOver, TalkBack, JAWS, and NVDA all have
> different quirks as well.
>
>
>
>
>
> *From:* Matt Elton [mailto:mattelton35@gmail.com <mattelton35@gmail.com>]
> *Sent:* Friday, August 17, 2018 10:07 AM
> *To:* w3c-wai-ig@w3.org
> *Subject:* WCAG v2.1 for mobile website evaluation
>
>
>
> Hi everyone,
>
>
>
> I hope you can help me with a question I have been thinking about for a
> while.
>
>
>
> The updated WCAG v2.1 guidelines seem to be device independent but I was
> wondering if all the non-compliant issues would be discovered if someone
> was to conduct an assessment of a mobile version of a responsive site using
> just an iPhone (and VoiceOver). Is this sufficient or should the desktop
> version also be assessed (using a desktop screen reader like JAWS or NVDA).
>
>
>
> Thank you very much for your help.
>
>
>
> Cheers,
>
> Matt
>
>
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com
> ______________________________________________________________________
> The information contained in this email and any attachment may be
> confidential and/or legally privileged and has been sent for the sole use
> of the intended recipient. If you are not an intended recipient, you are
> not authorized to review, use, disclose or copy any of its contents. If you
> have received this email in error please reply to the sender and destroy
> all copies of the message. Thank you.
>
> To the extent that the matters contained in this email relate to services
> being provided by Princess Cruises and/or Holland America Line (together
> "HA Group") to Carnival Australia/P&O Cruises Australia, HA Group is
> providing these services under the terms of a Services Agreement between HA
> Group and Carnival Australia.
>
Received on Friday, 17 August 2018 15:13:47 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:37:20 UTC