Mapping @aria-invalid: string versus token value from James Craig on 2014-07-28 (public-pfwg@w3.org from July 2014)

From: James Craig <jcraig@apple.com>
Date: Mon, 28 Jul 2014 12:02:51 -0700
To: PF <public-pfwg@w3.org>
Cc: Joseph Scheuhammer <clown@alum.mit.edu>
Message-id: <0BB0369E-F57D-485D-BDF0-2B91AE462AA3@apple.com>

@aria-invalid is a token value, but as Joseph pointed out today, the UAIG instructs user agents to map string values to the platform APIs. I think this is an error in the UAIG, even if some (or all) of the implementations are doing it. 

Free-form string tokens mean some AT could start providing special behavior for a non-standardized value. For example: JAWS could start using "warning-length" versus NVDA supporting "size-warning" to mean the same thing. I'd like to avoid the inconsistencies of the "browser war" years, so I don't think this possibility should exist.

Thoughts?

Received on Monday, 28 July 2014 19:03:20 UTC