WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Making mobile view available to all as way of constraining a11y testing costs

for

From: Robert Fentress
Date: Jan 11, 2018 11:42AM


Thanks, again, for the feedback. Perhaps I am just straining at gnats, as
is my wont. It may suffice to use common sense in identifying what
specific content needs to be checked at the different breakpoints, and I
shouldn't worry too much that I may be missing something. Still, I like
the idea of providing a visible option for users to switch to a
presentation that would ordinarily only be available at the smaller
viewport. Often, it is simpler and less cluttered.

On Thu, Jan 11, 2018 at 9:03 AM, Patrick H. Lauke < <EMAIL REMOVED> >
wrote:

> On 11/01/2018 13:47, Tim Harshbarger wrote:
>
>> I want to revisit an earlier part of the discussion.
>>
>> If you do decide to test only one view of the site to limit testing
>> costs, you should also clearly state to your users which view is the
>> accessible one. Users should not have to switch back and forth between
>> views of your site to figure out which one is accessible.
>>
>
> Noting that if the switching happens based on things like viewport size
> outside the user's control, then that won't fly. But yes, if there's an
> actual link/button/setting that lets users switch, agree that it should be
> made clear which one is and which one isn't "accessible" (or at least has
> been tested as being accessible).
>
> [...]
>
>> However, I am sure we all recognize that we don't always get the
>> resources we want for accessibility testing so we have to do the best with
>> what we are given. Robert is definitely doing his best to try to figure out
>> how to conduct accessibility testing within the boundaries he is
>> given--which really isn't any different from anything else having to do
>> with software engineering.
>> I dislike the limitations we find ourselves dealing with, but I do admire
>> how creative our community can be in trying to figure out how to get things
>> done within those limitations.
>>
>
> Oh absolutely, apologies if my remarks in this thread came across as a
> slight against Robert. I saw for the pragmatic proposal it was, just
> pointing out that it's not ideal and why.
>
> P
> --
> Patrick H. Lauke
>
> www.splintered.co.uk | https://github.com/patrickhlauke
> http://flickr.com/photos/redux/ | http://redux.deviantart.com
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
> > > > >



--
Rob Fentress
Senior Accessibility Solutions Designer
Assistive Technologies at Virginia Tech
Electronic Business Card (vCard)
<http://search.vt.edu/search/person.vcf?person54847>
LinkedIn Profile
<https://www.linkedin.com/in/rob-fentress-aa0b609?trk=profile-badge>