W3C

– DRAFT –
Guidance for Policy Makers Subgroup

03 July 2023

Attendees

Present
Jason_K, Jaunita_George
Regrets
-
Chair
Shadi
Scribe
Jaunita George, Jaunita_George

Meeting minutes

<shadi> https://docs.google.com/document/d/1B-qfTrPxnhIa0AxhPEF6SIDTLAGnneoauBRHGzS5q7U/edit#heading=h.6vf1synr92ek

Shadi: We should start off by having an introduction before we start getting into considerations.
… Let's look at the introduction section now.

agenda
… is there anything that needs to be added or reworded? The objective is to set the tone and purpose.
… any thoughts

<SusiPallero> apart from the notes already in the document?

Jason_K: This is going to the larger group for evaluation. Clearly outlining how this relate to the broader scope of WCAG and what this is not could help.
… We want to make sure we tell people what this isn't as well as what it's meant to do

shadi: Would this repeat what's in the abstract or expand that

Jason_K: Yeah and I can help wordsmith

shadi: Maybe we draft an introduction and background

Azlan: I agree with Jason. I'm just wondering where the right place is to call those out and whether it should be the introduction?
… actually calling out what this does not address should be a section in of itself

shadi: Why don't we rename the introduction

Jason_K: Why not use "scope"?

Azlan: We need to include a section about what this is/isn't

<Jason_K> Jaunita_George: Thinks a seperate section might be a good idea. Considerations might be misunderstood

<SusiPallero> +1 to Jaunita

<Jason_K> Jaunita_George: Have had things proposed in the past that might cause confusion, i.e third-party. If we don't carefully word things we may unintentially put in exceptions

shadi: In the introduction I tried to address this. I want to get the framing in place before digging in
… please read consideration 2

Azlan: I got lost in the second sentence. Who is requesting the help? Are we talking about the end user or are we talking about the help to get an accessible solution.

<Jason_K> Jaunita_George: This could lead to a potential legal risk, and as such be reluctant to provide a method in fear once its brought they can't fix in time

<Jason_K> ... also this is a way to provide alternate methods to provide accessible methods

<Jason_K> ... people migh use this is an attempt to get out of digital accessible altogether

shadi: It's a legal risk because of policies that incorporate WCAG. That's what we're trying to address. Who is this talking to.

Azlan: This document is aimed at policymakers, so this should be made for them.

shadi: It could be a secondary outcome of this work.

SusiPallero: I'm going a little back in the discussion. Are we going to address things related to physical accessibility? Maybe we can define that here if so. The second sentence was a bit difficult for me to understand as well.

Jason_K: The more we're talking about this, the more we're approaching this from a barrier standpoint rather than solutions standpoints.
… we should ensure that you
… maintain WCAG compliance or have a path to that

shadi: I would really like us to come up with 1-2 considerations that are well-drafted

<Jason_K> Jaunita_George: I wonder we make a set of criteria if organization has sufficent controls to provide enough safe guards to act as a safe harbor

<Jason_K> ... set expiration date to safe harbor, ie you have 2 years to do x and you move up the maturity curve

<Jason_K> ... this would apply to all, the courts etc, to determine if you are meeting the spirit of WCAG

<Jason_K> ... 98% of internet in inaccessible, and how do we get them further along the path of success

shadi: There could be other ideas from the maturity model we could incorporate
… many of the considerations currently are interrelated. There's also the prioritization question. Some organizations may have little work to do, while others may have a ways to go. It's very different between organizations

Jason_K: I like Jaunita's idea of building a framework to evaluating maturity and considerations.

shadi: We're saying in addition to focusing on just the outcome, we consider things that look at the maturity and capacity growth of an organizations.

<Jason_K> Jaunita_George: Get into situation where ppl give up, and not enough oversite to compel ppl to make these changes

<Jason_K> ... they'll get into an audit that doesn't lead to accessible products/changes, or stop audit

<Jason_K> ... a lot of loop holes, atleast in the US, to do not do what they are supposed to do

<Jason_K> ... give them ways a do it, and a body to judge the whole program and give them more tools to hold them accountable

<Jason_K> * no worries! Teamwork makes the dream work hahhaha

shadi: Anything else? I'll take this feedback and add to the scope and move that content to a new section and address comments. Hope to have a consideration drafted and maybe one or two others.
… We meet again next week, the 10th of July.

rrs agent, make minutes

Minutes manually created (not a transcript), formatted by scribe.perl version 210 (Wed Jan 11 19:21:32 2023 UTC).

Diagnostics

No scribenick or scribe found. Guessed: Jaunita_George

Maybe present: Azlan, Shadi, SusiPallero

All speakers: Azlan, Jason_K, Shadi, SusiPallero

Active on IRC: Azlan, Jason_K, Jaunita_George, shadi, SusiPallero