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 [2020/08/01 16:13] rachel.osolen |
public:nnels:etext:lists [2024/05/09 05:04] (current) |
||
---|---|---|---|
Line 3: | Line 3: | ||
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. | 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, | + | 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 35: | 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 54: | Line 54: | ||
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:// | ||
+ | |||
+ | < | ||
+ | |||
+ | <note tip>If you have any questions, check the archive below, if still not clear, post your question on the [[public: | ||
+ | </ | ||
+ | |||
+ | ---- | ||
Line 63: | Line 70: | ||
A: Yes, using H2 for Canada, with the underlying content a nested list, seems like a logical structure. | 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. | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | 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. | ||
+ | |||
---- | ---- | ||
Line 68: | Line 84: | ||
WCAG 2.0 - H40: [[https:// | WCAG 2.0 - H40: [[https:// | ||
+ | |||
+ | [[public: |