Re: Obscuring active elements and text

I agree. The last statement is really good.

On Mon, Mar 7, 2016 at 8:33 AM, Rochford, John <john.rochford@umassmed.edu>
wrote:

> Hi Laura and All,
>
> I echo Jon's endorsement of Laura's suggestion: "+1 to not adding a new
> user need but updating it to add pointers/cursors/carets."
>
> John
>
> -----Original Message-----
> From: Jonathan Avila [mailto:jon.avila@ssbbartgroup.com]
> Sent: Friday, March 04, 2016 5:31 PM
> To: Laura Carlson <laura.lee.carlson@gmail.com>; Rochford, John <
> john.rochford@umassmed.edu>
> Cc: Wayne Dick <wayneedick@gmail.com>; public-low-vision-a11y-tf <
> public-low-vision-a11y-tf@w3.org>
> Subject: RE: Obscuring active elements and text
>
> > "User Need: Users can see and operate all interface elements that are
> intended for users to see and operate. This includes when users have
> changed display settings such as text size, magnification level, and cursor
> size.
>
> +1 to not adding a new user need but updating it to add
> pointers/cursors/carets.
>
> Jonathan
>
> -----Original Message-----
> From: Laura Carlson [mailto:laura.lee.carlson@gmail.com]
> Sent: Friday, March 04, 2016 5:26 PM
> To: Rochford, John
> Cc: Wayne Dick; public-low-vision-a11y-tf
> Subject: Re: Obscuring active elements and text
>
> Hello everyone,
>
> Thanks, John. I agree with Wayne. Yours rendition is an improvement.
>
> I've been thinking about it more. At first I thought swapping out
> "text-pointer icons" with the word "cursors" as more than pointer cursors
> exist. i.e. hand, help, etc might be an improvement. The images in the Wiki
> use the hand cursor.
>
> Then I went back to our requirements doc [1]. We already have:
>
> "User Need: Users can see all interface elements that are intended for
> users to see, including when users have changed display settings such as
> text size."
>
> So now I am wondering does that already cover it? Maybe we don't need a
> separate user need for obscured active elements and text.
>
> Or would it help if we added a bit to read something such as:
>
> "User Need: Users can see and operate all interface elements that are
> intended for users to see and operate. This includes when users have
> changed display settings such as text size, magnification level, and cursor
> size.
>
> Thanks.
>
> Kindest Regards,
> Laura
>
> [1] http://w3c.github.io/low-vision-a11y-tf/requirements.html
>
>
> I agree with Wayne. I think yours is an improvement.
>
>  What do you think of...
>
>
> Users can set both cursor and tooltip size and placement.
>
> User Need: such that elements are not obscured and are operable and
> understandable.
>
>
>
>
> On 3/4/16, Rochford, John <john.rochford@umassmed.edu> wrote:
> > Hi Wayne,
> >
> > Do you think these versions would be easier to comprehend?
> >
> > To enable understanding and activation, elements and functionality
> > can’t be obscured by text-pointer icons, messages, or tooltips.
> >
> > Web sites designed to accommodate text-size enlargement such that
> > elements do not overlap, are not obscured, and are operable.
> >
> > John
> >
> > John Rochford<http://profiles.umassmed.edu/profiles/display/132901>
> > UMass Medical School/E.K. Shriver Center Director, INDEX Program
> > Instructor, Family Medicine & Community Health www.DisabilityInfo.org
> > Twitter: @ClearHelper<https://twitter.com/clearhelper>
> >
> >
> > From: Wayne Dick [mailto:wayneedick@gmail.com]
> > Sent: Thursday, March 03, 2016 5:34 PM
> > To: public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>
> > Subject: Obscuring active elements and text
> >
> >
> > Obscuring Functionality or Text Pointers icons, messages or tooltips
> > should not obscure active elements that depend on the pointers,
> > messages or tooltips for activation or understanding.
> > With large print, especially when reformatting is necessary, large
> > objects may overlap. When one of these is a active element operability
> > can be impaired. There should be some mechanism to position objects so
> > they do not interfere with each other.
>
> --
> Laura L. Carlson
>
>