- From: Becky Gibson <Becky_Gibson@notesdev.ibm.com>
- Date: Mon, 6 Feb 2006 14:31:13 -0500
- To: public-wcag-teamb@w3.org
I have created failure techniques for several success criteria in GL 1.3. 1.3.1: notification of draft failure techniques previously sent to team b list [0]. 1.3.2: Failure due to providing text alternatives that include words that appear in a text image, but fail to include information that is conveyed by the color of certain words in the image [1] 1.3.3: Failure due to using CSS to create variations in presentation of text that conveys information without also using structure.[2] 1.3.4: no failures listed 1.3.5: There are two existing failure that still need decisions and one that I think can reuse a 1.3.1 failure. 1. Failure due to positioning information with CSS so that the visual reading order or the programmatically determined reading order does not convey the meaning of the content. [3] It seems to have a failure example and a good example - perhaps this should be split into a failure technique and a positive CSS technique? 2. I have already proposed removing this one, Failure due to positioning information with HTML layout tables so that the visual reading order or the programmatically determined reading order does not convey the meaning of the content. See my proposal at [4]. 3. I believe that this one (which is currently empty), Failure due to creating multiple columns of text in a plain text document by including lines from both columns, separated by a tab character, in a single text line, can be replaced with the one I create for 1.3.1, Failure due to using space characters to create multiple columns in simple text content. [5]. 1.3.6 has two failures: 1. Failure due to identifying content only by its shape or location. [6] 2. Failure due to using "?"(circle mark glyph) and/or "?"(cross mark glyph) alone in order to convey information such as "available" or "not available", "good" or "bad", "yes" or "no" in the comparison table which shows the characteristics of the products. [7]. Which I suggest renaming to, "Failure due to using a non-text mark alone in order to convey information". Please try to review before the team b meeting so we can decide if these are ready for survey and determine what to do with the CSS failure for 1.3.5. thanks, -becky [0] http://lists.w3.org/Archives/Public/public-wcag-teamb/2006Feb/0023.html [1] http://trace.wisc.edu/wcag_wiki/index.php?title=Failure_due_to_providing_text_alternatives_that_include_words_that_appear_in_a_text_image%2C_but_fail_to_include_information_that_is_conveyed_by_the_color_of_certain_words_in_the_image [2] http://trace.wisc.edu/wcag_wiki/index.php?title=Failure_due_to_using_CSS_to_create_variations_in_presentation_of_text_that_conveys_information_without_also_using_structure [3] http://trace.wisc.edu/wcag_wiki/index.php?title=Failure_due_to_positioning_information_with_CSS_so_that_the_visual_reading_order_or_the_programmatically_determined_reading_order_does_not_convey_the_meaning_of_the_content [4] http://lists.w3.org/Archives/Public/public-wcag-teamb/2006Feb/0038.html [5] http://trace.wisc.edu/wcag_wiki/index.php?title=Failure_due_to_using_space_characters_to_create_multiple_columns_in_simple_text_content [6] http://trace.wisc.edu/wcag_wiki/index.php?title=Failure_due_to_identifying_content_only_by_its_shape_or_location [7] http://trace.wisc.edu/wcag_wiki/index.php?title=Failure_due_to_using_%22%E2%97%8B%22%28circle_mark_glyph%29_and/or_%22%C3%97%22%28cross_mark_glyph%29_alone_in_order_to_convey_information_such_as_%22available%22_or_%22not_available%22%2C_%22good%22_or_%22bad%22%2C_%22yes%22_or_%22no%22_in_the_comparison_table_which_shows_the_characteristics_of_the_products Becky Gibson Web Accessibility Architect IBM Emerging Internet Technologies 5 Technology Park Drive Westford, MA 01886 Voice: 978 399-6101; t/l 333-6101 Email: gibsonb@us.ibm.com
Received on Monday, 6 February 2006 19:31:21 UTC