Relationships be programmatically determined rather than described in text. Support programmatic relationships, it is strongly encouraged that information and Should be programmatically determined or be presented in text. There may also be cases where it may be a judgment call as to whether the relationships (when the page is linearized), such as in the parent element or in the adjacent element. The text description should be near the information it is describing For instance, "all required fields are marked In that case then there should be a text description Some technologies do not provide a means to programmatically determine some types Who cannot perceive red, still has the information about the price as long as it is An on-lineĬatalog may indicate prices using a larger font colored red. Reader user will hear that the item is a link when the glossary term is encounteredĮven though they may not receive information about the change in font face. If links to glossary items are implemented using anchor elements (or the proper linkĮlement for the technology in use) and identified using a different font face, a screen Has been properly provided to all users is to access the information serially in different One method of determining whether or not information When such relationships are perceivable to one set of users, those relationships canīe made to be perceivable to all. Important information or to indicate quoted text etc. Of a new section a change in voice pitch or speech rate may be used to emphasize For example, a chime might indicate the beginning Having these structures and these relationships programmaticallyĭetermined or available in text ensures that information important for comprehensionĪuditory cues may be used as well. To each other words that have special status are indicated by changing the font familyĪnd /or bolding, italicizing, or underlining them items that share a common characteristicĪre organized into a table where the relationship of cells sharing the same row orĬolumn and the relationship of each cell to its row and/or column header are necessaryįor understanding and so on. Rows and columns form fields may be positioned as groups that share text labels Ī different background color may be used to indicate that several items are related List items are preceded by a bullet and perhaps indented paragraphs are separatedīy a blank line items that share a common characteristic are organized into tabular headings are often in a larger, bold font separated from paragraphs by blank lines Sighted users perceive structure and relationships through various visual cues For example, the presentation format changes when the content is readīy a screen reader or when a user style sheet is substituted for the style sheet provided That are implied by visual or auditory formatting are preserved when the presentationįormat changes. The intent of this Success Criterion is to ensure that information and relationships Success Criterion 1.3.1 Info and Relationships (Level A): Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. Understanding Success Criterion 1.3.1: Info and Relationships
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |