Unordered List is read as Order

[nanderer]

Hi,

there is an error interpreting <ul> elements, they are handled like <ol> elements so they are read with 1., 2. 3. and thereby confuses the listener...

Please have a look into it and keep up the good work

[ken107]

Hello, thank you for reporting issue.

This was actually a design choice. Without them the list would sound like prose. By reading out #s, not only listener knows it's a list, it aids the listener's sense of location.

[nanderer]

i thing that is bad design, at least in german language an enumeration like first that second this and third those implies a special kind of most uplifting strain of though. if then a text is spoken out with 1. ....; 2....; 3... and so on you try to find the meaning of that and are confused by it until you find out that the stupid software just put something in that wasnt there intended by th author of the text, so i wold really appreciate to nod add numbers where there arent one.

and if it sounds a bit like prosa it is ok i guess, most times when i read a list by myself it has a certain ring to it to, i also dont take i account the pronunciation or the tone of the voice when i know that it is generated by a tts system, so it dosnt matter how it sounds but if i hear sonething that was not written in confuses the hell out of me!

[nanderer]

and in terms of "sense of location" i would also thing its confusing, imagine you listen to a long text while not following on the screen, then want to find the place that is read right now and scroll to the text searching for the non existing number that you just heard, not very nice i guess

[nanderer]

i hope i made myselfe somehow clear, sorry, my english is not that good, buy maybe ask some other folks whats there opinion i am sure most are unhappy if there are numbers added that where not there before.

[FajnB]

I do to some extent agree with @nanderer that this sometimes makes the read text very confusing, especially when there is a lot of separate lists or a very long list, but in the other hand I do agree with you @ken107 that it is needed to differentiate between plain text and lists.

I have several ideas how to enhance UX in this area.
(This only applies to list that are NOT numbered, i.e. they only have bullet points or are defined as list in html)

1. (Less elegant way) It could say at the start of the list "Start of the list" and the end of the list "End of the list"
   This though would be rough to implement for every language and could confuse people even more
2. (More elegant way) Read in front of every list entry "Bullet point"
   This have the benefit that it can be easily translated to multiple languages
3. (Maybe an option) Make a sound every time there is a new list entry (Bullet point) present
   This would need to be mentioned in documentation or settings (make sound on bullet points) so that people know what that sound is
4. (Combination of the above) For ex.: "Start of the list. 1st bullet point:" and so on.

[ArtofBugs]

Screen readers seem to use a combination of 1 and 2 - examples https://collab-help.its.virginia.edu/m/gettingstarted/l/466118-how-can-i-make-lists-of-items-accessible ("List of three items. Bullet 1.") and https://libguides.slcc.edu/Accessibility/Lists ("begin bulleted list bullet milk exit bulleted list")