End to End analysis of Guideline 1.5

Summary

Level 1 Success Criteria for Guideline 1.3 seems well supported by HTML techniques document. Beyond that I did not find clear techniques to the level two success criteria a Information presented using color is also available without color and without having to interpret markup .

I found gateway techniques had less details on what tasks needed to be completed, then the success criteria had itself

CSS techniques document did not directly address this guideline, although , of course, there was a lot of implied and defacto useful help for this checkpoint.

The guidelines in the document

Guideline 1.3 in WCAG 2.0 - Ensure that information, functionality, and structure are separable from presentation.

Level 1 Success Criteria for Guideline 1.3

  1. The following can be derived programmatically (for example, through a markup or data model) from the content without requiring user interpretation of presentation. [I]

    1. Hierarchical elements and relationships, such as:

      • paragraphs

      • lists

      • headings

      • associations between table cells and their headers

    2. Non-hierarchical relationships between elements such as:

      • cross-references and other associations,

      • associations between labels and controls,

    3. Emphasis or other formatting of specific words, phrases, and quotes.

      Level 2 Success Criteria for Guideline 1.3 - Information presented using color is also available without color and without having to interpret markup (for example through context or text coding). @@issue 317 [V]

      Gateway - Guideline 1.3

      Gateway seemed to think that there was two subsections

      1.3.1 - Ensure that information, functionality, and structure are separable from presentation. The document explain=ned the advantages with some HTML examples but without the full details of what needs to be done were. The task was set to: Ensure both [information/substance] and structure are separable from presentation.

      1.3.2 was the Presentation of structure

      HTML Techniques - Guideline 1.3

      This document had a lot on how to use structural mark up. This list is not exhaustive:

      • Section 3 talked about Structural Grouping.
      • Section 3.1 talks about headings.
      • Section 3.2 tells the user to use CSS, not HTML header elements, to create font effects.
      • 5.7 Markup and style sheets rather than images: The example of math,
      • 5.8 Eight other structural elements (to identify citations, code fragments, deleted text, and others).
      • section 6 Lists section 7 talks about this issue for tables

      There was also the following technique on color: To further ensure that users understand differences between list items indicated visually, content developers should provide a text label before or after the list item phrase:

      CSS Techniques - Guideline 1.3

      This document had a lot of implied relivense - but I did not see the explicit reference to this checkpoint that I anticipated. For example it was not brought as a user benefit.

      Providing good structural markup for graceful degradation had examples that shows a meaningful presentation when style sheets are not applied. I did not find that too relevant.