This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
public:nnels:etext:lists [2017/11/02 16:42] farrah.little [Use the correct list type] |
public:nnels:etext:lists [2024/05/09 05:04] (current) |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ===== Lists ===== | + | ====== Lists ====== |
- | Lists are often overlooked as an accessibility feature, but the ability to move quickly and effectively through long lists of points is a key reading need. Unfortunately, | + | Lists are often overlooked as an accessibility feature, but the ability to move quickly and effectively through long lists of points is a key reading need. |
+ | |||
+ | Unfortunately, | ||
When a reader has to traverse every item in the list one item at a time to get to the end, or listen to the entire list from beginning to end, the problems of bad markup become more pronounced. Properly tagging lists is a small measure that can greatly decrease reader frustration. | When a reader has to traverse every item in the list one item at a time to get to the end, or listen to the entire list from beginning to end, the problems of bad markup become more pronounced. Properly tagging lists is a small measure that can greatly decrease reader frustration. | ||
< | < | ||
+ | |||
+ | < | ||
+ | * [[public: | ||
+ | * [[public: | ||
+ | * [[public: | ||
+ | </ | ||
Do not make lists with just manually typed characters like dashes, numbers, asterisks, or graphics as a screenreader may not be able to read the list in the proper order. When bullet or numbered list formatting is used, screenreaders will properly announce the text as being part of a list, and provide a means for the user to quickly navigate between items as well as move in and out of lists. | Do not make lists with just manually typed characters like dashes, numbers, asterisks, or graphics as a screenreader may not be able to read the list in the proper order. When bullet or numbered list formatting is used, screenreaders will properly announce the text as being part of a list, and provide a means for the user to quickly navigate between items as well as move in and out of lists. | ||
< | < | ||
- | ====Create a list in Word==== | + | =====Create a list in Word===== |
Use the appropriate button in Word’s formatting toolbar, i.e. bullet or numbered list. | Use the appropriate button in Word’s formatting toolbar, i.e. bullet or numbered list. | ||
Line 20: | Line 28: | ||
{{: | {{: | ||
- | ====Use the correct list type==== | + | =====Use the correct list type===== |
Using the correct list type is also important as it may be the only cue to the reader whether the order of items is significant. An alphabetical list is not necessarily an ordered list; for example, arranging items is not the same as assigning them a specific order. If you can re-arrange the items without changing the meaning of the list, you've defined an unordered list (i.e. indexes and bibliographies do not lose meaning when re-ordered). | Using the correct list type is also important as it may be the only cue to the reader whether the order of items is significant. An alphabetical list is not necessarily an ordered list; for example, arranging items is not the same as assigning them a specific order. If you can re-arrange the items without changing the meaning of the list, you've defined an unordered list (i.e. indexes and bibliographies do not lose meaning when re-ordered). | ||
- | ===Unordered=== | + | ====Unordered==== |
For unordered lists, use the bulleted list tool. The icon looks like this: {{: | For unordered lists, use the bulleted list tool. The icon looks like this: {{: | ||
- | Optional: for display purposes, you can create an invisible bullet using " | + | Optional: for display purposes, you can create an invisible bullet using " |
{{: | {{: | ||
{{: | {{: | ||
- | ===Ordered=== | + | ====Ordered==== |
For ordered lists, use the numbered list tool. The icon looks like this: | For ordered lists, use the numbered list tool. The icon looks like this: | ||
{{: | {{: | ||
+ | Sometimes you will have text that has ordered lists that are broken up by other bodies of text. In these instances: | ||
+ | * Highlight the section that is part of the list | ||
+ | * Apply the ordered list as usual | ||
+ | * Scroll down to the next instance of the ordered list | ||
+ | * Highlight and repeat | ||
- | ===Definition Lists=== | + | < |
- | In addition | + | For more information on how to continue ordered |
- | Definition lists generally consist of term/definition pairs - a term followed by its definition. | + | < |
- | For example, a glossary of terms would be a definition list: | + | <note tip>If you have any questions, check the archive below, if still not clear, post your question on the [[public: |
+ | </ | ||
- | | + | ---- |
- | | + | |
- | | + | |
- | | + | |
- | There are two definition list styles in the [[public: | ||
- | * Definition Data (DAISY) | + | =====Q& |
- | * Definition Term (DAISY) | + | |
- | Both styles are used together to create a definition list. When creating a definition | + | **Q: Should this list be formatted using H2 and H3 for the countries and institutions, and Lists for the collections? |
- | - Select all the text that comprise the list (terms and values) and apply the **Definition Data (DAISY)** style. | + | {{ : |
- | - Select each definition term (i.e. mango, lychee, etc.) and apply the **Definition Term (DAISY)** style. | + | |
- | That's it. This will give us the below output in XML: | + | A: Yes, using H2 for Canada, with the underlying content a nested list, seems like a logical structure. |
- | < | + | Q: I'm working on the Cooking for Two cookbook. I know that we format something as a list, even when it isn't presented that way in the source file, and we previously discussed formatting the recipe variation sections as lists. My questions is to what degree do I format these sections as lists? Should I just make each sentence a list? Or when there is a list within a sentence should I use a nested list? This often occurs when they are listing what to substitute. I've been debating back and forth, and I know consistency is important. I'm a bit in the weeds on this and really appreciate your help. The following are two instances |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | </ | + | |
- | + | ||
- | Definition | + | |
- | For example, a list of cast members should be marked up as a definition list: | + | {{ :public: |
- | | + | {{ :public:nnels:etext:screen_shot_2021-11-04_at_10.24.22_am.png? |
- | + | ||
- | Rita: Jennifer Copping | + | |
- | | + | |
- | | + | |
- | Asta: Caitlin McFarlane | + | |
- | | + | |
- | + | ||
- | | + | |
- | + | ||
- | | + | |
- | | + | |
- | | + | |
- | Sound Designer: James Coomber | + | |
- | | + | |
- | Stage Manager: Collette Brown | + | |
- | | + | |
- | | + | |
- | | + | |
- | + | ||
- | With the application of the definition list styles, this results in the below XML output: | + | |
- | + | ||
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | </ | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | </ | + | |
+ | A: The general rule is if it is a list, or can be a list (i.e. directions, items separated by commas, etc.) then it should be formatted as such. I am going to download the book and take a look more at the pages again. I will update this space once I have a clearer idea of the changes in the book. | ||
---- | ---- | ||
WCAG 2.0 — H48: [[http:// | WCAG 2.0 — H48: [[http:// | ||
+ | |||
+ | WCAG 2.0 - H40: [[https:// | ||
+ | |||
+ | [[public: |