Issue 106: The <form> element should only map to FORM landmark with restriction of accessible name

[jongund]

Updated the form element mapping to only be a form landmark when it html as an accessible name

[jongund]

I am working on some landmark rules with Deque labs and having this requirement in the spec would similify rules relating to top level landmarks (e.g. main, banner and contentinfo)

[stevefaulkner]

thanks @jongund

[joanmarie]

What does "no corresponding role" mean with respect to platforms? Does it mean "pruned from the tree" or is it mapped to a platform accessibility role? I don't have strong feelings either way, as long as it doesn't show up as ATK_ROLE_UNKNOWN on my platform. 😄 But I do think more guidance is called for in order to ensure implementors know what to do for nameless HTML form elements.

Speaking just for my platform, if it is not pruned from the accessibility tree, possible mappings would be:

• ATK_ROLE_SECTION (which is the mapping used for the div element and other generic block elements which need to remain in the accessibility tree but have no semantic meaning)
• ATK_ROLE_FORM (which is not the same as the mapping for the ARIA form role, which should be exposed as an ATK_ROLE_LANDMARK).

Thoughts?

EDIT: Compare to what was done for the footer element which has "no corresponding role" in the ARIA row, AND explicit platform mappings beneath.

[stevefaulkner]

@joanmarie I will add extra suggested mappings and we can take it from there, thanks!

[stevefaulkner]

fixed via 2724b29