Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[HTML AAM] Mapping of 'form' element to ARIA 'form' role should only be done when element has a label #45

Closed
jasonkiss opened this issue Oct 12, 2016 · 3 comments
Assignees
Milestone

Comments

@jasonkiss
Copy link
Contributor

From @richschwer on April 26, 2016 19:58

The form element in HTML should only map to the ARIA form role if it has a label. Otherwise, it maps to the normal form mapping on the platforms. The reason is backward compatibility for old code that does things like embed a single button in form or make form the container for all the content in the page besides

Copied from original issue: w3c/aria#353

@jasonkiss
Copy link
Contributor Author

Given that HTML-AAM defers to Core-AAM where it can, will wait for Core-AAM to resolve its issue #514 before following suit.

@LJWatson LJWatson added this to the WD for wide review milestone Jun 17, 2017
@jasonkiss jasonkiss added AAM V2 and removed AAM labels Jan 9, 2018
@scottaohara
Copy link
Member

scottaohara commented Jun 3, 2019

Noting Core-AAM issue now exists at Add conditional platform mappings for nameless forms #11

@scottaohara
Copy link
Member

Closing this issue as HTML AAM is mapping to the correct roles / definitions in Core AAM if an HTML form has a name or not.

cc @carmacleod as we spoke about this today.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants