<div>I think using the role attribute is the best solution here:<br></div><br><input type="text" role="username"><br><input type="email" role="username"><br><br>This way we're using the type attribute to indicate what sort of data<br>
is being entered, and the role attribute to indicate how it will be<br>used. I think the separation of these is sensible, although it's not<br>entirely consistent across the spec (in my model, "search" would be a<br>
role on a type="text"). It's also backwards compatible with HTML4 and<br>with current implementations of HTML5, and could tie in with the rest<br>of ARIA's roles model.<br><br>The same concept could, for instance, also be applied to a signup form<br>
where there is a check box for opting in to marketing:<br><br><input type="checkbox" role="optin"><br><br>You'd need to use a role attribute of "login" or "signup" on the form<br>
as well to give context to things like role="username" so the browser<br>would know what behaviour is appropriate. As someone pointed out, the<br>form element isn't always available if you're working with <a href="http://ASP.NET">ASP.NET</a>, so<br>
it would seem right to make the roles legal for fieldset, section and<br><div>div as well. In fact, it would seem right anyway because you could have <br></div><div>something like an ecommerce site where there's a single form to place</div>
<div>an order which deals with payment for the current order as well as </div><div>signup for the account.</div><div><br></div><div>David Goss</div>