<p>Accessibility considerations? I think they belong in an UI extension, maybe in a non-normative section.</p>
<p><blockquote type="cite">On May 19, 2009 9:16 PM, "Andrew Arnott" <<a href="mailto:andrewarnott@gmail.com">andrewarnott@gmail.com</a>> wrote:<br><br>I've been building up UI extension support in DotNetOpenAuth and came up with something I'd like to see added to the UI extension:<br>
<br><div style="margin-left:40px">The Provider SHOULD handle the escape key and close the window or send a negative assertion.<br>
</div><br>Especially when the RP uses window.showModalDialog to popup the window with the Provider in it, the fact that it's modal aids the UX because the user easily sees that he should interact with that window instead of with the RP. But if the user changes their mind, rather than find the Cancel or X buttons to close the window, the Escape key is what a user tends to do to back out of a modal dialog they don't want to be in. <br>
<br>Is this the right forum to discuss this?<br><font color="#888888"><br clear="all">--<br>Andrew Arnott<br>"I [may] not agree with what you have to say, but I'll defend to the death your right to say it." - S. G. Tallentyre<br>
</font><br>_______________________________________________<br>
specs mailing list<br>
<a href="mailto:specs@openid.net">specs@openid.net</a><br>
<a href="http://openid.net/mailman/listinfo/specs" target="_blank">http://openid.net/mailman/listinfo/specs</a><br>
<br></blockquote></p>