[Draft] Method Prototype for Information and Relationships

Original:

Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.

Draft: Information and Relationships

Short Description:

Code matches presentation

Long Description:

Make the code correspond to the visual layout, or describe the visual layout in text.

Expected Outcome: [task-based outcome]

Screen reader users have a similar experience of the structure of the document as a sighted people and can quickly find sections of the page.

Related Methods

Instructions: Select the situation below that matches your content.

1. ARIA11: Using ARIA landmarks to identify regions of a page (ARIA)

2. ARIA12: Using role=heading to identify headings (ARIA)

3. ARIA13: Using aria-labelledby to name regions and landmarks (ARIA)

4. ARIA16: Using aria-labelledby to provide a name for user interface controls (ARIA)

5. ARIA17: Using grouping roles to identify related form controls (ARIA)

6. ARIA20: Using the region role to identify a region of the page (ARIA)

7. G115: Using semantic elements to mark up structure AND H49: Using semantic markup to mark emphasized or special text (HTML)

8. G117: Using text to convey information that is conveyed by variations in presentation of text

9. G140: Separating information and structure from presentation to enable different presentations

10. Making information and relationships conveyed through presentation programmatically determinable using the following techniques:

    • G138: Using semantic markup whenever color cues are used

    • H51: Using table markup to present tabular information (HTML)

    • PDF6: Using table elements for table markup in PDF Documents (PDF)

    • PDF20: Using Adobe Acrobat Pro's Table Editor to repair mistagged tables (PDF)

    • H39: Using caption elements to associate data table captions with data tables (HTML)

    • FLASH31: Specifying caption text for a DataGrid (Flash)

    • H73: Using the summary attribute of the table element to give an overview of data tables (HTML)

    • FLASH23: Adding summary information to a DataGrid (Flash)

    • H63: Using the scope attribute to associate header cells and data cells in data tables (HTML)

    • H43: Using id and headers attributes to associate data cells with header cells in data tables (HTML)

    • FLASH21: Using the DataGrid component to associate column headers with cells (Flash)

    • H44: Using label elements to associate text labels with form controls (HTML)

    • H65: Using the title attribute to identify form controls when the label element cannot be used (HTML)

    • PDF10: Providing labels for interactive form controls in PDF documents (PDF)

    • PDF12: Providing name, role, value information for form fields in PDF documents (PDF)

    • FLASH32: Using auto labeling to associate text labels with form controls (Flash)

    • FLASH29: Setting the label property for form components (Flash)

    • FLASH25: Labeling a form control by setting its accessible name (Flash)

    • H71: Providing a description for groups of form controls using fieldset and legend elements (HTML)

    • SL20: Relying on Silverlight AutomationPeer Behavior to Set AutomationProperties.Name (Silverlight)

    • SL26: Using LabeledBy to Associate Labels and Targets in Silverlight (Silverlight)

    • H85: Using OPTGROUP to group OPTION elements inside a SELECT (HTML)

    • H48: Using ol, ul and dl for lists or groups of links (HTML)

    • H42: Using h1-h6 to identify headings (HTML)

    • PDF9: Providing headings by marking content with heading tags in PDF documents (PDF)

    • SCR21: Using functions of the Document Object Model (DOM) to add content to a page (Scripting)

    • PDF11: Providing links and link text using the Link annotation and the /Link structure element in PDF documents (PDF)

    • PDF17: Specifying consistent page numbering for PDF documents (PDF)

    • PDF21: Using List tags for lists in PDF documents (PDF)

    • H97: Grouping related links using the nav element (HTML)

11. Fallback Method (for new technologies and situations where the methods above don't apply) : Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.

Examples:

Same is current understanding.

Tests:

Associated Tags: [Static Web, Perceivable, Distinguishable, Operable]

Questions to ask yourself to assess your draft:

• Is the Style Guide understandable to follow? Yes
• Did the outcome match the instruction? I hope so.
• Did the particular success criterion that you chose to re-write present a challenge to this process? I'm not sure. Right now I don't know where the measurable statements will live. I'm guessing the trouble with keeping things short may be that most of the wordiness in WCAG is caused by the important exceptions. It reminds me of Einstein's quote "Make things as simple as possible, but no simpler."