W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2018

RE: Agenda for AGWG Call, Tuesday May 1, 2018

From: Jonathan Avila <jon.avila@levelaccess.com>
Date: Wed, 2 May 2018 00:05:28 +0000
To: Katie Haritos-Shea <ryladog@gmail.com>, Alastair Campbell <acampbell@nomensa.com>
CC: WCAG <w3c-wai-gl@w3.org>
Message-ID: <BN6PR03MB251304C163FC917AC48BEC1FF1800@BN6PR03MB2513.namprd03.prod.outlook.com>
A simple example like the following puts white text over a white background when you zoom in.   The content is still there – the contrast is just 0.

Zooming may or may not trigger responsive breakpoints.  Breakpoints, fluid sites, or other methods will be needed for SC 1.4.10.  If we don’t need to test other SCs for different breakpoints and the zoom user is forced into the breakpoint then there can be issues that the low vision user is forced into but prevent him/her from using the page.  For example, I’ve seen keyboard accessible pages that when flipped into a responsive view have keyboard focus issues because suddenly something that was displayed in one view is layered behind content in a responsive view but not taken out of the focus order.  I’ve also seen radio buttons that morph into combo boxes in different responsive views.   The roles of these items don’t reflect the new visual meaning failing SC 1.3.1 and breaking keyboard patterns.  So at the very least we have to test each breakpoint that the zoom user will be thrown into NOT by our choice.  We can’t say ok—you can zoom in but the site doesn’t actually have to have sufficient contrast anymore.  Or you can zoom in but now there is no indication of keyboard focus.  What’s the point of zooming in if the site then fails the other requirements of WCAG?  The content and functionality may be there but users can’t actually use it.  That seems to go against the intent of the having the functionality and content be available.


From: Katie Haritos-Shea <ryladog@gmail.com>
Sent: Tuesday, May 1, 2018 7:48 PM
To: Alastair Campbell <acampbell@nomensa.com>
Cc: WCAG <w3c-wai-gl@w3.org>
Subject: Re: Agenda for AGWG Call, Tuesday May 1, 2018

Thank you Alastair, I had just never thought about where a page reflows and would shift the text around over a background before - other than for text in SPAs - where we always suggest having a border or blur around text to accommodate any change to the background behind the text for 1.4.3. I don't think I have ever seen an example like the Hilton site before.

I want to weigh in on the combining SC issue - I am not for it. It adds too many layers of complexity. Each requirement needs to be testable independently IMO. If one wants that, one needs a SC that combines such things, as in the 1.4.12 that combines line height, letter spacing, paragraph spacing and word spacing wrapped into one SC.

* katie *

Katie Haritos-Shea
Principal ICT Accessibility Architect

WCAG/Section 508/ADA/AODA/QA/FinServ/FinTech/Privacy, IAAP CPACC+WAS = CPWA<http://www.accessibilityassociation.org/cpwacertificants>

Cell: 703-371-5545<tel:703-371-5545> | ryladog@gmail.com<mailto:ryladog@gmail.com> | Oakton, VA | LinkedIn Profile<http://www.linkedin.com/in/katieharitosshea/>

People may forget exactly what it was that you said or did,
but people will never forget how you made them feel.......

Our scars remind us of where we have been........they do not have to dictate where we are going.

On Tue, May 1, 2018 at 7:00 PM, Alastair Campbell <acampbell@nomensa.com<mailto:acampbell@nomensa.com>> wrote:
Katie wrote:
> The contrast change that Jon demonstrated (thanks that this was in the minutes) Hilton site is something I was entirely unaware of. Thanks for bring it to our attention, apparently again.....:-)

Just to note, that’s a non-responsive site that has somehow managed to find a way to not expand a background whilst everything else expands. Some absolute positioning and z-index stuff going on there.

You can see the logo in the top right stay fixed to the viewport, whilst the rest of the layout expands underneath.

If something fails 1.4.10 like this, I don’t think you can fail it on contrast on top of that? It isn’t providing other views (in the way the new note describes), so simply fails on 1.4.10

There are examples where a page reflows and text shifts around over a background though, which is where the question came from.



Received on Wednesday, 2 May 2018 00:06:26 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:08:26 UTC