- From: Katie Haritos-Shea <ryladog@gmail.com>
- Date: Tue, 10 May 2016 15:14:36 -0400
- To: CAE-Vanderhe <gregg@raisingthefloor.org>
- Cc: Joshue O Connor <josh@interaccess.ie>, Jonathan Avila <jon.avila@ssbbartgroup.com>, "Patrick H. Lauke" <redux@splintered.co.uk>, GLWAI Guidelines WG org <w3c-wai-gl@w3.org>
- Message-ID: <CAEy-OxGMhKmejEWpX3LSCnfzEYKCRGjTThgrA9+3KJov455TWg@mail.gmail.com>
Another option is to have a two or more pixel - halo like - contrasting color right behind/underneath the text (and on top of the busy background) - as is often done in parrallel s rilling situations for 1.4.3 conformance If the background is in motionat all, this calls in 2.2.2, stopping at a logical places and ensuring that those stopping points meet the 1.4.3 contrast requirements. Katie Haritos-Shea 703-371-5545 On May 10, 2016 11:45 AM, "Gregg Vanderheiden" <gregg@raisingthefloor.org> wrote: the problem with “readability” as a category is that it covers both “Perceivable” and “Understandable” If Readability is to be used in any future document — you will either need to abandon “Perceivable”, “Understandable” , etc. unless you break it into “Sensory Readability” and “Cognitive readability” . Also, it is interesting but some people associate “readability” only with visual reading. Readability of an audio recording does not make sense to them (e.g. cognitive readability is not recognized to all if there is no "visual readability” component) Comprehensibility Readability Clarity of perceivability Understandability all get confounded — with some people including comprehension in readability and others not — esp if the content is non-visual. Readability of a recording doesnt make sense but readability of its transcript does — and the will say readability of the transcript is both visual and wording but readability of the recording makes no sense to them… *gregg* On May 10, 2016, at 7:28 AM, Jonathan Avila <jon.avila@ssbbartgroup.com> wrote: Interesting, I'd say that's a maybe. As looking at 1.4.3, I see F83 does call out that the the background image should provide sufficient colour contrast, a better fit. It still doesn't explicitly address the issue of legibility, that may not be due to contrast issues. SC 1.4.3 is what we have at the A/AA level to address this. Perhaps readability is a topic for the next WCAG. Also of note, there has been some discussion in the LVTF about the difference between legibility and readability, etc. Jonathan -----Original Message----- From: josh@interaccess.ie [mailto:josh@interaccess.ie <josh@interaccess.ie>] Sent: Tuesday, May 10, 2016 7:49 AM To: Patrick H. Lauke; w3c-wai-gl@w3.org Subject: Re[2]: SC for 'real' text over a busy background image Interesting, I'd say that's a maybe. As looking at 1.4.3, I see F83 does call out that the the background image should provide sufficient colour contrast, a better fit. It still doesn't explicitly address the issue of legibility, that may not be due to contrast issues. One of the LVTF, if they haven't started looking at this already. Thanks Josh ------ Original Message ------ From: "Patrick H. Lauke" <redux@splintered.co.uk> To: w3c-wai-gl@w3.org Sent: 10/05/2016 12:36:22 Subject: Re: SC for 'real' text over a busy background image On 10/05/2016 12:32, josh@interaccess.ie wrote: I'm working with a client and finding text (real text) that is displayed over a busy background image that obscures its legibility. Currently I don't see a clear SC for this kind of problem and it seems to just sit somewhere under the principle that content must be perceivable. The closest that I see is 1.4.5. Am I missing something? 1.4.3 ? -- 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
Received on Tuesday, 10 May 2016 19:15:06 UTC