W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > October to December 2014

Re: WCAG-ISSUE-43: ARIA2 and PDF5 do not apply to SC 3.3.3 [HTML & ARIA Techniques TF]

From: Sailesh Panchang <sailesh.panchang@deque.com>
Date: Tue, 16 Dec 2014 11:26:28 -0500
Message-ID: <CAJi9Cqpb6sw_3q4HdddtS39qDXR3+FE4pdNFXjeUy4qB9kOLEQ@mail.gmail.com>
To: Jonathan Avila <jon.avila@ssbbartgroup.com>
Cc: Web Content Accessibility Guidelines Working Group <w3c-wai-gl@w3.org>
Hi Jonathan,
Consider  a case where there is an asterisk next to  first and last
name fields (not part of field's label). And there is a middle name
field without the star. One  could bring the star within the label to
make it PD. Or one could place aria-required=true.   The star does not
go away when when one enters data into the fields. Are you suggesting
one should remove the star and aria-required or set it to false when
one enters data into the fields? The aria-required serves the same
purpose as the star and it can be PD. If I choose to review the form
before submitting it  I'll not know that I need not have entered a
middle name. This is misleading when a star is displayed only for 2 of
the 3 fields.
When form submission fails,  it is not good enough for SC 3.3.3 if the
PD text for first name simply reads the label and the word required.
That was read even before the form was submitted. The suggestion
should say something like "Please enter a first name"  for SC 3.3.3
compliance. And if this is done, do you not agree that aria-invalid
simply creates more noise for the end user? Refer to examples for
aria-invalid.
Thanks,
Sailesh




On 12/16/14, Jonathan Avila <jon.avila@ssbbartgroup.com> wrote:
>> ARIA2  nor PDF5 do not apply to SC 3.3.3. Simply placing
>> aria-required=true by itself does not help to say how an
>
> I see this as a layered approach.  ARIA2 can only be used if the field is
> empty.  Once the field contains data then you would need different
> suggestion of the field is still in error and the field is automatically
> detected.
>
> Jonathan
>
> -----Original Message-----
> From: Web Content Accessibility Guidelines Working Group Issue Tracker
> [mailto:sysbot+tracker@w3.org]
> Sent: Tuesday, December 16, 2014 10:32 AM
> To: w3c-wai-gl@w3.org
> Subject: WCAG-ISSUE-43: ARIA2 and PDF5 do not apply to SC 3.3.3 [HTML & ARIA
> Techniques TF]
>
> WCAG-ISSUE-43: ARIA2 and PDF5 do not apply to SC 3.3.3 [HTML & ARIA
> Techniques TF]
>
> http://www.w3.org/WAI/GL/track/issues/43
>
> Raised by: Sailesh Panchang
> On product: HTML & ARIA Techniques TF
>
> ARIA2  nor PDF5 do not apply to SC 3.3.3. Simply placing aria-required=true
> by itself does not help to say how an input error may be fixed.
> The attribute is seldom added after form submission when input errors are
> detected.
> When it is used, generally, is exposed before form submission.
> So I do not see how ARIA2 / PDF5 apply to SC 3.3.3.
>
>
>
>
>
Received on Tuesday, 16 December 2014 16:27:01 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 16 January 2018 15:34:16 UTC