W3C home > Mailing lists > Public > spec-prod@w3.org > October to December 2011

Re: Working on New Styles for W3C Specifications

From: Steve Faulkner <faulkner.steve@gmail.com>
Date: Wed, 30 Nov 2011 10:24:57 +0000
Message-ID: <CA+ri+V=QqArk-=cee7eqN_8FSCR4ky8KHquJ2dzPxF=hgsChZQ@mail.gmail.com>
To: spec-prod@w3.org
Cc: Loretta Guarino Reid <Lorettaguarino@google.com>
Hi Vincent,

Loretta wrote:

"Speaking of all the contrast issues, can we please ensure that the new
style meets WCAG 2.0 AA? I haven't yet done an analysis, but this should be
a requirement."

I had a quick look at the shaders spec.

found the following:

http://dvcs.w3.org/hg/FXTF/raw-file/tip/custom/alternate-spec-style.css

link text
CSS:

a, a:visited, a:link, *:link {
    color: #46A4E9;
}

link hover

.toc a:hover {
    background-color: white;
    color: #46A4E9;
}


Colour contrast results:

Foreground:#46A4E9  Background:#FFFFFF

The contrast ratio is: 2.7:1 (needs to be at least 4.5:1)

Text failed at Level AA

Text failed at Level AAA


WCAG 2.0 SC 1.4.3 Contrast
(Minimum)<http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html>:
The visual presentation of text and images of text has a contrast ratio of
at least 4.5:1, except for the following: (Level AA)  Large Print:
Large-scale text and images of large-scale text have a contrast ratio of at
least 3:1;
tools for testing:

tools for testing
contrast<http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html#visual-audio-contrast-contrast-resources-head>

Also hover style which changes link text style should also be applied on
a:focus

a[href]:hover {
    background-color: white;
    color: #005A9C;
}

*WCAG 2.0 2.4.7 Focus
Visible:*<http://www.w3.org/TR/2008/REC-WCAG20-20081211/#navigation-mechanisms-focus-visible>Any
keyboard operable user interface has a mode of operation where the
keyboard focus indicator is visible. (Level AA)


Other:

Images don't have text alternatives:

example:

<img width="800" src="images/shader-model.png">

WCAG 2.0 1.1.1 Non-text
Content<http://www.w3.org/TR/2008/REC-WCAG20-20081211/#text-equiv-all>:All
non-text content<http://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv-all.html#non-text-contentdef>that
is presented to the user has a text
alternative<http://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv-all.html#text-altdef>that
serves the equivalent purpose, except for the situations listed below.
(Level A)

advice available in  HTML5: Techniques for providing useful text
alternatives <http://dev.w3.org/html5/alt-techniques/developer.html>
in particular  section 3.2 <http://goog_934301341>Graphical
representations: charts, diagrams, graphs, maps,
illustrations<http://dev.w3.org/html5/alt-techniques/developer.html#sec2>may
be helpful.

-- 
with regards

Steve Faulkner
Technical Director - TPG

www.paciellogroup.com | www.HTML5accessibility.com |
www.twitter.com/stevefaulkner
HTML5: Techniques for providing useful text alternatives -
dev.w3.org/html5/alt-techniques/
Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.html
Received on Wednesday, 30 November 2011 10:25:57 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 10 March 2012 06:19:18 GMT