Indeed, and that's where the problem lies. I don't believe that using <button> (which must be placed within a <form>) purely for _hyperlink_ purposes is good practice or semantically correct. My apologies, I may have gotten a bit ahead of myself.
Med vennlig hilsen / Kind regards, Frank M. Palinkas Technical Writer, Opera Software http://dev.opera.com/articles/accessibility/ On Mon, Feb 23, 2009 at 3:10 PM, <michael.brocking...@bt.com> wrote: > Surely the button element is REQUIRED to be enclosed in a <form> ?? > > Mike > > ------------------------------ > *From:* li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] *On > Behalf Of *Frank Palinkas > *Sent:* 23 February 2009 12:56 > *To:* wsg@webstandardsgroup.org > *Subject:* Re: [WSG] IE and the <button> element > > IMHO, not very semantic in nature. We need the button element to be able to > carry a valid link-type attribute. Enclosing it in a form just don't cut it. > It must be able to stand by itself as an alternative means to activate a > hyperlink, as another aspect of its functionality. > Med vennlig hilsen / Kind regards, > > Frank M. Palinkas > Technical Writer, Opera Software > http://dev.opera.com/articles/accessibility/ > > ******************************************************************* > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > Help: memberh...@webstandardsgroup.org > ******************************************************************* > ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org *******************************************************************
