Meeting minutes
New Business
JeffAdams-UN Working with a client, showing them the maturity model. Will likely use.
They have an RFP in Irving, Texas – Do you use a maturity model
jkline: Notes that Texas solicitation on accessibility has been there for awhile and maybe someone just picked up on it
Fazio: Meeting in the next hour to discuss the publication.
Task Force Roadmap
Fazio: Should discuss next steps now that we've readied the publication.
Fazio: Work through github, get language shored up. We've got a scoring system, but might want to rename and evolve to "tracking system" so maturity can be tracked.
Sheri_B-H: Agrees we need a plain language review. Not sure when it's best to review. If we review that early, then we have to make sure we continue with plain language
Fazio: Whatever we do, will also be reviewed by wai management
Sheri_B-H: Also wants to kick off project to understand where AI could be invovled in the model and add in info where there could be bais.
@Fazio: Need to discuss process around edits that we receive from wai management.
<gb> @Fazio
jkline: For "tracking system" suggests "progress tracking system"
janina: This is future looking at how the model can insert into WCAG 3
Fazio: It's looking beyond the initial publication
Fazio: This is not "normative" work at this moment.
janina: Suggests to have a "1.0" on the document so that future updates can marked.
<CharlesL1> the 1.1 version I think would include the AI improvements Sheri wants to add.
Mark_Miller: Scoring vs. tracking. Thinks it's exciting it's being looked at how it will lineup to WCAG 3. Maturity model though tracks through levels, so wondering what they're looking for and what they're trying to solve.
janina: Expects a joint meeting sometime after TPAC to hear those requirements.
CharlesL1: Likes the "1.1" idea, and might be where Sheri's AI request comes in.
CharlesL1: If scoring is a sticking point, instead of tallying scores as specific numbers, it could just be that 50% were at optimize state and report where the org is within the different levels.
Mark_Miller: Has some scoring ideas that he can share.
Fazio: Can envision 2.0 being normative
Fazio: Something that could be explored, and invite more people to join us because of the interest.
Sheri: Sorry I think that's a great aspiration, but we would have to get more people on board.
… I think we need to stay away from "vastly different" or that might work against us for publishing 1.0
Fazio: Having both versions benefits us.
janina: We're not chartered for normative currently, but we re-charter next year.
jkline: If doing subsequent releases, it's hard for world to stay synced up. Coming with changes too frequently can cause havoc. A .x release could be a "maintenance" release since that's fairly common.
janina: If we had more than the spreadsheet for tracking, it looks like a normative requirement even though we don't mean it that way.
Fazio: Building a timeline for future work can help. Will look for time to do that.
jkline: Will there be a group working on the roadmap? We've talked about a different tool beyond the spreadsheet, such as HTML.
Fazio: Likely some sub-committees to work on that, just trying to layout what we'll be working on.
Sheri_B-H: Order of doing things should be in the timeline/roadmap. Would start with list of projects with dependencies and then bring to larger group to determine timeline.
jkline: More interested in what we're working on versus the timeline. Acknowledges the roadmap will have changes and can be fluid.
janina: The roadmap can be published on taskforce page as well.
janina: URIs of our minutes have a predictive format so it would not be hard for AI to read and summerize.
Mark_Miller: Will take a shot at creating the list from the meeting notes