- From: Gregg Vanderheiden <gv@trace.wisc.edu>
- Date: Tue, 29 Nov 2005 23:27:33 -0600
- To: <w3c-wai-gl@w3.org>
- Message-ID: <003801c5f56e$c9091330$ee8cfea9@NC6000BAK>
Here are the open issues for 1.4 8 can be closed due to current wording 1 can be closed because suggestion is not technically possible today Proposals are presented for last 4 to close them. Gregg Suggests the following be CLOSED * 344. <http://trace.wisc.edu/bugzilla_wcag/issuereports/visual-audio-contrast_issu es.php#344> Algorithm for testing foreground/background contrast. * this one says we should have a success criterion regarding foreground background contrast like the one we now have. * Suggest we CLOSE this with comment "success criterion 1.4.1 and 1.4.3 now meet this need" * 454. <http://trace.wisc.edu/bugzilla_wcag/issuereports/visual-audio-contrast_issu es.php#454> sugg. test for contrast * This one says that a tool is in development but that algorithm isn't complete. * Suggest we CLOSE this with comment "algorithm now exists in 1.4.1 and 1.4.3" * 489. <http://trace.wisc.edu/bugzilla_wcag/issuereports/visual-audio-contrast_issu es.php#489> how to objectively measure questionable contrast? * Need an algorithm that would make measuring contrast objectively measurable. * Suggest we CLOSE this with comment "algorithm now exists in 1.4.1 and 1.4.3" * 592. <http://trace.wisc.edu/bugzilla_wcag/issuereports/visual-audio-contrast_issu es.php#592> what are "standard foreground/background contrast reqs."? * What are the "standard foreground/background contrast requirements"? If there are any, please clarify (and cite) * Suggest we CLOSE this with comment "algorithm now exists in 1.4.1 and 1.4.3" * 996. <http://trace.wisc.edu/bugzilla_wcag/issuereports/visual-audio-contrast_issu es.php#996> Codifying color contrast * Suggests a method for contrast. " When I read that text, the first thing I thought of was finding the effective luminance of the two colors and requiring some minimum separation." * Suggest we CLOSE this with comment "algorithm now exists in 1.4.1 and 1.4.3" * 1699. <http://trace.wisc.edu/bugzilla_wcag/issuereports/visual-audio-contrast_issu es.php#1699> Take colorblindness into account when evaluating contrast * Two issues. One is contrast if user has color blindness * Second is that no information shall built on that you have to be able to see a certain color * SUGGEST CLOSING with message "Current algorithm in 1.4.1 and 1.4.3 takes color deficiency in to account by using luminosity" and success criterion 1.3.2 requires color not be only way to convey information * 1719. <http://trace.wisc.edu/bugzilla_wcag/issuereports/visual-audio-contrast_issu es.php#1719> L2 SC2 is difficult to follow * All that is said by commenter is "1.4 L2 SC2 is difficult to follow" * Suggest we CLOSE this with comment "1.4 L2 SC2 (now 1.4.2) reworded for clarity" * 1736. <http://trace.wisc.edu/bugzilla_wcag/issuereports/visual-audio-contrast_issu es.php#1736> GL 1.4 L1 - should require colors to be visually discernible * Shouldn't there be a requirement for the colours to be visually discernable? This does not protect against near identical shades of green being used for both foreground and background. This also risks the possibility of colour-blind users being unable to discern the foreground from the background. [TWG] * SUGGEST CLOSING with message "Current algorithm in 1.4.1 and 1.4.3 takes color deficiency in to account by using luminosity contrast" Suggest we close the following item by rejecting it. * 1528. <http://trace.wisc.edu/bugzilla_wcag/issuereports/visual-audio-contrast_issu es.php#1528> Question about example * suggested example: as it is possible with graphics to change the contrast, it is possible (if the speech was recorded separately, or not, thanks to sound processing algorithms) to let the end user choose whether (s)he wants the background sound a all, and leave the possibility to set the contrast between the two. * Suggest CLOSING this with the comment "Unless content has separate tracks for foreground and background sound this is not possible. Since this is not currently done with content (only with source tapes), nor do user agents allow mixing of tracks, this would not be an option to users or authors". Suggest we consider the following and close these items. * 892. <http://trace.wisc.edu/bugzilla_wcag/issuereports/visual-audio-contrast_issu es.php#892> Readable fonts * JIS has a guideline that describes choosing default readable fonts. Suggestion that we consider something similar * This is not yet addressed. * Choices * Reject this suggestion as not being something we want to require. * Add this as a level 3 success criterion * Add this as an advisory technique under 1.4.3 (because larger fonts make it easier to tell text from background) * 1522. <http://trace.wisc.edu/bugzilla_wcag/issuereports/visual-audio-contrast_issu es.php#1522> Criterion needed to address increasing font size * "At the 27 April 2005 Techniques Task Force of the WCAG WG telecon [1], we determined that text magnification and reflow of content is not addressed by existing success criteria. We felt it related best to this guideline because it talks about consistent presentation and visual design. There is concern about how large of a font developers should test with. Someone should do research to determine the general rule of thumb for users to move from using the browser to increase the font size to using magnification software." * This is not yet addressed. * Choices * Reject this suggestion as not being something we want to require. * Add this as an advisory technique under 1.4.3 (or under the guideline itself) * "Testing their pages with increased font sizes up to 8 times default to see if the content will enlarge and wrap appropriately." * 1706. <http://trace.wisc.edu/bugzilla_wcag/issuereports/visual-audio-contrast_issu es.php#1706> 1.4 guideline text not general enough (should also mention color) * Guideline 1.4 does not seem general enough, specifying images or sound, but not colour (though colour is mentioned is the level 1 success criteria). * SUGGEST we drop "images and sound from Guideline to change Guideline * FROM: Guideline 1.4 Make it easy to distinguish foreground information from background images or sounds * TO Guideline 1.4 Make it easy to distinguish foreground information from background. * Then CLOSE this item with message " removed 'images and sound' to meet this issue. 1707. <http://trace.wisc.edu/bugzilla_wcag/issuereports/visual-audio-contrast_issu es.php#1707> L1 SC seems a little weak * 1737. <http://trace.wisc.edu/bugzilla_wcag/issuereports/visual-audio-contrast_issu es.php#1737> GL 1.4 Example 1 - Overlaying text on an image may blend into the darker area of the image * This one questions one of our examples where we have text over an image. * SUGGEST WE * Change example to say that "Area around lettering that is part of an image is made lighter so that the letters contrast with the background image" * CLOSE ISSUE this with message " Example changed to reflect fact that lettering is part of image - not "text" displayed over an image. " Gregg ------------------------ Gregg C Vanderheiden Ph.D. Professor - Depts of Ind. Engr. & BioMed Engr. Director - Trace R & D Center University of Wisconsin-Madison < <http://trace.wisc.edu/> http://trace.wisc.edu/> FAX 608/262-8848 For a list of our list discussions http://trace.wisc.edu/lists/ <http://trace.wisc.edu:8080/mailman/listinfo/>
Received on Wednesday, 30 November 2005 05:27:48 UTC