Re: [WSG] Playing a sound file - what is the best way?
You can use media component in flash and import dynamic mp3. If you want, I can send you an example. cheers Daniele http://www.gizax.it - Original Message - From: Stevio [EMAIL PROTECTED] To: wsg@webstandardsgroup.org Sent: Wednesday, May 18, 2005 5:35 PM Subject: Re: [WSG] Playing a sound file - what is the best way? Here is the code I am using at the moment. Please let me know what browsers and platforms would have a problem accessing the mp3 file. object id=MPlayer6-4 height=69 classid=clsid:22D6F312-B0F6-11D0-94AB-0080C74C7E95 param name=AutoStart value=false param name=AutoSize value=true param name=AnimationAtStart value=true param name=EnableContextMenu value=true param name=filename value=media/file.mp3 param name=ShowStatusBar value=true param name=ShowControls value=true param name=ShowPositionControls value=true param name=EnableFullScreenControls value=false param name=volume value=-200 embed src=media/file.mp3 autostart=0 audiostream=1 showcontrols=1 width=280 height=69 volume=-200 type=application/x-mplayer2 showstatusbar=1 pluginspage=http://www.microsoft.com/Windows/MediaPlayer/;/embed diva href=media/file.mp3 class=bodylinkListen to advert/a/div /object Thanks, Stephen - Original Message - From: Stevio [EMAIL PROTECTED] To: wsg@webstandardsgroup.org Sent: Wednesday, May 18, 2005 4:09 PM Subject: Re: [WSG] Playing a sound file - what is the best way? Does anyone have a link to an online article that shows you how to do this in Flash? Thanks, Stephen - Original Message - From: Mike Foskett [EMAIL PROTECTED] To: wsg@webstandardsgroup.org Sent: Tuesday, May 17, 2005 5:14 PM Subject: RE: [WSG] Playing a sound file - what is the best way? I completely agree, use Flash. I'd say the same for video too, for the same reasons. Why: One solution multiple platforms. Saturation on all computers is over 90%. That's more than any browser. No platform compatibility issues Mac / PC. No browser issues Firefox / IE / Netscape / Opera. With a single start / stop button in Flash, alongside a link to download the file. -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.322 / Virus Database: 266.11.12 - Release Date: 17/05/2005 ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.322 / Virus Database: 266.11.12 - Release Date: 17/05/2005 ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] flash and accessabilty
what happened? I've received more responses like this - Original Message - From: scott parsons [EMAIL PROTECTED] To: wsg@webstandardsgroup.org; IMB Recipient 1 [EMAIL PROTECTED] Sent: Saturday, April 09, 2005 9:16 AM Subject: Re: [WSG] flash and accessabilty Patrick Lauke wrote: In and of itself, flash will never be accessible to everybody, as it requires a plugin; it's not a web native technology. A plugin huh?, I've always wondered what the difference was between having to have the flash plugin and having to have a web browser? it is very hard to see any html css website without the correct plugin (that is a browser), so why does it suddenly become so much worse when flash is required? Sorry but I have just never understood this argument, would you mind explaining? Older screenreaders can't access its content at all. So, it's important to provide accessible fallback mechanisms. Yeah but my fallback positions for older browsers, like say netscape 2 are pretty hazy, theoretically they could understand the plain html, ignoring more modern tags but I haven't really tested it recently. However, for the percentage of users that *can* use flash (have the plugin, have assistive technology that works correctly with it, etc), you should then ensure that the flash itself follows sensible, accessibility-related norms and conventions. I'd suggest having a look at Bob Regan's recent post on Flash Accessibility http://www.markme.com/accessibility/archives/007003.cfm and the interesting WCAG 1.0 Techniques for Flash http://www.markme.com/accessibility/archives/007344.cfm (just to clarify: WCAG itself does not necessarily cover Flash, as it's not an official W3C technology...so this document makes recommendations that are similar / in sympathy with what WCAG tries to achieve, but in a Flash context). These links are really useful as I work in advertising and it is a constant battle to get any kind of adherence to accessibility requirements. But also because there are many flash designers out there who would like to learn but haven't found good resources. ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] flash and accessabilty
what happened? I've received more responses like this - Original Message - From: scott parsons [EMAIL PROTECTED] To: wsg@webstandardsgroup.org; IMB Recipient 1 [EMAIL PROTECTED] Sent: Saturday, April 09, 2005 9:16 AM Subject: Re: [WSG] flash and accessabilty Patrick Lauke wrote: In and of itself, flash will never be accessible to everybody, as it requires a plugin; it's not a web native technology. A plugin huh?, I've always wondered what the difference was between having to have the flash plugin and having to have a web browser? it is very hard to see any html css website without the correct plugin (that is a browser), so why does it suddenly become so much worse when flash is required? Sorry but I have just never understood this argument, would you mind explaining? Older screenreaders can't access its content at all. So, it's important to provide accessible fallback mechanisms. Yeah but my fallback positions for older browsers, like say netscape 2 are pretty hazy, theoretically they could understand the plain html, ignoring more modern tags but I haven't really tested it recently. However, for the percentage of users that *can* use flash (have the plugin, have assistive technology that works correctly with it, etc), you should then ensure that the flash itself follows sensible, accessibility-related norms and conventions. I'd suggest having a look at Bob Regan's recent post on Flash Accessibility http://www.markme.com/accessibility/archives/007003.cfm and the interesting WCAG 1.0 Techniques for Flash http://www.markme.com/accessibility/archives/007344.cfm (just to clarify: WCAG itself does not necessarily cover Flash, as it's not an official W3C technology...so this document makes recommendations that are similar / in sympathy with what WCAG tries to achieve, but in a Flash context). These links are really useful as I work in advertising and it is a constant battle to get any kind of adherence to accessibility requirements. But also because there are many flash designers out there who would like to learn but haven't found good resources. ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] flash and accessabilty
what happened? I've received more responses like this - Original Message - From: scott parsons [EMAIL PROTECTED] To: wsg@webstandardsgroup.org; IMB Recipient 1 [EMAIL PROTECTED] Sent: Saturday, April 09, 2005 9:16 AM Subject: Re: [WSG] flash and accessabilty Patrick Lauke wrote: In and of itself, flash will never be accessible to everybody, as it requires a plugin; it's not a web native technology. A plugin huh?, I've always wondered what the difference was between having to have the flash plugin and having to have a web browser? it is very hard to see any html css website without the correct plugin (that is a browser), so why does it suddenly become so much worse when flash is required? Sorry but I have just never understood this argument, would you mind explaining? Older screenreaders can't access its content at all. So, it's important to provide accessible fallback mechanisms. Yeah but my fallback positions for older browsers, like say netscape 2 are pretty hazy, theoretically they could understand the plain html, ignoring more modern tags but I haven't really tested it recently. However, for the percentage of users that *can* use flash (have the plugin, have assistive technology that works correctly with it, etc), you should then ensure that the flash itself follows sensible, accessibility-related norms and conventions. I'd suggest having a look at Bob Regan's recent post on Flash Accessibility http://www.markme.com/accessibility/archives/007003.cfm and the interesting WCAG 1.0 Techniques for Flash http://www.markme.com/accessibility/archives/007344.cfm (just to clarify: WCAG itself does not necessarily cover Flash, as it's not an official W3C technology...so this document makes recommendations that are similar / in sympathy with what WCAG tries to achieve, but in a Flash context). These links are really useful as I work in advertising and it is a constant battle to get any kind of adherence to accessibility requirements. But also because there are many flash designers out there who would like to learn but haven't found good resources. ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] flash and accessabilty
what happened? I've received more responses like this - Original Message - From: scott parsons [EMAIL PROTECTED] To: wsg@webstandardsgroup.org; IMB Recipient 1 [EMAIL PROTECTED] Sent: Saturday, April 09, 2005 9:16 AM Subject: Re: [WSG] flash and accessabilty Patrick Lauke wrote: In and of itself, flash will never be accessible to everybody, as it requires a plugin; it's not a web native technology. A plugin huh?, I've always wondered what the difference was between having to have the flash plugin and having to have a web browser? it is very hard to see any html css website without the correct plugin (that is a browser), so why does it suddenly become so much worse when flash is required? Sorry but I have just never understood this argument, would you mind explaining? Older screenreaders can't access its content at all. So, it's important to provide accessible fallback mechanisms. Yeah but my fallback positions for older browsers, like say netscape 2 are pretty hazy, theoretically they could understand the plain html, ignoring more modern tags but I haven't really tested it recently. However, for the percentage of users that *can* use flash (have the plugin, have assistive technology that works correctly with it, etc), you should then ensure that the flash itself follows sensible, accessibility-related norms and conventions. I'd suggest having a look at Bob Regan's recent post on Flash Accessibility http://www.markme.com/accessibility/archives/007003.cfm and the interesting WCAG 1.0 Techniques for Flash http://www.markme.com/accessibility/archives/007344.cfm (just to clarify: WCAG itself does not necessarily cover Flash, as it's not an official W3C technology...so this document makes recommendations that are similar / in sympathy with what WCAG tries to achieve, but in a Flash context). These links are really useful as I work in advertising and it is a constant battle to get any kind of adherence to accessibility requirements. But also because there are many flash designers out there who would like to learn but haven't found good resources. ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] flash and accessabilty
what happened? I've received more responses like this - Original Message - From: scott parsons [EMAIL PROTECTED] To: wsg@webstandardsgroup.org; IMB Recipient 1 [EMAIL PROTECTED] Sent: Saturday, April 09, 2005 9:16 AM Subject: Re: [WSG] flash and accessabilty Patrick Lauke wrote: In and of itself, flash will never be accessible to everybody, as it requires a plugin; it's not a web native technology. A plugin huh?, I've always wondered what the difference was between having to have the flash plugin and having to have a web browser? it is very hard to see any html css website without the correct plugin (that is a browser), so why does it suddenly become so much worse when flash is required? Sorry but I have just never understood this argument, would you mind explaining? Older screenreaders can't access its content at all. So, it's important to provide accessible fallback mechanisms. Yeah but my fallback positions for older browsers, like say netscape 2 are pretty hazy, theoretically they could understand the plain html, ignoring more modern tags but I haven't really tested it recently. However, for the percentage of users that *can* use flash (have the plugin, have assistive technology that works correctly with it, etc), you should then ensure that the flash itself follows sensible, accessibility-related norms and conventions. I'd suggest having a look at Bob Regan's recent post on Flash Accessibility http://www.markme.com/accessibility/archives/007003.cfm and the interesting WCAG 1.0 Techniques for Flash http://www.markme.com/accessibility/archives/007344.cfm (just to clarify: WCAG itself does not necessarily cover Flash, as it's not an official W3C technology...so this document makes recommendations that are similar / in sympathy with what WCAG tries to achieve, but in a Flash context). These links are really useful as I work in advertising and it is a constant battle to get any kind of adherence to accessibility requirements. But also because there are many flash designers out there who would like to learn but haven't found good resources. ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] flash and accessabilty
what happened? I've received more responses like this - Original Message - From: scott parsons [EMAIL PROTECTED] To: wsg@webstandardsgroup.org; IMB Recipient 1 [EMAIL PROTECTED] Sent: Saturday, April 09, 2005 9:16 AM Subject: Re: [WSG] flash and accessabilty Patrick Lauke wrote: In and of itself, flash will never be accessible to everybody, as it requires a plugin; it's not a web native technology. A plugin huh?, I've always wondered what the difference was between having to have the flash plugin and having to have a web browser? it is very hard to see any html css website without the correct plugin (that is a browser), so why does it suddenly become so much worse when flash is required? Sorry but I have just never understood this argument, would you mind explaining? Older screenreaders can't access its content at all. So, it's important to provide accessible fallback mechanisms. Yeah but my fallback positions for older browsers, like say netscape 2 are pretty hazy, theoretically they could understand the plain html, ignoring more modern tags but I haven't really tested it recently. However, for the percentage of users that *can* use flash (have the plugin, have assistive technology that works correctly with it, etc), you should then ensure that the flash itself follows sensible, accessibility-related norms and conventions. I'd suggest having a look at Bob Regan's recent post on Flash Accessibility http://www.markme.com/accessibility/archives/007003.cfm and the interesting WCAG 1.0 Techniques for Flash http://www.markme.com/accessibility/archives/007344.cfm (just to clarify: WCAG itself does not necessarily cover Flash, as it's not an official W3C technology...so this document makes recommendations that are similar / in sympathy with what WCAG tries to achieve, but in a Flash context). These links are really useful as I work in advertising and it is a constant battle to get any kind of adherence to accessibility requirements. But also because there are many flash designers out there who would like to learn but haven't found good resources. ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] flash and accessabilty
what happened? I've received more responses like this - Original Message - From: scott parsons [EMAIL PROTECTED] To: wsg@webstandardsgroup.org; IMB Recipient 1 [EMAIL PROTECTED] Sent: Saturday, April 09, 2005 9:16 AM Subject: Re: [WSG] flash and accessabilty Patrick Lauke wrote: In and of itself, flash will never be accessible to everybody, as it requires a plugin; it's not a web native technology. A plugin huh?, I've always wondered what the difference was between having to have the flash plugin and having to have a web browser? it is very hard to see any html css website without the correct plugin (that is a browser), so why does it suddenly become so much worse when flash is required? Sorry but I have just never understood this argument, would you mind explaining? Older screenreaders can't access its content at all. So, it's important to provide accessible fallback mechanisms. Yeah but my fallback positions for older browsers, like say netscape 2 are pretty hazy, theoretically they could understand the plain html, ignoring more modern tags but I haven't really tested it recently. However, for the percentage of users that *can* use flash (have the plugin, have assistive technology that works correctly with it, etc), you should then ensure that the flash itself follows sensible, accessibility-related norms and conventions. I'd suggest having a look at Bob Regan's recent post on Flash Accessibility http://www.markme.com/accessibility/archives/007003.cfm and the interesting WCAG 1.0 Techniques for Flash http://www.markme.com/accessibility/archives/007344.cfm (just to clarify: WCAG itself does not necessarily cover Flash, as it's not an official W3C technology...so this document makes recommendations that are similar / in sympathy with what WCAG tries to achieve, but in a Flash context). These links are really useful as I work in advertising and it is a constant battle to get any kind of adherence to accessibility requirements. But also because there are many flash designers out there who would like to learn but haven't found good resources. ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] flash and accessabilty
what happened? I've received more responses like this - Original Message - From: scott parsons [EMAIL PROTECTED] To: wsg@webstandardsgroup.org; IMB Recipient 1 [EMAIL PROTECTED] Sent: Saturday, April 09, 2005 9:16 AM Subject: Re: [WSG] flash and accessabilty Patrick Lauke wrote: In and of itself, flash will never be accessible to everybody, as it requires a plugin; it's not a web native technology. A plugin huh?, I've always wondered what the difference was between having to have the flash plugin and having to have a web browser? it is very hard to see any html css website without the correct plugin (that is a browser), so why does it suddenly become so much worse when flash is required? Sorry but I have just never understood this argument, would you mind explaining? Older screenreaders can't access its content at all. So, it's important to provide accessible fallback mechanisms. Yeah but my fallback positions for older browsers, like say netscape 2 are pretty hazy, theoretically they could understand the plain html, ignoring more modern tags but I haven't really tested it recently. However, for the percentage of users that *can* use flash (have the plugin, have assistive technology that works correctly with it, etc), you should then ensure that the flash itself follows sensible, accessibility-related norms and conventions. I'd suggest having a look at Bob Regan's recent post on Flash Accessibility http://www.markme.com/accessibility/archives/007003.cfm and the interesting WCAG 1.0 Techniques for Flash http://www.markme.com/accessibility/archives/007344.cfm (just to clarify: WCAG itself does not necessarily cover Flash, as it's not an official W3C technology...so this document makes recommendations that are similar / in sympathy with what WCAG tries to achieve, but in a Flash context). These links are really useful as I work in advertising and it is a constant battle to get any kind of adherence to accessibility requirements. But also because there are many flash designers out there who would like to learn but haven't found good resources. ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] flash and accessabilty
what happened? I've received more responses like this - Original Message - From: scott parsons [EMAIL PROTECTED] To: wsg@webstandardsgroup.org; IMB Recipient 1 [EMAIL PROTECTED] Sent: Saturday, April 09, 2005 9:16 AM Subject: Re: [WSG] flash and accessabilty Patrick Lauke wrote: In and of itself, flash will never be accessible to everybody, as it requires a plugin; it's not a web native technology. A plugin huh?, I've always wondered what the difference was between having to have the flash plugin and having to have a web browser? it is very hard to see any html css website without the correct plugin (that is a browser), so why does it suddenly become so much worse when flash is required? Sorry but I have just never understood this argument, would you mind explaining? Older screenreaders can't access its content at all. So, it's important to provide accessible fallback mechanisms. Yeah but my fallback positions for older browsers, like say netscape 2 are pretty hazy, theoretically they could understand the plain html, ignoring more modern tags but I haven't really tested it recently. However, for the percentage of users that *can* use flash (have the plugin, have assistive technology that works correctly with it, etc), you should then ensure that the flash itself follows sensible, accessibility-related norms and conventions. I'd suggest having a look at Bob Regan's recent post on Flash Accessibility http://www.markme.com/accessibility/archives/007003.cfm and the interesting WCAG 1.0 Techniques for Flash http://www.markme.com/accessibility/archives/007344.cfm (just to clarify: WCAG itself does not necessarily cover Flash, as it's not an official W3C technology...so this document makes recommendations that are similar / in sympathy with what WCAG tries to achieve, but in a Flash context). These links are really useful as I work in advertising and it is a constant battle to get any kind of adherence to accessibility requirements. But also because there are many flash designers out there who would like to learn but haven't found good resources. ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] flash and accessabilty
what happened? I've received more responses like this - Original Message - From: scott parsons [EMAIL PROTECTED] To: wsg@webstandardsgroup.org; IMB Recipient 1 [EMAIL PROTECTED] Sent: Saturday, April 09, 2005 9:16 AM Subject: Re: [WSG] flash and accessabilty Patrick Lauke wrote: In and of itself, flash will never be accessible to everybody, as it requires a plugin; it's not a web native technology. A plugin huh?, I've always wondered what the difference was between having to have the flash plugin and having to have a web browser? it is very hard to see any html css website without the correct plugin (that is a browser), so why does it suddenly become so much worse when flash is required? Sorry but I have just never understood this argument, would you mind explaining? Older screenreaders can't access its content at all. So, it's important to provide accessible fallback mechanisms. Yeah but my fallback positions for older browsers, like say netscape 2 are pretty hazy, theoretically they could understand the plain html, ignoring more modern tags but I haven't really tested it recently. However, for the percentage of users that *can* use flash (have the plugin, have assistive technology that works correctly with it, etc), you should then ensure that the flash itself follows sensible, accessibility-related norms and conventions. I'd suggest having a look at Bob Regan's recent post on Flash Accessibility http://www.markme.com/accessibility/archives/007003.cfm and the interesting WCAG 1.0 Techniques for Flash http://www.markme.com/accessibility/archives/007344.cfm (just to clarify: WCAG itself does not necessarily cover Flash, as it's not an official W3C technology...so this document makes recommendations that are similar / in sympathy with what WCAG tries to achieve, but in a Flash context). These links are really useful as I work in advertising and it is a constant battle to get any kind of adherence to accessibility requirements. But also because there are many flash designers out there who would like to learn but haven't found good resources. ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
[WSG] review
Hi all, can you please review http://www.gizax.it ? Thanks in advance Daniel
Re: [WSG] Gnews
sorry but thread is closed - Original Message - From: Olajide Olaolorun [EMAIL PROTECTED] To: Web Standards Group wsg@webstandardsgroup.org Sent: Tuesday, March 08, 2005 3:35 PM Subject: Re: [WSG] Gnews If you use what Jamie says you should, make sure it is safe with Register Globals cause hackers use that to hack you... :) Nice work :) -- Best Regards, Olajide Olaolorun @ www.olajideolaolorun.com ...ain't nothing impossible unless you make it... ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
[WSG] Gnews
Hi all,I 'd like that you try my new experimental application called GNEWS.Gnews is a fast and practical system to manage news of your website, without DB and with your code always validated. Thanks to its easy personalization, Gnews manages news through text files, therefore also who has problems to find DB, can have capacity to use this tool. If you want to try it click herehttp://www.gizax.it/experiments/admin.phpenter with user "demo", password "demo"best regards Daniel
Re: [WSG] Gnews
yes, thank for your advice :)
- Original Message -
From:
Jamie Mason
To: 'wsg@webstandardsgroup.org'
Sent: Monday, March 07, 2005 4:49
PM
Subject: RE: [WSG] Gnews
looks good, it lets you submit empty forms though, use something
like;
if (strlen($whatever) 1) {computer says
no};
or
if
(!$whatever) {computer says no};
Jamie
From: Gizax Studios [mailto:[EMAIL PROTECTED]
Sent: 07 March 2005 15:35To: wsg@webstandardsgroup.orgSubject:
[WSG] Gnews
Hi
all,I 'd like that you try my new experimental application called
GNEWS.Gnews is a fast and
practical system to manage news of your website, without DB and with your code
always validated. Thanks to its easy personalization, Gnews manages news through text files,
therefore also who has problems to find DB,
can have capacity
to use this tool. If you want to try it click herehttp://www.gizax.it/experiments/admin.phpenter with user "demo", password "demo"best
regards Daniel
Re: [WSG] Site Review - CAR SELLER PORTAL
good work, only two things : http://validator.w3.org/check?uri=http%3A%2F%2Fwww.meucarronovo.com.br%2F;verbose=1 http://jigsaw.w3.org/css-validator/validator?uri=http://www.meucarronovo.com.br/c/mcn.css regards Daniele http://www.gizax.it Internet Accessibility - Original Message - From: Genau Lopes Jr. [EMAIL PROTECTED] To: wsg@webstandardsgroup.org Sent: Saturday, March 05, 2005 2:59 PM Subject: [WSG] Site Review - CAR SELLER PORTAL Hi, I would like to show you some improvements that we did in our Portal. http://www.meucarronovo.com.br After some advices about our XHTML validation, we almost fixed all bugs in xhtml, leaving just one bit problem with our js function that detects the resolution to advertisement skyscrapper. We proud to be the first car seller world wide portal to use XHTML and Webstandards, iether using some Disabilities functions like ShortTag, to users with Carpal Tunnel and notebooks users. (as you can see http://www.meucarronovo.com.br/acessibilidade.php ). I would like to thanks all people that help us to improve the quality standards and ask for some Advices and oppinions. Thanks , Genau Lopes Junior Webdesigner/MediaDeveloper www.meucarronovo.com.br/quemsomos.php ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Check website
thanks :))) Daniel - Original Message - From: David Laakso [EMAIL PROTECTED] To: wsg@webstandardsgroup.org Sent: Monday, February 21, 2005 8:24 AM Subject: Re: [WSG] Check website On Mon, 21 Feb 2005 07:18:44 +0100, Gizax Studios [EMAIL PROTECTED] wrote: Hi all, Check this website for a marketing company. Some section are coming soon. http://www.arcapplied.org/tempodaniele/index.php regards Daniel http://www.gizax.it Daniel, I like the color and general feel ot the site but find the nav menu and content text too small. The banner logo is not happy with it's position at 800, nor at higher screen resolutions with a sidebar in place, sliding under the outer container. Alternate text for that image might be a good idea. A couple of errors on the CSS file, including the inclusion of MS proprietary stuff, keeps it from validating. Page shift happening when going to and from pages not long enough to draw a scroll bar.The comment form is breaking right on zoom. Regards, David -- de gustibus non est disputandum http://www.dlaakso.com/ ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
[WSG] Check website
Hi all, Check this website for a marketing company. Some section are coming soon. http://www.arcapplied.org/tempodaniele/index.php regards Daniel http://www.gizax.it ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
