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

form element should have the default role of none, unless it has an accessible name #94

Closed
jongund opened this issue Mar 8, 2018 · 1 comment

Comments

@jongund
Copy link

jongund commented Mar 8, 2018

There are a lot of empty form elements in documents and typically a form element (usually as an artifact of some javascript library) and the associated controls are already in a more useful landmark like "main" or "search". It is unlikely that authors will know that they are creating a landmark when they add the form element to a page, the form landmark should only be used explicitly by an author by adding the role=form attribute.

In previous discussions on the form element I believe the consensus was the default role should be "none", unless the form element has an accessible name, in the case the form element has accessible name the role would be "form".

The other allowed roles should be "form" or "search".

I encourage you to change this before entering CR, it is the biggest issue in the spec that I would like resolved.

@jongund jongund changed the title form element should have the default role of none form element should have the default role of none, unless it has an accessible name Mar 9, 2018
@stevefaulkner
Copy link
Collaborator

Yes, it is an issue, which has been fixed, but this is not where the mapping is defined, it is defined in the HTML AAM and what you are asking is defined appropriately there.

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

2 participants