Re: Understanding Success Criterion 1.4.8 | Understanding WCAG 2.0

I'd like to make a comment pleas:
 
There's an apparent contradiction within Understanding 1.4.8:  
 
http://www.w3.org/TR/2007/WD-UNDERSTANDING-WCAG20-20071211/visual-audio-
contrast-visual-presentation.html 
 
In the Intent of this Success Criterion  
 
"People with some cognitive, language and learning disabilities and some
low vision users cannot perceive the text and/or lose their reading
place if the text is presented in a manner that is difficult for them to
read. " 
 
and again under benefits:
 
Specific Benefits of Success Criterion 1.4.7: (sic)
 
This Success Criterion helps low vision users by letting them see text
without distracting presentational features. It lets them configure text
in ways that will be easier for them to see by letting them control the
color and size of blocks of text. 
 
....
 
People with some cognitive disabilities can read text better when they
select their own foreground and background color combinations. 
 
All of which appears to indicate that users should be allowed to define
foreground and background colors in their browsers.
 
However, this isn't reflected in the techniques, where, the first bullet
point seems to recommend specifying background and text colours. 
 
Sufficient Techniques 
1. Techniques to ensure foreground and background colors can be selected
by the user 
 

* Specifying foreground and background colors in CSS (future link) OR 
 
* Providing a color selection tool that allows a pastel background
(future link) OR 
 
* Providing a multi color selection tool on the page for foreground and
background colors (JavaScript, Future Link) OR 
 
* Using a technology that has commonly-available user agents that can
change the foreground and background of blocks of text (General, future
link) 
 
 
If authors DO specify all foreground and background colors, it is
virtually impossible for users to select their preferred, or required,
choice, without also losing visual clues to menu bars etc.  Colour is an
important aid to recognising menu content when reading is difficult.
 
Shouldn't the first sufficient technique ask authors to refrain from
specifying inessential foreground and background  colors for substantial
blocks of text?   After that, the current list  could continue, with a
slight amendment to the present first bullet:
* Any specified foreground and background colors are in CSS, not HTML
(future link) OR 
 
 
I do hope I've made this clear, but do reply if there are any questions.
I'd be delighted to create a page that demonstrates the advantages of
not specifying either background or foreground, if this would help.

Kind regards,


Bim
--------
Bim Egan
Website Accessibility Consultant
T: 020 7391 2048
M: 07973 788613
E: Bim.Egan@rnib.org.uk
A: 105 Judd Street, London, WC1H 9NE

Need to know more about web accessibility? Enrol on one of our training
courses.
http://www.rnib.org.uk/webaccesstraining


Also keep up to date with news in the world of accessibility in our blog
at http://www.rnib.org.uk/wacblog




-- 
DISCLAIMER:

NOTICE: The information contained in this email and any attachments is 
confidential and may be privileged.  If you are not the intended 
recipient you should not use, disclose, distribute or copy any of the 
content of it or of any attachment; you are requested to notify the 
sender immediately of your receipt of the email and then to delete it 
and any attachments from your system.

RNIB endeavours to ensure that emails and any attachments generated by
its staff are free from viruses or other contaminants.  However, it 
cannot accept any responsibility for any  such which are transmitted.
We therefore recommend you scan all attachments.

Please note that the statements and views expressed in this email and 
any attachments are those of the author and do not necessarily represent
those of RNIB.

RNIB Registered Charity Number: 226227

Website: http://www.rnib.org.uk



This message has been scanned for viruses by BlackSpider MailControl - www.blackspider.com