<scribe> scribe: jeanne
<Lauriat> Current wording: "The use of the guidelines supports and motivates organizations to acknowledge gaps and strive to be more inclusive. The intent is to give organizations a path toward greater accessibility."
<Lauriat> Jeanne's wording: "The Guidelines motivate organizations to go beyond minimal accessibility requirements by providing a scoring system that rewards organizations that demonstrate a greater effort to improve accessibility. For example, Methods that go beyond the minimum (such as: Methods for Guidelines that are not included in WCAG 2.x A or AA, task-completion evalations, or testing with users with disabilities) are worth more points in the scoring [CUT]
<Lauriat> Chuck's edit: "The Guidelines motivate organizations to go beyond minimal accessibility requirements by providing a scoring system that rewards organizations which demonstrate a greater effort to improve accessibility. For example, Methods that go beyond the minimum (such as: Methods for Guidelines that are not included in WCAG 2.x A or AA, task-completion evaluations, or testing with users with disabilities) are worth more points in the scoring system."
<shari> +1
<Chuck> The Guidelines motivate organizations to go beyond minimal accessibility requirements by providing a scoring system that rewards organizations which demonstrate a greater effort to improve accessibility.
Shawn: I don't like it because it is too much about the "how"
Jeanne: I used "scoring system" to be generic.
Shawn: I don't like the specific examples
Denis: I propose using on the first sentence.
<Chuck> Jeane: A couple of the requirements included some examples for other groups, but not attached to it at all.
Denis: I propose a second sentence that explains why, instead of how.
Alastair sent a note to the group saying he thought we should do it.
Shawn: How does a large/complex or large and complex site demonstrate conformance?
<dboudreau> Proposal to add to 3.7 (as a second sentence): This scoring system would encourage organizations to leverage findings from their usability testing with people with disabilities to improve the overall level of accessibility of their site or application.
Shawn: I think we should come up with a wording that addresses that case.
Jeanne: I would add "For
example," preceding it.
... What's the challenge of a positive scoring system?
Shawn: To provide a framework for showing that you have gone beyond the minimum. It provides a way through the conformance model itself to show "not only did we meet these guidelines, but we met them really well, and here's how."
Charles: It's more about striving for a better practice instead of striving for more points.
Shawn: WCAG 2.x has that requirement, AAA, but I wouldn't call it successful.
Jan: AAA isn't even achievable in some cases.
Chuck: I think the first sentence is sufficient.
<Jan> +1 tp forst sentence being sufficient by itself
Shawn: That's where I'm ending up with myself.
<Chuck> +1 first sentence.
<Jan> +1 to first sentence being sufficient by itself
The Guidelines motivate organizations to go beyond minimal accessibility requirements by providing a scoring system that rewards organizations which demonstrate a greater effort to improve accessibility.
<dboudreau> +1 eith the first sentence only
<shari> +1 to first sentence only
+ 1 to first sentence
<Jan> I would reword the first sentence a bit
RESOLUTION: 3.7 Motivation: The Guidelines motivate organizations to go beyond minimal accessibility requirements by providing a scoring system that rewards organizations which demonstrate a greater effort to improve accessibility.
<Lauriat> From Alastair: "Scalable measures: Where some guidelines can be tested across large areas of a website (e.g. the interface enforces and guides end-users to create useful alt text) that can be used for large and frequently updated sites to claim a partial conformance for many pages, so long as the task based testing is also completed."
<Lauriat> "Conformance should be flexible enough to work for small and very large sites."
Jeanne: What about putting "Conformance should be flexible enough to work for small and very large sites." as a Design PRinciple?
Shawn: It could also fit in Scope
<Lauriat> Scope: The guidelines provide guidance for people and organisations that produce digital assets and technology. Our intent is to provice guideance for a diverse group of stakeholders including including content creators, browsers, authoring tools, assistive technologies, and more.
Scope: The guidelines provide guidance for people and organisations that produce digital assets and technology. Our intent is to provice guideance for a diverse group of stakeholders including including content creators, organizations with different levels of size and complexity, browsers, authoring tools, assistive technologies, and more.
<KimD> How about: The guidelines provide guidance for people and organizations that produce digital assets and technology of varying size and complexity. Our intent is to provide guidance for a diverse group of stakeholders including content creators, browsers, authoring tools, assistive technologies, and more.
<Chuck> +1
<Lauriat> +1
<dboudreau> +1
+1
<AngelaAccessForAll> +1
<CharlesHall> +1
RESOLUTION: The guidelines provide guidance for people and organizations that produce digital assets and technology of varying size and complexity. Our intent is to provide guidance for a diverse group of stakeholders including content creators, browsers, authoring tools, assistive technologies, and more.
Shawn: I think it should include all the changes since CSUN? How do we do it in Github?
Jeanne: Let's ask Mike Crabb.
Shawn: A diff between March 6 and today.
RESOLUTON: Ask Mike Crabb. Shawn will email him.
Shawn: We discussed with AWK how
to get approval from AGWG. He suggested that we should send a
survey to AGWG:
... Here are the changes
... Here are the Design Principles. Can you live with them? If
not, then make comments
... Here are the Requirements. Can you live with them? If not,
then make comments
Denis: I took some action items for minor changes, can I still do them?
Shawn: We want to send it out by Friday.
Denis: I'll do my best, otherwise, I'll submit them through the survey.
Shawn: We worked on this at CSUN
Silver meeting.
... We started to look at each of the WCAG SC, and look at the
user need.
... Then we started grouping user needs together.
... For example: When we looked at 1.1.1, we grouped it as
"anything that isn't text, needs text"
... We started by ignoring all the exemptions, because we
wanted to boil it down to the user need and then build up the
guidance from there.
... At one point, Wayne Dick joined us, which was very helpful.
One of them we ended up breaking the SC down into 4 different
user needs.
... The complex example was SC 2.4.4 <-https://docs.google.com/document/d/1aCRXrtmnSSTso-6S_IO9GQ3AKTB4FYt9k92eT_1PWX4/edit#heading=h.fjszln5otgkv
... and we started working on the Methods, because Wayne was
giving expertise.
... Customization of text rendering was sufficiently complex
that we needed to break it down more.
... Reflow, for example, was viewport customization not text
customization
Denis: How much is done?
Shawn: We got to 2.1.4
Denis: What should new people to this activity do to get caught up?
Shawn: That's the overall project plan
<Lauriat> Project Plan Draft: https://docs.google.com/document/d/1zFgVcDUMSOrZ5nnGRocs2pZYkqOhwdyMU_Z62_CedbQ/edit
SHawn: It's not a project plan
yet, more of an outline of what we have and what we need.
... the third part of the Content section describes how to move
the WCAG guidance to Silver.
,,, you can skim the document and get a feel for what we are doing, and then just jump on board.
scribe: today, the actual WCAG
Guidelines are super high level, and we are landing a little
below that.
... it's not really clear what that means (example from
WCAG)
Denis: Is the goal of this exercise to lay the foundation for Plain Language
Shawn: It's more of the Information Architecture. The simplification of wording is so we can have a fundamental understanding of the essense of a success criterion.
Jeanne: This also sets us up for the prototype of how to build the guidelines: starting with user needs, identifying the tests, writing the Methods and then writing the Guidelines.
This is scribe.perl Revision: 1.154 of Date: 2018/09/25 16:35:56 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Present: Chuck Lauriat jeanne Shri dboudreau Jan AngelaAccessForAll KimD CharlesHall Rachael JakeAbma Found Scribe: jeanne Inferring ScribeNick: jeanne WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 09 Apr 2019 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.)[End of scribe.perl diagnostic output]