Meeting minutes
<SusiPallero> oresent+
<Fazio> hakim, next item
<Fazio> hakim, next item
New Business
janina TPAC this year is toward end of October and will be in Dublin. Proposals are welcome and sessions are generally problem solving and joint meetings.
Github Issue #328 Clarify what model can do in abstract
<Fazio> w3c/
<gb> Issue 328 Clarify what model can do in abstract (by iadawn)
Proposed Edits: The W3C Accessibility Maturity Model (AMM) provides a framework that provides individuals and organizations of all sizes with a roadmap, including benchmarks, to develop, deploy, and maintain the accessibility of both internal and external digital resources over time. This comprehensive framework encompasses all aspects of managing
an organization's staff resources as well as its ever-evolving public ones. It readily scales in support of:
• single person consultancies,
• nonprofits, NGOs of any size,
• local and national governmental departments, courts, legislatures, agencies, and commissions, and
• SOHO businesses, major international corporate organizations or corporate departments, and any business entity type or size.
The AMM includes guidance for public-facing content deployment and the provision of public-facing, interactive services, as well as internal activities and Human Resources that are related to employee relations.
The AMM provides a framework for evaluating operational effectiveness to adhere to accessibility principles, identify gaps in the effectiveness of operations to support accessibility, and follow a continuous process of accessibility improvement. It aligns staff teams toward common goals and objectives.
The AMM provides actionable guidance for establishing or improving policies, employee communication, training, and tools. It also includes a way to measure and document organizational, cultural and technical capabilities.
Fazio going back to Kevin in GitHub to ask for suggestions to inform our editing.
Fazio Lets also put into LLM to ask for redundancies and clarifications to help with the revision
<jkline> connection keeps dropping
JeffAdams-UN Will review this text with LLM alongside the other content review he has
Github Issue #334 Improve the About section
<CharlesL> w3c/
<gb> Issue 334 Improve the About section (by iadawn)
janina We have to have an abstract, but we don't necessairly need to have an "about"
Mark_Miller Looking at definitions... Abstract is what the document is about and includes purpose, methods or approach, key findings, and conclusion. About section should be who created this and why does it exist and includes who you are, team, organization, author, mission/purpose, what you do, values, approach, etc.
JeffK Has looked at the two sections. They're both different. The Abstract has to be there. But the About also includes critical information, including specifics on the framework and that the model is different from conformance testing.
Above CharlesL item is actually JeffK....
Mark_Miller Take Abstract and About, consider the definitions, and consider what goes into section.
Mark_Miller Jeff and Mark will review this as well.
CharlesL: We don't currently have a complete about section. Should that subtitle be removed since it may not be needed but the info is.
CharlesL: There's additional headers as well with 1.1.1 and 1.1.2 so it's split up awkwardly perhaps
Fazio: Some of the material is actually "how to use" which maybe should be its own section.