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: Jonathan Avila <jon.avila@ssbbartgroup.com>
Date: Tue, 16 Dec 2014 15:38:47 +0000
To: Web Content Accessibility Guidelines Working Group <w3c-wai-gl@w3.org>
Message-ID: <BY2PR03MB2725F1718356BEBF20B23269B6C0@BY2PR03MB272.namprd03.prod.outlook.com>
> 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 15:39:18 UTC

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