This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
public:nnels:etext:lists [2019/10/02 11:22] rachel.osolen [Definition Lists] |
public:nnels:etext:lists [2020/08/01 09:13] rachel.osolen |
||
---|---|---|---|
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 53: | Line 55: | ||
For more information on how to continue ordered lists with breaks please see this [[https:// | For more information on how to continue ordered lists with breaks please see this [[https:// | ||
- | ====Definition Lists==== | ||
- | |||
- | In addition to the common types of lists mentioned above, there also exists what we call a " | ||
- | |||
- | Definition lists generally consist of term/ | ||
- | |||
- | For example, a glossary of terms would be a definition list: | ||
- | |||
- | | ||
- | | ||
- | | ||
- | | ||
- | |||
- | There are two definition list styles in the [[public: | ||
- | |||
- | * Definition Data (DAISY) | ||
- | * Definition Term (DAISY) | ||
- | |||
- | Both styles are used together to create a definition list. When creating a definition list, we follow these steps: | ||
- | |||
- | - 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: | ||
- | < | + | =====Q& |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | </ | + | |
- | + | ||
- | 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, | + | |
- | =====Q& | + | |
**Q: Should this list be formatted using H2 and H3 for the countries and institutions, | **Q: Should this list be formatted using H2 and H3 for the countries and institutions, |