<shawn> agenda order 1, 3, 2

<shawn> agenda order 3, 1, 2

scribe+

2024 Priorities and Specific Objectives https://wai-mission.netlify.app/draft/#2024-priorities-and-specific-objectives

shawn: You may recall, last Sept we were working on vision and strategic planning

<shawn> discussions https://github.com/w3c/wai-mission/discussions

<shawn> priorities for 2024 https://wai-mission.netlify.app/draft/#2024-priorities-and-specific-objectives

shawn: we have drafted priorities and would like to discuss them

lisa: I find missing is WAI's main job: enable and promote make ALL the web accessible to ALL people with disabilities.
... people with Cognitive disabilities, and other disabilities as well, have not been addresses as well as others
... the end-user isn't mentioned
... it does mention incremental steps that we need to get to these important goals
... bottom line, it does not capture the mission of equity and human rights

Matt_King: The mission statement has "strategies, standards, and supporting", and does not have the word "all" in front of "disabilities

lisa: We need the word, "all"
... to make the web accessible to ALL people with ALL TYPES OF disabilities.
... a lot of things in WAI-Adapt now, were things we proposed to ARIA at the start
... the scope feels like it has narrowed
... perhaps also move from WEB accessibility to DIGITAL accessibility

shawn: I hear the discussion item, to add "ALL" to the mission
... the topic of web v digital is a larger and well known topic

lisa: If the 1st thing in our vision is to harmonize, we may be forced to 'cut a group'

kevin: We are already facing harmonization demands. Understand that harmonization might involve some exclusion
... we could stress building or developing standards that are inclusive to ALL people with ALL types of disabilities

Matt_King: Digital v web is even more important due to the EAA
... I see tremendous industry and investment on the part of companies vying to get into a better position before June 2025
... we will have to double down on WCAG2ICT
... it appears EAA will line up with WCAG 2.2 and this will be incorporated into EN 301 549

<shawn> https://www.w3.org/WAI/standards-guidelines/wcag/non-web-ict/

Matt_King: WCAG2ICT is a note being written to address this issue

<kevin> scribe+ kevin

<kevin> Lionel_Wolberger: Slightly different topic, bullet 4 'everyone who creates or manages *has* ...'

<kevin> ... I would suggest some more practical. For example 'has access to'

<kevin> ... 'has' could be over reaching, wish it wasn't but could be

<kevin> shawn: Intention for the Vision is to be the big picture, the dream

<kevin> scribe- kevin

<kevin> scribe+ kevin

<kevin> Matt_King: One other bit, there is somethign related to AT that is missing from the Vision

<kevin> ... Even if everything on the Vision is true, if we don't have AT harmonization and interoperability then nothing matters

<kevin> ... The last mile to the user has to work and be predictable

<kevin> ... If devs can't predict what happens in the last mile then they can't build things

<kevin> shawn: Add to third bullet?

<kevin> Matt_King: Possibly, but AT isn't necessarily seen as Tools, but might work

<kevin> shawn: Will send out in email for additional input

This is scribe.perl Revision VERSION of 2020-12-31
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/WCAG to ICT/WCAG2ICT/
Present: Shawn, kevin, valerie_young, lisa, Lionel_Wolberger, Daniel, Matt_King
No ScribeNick specified.  Guessing ScribeNick: Lionel_Wolberger
Inferring Scribes: Lionel_Wolberger

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth


WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: 

WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)