[Draft] Method Prototype for Information and Relationships
Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.
Draft: Information and Relationships
Code matches presentation
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.
Instructions: Select the situation below that matches your content.
Same is current understanding.
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."