– DRAFT –
WCAG2ICT Task Force Teleconference

reagent, make minutes

Announcements

Maryjom: Reminder from last week, Maryjom - this is my last day in this task force.

bbailey: Tuesday call, one provision per person per week.

Maryjom: This will be a good time to contribute to the WCAG 3 Criteria

Maryjom: I'll be in contact with Philday until the open items are done.

<Zakim> PhilDay, you wanted to ask for a co-chair, editor, or any other help

PhilDay: If there is anyone that has time at all, if anyone has time to take on editing duties or be co chair, drop me a message.

Maryjom: Email from someone at Intuit who is interested in joining the task force

12 Feb survey Survey Results for Level AAA SCs

<maryjom> Link to Survey: https://www.w3.org/wbs/55145/AAA-take-two/results/

Question 1: Introductory information for AAA in the SC Problematic for Closed Functionality

<maryjom> Link to question 1: https://www.w3.org/wbs/55145/AAA-take-two/results/#xq1

<maryjom> Link to SC problematic for closed section from PR 828: https://w3c.github.io/wcag2ict/#level-aaa-criteria

Maryjom: First paragraph under level AAA

Maryjom: reviewing survey responses, Gregg had some minor language changes, PhilDay said "ok as is", Loic plussed the changes from Gregg. Daniel had some substantive changes

bbailey: The assignment was to put the AAA statement from WCAG into WCAG2ICT.

Current text from editor's draft:

Level AAA success criteria are not considered mandatory, and per WCAG 2, "It is not recommended that Level AAA conformance be required as a general policy for entire sites because it is not possible to satisfy all Level AAA success criteria for some content." This is especially true for ICT with closed functionality, where there may not be

available assistive technology and/or platform support (including user agents, such as browsers) to satisfy these criteria. The applicability of the following WCAG 2 Level AAA success criteria are considered problematic to apply to ICT with closed functionality:

Gregg's change

Level AAA success criteria are not considered mandatory, and per WCAG 2, "It is not recommended that Level AAA conformance be required as a general policy for entire sites because it is not possible to satisfy all Level AAA success criteria for some content." This is especially true for ICT with closed functionality, where assistive technology

and/or platform support (including user agents, such as browsers) may not be available to satisfy these criteria. The applicability of the following WCAG 2 Level AAA success criteria are considered problematic to apply to ICT with closed functionality:

<maryjom> It is not recommended that Level AAA conformance be required as a general policy for entire sites because it is not possible to satisfy all Level AAA success criteria for some content." This is especially true for ICT with closed functionality, where assistive technology and/or platform support (including user agents<#user-agents>) may not be

<maryjom> available to satisfy these criteria. The applicability of the following WCAG 2 Level AAA success criteria is considered problematic to apply to ICT with closed functionality:

<maryjom> WCAG 2 states that "It is not recommended that Level AAA conformance be required as a general policy for entire sites because it is not possible to satisfy all Level AAA success criteria for some content." This is especially true for ICT with closed functionality, where assistive technology and/or platform support (including user

<maryjom> agents<#user-agents>) may not be available to satisfy these criteria. The applicability of the following WCAG 2 Level AAA success criteria is considered problematic to apply to ICT with closed functionality:

Daniel's further change (as per Mary Jo's edits above):

