Re: "Error correction (Processes)" to WCAG 2.2 draft

Consider  two scenarios:
Case 1: a 100%  validation of input is done  before submission is successful.
Case 2: Form submission is accepted with some data validation checks.
User is notified later on of acceptance / rejection of submission or
given a chance to change data.

I understand this SC is introducing privacy and security newly over
financial, legal, data aspects covered in SC 3.3.4.
But I do not understand "logical" ...does it mean functionality
requirements of the application? If yes, the submission will not sail
through either case 1 or 2.
And for the same reason, a mere warning may be insufficient if other
previously entered information is invalidated. That too will not make
the submission a success in case 1. It may be OK for case 2 pending
final approval of submission.

Privacy and security impacts all users not just PWD depending on
accessible content.
Content authors always have the option not to permit certain aspects /
features of their app  by citing these reasons. Is an SC needed
telling them they can do so? Can content owners be relied upon to
design content and business rules with the best interests of their
users in mind? Users need to figure out privacy terms and policies and
set suitable preferences and protect their interests.
 SC 3.3.4  shortlists certain types of apps (financial, legal, data)
for sound reasons.
I agree to Jonathan's point: when SC 3.3.6 is already available, why
craft another SC? Elevating it to Level AA too does not make sense ...
then where is the distinction between SC 3.3.4 and 3.3.6?
Thanks,
-- 
Sailesh Panchang
Principal Accessibility Consultant
Deque Systems Inc
381 Elden Street, Suite 2000, Herndon, VA 20170
Mobile: 571-344-1765



On 7/10/20, Jonathan Avila <jon.avila@levelaccess.com> wrote:
> This SC seems similar to SC 3.3.6 (which is Level AAA) although this one
> mentions processes and seems stricter than 3.3.4 which is Level AA.  I would
> like more clarity on relationship to existing criteria before committing to
> a CFC.
>
> Jonathan
>
> From: Pascalides, Justine E ( JPASCALIDES ) <JPascalides@ETS.ORG>
> Sent: Friday, July 10, 2020 2:07 PM
> To: Alastair Campbell <acampbell@nomensa.com>; WCAG list (w3c-wai-gl@w3.org)
> <w3c-wai-gl@w3.org>
> Subject: RE: CFC - Add "Error correction (Processes)" to WCAG 2.2 draft
>
> CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know the
> content is safe.
>
> Hi All,
>
> An exception to the SC is implied with the current verbiage. It seems to me
> that explicitly calling out the exception (i.e., "unless essential to the
> activity") would align with the presentation of exceptions in other success
> criteria - which would cover the logical, security, privacy, and other valid
> reasons where an exception might be applicable.
>
> Does the use of a "Next" button within a process constitute a submission? If
> buttons used to advance but not complete a process are out of scope, perhaps
> explicitly mentioning that would be helpful in defining a "submission" for
> purposes of this SC.
>
> Justine
>
> From: Alastair Campbell
> <acampbell@nomensa..com<mailto:acampbell@nomensa..com>>
> Sent: Friday, July 10, 2020 5:51 AM
> To: WCAG list (w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>)
> <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>>
> Subject: RE: CFC - Add "Error correction (Processes)" to WCAG 2.2 draft
> Importance: High
>
> Apologies, that was the wrong PR link, it should be:
> https://github.com/w3c/wcag/pull/1157<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwcag%2Fpull%2F1157&data=02%7C01%7Cjpascalides%40ets.org%7Ccd582c94933c405cf7be08d824b6bba0%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637299714540028847&sdata=jtqO%2BOk6QzJyu6uPmCPcKTNZNaWu27JEXPDbUaYDTUQ%3D&reserved=0>
>
>
> From: Alastair Campbell
>
>
> Call For Consensus - ends Wednesday July 15th at midday Boston time.
>
>
>
> The Working Group has discussed adding the new SC "Error correction
> (Processes)" to the WCAG 2.2 draft:
>
> https://www.w3.org/2020/03/25-ag-minutes.html#item03<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2020%2F03%2F25-ag-minutes.html%23item03&data=02%7C01%7Cjpascalides%40ets.org%7Ccd582c94933c405cf7be08d824b6bba0%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637299714540028847&sdata=d3y5bvaHRbrp65DPhFPypUheLUDzgWDOYBO2kjc%2B7%2Fo%3D&reserved=0>
>
>
>
> The changes, preview of the documents, and survey link are detailed in this
> pull request:
>
> https://github.com/w3c/wcag/pull/1046<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwcag%2Fpull%2F1046&data=02%7C01%7Cjpascalides%40ets.org%7Ccd582c94933c405cf7be08d824b6bba0%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637299714540038841&sdata=jce6Q7NL4o2gWUxzLv0AClEY2CXRLAl%2BxpggyByttRM%3D&reserved=0>
>
>
>
> If you have concerns about this proposed consensus position that have not
> been discussed already and feel that those concerns result in you "not being
> able to live with" this decision, please let the group know before the CfC
> deadline.
>
> Kind regards,
>
> -Alastair
>
> --
>
> www.nomensa.com<https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.nomensa.com%2F&data=02%7C01%7Cjpascalides%40ets.org%7Ccd582c94933c405cf7be08d824b6bba0%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637299714540048833&sdata=h5n8AdbjK20hVzqbMWoIzchT%2B%2B7k10qrhdbtoEcXVCU%3D&reserved=0>
> / @alastc
>
>
> ________________________________
>
> This e-mail and any files transmitted with it may contain privileged or
> confidential information. It is solely for use by the individual for whom it
> is intended, even if addressed incorrectly. If you received this e-mail in
> error, please notify the sender; do not disclose, copy, distribute, or take
> any action in reliance on the contents of this information; and delete it
> from your system. Any other use of this e-mail is prohibited.
>
>
> Thank you for your compliance.
>
> ________________________________
>

Received on Friday, 10 July 2020 21:01:10 UTC