HTML-AAM: UIA mapping for time element

[jasonkiss]

From @cyns on March 31, 2016 19:37

ControlType: Text
LocalizedControlType: "time"
FullDescription: value of datetime attribute

Add the datetime attribute value as the lowest priority for description mapping for the element

Copied from original issue: w3c/aria#314

[jasonkiss]

The mappings as above were already present.

Add the datetime attribute value as the lowest priority for description mapping for the element

I'm assuming that rule 2D of the text alternative in ACCNAME-AAM sufficiently covers this issue, or is there a reason this should be explicitly mentioned?

On a related note, the current UIA mapping for time has the following note:

Note: create a separate UIA Control of type Text. This is different from most UIA text mappings, which only create ranges in the page text pattern.

I'm assuming we want to keep this? Should it be rephrased in any way? For example:

"Note: Create a separate accessible object of the Text ControlType."

Ultimately, this last question is directly related to issue #58 and how we address UIA behaviour with such objects.

[jasonkiss]

Need to confirm if ACCNAME-AAM still sufficiently addresses use of datetime attribute as last option for accessible description computation.

Also need to confirm need for and phrasing of the note regarding use of Text Control Type, which is related to issue #58.

Accordingly, moving this issue to AAM v2.

[boggydigital]

AccName-AAM 2D sufficiently covers this issue and we don't need to explicitly mention this.

[boggydigital]

As for the keeping the note - I don't have a strong preference, @jasonkiss version looks good to me, but even the original doesn't strike me as wrong that much, so not sure there is value in changing.

[boggydigital]

Finally see my notes in #58 - I'd like to converge on the consistent model we'd be able to document and go from there. Where we are today, I'd say small (specification wording) tweak are not really needed.