WCAG2 states: "It is not recommended that Level AAA conformance be required as a general policy for entire sites because it is not possible to satisfy all Level AAA success criteria for some content." This is especially true for ICT with closed functionality, where assistive technology and/or platform support (including user agents<#user-agents>)

may not be available to satisfy these criteria. The applicability of the following WCAG 2 Level AAA success criteria is considered problematic to apply to ICT with closed functionality:

LauraM: Can we switch from the negative to the positive (instead of not recommended, ... level AAA should be considered where possible)

Daniel: +1 to LauraM's proposal of positive framing

<Zakim> bbailey, you wanted to ask about "states"

maryjom: That is a direct quote from WCAG2, but we could paraphrase and make it positive if we rewrite it in our own words

bbailey: Didn't like states, so rewriting it helps this as well

daniel: we can keep the reference to WCAG.

Daniel: Just link to the reference, but OK to change the words

maryjom: Retrieving WCAG 2 link to the content about AAA not being required.

<maryjom> https://www.w3.org/TR/WCAG22/#conformance-reqs

Pulling from Note 2 here.

<bbailey> CR 1 note two: https://www.w3.org/TR/WCAG22/#cc1

Possible wording: WCAG2 (5.2.1 Conformance Level)[https://www.w3.org/TR/WCAG22/#conformance-reqs], NOTE 2 indicates that Level AAA conformance should be considered where possible for applicable content.

Updated wording with correct link:

WCAG2 (5.2.1 Conformance Level)[https://www.w3.org/TR/WCAG22/#cc1], NOTE 2 indicates that Level AAA conformance should be considered where possible for applicable content.

<LauraM> +1 PhilDay above

<bbailey> +1

Daniel: WCAG says that AAA not be required so we should acknowledge. And add the language from PhilDay above as well

Both statements:

WCAG2 (Conformance Level)[https://www.w3.org/TR/WCAG22/#cc1], NOTE 2 indicates that Level AAA conformance should be considered where possible for applicable content. However, it also states that "It is not recommended that Level AAA conformance be required as a general policy for entire sites because it is not possible to satisfy all Level AAA

success criteria for some content." This is especially true for ICT with closed functionality, where assistive technology and/or platform support (including user agents<#user-agents>) may not be available to satisfy these criteria. The applicability of the following WCAG 2 Level AAA success criteria is considered problematic to apply to ICT with

closed functionality:

<maryjom> WCAG 2 (5.2.1 Conformance Level)[https://www.w3.org/TR/WCAG22/#cc1], NOTE 2 indicates that Level AAA conformance should not be required. However, Level AAA should be considered where possible for applicable content.

Daniel: The note should be attached to the phrase and the link.

LauraM: Q+ to say agree with Daniel

Longer version: WCAG2 encourages that Level AAA conformance should be considered where possible for applicable content. However, WCAG2 (Conformance Level)[https://www.w3.org/TR/WCAG22/#cc1], NOTE 2 states that "It is not recommended that Level AAA conformance be required as a general policy for entire sites because it is not possible to satisfy

all Level AAA success criteria for some content." This is especially true for ICT with closed functionality, where assistive technology and/or platform support (including user agents<#user-agents>) may not be available to satisfy these criteria. The applicability of the following WCAG 2 Level AAA success criteria is considered problematic to apply

to ICT with closed functionality:

Daniel: The obvious reason it should be considered is that AAA SC contain provisions that meet user needs that are not otherwise met.

<maryjom> WCAG 2 (5.2.1 Conformance Level)[https://www.w3.org/TR/WCAG22/#cc1], NOTE 2 indicates that Level AAA conformance should not be required. however, Level AAA should be considered, where possible, for applicable content because these success criteria cover user needs that are not met with Level A and AA success criteria.

Do we want to keep the last two sentences on closed functionality?

<bbailey> +1

Maryjom: Yes, just still working above that.

<bbailey> +1 to first two sentences

Revised version (with latest edits to start): WCAG 2 (5.2.1 Conformance Level)[https://www.w3.org/TR/WCAG22/#cc1], NOTE 2 indicates that Level AAA conformance should not be required, However, Level AAA should be considered, where possible, for applicable content because these success criteria cover user needs that are not met with Level A and AA

success criteria. This is especially true for ICT with closed functionality, where assistive technology and/or platform support (including user agents<#user-agents>) may not be available to satisfy these criteria. The applicability of the following WCAG 2 Level AAA success criteria is considered problematic to apply to ICT with closed

functionality:

<maryjom> WCAG 2 (5.2.1 Conformance Level)[https://www.w3.org/TR/WCAG22/#cc1], NOTE 2 indicates that Level AAA conformance should not be required. However, Level AAA should be considered, where possible, for applicable content because these success criteria cover user needs that are not met in full with Level A and AA success criteria.

This is especially true for ICT with closed functionality, where assistive technology and/or platform support (including user agents<#user-agents>) may not be available to satisfy these criteria. The applicability of the following WCAG 2 Level AAA success criteria is considered problematic to apply to ICT with closed functionality:

<maryjom> POLL: Is the edited introductory text for the Level AAA section of the SC Problematic for Closed Functionality ready to incorporate into the editor's draft?

<PhilDay> +1

<Daniel> +1

Edited text in single paragraph for ease of reference:

WCAG 2 (5.2.1 Conformance Level)[https://www.w3.org/TR/WCAG22/#cc1], NOTE 2 indicates that Level AAA conformance should not be required. However, Level AAA should be considered, where possible, for applicable content because these success criteria cover user needs that are not met in full with Level A and AA success criteria. This is especially

true for ICT with closed functionality, where assistive technology and/or platform support (including user agents<#user-agents>) may not be available to satisfy these criteria. The applicability of the following WCAG 2 Level AAA success criteria is considered problematic to apply to ICT with closed functionality:

<bbailey> +1

<LauraM> +1

Daniel: If we put the positive first and then the negative, it might flow better

Latest tweak: Level AAA should be considered, where possible, for applicable content because these success criteria cover user needs that are not met in full with Level A and AA success criteria.

However, WCAG 2 (5.2.1 Conformance Level)[https://www.w3.org/TR/WCAG22/#cc1], NOTE 2 indicates that Level AAA conformance should not be required. This is especially true for ICT with closed functionality, where assistive technology and/or platform support (including user agents<#user-agents>) may not be available to satisfy these criteria. The

applicability of the following WCAG 2 Level AAA success criteria is considered problematic to apply to ICT with closed functionality:

Minor edit to get Daniel's change:

Level AAA should be considered, where possible, for applicable content because these success criteria cover user needs that are not met in full with Level A and AA success criteria.

However, WCAG 2 (5.2.1 Conformance Level)[https://www.w3.org/TR/WCAG22/#cc1], NOTE 2 indicates that it is not recommended that Level AAA conformance be required. This is especially true for ICT with closed functionality, where assistive technology and/or platform support (including user agents<#user-agents>) may not be available to satisfy these

criteria. The applicability of the following WCAG 2 Level AAA success criteria is considered problematic to apply to ICT with closed functionality:

<maryjom> DRAFT RESOLUTION: Incorporate the edited introductory text for the Level AAA section of the SC Problematic for Closed Functionality into the editor's draft, as shown above.

<PhilDay> +1

<bbailey> +1

+!

<LauraM> +1

<Daniel> +1

RESOLUTION: Incorporate the edited introductory text for the Level AAA section of the SC Problematic for Closed Functionality into the editor's draft, as shown above.

<bbailey> not be required **as a general policy**

Question 2: Adding Level AAA into the introduction section of WCAG2ICT Group Note

<maryjom> Link to question 2: https://www.w3.org/wbs/55145/AAA-take-two/results/#xq2

<maryjom> Link to PR 832: w3c/wcag2ict#832

Link to Daniel's comment: https://github.com/w3c/wcag2ict/pull/832/#issuecomment-3890606706

<Daniel> `/me just put link to the preview on the PR

Link to preview of PR: https://deploy-preview-832--wcag2ict.netlify.app/

<maryjom> Daniel's comment/question is about this new statement: It is not recommended that WCAG 2 conformance be required as a general policy for non-web documents and software because it is not possible to satisfy all success criteria for some non-web ICT.

bbailey: We like WCAG2ICT and WCAG2 conformance given the input from WCAG2ICT but as a general policy, we want people using WCAG2 out of the box for non web docs and software.

Daniel: on the other hand, we could say that we recommend people use the guidance and make it positive.

Daniel: This is more editorial than substantive.

Attempt at a more positive framing:

WCAG2ICT can be useful as guidance for policy for non-web documents and software

However, because it is not possible to satisfy all success criteria for some non-web ICT, and therefore it is not recommended that WCAG 2 conformance be required without changes as a general policy for non-web documents and software.

Bbailey: It is not possible to satisfy all AAA SC for all conditions

Maryjom: Bbailey has a task which is to edit this content

Maryjom: Bbailey can do a PR against my pr.

Daniel: I recommend using the suggestion feature.

Daniel: Suggest we don't nest PRs. Instead use the Suggestion feature (click + on the line, then click on suggestion button which looks a bit like a document, then create suggested text).
… Above is within a PR in github

Question 3: Section Titles revisited

<maryjom> Link to question 3: https://www.w3.org/wbs/55145/AAA-take-two/results/#xq3

<maryjom> Link to PR 833: https://github.com/w3c/wcag2ict/pull/833/

<maryjom> Preview of document: https://deploy-preview-833--wcag2ict.netlify.app/

Note: Comments on level A and AA title needs editing - there is a typo (currently states AAA)

<maryjom> DRAFT RESOLUTION: Incorporate PR 833 to adjust the section titles as proposed

<bbailey> +1

<LauraM9> +1

<PhilDay> +1

<Daniel> +1

RESOLUTION: Incorporate PR 833 to adjust the section titles as proposed

[Mary Jo looking at next few questions]

Daniel: what we are discussing is if to merge the Part 2 of 2 1.3.6 into the editors draft.

We will pick up questions 4 onwards next week, and also question 2 with Bruce's edits

Daniel: It is possible to submit answers even if the survey is closed - you just get a warning.

maryjom: Will change the end date on the survey so you can give more input

o rrsagent, make minutes

<Daniel> rrsageent, draft minutes