– DRAFT –
RQTF meeting

<gb> Issue 16 not found

<gb> Issue 21 not found

<gb> Issue 17 not found

<gb> Issue 18 not found

<gb> Issue 19 not found

<gb> Issue 20 not found

<gb> Issue 16 not found

<gb> Issue 21 not found

<gb> Issue 17 not found

<gb> Issue 18 not found

<gb> Issue 19 not found

<gb> Issue 20 not found

Issue #16: Replace "overlays" as a section

<gb> Issue 16 not found

jason: asked to replace overlays as a section

not a product category, shoudl be discusison on more borader topic of browser extentsions

scott: Thought important to ack orgs turn to overlays to remediate

scott: Here in AU it's not necessrily a negative term

janina: Forthcoming CG report suggests AI not yet sufficient:

janina: https://A11yEdge.github.io/capabilities/

Janin: can reference findings of this report regarding AI relevance

jason: three actions potentially:

1. align terminology with community group report

2. make sure limitations of machine learning in remediation are clearly specified in this document

3. cite work of community group appropriately

revisit issue 16 when report comes out next week

Issue #21: Jumping to Overlays in "accessibility context" missies the real value of AI in Design and Development

<gb> Issue 21 not found

isue 21

diffent ways of machine learning bieng applied to accessibility are not currently here

possibility of restructure addressing it

janina: beleive our restructuring will cover this

janina: defer to next week to check with Josh

Issue #17:: Opportunity to disambiguate the term "AI"

<gb> Issue 17 not found

issue 17

disambiguate th term AI is discussed

janian: wants more time on defining, agreed we'd do more of this in teh introduction

stacey: good to be a bit more specific in plain language that we're talking about TTS, specific capability rathe rthan just 'AI'

janian: seems to be there

jason: difference between potential paplicaiotn of technology rather than discussing the technology itself

janina: we coudl go back to this issue once restructure complete and see what's covered or missing

jason: yes, woudl confirm examples match

janina: yes, will check this agian before publishing

zakin, next item

Issue #18: Sign language section: needs evidence, context, and explicit examples

<gb> Issue 18 not found

issue 18

sign language needs specific exmaples

stacey: relates to Section 3.10

as sits in WCAG Level AAA, not widely implemented

generative AI can provide translation services,

asking about what is evidence that AI can translat symbols,

what websites

and no dicussion on facial movements, acitons etc.

raja: general comment - use of AI broadly from emergencies, informaiton, communicating,

some use cases beneficial for generating messages where need ot know informaiton quicly that doesn't need as much emotion

thinking about the most important scenarios

Issue #19: Suggest Flow or groupings

<gb> Issue 19 not found

issue 19

askng if we shoudl ahve this structure din teh website devleopment cycle

stacey: document goes beyond tthe cycle

janina: quesiton to ask is what's our horizon in this documnt?

stacy: good to have both - today quesitons and tomorrow quesitons

jason: is this largely ocvered in teh restructure?

janian: more faminiar terminology

stacey: PDLC could be useful with ai and accessibility but is that this document

janina: wil respond loking at restructure, and reivew on near and long-term applicaibility