Change Details

- Article (in order one would encounter in article) - [ ] 2. Header image - isn’t read by VoiceOver, and isn’t selectable at all - fix this - [ ] 3. Very low priority: between subhead and start of article says “separator, dim, en, banner”… could just be “small separator” - [ ] 1. All edit article buttons are read as “Index php link” - should be “Edit article link” or “Edit section link” - [ ] 2. Images in article - they read a lot of unneeded info, and never say they’re a link - correct this - [ ] 2. W button on top: Read something like “Wikipedia back to Explore button” - starting with “Wikipedia” seems unnecessary and clunky. Let’s just describe the actual action. - [ ] 1. Closed fact box - Reads as “Quick facts, colon [first couple words of box]”… It never announces the down arrow (which opens the box), and never explains it’s tappable. Let’s change this to “Quick facts, tap to open box” or something similar? - [ ] 2. Open fact box: the last link (which collapses the box) just says “close”. Could it say “close fact box” or simply “close box” or something similar? - [ ] 1. The reading experience is very difficult. When scrolling piece-by-piece, each “chunk” that it reads is whatever is in the exact same style. Anything bold, any link (including references), etc. - all those are different readable sections. Most sentences (especially those early in the article) have half a dozen sections. That’s… rough. - Examples - Just “we went to [Portland]. [2]” has 5 distinct sections one needs to swipe through: “we went to open bracket”, “Portland link”, “close bracket period open bracket”, “2 link” and “close bracket”. - In Greater Wynnewood Exotic Animal Park… “is situation on [break] 16 acres (6.5 [break] ha [break] and began as a shelter…” - Considering the three ways users can read (there could be more I’m unaware of), and how this plays out: - Swiping to have the entire screen read to you without stopping: This actually works well, but only works if you don’t want to pause or jump around. - Swiping between items (two fingers forward or backwards): This is tough, but workable. You have to prompt it to continue between every section, which typically ends up being several times per sentence. - Swiping your finger around the screen, having whatever you’re currently on be read out loud: This is non-functional, because some fragments span multiple lines, others don’t, etc. - … This obviously needs to be fixed. Apple News reads out the entire article, and just says things like “We went to Portland link 2 link.” We should do something like that. (News has a slight pause before reading the link, and says the word “link” afterward. We should ensure we have this pause at the start of the link, so there is a tell as to where the link begins. Example from News: “Far less deaths than [slight pause] Italy link, where fatalities…”) - [ ] 2. Citations could be improved: [2] is currently read as “open bracket, 2 link, close bracket”. Either “citation link” or “citation 2 link”? - [ ] 2. Small boxes that link to other wikimedia projects (“wikipedia commons has media related to [article title]”) - [ ] These read out the image w/ the logo for the project - those shouldn’t be read. - [ ] They also don’t have any indication they’re in a little grey box, almost as an aside - they are read as part of the article. This should be updated. - [ ] 1. “References” and “external links” are collapsed but don’t say anything about being expandable, and the upside down caret next to them don’t read in VoiceOver. Have VoiceOver read “tap for list” after the names, or something similar. - [ ] 3. “About this article” items are described as “menu item” after reading the text of each. Let’s update this to read as “link”. - [ ] 2. “Read more” - each article in this section has its title and description read as separate items, both with the word “link” afterward. Group these labels so they’re read together, and say “link” just once. (They’re grouped appropriately elsewhere in the app, like in search results.) - [ ] 3. Footer - “wikipedia” image doesn’t read at all - I don’t think we need it to, but wanted to mention it as we use that image as branding for sighted users, and so this seems like a difference. - [ ] 1. The Creative Commons and “view article in browser” links don’t read as links, just as text (even when they’re working - on some branches, bug to fix them is yet to deploy). Update them to read as the standard “view article in browser link”. - [ ] 3?. Have a hidden link (shown/read in VoiceOver, otherwise not present) at top of “table of contents” between the table of contents and starting to read it: “skip to article”? Otherwise when reading the entire page, it goes through the entire TOC. The more I think about it, the more I don’t like this idea - as soon as the user has an idea of our layout, it’s easy to skip over to the content by tapping the proper part of the screen. And this seems somewhat non-standard for VoiceOver, though I’m not quite sure. But leaving this on the list.

- Article (in order one would encounter in article) - [ ] 2. Header image - isn’t read by VoiceOver, and isn’t selectable at all - fix this - [ ] 3. Very low priority: between subhead and start of article says “separator, dim, en, banner”… could just be “small separator” - [ ] 1. All edit article buttons are read as “Index php link” - should be “Edit article link” or “Edit section link” - [ ] 2. Images in article - they read a lot of unneeded info, and never say they’re a link - correct this - [ ] 2. W button on top: Read something like “Wikipedia back to Explore button” - starting with “Wikipedia” seems unnecessary and clunky. Let’s just describe the actual action. - [ ] 1. Closed fact box - Reads as “Quick facts, colon [first couple words of box]”… It never announces the down arrow (which opens the box), and never explains it’s tappable. Let’s change this to “Quick facts, tap to open box” or something similar? - [ ] 2. Open fact box: the last link (which collapses the box) just says “close”. Could it say “close fact box” or simply “close box” or something similar? - [ ] 2. Citations could be improved: [2] is currently read as “open bracket, 2 link, close bracket”. Either “citation link” or “citation 2 link”? - [ ] 2. Small boxes that link to other wikimedia projects (“wikipedia commons has media related to [article title]”) - [ ] These read out the image w/ the logo for the project - those shouldn’t be read. - [ ] They also don’t have any indication they’re in a little grey box, almost as an aside - they are read as part of the article. This should be updated. - [ ] 1. “References” and “external links” are collapsed but don’t say anything about being expandable, and the upside down caret next to them don’t read in VoiceOver. Have VoiceOver read “tap for list” after the names, or something similar. - [ ] 3. “About this article” items are described as “menu item” after reading the text of each. Let’s update this to read as “link”. - [ ] 2. “Read more” - each article in this section has its title and description read as separate items, both with the word “link” afterward. Group these labels so they’re read together, and say “link” just once. (They’re grouped appropriately elsewhere in the app, like in search results.) - [ ] 3. Footer - “wikipedia” image doesn’t read at all - I don’t think we need it to, but wanted to mention it as we use that image as branding for sighted users, and so this seems like a difference. - [ ] 1. The Creative Commons and “view article in browser” links don’t read as links, just as text (even when they’re working - on some branches, bug to fix them is yet to deploy). Update them to read as the standard “view article in browser link”. - [ ] 3?. Have a hidden link (shown/read in VoiceOver, otherwise not present) at top of “table of contents” between the table of contents and starting to read it: “skip to article”? Otherwise when reading the entire page, it goes through the entire TOC. The more I think about it, the more I don’t like this idea - as soon as the user has an idea of our layout, it’s easy to skip over to the content by tapping the proper part of the screen. And this seems somewhat non-standard for VoiceOver, though I’m not quite sure. But leaving this on the list.

- Article (in order one would encounter in article) - [ ] 2. Header image - isn’t read by VoiceOver, and isn’t selectable at all - fix this - [ ] 3. Very low priority: between subhead and start of article says “separator, dim, en, banner”… could just be “small separator” - [ ] 1. All edit article buttons are read as “Index php link” - should be “Edit article link” or “Edit section link” - [ ] 2. Images in article - they read a lot of unneeded info, and never say they’re a link - correct this - [ ] 2. W button on top: Read something like “Wikipedia back to Explore button” - starting with “Wikipedia” seems unnecessary and clunky. Let’s just describe the actual action. - [ ] 1. Closed fact box - Reads as “Quick facts, colon [first couple words of box]”… It never announces the down arrow (which opens the box), and never explains it’s tappable. Let’s change this to “Quick facts, tap to open box” or something similar? - [ ] 2. Open fact box: the last link (which collapses the box) just says “close”. Could it say “close fact box” or simply “close box” or something similar? - [ ] 1. The reading experience is very difficult. When scrolling piece-by-piece, each “chunk” that it reads is whatever is in the exact same style. Anything bold, any link (including references), etc. - all those are different readable sections. Most sentences (especially those early in the article) have half a dozen sections. That’s… rough. - Examples - Just “we went to [Portland]. [2]” has 5 distinct sections one needs to swipe through: “we went to open bracket”, “Portland link”, “close bracket period open bracket”, “2 link” and “close bracket”. - In Greater Wynnewood Exotic Animal Park… “is situation on [break] 16 acres (6.5 [break] ha [break] and began as a shelter…” - Considering the three ways users can read (there could be more I’m unaware of), and how this plays out: - Swiping to have the entire screen read to you without stopping: This actually works well, but only works if you don’t want to pause or jump around. - Swiping between items (two fingers forward or backwards): This is tough, but workable. You have to prompt it to continue between every section, which typically ends up being several times per sentence. - Swiping your finger around the screen, having whatever you’re currently on be read out loud: This is non-functional, because some fragments span multiple lines, others don’t, etc. - … This obviously needs to be fixed. Apple News reads out the entire article, and just says things like “We went to Portland link 2 link.” We should do something like that. (News has a slight pause before reading the link, and says the word “link” afterward. We should ensure we have this pause at the start of the link, so there is a tell as to where the link begins. Example from News: “Far less deaths than [slight pause] Italy link, where fatalities…”) - [ ] 2. Citations could be improved: [2] is currently read as “open bracket, 2 link, close bracket”. Either “citation link” or “citation 2 link”? - [ ] 2. Small boxes that link to other wikimedia projects (“wikipedia commons has media related to [article title]”) - [ ] These read out the image w/ the logo for the project - those shouldn’t be read. - [ ] They also don’t have any indication they’re in a little grey box, almost as an aside - they are read as part of the article. This should be updated. - [ ] 1. “References” and “external links” are collapsed but don’t say anything about being expandable, and the upside down caret next to them don’t read in VoiceOver. Have VoiceOver read “tap for list” after the names, or something similar. - [ ] 3. “About this article” items are described as “menu item” after reading the text of each. Let’s update this to read as “link”. - [ ] 2. “Read more” - each article in this section has its title and description read as separate items, both with the word “link” afterward. Group these labels so they’re read together, and say “link” just once. (They’re grouped appropriately elsewhere in the app, like in search results.) - [ ] 3. Footer - “wikipedia” image doesn’t read at all - I don’t think we need it to, but wanted to mention it as we use that image as branding for sighted users, and so this seems like a difference. - [ ] 1. The Creative Commons and “view article in browser” links don’t read as links, just as text (even when they’re working - on some branches, bug to fix them is yet to deploy). Update them to read as the standard “view article in browser link”. - [ ] 3?. Have a hidden link (shown/read in VoiceOver, otherwise not present) at top of “table of contents” between the table of contents and starting to read it: “skip to article”? Otherwise when reading the entire page, it goes through the entire TOC. The more I think about it, the more I don’t like this idea - as soon as the user has an idea of our layout, it’s easy to skip over to the content by tapping the proper part of the screen. And this seems somewhat non-standard for VoiceOver, though I’m not quite sure. But leaving this on the list.