Eitan Isaacson [:eeejay] Reporter
	Description • 12 years ago

I am thinking 3 levels of verbosity should be enough. Right now it is very verbose in lists for example.

	David Bolter [:davidb] (NeedInfo me for attention)
	Comment 1 • 12 years ago

Marco what do you think?

	Marco Zehe (:MarcoZ)
	Comment 2 • 12 years ago

Neither Apple nor Google have verbosity levels for speech output by default. We shouldn't make it too complicated, and past experience shows that verbosity granularity is hardly ever customized. We should rather think about which the items are that should be configurable, for example Apple allows turning on and off of the hints that are spoken roughly 2 seconds after the main control. We could introduce a long and short form for certain controls like lists where we say "list item 2 of 3" as we do now, in the long form, but only "item 2" in the short form, for example.

When we introduce table cell support with header cells, we should maybe give an option to turn speaking of header cells on and off.

For most, if not all, other controls, there's not much one can do. I know you can configure a screen reader like JAWS to death with changing the order of name, type and state of a control, and can change each verbosity level very granually, but 99.9% of users won't ever touch those settings in practice.

So what we should do is think about the examples where we want different options, and then put these in individually. Make them check boxes if possible, on and off states that are easy to imagine what they do etc. Nothing too complicated.

	David Bolter [:davidb] (NeedInfo me for attention)
	Comment 3 • 12 years ago

(In reply to Marco Zehe (:MarcoZ) from comment #2)

Sounds right to me.

Marco what do you think about how accessfu currently speaks lists?

	Marco Zehe (:MarcoZ)
	Comment 4 • 12 years ago

I'm OK with it, but I'm also used to it. Other screen readers, like NVDA and VoiceOver, indicate at the entry of a list and the exit, or transition to another list, but don't speak the item count on each. They speak the bullet type instead, or the numbering. Perhaps we could shorten this a bit on our end, but I am OK with either this or a config option. Eitan, did anyone on the eyes-free list complain about the verbosity of list items?

	Eitan Isaacson [:eeejay] Reporter
	Comment 5 • 12 years ago

(In reply to Marco Zehe (:MarcoZ) from comment #4)
> I'm OK with it, but I'm also used to it. Other screen readers, like NVDA and
> VoiceOver, indicate at the entry of a list and the exit, or transition to
> another list, but don't speak the item count on each. They speak the bullet
> type instead, or the numbering. Perhaps we could shorten this a bit on our
> end, but I am OK with either this or a config option. Eitan, did anyone on
> the eyes-free list complain about the verbosity of list items?

No, I don't remember anyone mentioning verbosity. I just personally think it is very verbose, and could quiet down a bit by default.