W3C home > Mailing lists > Public > public-comments-wcag20@w3.org > November 2011

Potential update to G18 or new failure technique for SC 1.4.3 [SEC=UNCLASSIFIED]

From: Calais, Raven <Raven.Calais@finance.gov.au>
Date: Thu, 24 Nov 2011 11:40:03 +1100
To: "public-comments-wcag20@w3.org" <public-comments-wcag20@w3.org>
CC: WCAG 2 <WCAG2@finance.gov.au>, "Van Teulingen, Jacqui" <Jacqui.vanTeulingen@finance.gov.au>, "Arch, Andrew" <Andrew.Arch@finance.gov.au>
Message-ID: <20FD9C4C0F47EA4B8E9DE659AE8F6CD26609E0CD36@PCW9FINMB03.mercury.network>
Greetings WCAG 2.0 Working Group

Update to Technique G18
I would like to make a recommendation to update General Technique 18, or create a new failure technique for insufficient colour contrast on anti-aliased text, to help address Success Criterion 1.4.3.

The problem occurs for anti-aliased text which while having sufficient colour contrast on vertical strokes, has insufficient contrast on pixels in parts of the character (especially diagonal strokes or corners of letters). To support this case, I have included two images of a website which currently displays this anti-aliased text which in parts both passes and fails G18. The text in the image uses #545454 on #ffffff (has a ratio of 7.6:1, but in parts of the anti-aliased letters has a ratio of just 1.7:1). This is especially problematic when viewing the text at normal size, as the font appears fuzzy and not sufficiently visible.

This was noticed on this website: http://www.verseone.com/main.cfm?type=WEBACCESSIBILITY on 24/11/11. I tested in Firefox 7.0.1 and Internet Explorer 8, as well as the Colour Contrast Analyser (Vision Australia) and the Firefox plug-in WCAG Contrast checker 1.1.02.

The lack of sufficient colour contrast appears on anti-aliased text typically on light/fine or serif fonts, or on thin character parts such as in the letters k, e, w and o as well as some numbers.

Currently G18 notes: "Note: For aliased letters, use the relative luminance value found two pixels in from the edge of the letter."

I would add that for anti-aliased letters, that perhaps a wider sample (2x2 or 4x4 pixels) or sampling all of horizontal, vertical and diagonal stokes (for at least one character) should be taken to find a more accurate sampling of text colour. This would only likely be an issue for anti-aliased text below 14pt or not bold.

I welcome your review or comment on this issue.

Wrong link
As an aside, the second link to the  Techniques Submission Form, from the Techniques page (http://www.w3.org/TR/WCAG20-TECHS/) under "Status of This Document", actually points to a WCAG 1 conformance logo page. See: http://www.w3.org/WAI/WCAG1-Conformance


Thanks and kind regards


Ravenna Calais

Senior Policy Officer
Web Advice and Policy
Australian Government Information Management Office (AGIMO)
Department of Finance and Deregulation

p: 02 6215 2048 | e: raven.calais@finance.gov.au<mailto:raven.calais@finance.gov.au>
w: http://webguide.gov.au/



________________________________

Finance Australian Business Number (ABN):   61 970 632 495	 
Finance Web Site:   www.finance.gov.au	 

IMPORTANT:

This transmission is intended only for the use of the addressee and may contain confidential or legally privileged information. If you are not the intended recipient, you are notified that any use or dissemination of this communication is strictly prohibited. 
If you have received this transmission in error, please notify us immediately by telephone on 61-2-6215-2222 and delete all copies of this transmission together with any attachments. 
If responding to this email, please send to the appropriate person using the suffix .gov.au. 

________________________________





anti-aliased text screen300pc.jpg
(image/jpeg attachment: anti-aliased_text_screen300pc.jpg)

anti-aliased text screen shot.jpg
(image/jpeg attachment: anti-aliased_text_screen_shot.jpg)

Received on Thursday, 24 November 2011 00:41:55 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:11:14 UTC