Hi Jonas, "Isn't it more semantically correct to use the <em> element? If not, is the <em> element failing to fulfill its intended purpose and should be removed?" It depends on how the warning is structured, use of the <em> and <strong> are not really useful for people who use AT as they are not currently supported [1]. We could say well that is the AT's fault, which is true, but if we want to provide meaningful semantics we should take support into account, which is why is suggested a heading. regards stevef [1] http://www.paciellogroup.com/blog/?p=41 On 28 October 2010 09:16, Jonas Sicking <jonas@sicking.cc> wrote: > On Thu, Oct 28, 2010 at 12:45 AM, Steve Faulkner > <faulkner.steve@gmail.com> wrote: > > Hi Maciej, > > > > I think that warning is fine, except that it is visually emphasised, but > not > > in the mark-up. suggest the most robust way to empahsise this information > is > > to provide a heading for it. > > Isn't it more semantically correct to use the <em> element? If not, is > the <em> element failing to fulfill its intended purpose and should be > removed? > > / Jonas > -- with regards Steve Faulkner Technical Director - TPG Europe Director - Web Accessibility Tools Consortium www.paciellogroup.com | www.wat-c.org Web Accessibility Toolbar - http://www.paciellogroup.com/resources/wat-ie-about.html
Received on Thursday, 28 October 2010 08:35:30 UTC