Meeting minutes
<gb> /issues/172 -> #172
<gb> /issues/193 -> #193
<gb> /issues/148 -> #148
Zakem,next item
Zakem, next item
New Business
<janina> https://
<Fazio> Asking for task force feedback for current charter by end January
<Fazio> What are our publishing goals by 2027
<jkline> present
<jkline> again
janina: APA is rechartering – all member management work reviewed. Like to be in charter to publish early and often.
RFC 2119 – formal meaning & requirements.
Should point out in non-normative section what we’re doing and how it fits in
End of January – Feedback
End of March – Expect to publish in July
Current Charter expires July 31st.
CharlesL: Outstanding pull request for new Excel spreadsheet.
Outstanding error – don’t know why. May need Roy
Updates to specification won’t appear if error.
CharlesL: Thank you, Jeff, for instruction on implementing new model
0, not applicable, 1 launch gave keyboard users quick access.
Calculations tied to renamed status levels. Names can be changed.
Zakem, next item
Github Issue #148 Add information fields for metadata for each dimension
<gb> /issues/148 -> #148
<Fazio> w3c/
<gb> Issue 148 Add information fields for metadata for each dimension (by jeffkline)
<gb> /issues/172 -> #172
Github Issue #172 Proof Point Discrepancies between Specification and Template
<Fazio> w3c/
<gb> Issue 172 Proof Point Discrepancies between Specification and Template (by clapierre)
<gb> /issues/193 -> #193
Github Issue #193 Apendix Roles need updating (feature request)
<Fazio> w3c/
<gb> Issue 193 Apendix Roles need updating (feature request) (by newtonsgroove)
Dr_Keith: Add and explanation to the roll in the use cases
<Fazio> New Use Case: 4.2.1 Use case one
<Fazio> A software company is responding to an RFP. They’ve been asked to demonstrate that they can retain the accuracy and timeliness of their VPATs and refresh them as needed.
<Fazio> Dimensions:
<Fazio> The critical dimensions are knowledge and Skills, ICT Dev Lifecycle, and Personnel.
<Fazio> Roles that could be involved in use case one:
<Fazio> • Accessibility consultants, advisors, influencers, disability specialists, outside contractors and industry organizations, chief accessibility/diversity and inclusion officers
<Fazio> • Designers, developers, product managers, project managers, IT, QA, researchers/User Experience
<Fazio> • Instructor/trainer, teaching resource developer
<Fazio> • Content provider/producer
<Fazio> • Lawyer, organizational policy-maker, standards maintainer
<Fazio> • Employees with disabilities
Dr_Kieth: Helpful to have it in each use case with each common term for the role.
NehaJ: If you add every use case it will be redundant.
Dr_Kieth: Explanation for roles may have different explanation per use case based on how it is applied to model.
<stacey> we can remove me from the queue - all good
<Dr_Keith> I got kicked out of IRC - can you provide the link again to the use cases from Stacy and Sherri?
JeffK: What Dr Keith has done is valuable.
Concerned that we have an exhaustive list.
Add contact to each skill we’ll have a big doc.
Reduce the number of use case (3)
Look at the key role involved in skill area and add explanation.
List other skills.
stacey: Good to add examples however two issues:
1. Too prescriptive
2. Things could get too long (maybe fewer use cases)
Dr_Keith: Limiting use cases & provide samples
Leave all but only examples for some
Breaking this off into a help document
<Fazio> Mark: could define roles in one section, add additional context in case studies, separating both
JeffK: Don’t know how much detail we need to go into. Should know what the skill sets and roles are in org.
Fazio: Work with mom & pop business, who don’t understand all roles and need the explanation.
However, it would make the doc long.
JeffK: While we don’t have all the definitions of roles, we do have prove points. They should be able to figure out who should work on the proof points.
Fazio: Dr Keith to work on an example