The thing that gets me with this discussion is why create all these "features" to cover up the problem?
If you created it in XHTML/ php etc and not flash, you would not have these problems and then you would not have to spend extra time fixing the problems that has been caused by using flash. >>> [EMAIL PROTECTED] 11/01/2007 11:30:16 am >>> Christian Montoya wrote: > On 1/10/07, Rob O'Rourke <[EMAIL PROTECTED]> wrote: >> Hassan Schroeder wrote: >> > Steve Green wrote: >> > >> >> We do a lot of user testing with screen reader users,... >> >> >> > >> > >> >> Also Flash movies are made in layers. >> >> >> > >> > Have you tested any (non-timelined) Flex-based sites or apps? >> > >> > >> >> Just my two pence but I think what you really need to do is add an audio >> layer to that flash site. As an example one of the sites we host (its >> not at all accessible code-wise) has audio to say hello and indicate >> what you can do on a page. I think similar use of audio on that site to >> read it from the flash would be a nice touch. Then it'd be accessible to >> blind users who don't have a screenreader too (...they must exist) > > I see a lot of problems with that idea. For one thing, audio content > is a very heavy-handed way of working around the lack of a > screenreader, especially for those with dial-up. It's also incorrect > to assume that there are any blind people who can reach your website > but not have some tool for "reading" the screen, be that a > screenreader or braile display or w/e. Chances are if the user can > reach your site, then they must have something assisting them. Ha! - good point. I could say I was thinking of those who use zoom features but it'd be BS =P It's an interesting thing that a screen-reader or assistive device wouldn't take any extra audio source on a page into account, the methods for adding any audio are typically via css or flash aren't they? It'd be good if the screen reader manufacturers added some control over it when it does happen, seeing as it can have such a big impact on accessibility. > Finally, you are assuming that you can guess the best audio speed for > blind users. If you have ever seen a blind person using a > screenreader, you would know that many of them set the audio speed to > something much faster than the average person speaks. > An audio description of a page would be much slower than most blind > people > would have it read to them by a screenreader. > > Audio descriptions are good when used to make captchas more > accessible, but providing them for entire web pages just doesn't sound > like the best solution. Well I didn't mean the ENTIRE web page, an introduction perhaps. Point is I wasn't thinking, what I suggested was kinda like getting flash to do a crap job of being a screen-reader... anyway. Back on the topic of Mihael's website I think it's all been said, he's got his work cut out! Cheers, Rob ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ******************************************************************* ****************************************************************************************************** The above message has been scanned and meets the Insurance Commission of Western Australia's Email security requirements for inbound transmission. ****************************************************************************************************** ******************************************************************************************************************************** The above message has been scanned and meets the Insurance Commission of Western Australia's Email security policy requirements for outbound transmission. This email (facsimile) and any attachments may be confidential and privileged. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this email (facsimile) is strictly prohibited. If you have received this email (facsimile) in error please contact the Insurance Commission. Web: www.icwa.wa.gov.au Phone: +61 08 9264 3333 ********************************************************************************************************************************* ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
