Open jasonjgw opened 3 years ago
This is a good catch @jasonjgw. I think it's for both - the user need did became less clear however, and you are right about removing the reference to deaf users. I'm going to suggest the following as a clearer description of the user need and then two separate requirements:
User Need 17: Hard of hearing users may need accommodations in order to perceive audio. REQ 17a: Provide spatialized audio content to emulate three dimensional sound forms in immersive environments. REQ 17b: Provide audio description.
Do you think it is sufficient to have audio description as a requirement? Or should it be text descriptions of audio, and if so what is the difference?
It should probably be "text descriptions of audio" or similar, as "audio description" is often used as a term of art which means audio description of video (i.e., for users who are blind, describing the video track), and using it here without explanation would tend to confuse readers for whom the term has a specific meaning.
Ok, great. Done.
@jasonjgw Can we say?
Provide text descriptions of important audio content.
Or should it say: "Provide captions, and text descriptions of important audio content"? I don't mind either way, as long as we're clear about what we're requesting.
@jasonjgw I'm not sure tbh - are we saying captions or text descriptions? Does that mean caption as an annotation to an item? Could be confusing if muxed with traditional captioning no?
I've just reviewed it, and, yes, captions are covered in the next item - so we don't need to mention them here. Perhaps saying "non-speech audio" would clarify this User Need further. Otherwise, it could be taken to refer to all audio (speech and non-speech alike).
User Need 17 is confusing, as currently drafted. It isn't clear whether the need is for both spatialized audio content and for descriptions, or only for descriptions. Also, presumably the descriptions are text descriptions of the audio - not "audio description", which is a rather ambiguous phrase in this context.
Obviously, users who are deaf cannot benefit from spatialized audio. Those who are hard of hearing may conceivably benefit, but it isn't clear that they would benefit more or in other ways than the user population in generl. Both users who are deaf and those who are hard of hearing may need descriptions of three-dimensional soundscapes (i.e., text descriptions of certain audio content).
I think User Need 17 and REQ 17 need to be reworked to clarify what the users need and how to satisfy those needs. If there are multiple needs, perhaps dividing it into two distinct User Needs would be better. Also, REQ 17a is not accompanied by any REQ 17b - probably an editorial oversight.