W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > April 2010

[Bug 9429] Unobsolete the <strike> element - instead suggest how to use it

From: <bugzilla@jessica.w3.org>
Date: Wed, 14 Apr 2010 02:21:01 +0000
To: mike@w3.org
Message-Id: <E1O1sDt-0002pC-AL@jessica.w3.org>

--- Comment #7 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>  2010-04-14 02:24:56 ---
(In reply to comment #5)

> Status: Did Not Understand Request
> Change Description: no spec change
> Rationale: Hmm... I might be able to work with that... How should it be
> rendered in a speech browser?

Isn't the question about speech browsers also relevant when it comes to the <b>
element? Is there a clear way to indicate <b> as opposed to e.g. <em> or
<strong> in speech browsers? If there arent a clear diff for <b>, then why need
there be a clear way for <strike>?

I am not sure how speech browsers should operate. Somewhat related: when I
tested Lynx and its relatives, then only one or two of them made any
distinction between <strike> and <del> (some did not understand <del>).  A text
console based browser requires that the user learns himself/herself to
interpret those conventions that the text browser offers. Likewise, if a speech
based browser announces a span of <del> as "deleted", then a span of <strike>
could be announced as "striked". 

If speech browsers is to separat the striked text stylistcally, rather than
through an announcement, then I am unsure. May be reading it a little faster
could be an option? When it is read faster, then one pays less attention to it. 

Authors should probably not overdo things - to overuse of the <strike>/<s>
element could perhaps be annoying to listen to.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Wednesday, 14 April 2010 02:32:27 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:16 UTC