RE: [WSG] Iframe navigation accessibility question
Thanks Steve, and John for your thoughts on this. I'll speak to the client and make the suggestion. James From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Green Sent: 21 November 2007 15:12 To: wsg@webstandardsgroup.org Subject: RE: [WSG] Iframe navigation accessibility question The accessibility issues relating to frames are often overstated, although they can cause difficulties with user agents that only support one window, such as Lynx. You can usually still use the site but it is not as convenient because you have to keep going back to the list of frames in order to access the navigation menus. We have done user testing on frame-based sites, and screen reader users had no problems. There's a bit more verbiage as the start and end of frames is announced, but the provision of frame titles can actually be helpful. The biggest problems with frame-based sites are more usability than accessibility issues e.g. bookmarking. Steve From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of James Leslie Sent: 21 November 2007 14:32 To: wsg@webstandardsgroup.org Subject: [WSG] Iframe navigation accessibility question Hi Folks, I have just inherited a bands website which places all of the navigation (both top and bottom links) in iframes. I don't 100% understand why the developer chose to do this unless it is emulating php includes in static html, anyway, it seems like a bad idea to me and is high on my list of things to sort out on the site. My question is: Is this as inaccessible as I fear it is? Will a screen reader be likely to have issues with it? I have to do a new version of the site around Easter next year when a new album comes out, I'm wondering whether I should spend the time fixing this version up in the meantime or whether it's issues are not as harmful as I fear. 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] ***
RE: [WSG] Iframe navigation accessibility question
The accessibility issues relating to frames are often overstated, although they can cause difficulties with user agents that only support one window, such as Lynx. You can usually still use the site but it is not as convenient because you have to keep going back to the list of frames in order to access the navigation menus. We have done user testing on frame-based sites, and screen reader users had no problems. There's a bit more verbiage as the start and end of frames is announced, but the provision of frame titles can actually be helpful. The biggest problems with frame-based sites are more usability than accessibility issues e.g. bookmarking. Steve _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of James Leslie Sent: 21 November 2007 14:32 To: wsg@webstandardsgroup.org Subject: [WSG] Iframe navigation accessibility question Hi Folks, I have just inherited a bands website which places all of the navigation (both top and bottom links) in iframes. I don't 100% understand why the developer chose to do this unless it is emulating php includes in static html, anyway, it seems like a bad idea to me and is high on my list of things to sort out on the site. My question is: Is this as inaccessible as I fear it is? Will a screen reader be likely to have issues with it? I have to do a new version of the site around Easter next year when a new album comes out, I'm wondering whether I should spend the time fixing this version up in the meantime or whether it's issues are not as harmful as I fear. 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] ***
Re: [WSG] Iframe navigation accessibility question
On 22/11/2007, at 1:31 AM, James Leslie wrote: Hi Folks, I have just inherited a bands website which places all of the navigation (both top and bottom links) in iframes. I don't 100% understand why the developer chose to do this unless it is emulating php includes in static html, anyway, it seems like a bad idea to me and is high on my list of things to sort out on the site. My question is: Is this as inaccessible as I fear it is? Yes, at least in my own (real world) testing. Will a screen reader be likely to have issues with it? Mine does, and my father-in-law's partner's does (older Jaws version). I have to do a new version of the site around Easter next year when a new album comes out, I'm wondering whether I should spend the time fixing this version up in the meantime or whether it's issues are not as harmful as I fear. I would fix it now, you can always mention it as a SEO problem if you need to provide a business case for it. kind regards, John Hancock Identity [EMAIL PROTECTED] t: +61 2 8012 0274 f: +61 2 9799 6135 *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
