Re: lvtf-ACTION-51: Write user need on "non-text contrast" - [can change the name, border, grids, etc]

Thanks Laura for catching the typo.
Jon, I think the use of borders is the author's depression. There are many
ways to implement call attention to content, borders are one

The issue I was trying to get at is this. If an author decides to use
borders for visual emphasis, then the borders should be visible. Also, the
author decides to use another mechanism for visual emphasis, that should be
visible too.

Authors use visual cues to draw the eye to important content. We don't have
to prescribe the cues authors choose, but I think we need to prescribe
visibility strong enough to draw the eyes of visually impaired users.



On Tue, Apr 26, 2016 at 6:23 AM, Jonathan Avila <jon.avila@ssbbartgroup.com>
wrote:

> Laura, that works for me on contrast. in the case when authors don't
> provide borders for inputs we may need to update another user requirement.
>   Perhaps we want to say that user with low vision require borders in input
> and may ne s borders in other situations to understand the relationship of
> content.  Perhaps my suggestion belongs in a different user requirement and
> is in the one related to contrast.
>
> Jonathan
>
> Sent from my iPhone
>
> > On Apr 26, 2016, at 9:07 AM, Laura Carlson <laura.lee.carlson@gmail.com>
> wrote:
> >
> > Hi Jon and all,
> >
> > Here is an idea to remove the subjectivity. How about using only the
> > second sentence in the actual User Need. We could use the rest in
> > explanatory text before it. Maybe something such as:
> >
> > Sometimes people have difficulty distinguishing the borders of form
> > controls and regions of content that authors call out by providing
> > borders. Form controls including radio buttons and check boxes can be
> > especially problematic.
> >
> > User Need: Borders have a baseline contrast ratio equal to or greater
> > than the minimum contrast ratio for text on the page.
> >
> > Does that help?
> >
> > Kindest Regards,
> > Laura
> >
> >> On 4/26/16, Jonathan Avila <jon.avila@ssbbartgroup.com> wrote:
> >> Ø  and regions of content
> >>
> >> Wayne, thank you for writing that up.  This is the part that concerns
> me as
> >> it is currently too subjective.  We would need to define what regions
> must
> >> have borders with sufficient contrast.  Too many border could be
> problematic
> >> and this would never be accepted by design folks.
> >>
> >> Jonathan
> >>
> >> Jonathan Avila
> >> Chief Accessibility Officer
> >> SSB BART Group
> >> jon.avila@ssbbartgroup.com<mailto:jon.avila@ssbbartgroup.com>
> >> 703.637.8957 (Office)
> >>
> >> Visit us online: Website<http://www.ssbbartgroup.com/> |
> >> Twitter<https://twitter.com/SSBBARTGroup> |
> >> Facebook<https://www.facebook.com/ssbbartgroup> |
> >> Linkedin<https://www.linkedin.com/company/355266?trk=tyah> |
> >> Blog<http://www.ssbbartgroup.com/blog/>
> >> Check out our Digital Accessibility
> >> Webinars!<http://www.ssbbartgroup.com/webinars/>
> >>
> >> From: Wayne Dick [mailto:wayneedick@gmail.com]
> >> Sent: Tuesday, April 26, 2016 3:21 AM
> >> To: Jonathan Avila
> >> Cc: Jim Allan; Low Vision Accessibility Task Force
> >> Subject: Re: lvtf-ACTION-51: Write user need on "non-text contrast" -
> [can
> >> change the name, border, grids, etc]
> >>
> >> What about this wording for a need:
> >>
> >> Users with low vision require sufficient contrast to be able to
> distinguish
> >> the borders of form controls and regions of content that authors call
> out by
> >> providing borders. Borders should have contrast rations equal to or
> greater
> >> than the minimum contrast ratio for text on the page. This applies to
> all
> >> form controls including radio buttons and check boxes.
> >> Does this do it?
> >>
> >>
> >> On Mon, Apr 25, 2016 at 6:33 PM, Jonathan Avila
> >> <jon.avila@ssbbartgroup.com<mailto:jon.avila@ssbbartgroup.com>> wrote:
> >>
> >>> That said, I think this is a major issue to be added to WCAG. Minimum
> >>> contrast (WCAG 1.4.3) should apply to more than only text and images of
> >>> text content. It should apply to form controls and other elements with
> >>> borders.
> >>
> >> I agree and I have two comments.
> >>
> >>
> >> 1.    After talking with  some designers I was told that they need clear
> >> recommendations on this with specific numbers and rationale in order to
> >> implement such as design change – just indicating it is helpful to users
> >> isn’t enough.  From what I found the size of the control may make a
> >> difference – that is the border on a checkbox may be more important
> than the
> >> border on an input field due to the size of the control.   Would we
> consider
> >> less contrast for larger size controls like SC 1.4.3 does for text?
> >>
> >> 2.    Some sites such as goFundMe.com have input fields with no borders
> on
> >> the inputs. We might want to consider whether we see this as an issue.
> To
> >> see the issue go to gofundme and then select a person to donate to  and
> >> click the donate button.  This is a very unfortunate design decision in
> my
> >> opinion.
> >>
> >> 3.    We might also consider what happens to borders when a user is in
> high
> >> contrast mode.
> >>
> >> Jonathan
> >>
> >> Jonathan Avila
> >> Chief Accessibility Officer
> >> SSB BART Group
> >> jon.avila@ssbbartgroup.com<mailto:jon.avila@ssbbartgroup.com>
> >> 703.637.8957<tel:703.637.8957> (Office)
> >>
> >> Visit us online: Website<http://www.ssbbartgroup.com/> |
> >> Twitter<https://twitter.com/SSBBARTGroup> |
> >> Facebook<https://www.facebook.com/ssbbartgroup> |
> >> Linkedin<https://www.linkedin.com/company/355266?trk=tyah> |
> >> Blog<http://www.ssbbartgroup.com/blog/>
> >> Check out our Digital Accessibility
> >> Webinars!<http://www.ssbbartgroup.com/webinars/>
> >>
> >> From: Jim Allan [mailto:jimallan@tsbvi.edu<mailto:jimallan@tsbvi.edu>]
> >> Sent: Wednesday, April 20, 2016 1:28 PM
> >> To: Low Vision Accessibility Task Force
> >> Subject: Re: lvtf-ACTION-51: Write user need on "non-text contrast" -
> [can
> >> change the name, border, grids, etc]
> >>
> >> Note: 3.5.1 Element-level customization talks about borders and colors.
> >> perhaps we can expand the explanatory text to illustrate the need to
> change
> >> "non-text contrast".
> >>
> >> That said, I think this is a major issue to be added to WCAG. Minimum
> >> contrast (WCAG 1.4.3) should apply to more than only text and images of
> text
> >> content. It should apply to form controls and other elements with
> borders.
> >> Jim
> >>
> >> On Wed, Apr 20, 2016 at 10:34 AM, Low Vision Accessibility Task Force
> Issue
> >> Tracker <sysbot+tracker@w3.org<mailto:sysbot+tracker@w3.org>> wrote:
> >> lvtf-ACTION-51: Write user need on "non-text contrast" - [can change the
> >> name, border, grids, etc]
> >>
> >> http://www.w3.org/WAI/GL/low-vision-a11y-tf/track/actions/51
> >>
> >> Assigned to: Wayne Dick
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> --
> >> Jim Allan, Accessibility Coordinator
> >> Texas School for the Blind and Visually Impaired
> >> 1100 W. 45th St., Austin, Texas 78756
> >> voice 512.206.9315<tel:512.206.9315>    fax: 512.206.9264<tel:
> 512.206.9264>
> >> http://www.tsbvi.edu/
> >> "We shape our tools and thereafter our tools shape us." McLuhan, 1964
> >>
> >>
> >
> >
> > --
> > Laura L. Carlson
>