Re: draft of Natural Language Interface Accessibility

Hi, Lisa and COGA TF, please see this draft summary of COGA's NAUR feedback
<https://docs.google.com/document/d/1lVkQv4_lKcuEyane3o2oDtC3Hzu_-YZRJKe8pSk7Qd4/edit#>
.

As with the Remote Meeting draft
<https://docs.google.com/document/d/1SmQFRTb24YDMkVpb9Bb-NJ_QD-YJ_zfVpqGL50lr9j4/edit#>I
shared earlier this evening, I recommend grouping our NAUR feedback into
two main sections:

   - Big Suggestions
   - Smaller Suggestions

My hope is that this structure and level of detail will make our team's
feedback as actionable and easy-to-skim as possible. Eager for your
thoughts, thanks!



On Sun, Dec 5, 2021 at 9:10 AM Lisa Seeman <lisa1seeman@gmail.com> wrote:

>   Hi Folks
>
> IHere ius my draft issue for APA for  Natural Language Interface
> Accessibility User Requirements at  https://www.w3.org/TR/naur/
> <https://www.w3.org/TR/naur/#speech-recognition-and-speech-production>
>
>
> Greeting APA.
> regarding   https://www.w3.org/TR/naur/
> <https://www.w3.org/TR/naur/#speech-recognition-and-speech-production>  .
> Coga has reviewed the document and felt that the needs of people with
> learning and cognitive disabilities are not adequately addressed
> The userneeds for our groups are stuck  together in a way that minimises
> the issues, and seems very problematic as the specific needs and range of
> needs are so different. Supporting an aging individual with dementia will
> be very different from supporting a young adult with down syndrome in this
> context.
>
>
> We feal the are many examples of user needs that are relevant here in m  Making
> Content Useable <https://www.w3.org/TR/coga-usable/> , and we would like
> to see how our needs mapp to the needs in NAUR and if they are adequately
> understandable and easy to inver.
>
> We may need a different approach. Maybe based on functional needs, such as
> impared short term memory, impaired exective function etc. Another aprouch
> would be based on different challenges face by our users such as the user
> needs in  Making Content Useable <https://www.w3.org/TR/coga-usable/> .
>
> We started collecting specific comments at /docs.google.com
> <https://docs.google.com/document/d/1I6QEmpWwDN_cXeR6I5OX5UnlcZQ9M2NV4bMalaAThuM/edit#>
> , however, again, this feedback is incomplete as there is so much to say
> here. It may be better to have a next editors draft which is more
> inclusive, and make specific comments on that. We also have two issue
> papers on this topic. I believe I have given them to you prevously, but for
> quick refrence please review  /issue-papers/voice-menus.html
> <https://w3c.github.io/coga/issue-papers/voice-menus.html> and google doc
> draft on conversational interfaces
> <https://docs.google.com/document/d/1B1vCqlU1IF5UmqxhJAy8Khdi-kRQNPalVX8f3lCMr7w/edit#>
>
> This topic is essential for our user groups, as so many of us feel
> completely unable to get critical services when these interfaces are used.
> This often results in our hat our independence being removed or
> curtailed. We must not publish a document that allows interface that bar us
> entry from being considered inclusive.
> Again we are happy to have a joint call to work help move this forward.
>
> Clearly this is a big task and we are happy to have a joint call to
> discuss how we can help.
>


-- 

Julie Rawe

Special Projects Editor, Editorial Content, Understood

E: jrawe@understood.org | M: 917.588.4738

Pronounced Joo-lee Raw (like 'uncooked')

She | her [image:
https://www.understood.org/take-note?utm_medium=email&utm_source=email-community&utm_campaign=take-note-mb-y2-2021-employee-email&utm_content=image]
<https://www.understood.org/take-note?utm_medium=email&utm_source=email-community&utm_campaign=take-note-mb-y2-2021-employee-email&utm_content=image>