Auto start false then let the audience choose if to play or not. Kate http://jungaling.com/Malaysia/ ----- Original Message ----- From: [EMAIL PROTECTED] To: wsg@webstandardsgroup.org Sent: Friday, August 15, 2008 4:16 PM Subject: RE: [WSG] Acceptable autoplay of music
On a more positive note - you could point out that having an embedded player would allow the band to offer the user a choice of music, which would be a better option than alienating many users. (Offering a client a 'better option' usually goes down a lot better than 'don't do that!') From an accessibility angle, it shouldn't be too hard to see that those people who are going to be most affected by this, ie those using a screen reader on top of a normal browser, are likely to be those least able to deal with turning if off, whatever the mechanism. As others have said, the easiest option for most users is to kill the browser/window/tab. Mike ---------------------------------------------------------------------------- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Prisca schmarsow Sent: Friday, August 15, 2008 4:09 PM To: wsg@webstandardsgroup.org Subject: Re: [WSG] Acceptable autoplay of music Hi, same here - I personally hate autoplay on site, I'm gone in a sec.... I also think this does affect anyone - personal preference or not - people can be caught out by this, in office environments (as mentioned before) as well as impaired users.... And though a band site might warrant the autoplay - I'd still try to allow site visitor's to be in control of whether or not to listen to the music. As the site is about music - a clearly visible player is likely to be included anyway, allowing easy access to the band's tracks. Not sure what the guidelines say on this - but when I teach best practices for webdesign I advise my students to always give the user the control and not bombard them with anything they might not expect. Just my thoughts... Prisca On Fri, Aug 15, 2008 at 3:53 PM, Nancy Johnson <[EMAIL PROTECTED]> wrote: If I come to a site with music playing, I leave it immediately without looking at the site. I don't know best practices, but I believe the user needs to be in control. On Fri, Aug 15, 2008 at 10:36 AM, Nick Taylor <[EMAIL PROTECTED]> wrote: > Good morning James, > > If it helps, what you will find is the typical user experience on band > websites is that the audio player automatically starts within 2-3 seconds of > the site fully loading. The file size of the player and the audio file are > both small so the site isn't slow when being viewed on the user's end. > > An important thing to keep in mind that the user always needs to have the > option to adjust the volume and to start/stop/pause the music. If that is > not a feature the user will get annoyed and could potentially leave the site > just as quickly as they got there! > > > I hope this helps and have a great day! > > ---------------------------------------- > Nicholas Taylor > Web Strategy & Systems Manager > Purdue University > South Campus Courts, Building D > 507 Harrison Street > West Lafayette, IN 47907 > (765) 496-6864 office > (765) 494-0793 fax > (616) 634-9193 mobile > > > > On 8/15/08 10:14 AM, "James Leslie" <[EMAIL PROTECTED]> wrote: > > Hi, > > This is a more best practices question than strictly standards, but I > *think* it is on-topic, apologies if not and please mail me off-list if you > feel that is more appropriate. > > I have a band for a client who are requesting that on the homepage loading a > music player starts automatically. Do people think this is acceptable for a > bands website or would you think that you should always get the user to > initiate playback? > > Thanks > > James > > > ******************************************************************* > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > Help: [EMAIL PROTECTED] > ******************************************************************* > > > > > > > > ******************************************************************* > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > Help: [EMAIL PROTECTED] > ******************************************************************* ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ******************************************************************* -- . graphiceyedea.co.uk . eyedea.eu . eyelearn.org . -- ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ******************************************************************* ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ******************************************************************* ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************