ISSUE-51: How should we address the issue of datatypes and formatters in ARIA?

We added values to the invalid state in response to Aaron's proposal: http://www.w3.org/mid/OFEDA428B6.4A59EDC0-ONC1257433.0055408E-C125744A.004492FF@us.ibm.com. This should be revisited in ARIA 2.0 to determine if we want to enrich the type for invalid to reflect what the type theory supports.

Related:

Allow the the aria-valuenow property of range widgets to be set directly by the user agent or assistive technology. This will allow range widgets to be more in line with the behavior of desktop range widgets, but would require a value format property (and potentially an increment value).

For example, if the range were to increment a currency amount from 0 to 100 US dollars, the value formation could be defined as "$###.##" with an aria-valuemin="0" and aria-valuemax="100", and if the range were to represent a date from December 10, 2008 through January 5, 2009, the value format could be "yyyy-mm-dd" with an aria-valuemin="2008-12-10" and aria-valuemax="2009-01-05". There may also need to some hint of increment value if it cannot be determined from the value format or other range data.

For some reason, originally posted to XTech instead of PF.
http://lists.w3.org/Archives/Public/wai-xtech/2008Dec/0031.html

[MichaelC]: Relates also to issue-18 http://www.w3.org/WAI/PF/Group/track/issues/18

close. won't fix.