In response to your first paragraph you already do this for aria-invalid:
https://www.w3.org/WAI/PF/testharness/testresults?testsuite_id=1&testcase_id=587
Why would we do things differently for aria-current?
Rich Schwerdtfeger
From: Alexander Surkov <surkov.alexander@gmail.com>
To: Joanmarie Diggs <jdiggs@igalia.com>
Cc: "W3C WAI Protocols & Formats" <public-pfwg@w3.org>
Date: 01/28/2015 08:01 AM
Subject: Re: [REVIEW REQUEST] Action-1548: Add aria-current attribute
I do not support this bit: "Any value not included in the list of allowed
values must be treated by user agents as if the value true had been
provided" because it forces the browser to validate the value and that's
performance downgrade even if there's no consumer for aria-current. So I
would exclude words "by user agents" or added "or assistive technologies"
instead. Also I would replaced "must" to "should" to make the attribute
value list extensible.
Also I think I don't get aria-current listbox example, in particular this
part " whereas aria-selected would be used to indicate the page of results
the user had selected to be displayed next". Also it would be good to
explain connection with focus. Is there any known app on the web
implementing this use case?
Thanks.
Alex.
On Thu, Jan 22, 2015 at 4:48 PM, Joanmarie Diggs <jdiggs@igalia.com> wrote:
Hi all.
The aria-current attribute is now in master. Please review. Thanks!
Done: http://rawgit.com/w3c/aria/master/aria/aria.html#aria-current
--joanie
