This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 28799 - Form element should have no default role or role of region
Summary: Form element should have no default role or role of region
Status: RESOLVED INVALID
Alias: None
Product: ARIA
Classification: Unclassified
Component: HTML AAM (show other bugs)
Version: Future
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: steve faulkner
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-11 21:39 UTC by jgunder
Modified: 2018-05-03 21:20 UTC (History)
3 users (show)

See Also:
jason: needinfo? (jongund)


Attachments

Description jgunder 2015-06-11 21:39:13 UTC
The role=form is considered a landmark and not all form elements on a page should be considered a landmark.  Sometimes there are multiple form elements on the same page, but several of them do not visible form controls or used to hold only input[type=hidden] or disabled form controls, so their should be no default role or maybe role=region so that it would only be a landmark if someone added a label to it.
Comment 1 Jason Kiss 2015-06-24 03:13:30 UTC
Are there other examples where a form on a page shouldn't be considered a landmark? In the three examples noted, two of them, namely invisible form controls and input[type=hidden], could be handled with role=none, or even aria-hidden=true on the form element, to the degree that they don't expect any user interaction and are not visible.

With regard to the third example, I'm not clear on the use for disabled controls that aren't part of a form that is otherwise expecting user input, and so would presumably be a reasonable landmark.

Regarding use of role=region without a label, I remember the discussions but note that in ARIA 1.1 the region role is always a landmark and MUST have a label [1].

[1] http://rawgit.com/w3c/aria/master/aria/aria.html#region
Comment 2 James Nurthen 2018-05-03 21:20:04 UTC
HTML AAM is no longer an ARIA Deliverable. If you wish to pursue this issue please file at https://github.com/w3c/html-aam/issues