Results of WCAG meeting -- regarding our submissions to them for edits to WCAG2ICT

Here are the results of the WCAG meeting regarding our submissions to them for edits to WCAG2ICT  


Edit to WCAG2ICT language for SC 1.1.1
M376 doesn't include the last sentence of Note 1 that begins "If they do not appear..."

RESOLUTION: remove the last sentence of note #1, that begins "If they do not appear..." [SHOWN IN BOLD and BRACKETS]

Rationale: this sentence isn't needed or appropriate.

-15Mar13

 
CURRENT TEXT - with DELETION shown in bold with square brackets

Additional guidance when applying Success Criterion 1.1.1 to Non-Web Documents and Software:

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

Note 1: CAPTCHAs do not currently appear outside of the Web. However, if they do appear, this guidance is accurate. [If they do not appear then the success criterion would be met automatically, as with any situation where a success criterion talks about something that is not present.]

Note 2: See also the discussion on Closed Functionality in the Introduction.


RESOLUTION:  accept with removal of the "or appropriate" in rationale
Rationale: this sentence isn't needed or appropriate.




Edit to WCAG2ICT language for SC 2.2.2
M376 replaces "page" and "Web page" with "document" in Note 2

RESOLUTION: Change first paragraph of our guidance to say "This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above)" replacing "page" and "Web page" with "non-web documents and software in Note 2.       [ADDITION SHOWN IN BOLD and CURLY BRACKETS]

Rationale: we missed making this change.

-8Mar13

CURRENT TEXT with ADDITION shown in bold with CURLY brackets

Additional guidance when applying Success Criterion 2.2.2 to Non-Web Documents and Software:

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above) {replacing "page" and "Web page" with "non-web documents and software" in Note 2 .}

Note: While the success criteria uses the term “information”, the WCAG 2.0 INTENT section makes it clear that this is to be applied to all content. Any content, whether informative or decorative, that is updated automatically, blinks, or moves may create an accessibility barrier.



RESOLUTION: accept with addition "of the success criterion" after "...Note 2"      (or else it is unclear what note is being referred to.)

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above) replacing "page" and "Web page" with "non-web documents and software" in Note 2 of the success criterion.



Edit to WCAG2ICT language for SC 2.4.2
M376 reminds readers that the title is sufficient if it describes the topic or person.

RESOLUTION:Add the the end of our first note: "if it describes the topic or purpose". [ADDITION SHOWN IN BOLD and CURLY BRACKETS]

Rationale: it is a useful reminder, taken directly from the SC language.

-8Mar13

CURRENT TEXT with ADDITION shown in bold with CURLY brackets

Additional guidance when applying Success Criterion 2.4.2 to Non-Web Documents and Software:

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above) replacing “Web pages” with “non-web documents or software”.

With these substitutions, it would read: 2.4.2 Page Titled: Non-web documents or software have titles that describe topic or purpose. (Level A)

Note 1: As described in the WCAG intent (above), the name of a software application or non-web document (e.g. document, media file, etc.) is a sufficient title {if it describes the topic or purpose}.

Note 2: See also the discussion on Closed Functionality in the Introduction.



RESOLUTION:  accepted as proposed



Edit to WCAG2ICT language for SC 3.3.4
WCAG2ICT incorrectly states the substitution is "set of web pages" not "web pages".

RESOLUTION:Correct our text to remove 'set of" language so it reads : "replacing 'Web pages' with 'non-web documents and software'.[TEXT TO REMOVE IS SHOWN IN BOLD and BRACKETS]

Rationale: we had made an error in our substitution language.

-15 Mar13

CURRENT TEXT with DELETION shown in bold with square brackets

Additional guidance when applying Success Criterion 3.3.4 to Non-Web Documents and Software:

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above) replacing  “[a set of] Web pages” with “a non-web document or software”.

With these substitutions, it would read:

3.3.4 Error Prevention (Legal, Financial, Data): For a non-web document or software that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true: (Level AA)

      Reversible: Submissions are reversible.

     Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.

    Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.


RESOLUTION:  accepted as proposed




Gregg
--------------------------------------------------------
Gregg Vanderheiden Ph.D.
Director Trace R&D Center
Professor Industrial & Systems Engineering
and Biomedical Engineering University of Wisconsin-Madison
Technical Director - Cloud4all Project - http://Cloud4all.info
Co-Director, Raising the Floor - International - http://Raisingthefloor.org
and the Global Public Inclusive Infrastructure Project -  http://GPII.net