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 [2019/07/23 19:46] rachel.osolen [Definition Lists] |
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. | ||
Line 8: | Line 10: | ||
< | < | ||
- | * [[public: | + | * [[public: |
* [[public: | * [[public: | ||
* [[public: | * [[public: | ||
Line 33: | Line 35: | ||
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 " |
{{: | {{: | ||
Line 43: | Line 45: | ||
{{: | {{: | ||
+ | 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. | + | 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 of what I'm referring to regarding the sections that need to be lists. |
- | This will give us the below output in XML: | + | {{ :public: |
- | < | + | {{ : |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | </ | + | |
- | + | ||
- | Definition lists are not restricted to glossaries of terms. We use them for all term-description groups. Term-description groups may be names and definitions, | + | |
- | For example, a list of cast members | + | 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 |
- | Cast | ||
- | |||
- | 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: | ||
- | |||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | </ | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | </ | ||
- | |||
- | As mentioned above, definition lists should also be used for Q & A or interviews within a text. For example, in the following text, the first line (Q) should be be Definition Term style, and the second line (A) should be Definition Data style: | ||
- | |||
- | Q: Did you fight any other battles during the course of the war?\\ A: No. I hiked east two days, hitched a ride near Cross Lake and ended up back in my hometown in southern Alabama. | ||
- | |||
- | < | ||
- | |||
- | =====Q& | ||
- | |||
- | **Q: Should this list be formatted using H2 and H3 for the countries and institutions, | ||
- | |||
- | {{ : | ||
- | |||
- | A: Yes, using H2 for Canada, with the underlying content a nested list, seems like a logical structure. | ||
---- | ---- | ||
Line 163: | Line 84: | ||
WCAG 2.0 - H40: [[https:// | WCAG 2.0 - H40: [[https:// | ||
+ | |||
+ | [[public: |