Meeting minutes
Artificial intelligence, machine learning, and accessibility.
jasonjgw: daft has been created
more detail is needed and we are started to pull that together to insert into the document
<janina> https://
janina: thinking of things that should be in scope. an AI assisted user agent would be good and likely possible
janina: the possiblities seem to be presented in the draft scope not not highlighted or as obvious as they could be
jasonjgw: we'd like to work the scope section into the draft
jasonjgw: that will be done
shawn: I'd like to view the topic from a higher level
Positioning AI document from W3C
<Zakim> shawn, you wanted to ask about higher level from W3C perspective and to -- and also communicating in a resource and to say other than wihtin the doc?
shawn: We need to think about how this work will be considered by other groups and ensure that it is clear externally that we are working within the remit of this group and not overstepping our boundaries.
janina: agreed. ways to do this may include to make sure we are citing previous work done on the topic.
shawn: it may be useful to announce the work is happening before TPAC (even without a draft)
scott_h: To explain the background of how the draft was put together. There has been a lot of discussion about a, what accessibility issues could be address by AI and b, what tools could be enhanced by AI.
scott_h: To address the question of stepping on toes the aim is to cover those areas of interest.
<Zakim> shawn, you wanted to ask about other work and to notes https://
shawn: this is a hot topic which will get a lot of attention. Part of encouraging positive engagement is to bring in leaders in the field such as Jutta and Shari. I'm happy to make those introductions. It may be useful to invite them to input as early as possible to make sure everyone is thinking in the same direction.
janina: This makes sense and is in-line with how work often progresses. Let's draw up a list of who would be good to speak to in the early stages of the work.
shawn: The discussion here around working on the accessibility aspects of AI should be clear internally at W3C but should be made clear for those outside W3C who will also have access to the documentation and may need that background.
<shawn> 1. start "requirements analysis" as a separate doc in GitHub
<shawn> 2. contact influencers in the field to get their support
shawn: I would like to request that the requirements analysis is in a separate, less formal, document to encourage participation.
jasonjgw: I would like a version of it in the main text in case people are not happy to follow a link to a separate document. This doesn't seem to be mutually exclusive.
shawn: It might be good pre-TPAC to have a high level page, not the formal draft, that people can land on first.
scott_h: this could maybe be a one pager on the "who, what and how to get in touch" of the work?
shawn: That sounds good.