Meeting minutes
New Business
Management do not want MM 1.1 version, but update note
Fazio: because we are not a spec and it is a note
Janina: but we can publish for a wide review
Fazio: is it for delegitamite us? We can do more
janina: We have to answer what is new in it
Sheri: Putting a new section related to AI would help
janina: responding to issues will not solve our problem
janina: we are getting a good support and it will be useful
Fazio: we can get a help from management would be helpful
janina: It is difficult to happen
Sheri: Do we want to review stuff related to issue #377?
janina: let us go ahead what we are doing right now
Sheri: Let us discuss today how to push WCAG 3 ?
Sheri: Send me recent spreadsheet which I can refer for AI related work
close, this item
WCAG 3 stuff
Sheri: Do we want to do shortcuts?
All: No
janina: some of them restated
jkline: we can request for some kind of formal statement
janina: they have already done on issue tracker
janina: but that is standard process
janina: do we have a exact pointer from WCAG 3?
<Fazio> https://
<Sheri> Assertions are not required to conform but are used to show procedural commitments to accessibility and improve comparison between products.
<Sheri> Content — these assertions focus on the content and include processes that determine whether the content is accessible. For example, plain language reviews, usability testing, AT testing, or style guides.
<Sheri> Organization — these assertions focus on the organization and include processes that help organizations create accessible content such as training staff in accessibility or providing public accessibility statements.
<Sheri> https://
Section from WCAG 3 - 4.1.3
janina: in this explanation they should give some examples and references
Sheri: 1. hey need to point examples, existing maturity models
2. For referening maturiory models you get the time
WCAG require organizations to track things over a time and MM is good way of doing it
janina: when did WCAG needs comments? deadline?
Sheri: atleast a month
Sheri: I can draft something
Sheri: By Friday
Fazio: I will coordiante with Matthew
Fazio, janina and Sheri will draft an email together
Issue #377
<gb> Issue 377 The Knowledge and Skills dimension is too narrowly focused on individual staff competencies (by zwiastunsw)
<janina> w3c/
Sheri sent two emails regarding issue 348 and 377
Jeff Adams will put email in #377 comment section
janina: we can be more clear and clean about our language that will be useful
Mark_Miller: Based on the comment, that person is confused between K and S, but here are very good points in it. Sheri is proposing to use these in model
Fazio: I dont think they are not confused
Sheri: We agreed capabilities are not mapped to organization but to employees
janina: Remedy proposed in issue is wrong
janina: we do not want individual's K and S should not be confused with organizational K and S