- From: Charles McCathieNevile <charles@w3.org>
- Date: Thu, 11 Mar 1999 19:36:59 -0500 (EST)
- To: "B.K. DeLong" <bkdelong@naw.org>
- cc: w3c-wai-au@w3.org
It is possible to use BGSOUND in a way which is accessible, which is to use it in conjunction with alternate presentation(s) of the content pointed to by the BGSOUND element. While BGSOUND does not, as far as I know, provide by itself any way to introduce that content, I don't see any difficulty in using BGSOUND in an authoring tool where the necessary alternative content is made available in a way consistent with W3C DTDs (for example, a textual transcript being made available. Some of this is provided in a way which may appeal to more designers by the OBJECT element of HTML 4, since it allows for cleaner presentation of a range of alterntive content types. On Thu, 11 Mar 1999, B.K. DeLong wrote: At 03:21 PM 3/11/99 -0800, Charles Oppermann wrote: >I agree that the tool should not write out HTML markup that causes >accessibility difficulties, but that is a very different issue than writing >out markup that isn't part of a W3C recommendation and they should not be >tied together. Then we need to make sure somewhere in the "validation and checking section," the authoring tool mentiones that certain elements specific to a single browser are not accessible....like BGSOUND. -- B.K. DeLong 360 Huntington Ave. Director Suite 140CSC-305 New England Chapter Boston, MA 02115 World Organization (617) 247-3753 of Webmasters http://www.world-webmasters.org bkdelong@naw.org --Charles McCathieNevile mailto:charles@w3.org phone: +1 617 258 0992 http://www.w3.org/People/Charles W3C Web Accessibility Initiative http://www.w3.org/WAI MIT/LCS - 545 Technology sq., Cambridge MA, 02139, USA
Received on Thursday, 11 March 1999 19:37:07 UTC