Ted - the content between the iframe tags doesn't need to be hidden or
commented out; in browsers that support iframes, it's automatically replaced
by the content specified in the source attribute, otherwise it's shown.
Think of it a little bit like the noframes or noscript tags in old school
HTML, where people usually just put something like "Sorry, your browser
doesn't support iframes ...".

Cheers,
Kevin

On 21/9/04 10:26 AM, "Ted Drake" <[EMAIL PROTECTED]> wrote:

> Here's what I figured out.
> When you have a frame, you need to specify what the content is.  You could do
> this with a title tag or even better, distinct text in the body of the frame.
> for instance, you would say, this is the navigation frame.
> 
> I did both.  I put a title attribute on the iframe saying title="dynamic
> calendar" and in the body of the iframe I added
> <span class="hidden">Dynamic Calendar for form fields</span>.
> 
> This satisfied the requirements and we are now 508 compliant and wai level 1
> happy.
> 
> 
> \/   \/   \/    \/    \/    \/    \/    \/    \/   \/
> To satisfy level 2 I have a problem with a series of input fields.  For
> multiple travelers, we have 10 boxes for ages.  I have a label associated with
> the first age and then alt tags on the following inputs.  Should I wrap all
> ten inputs in the lable tag as I've seen elsewhere?  I'd rather not create a
> label for each ten boxes.   What do you think?
> 
> Ted
> 
> 
> -----Original Message-----
> From: Ted Drake 
> Sent: Monday, September 20, 2004 5:05 PM
> To: [EMAIL PROTECTED]
> Subject: [WSG] question about iframe accessibility
> 
> 
> We are using a popup calendar for forms on our site and it uses an iframe for
> the calendar.
> I'm getting this message from the developers toolbar 508 checker
> 
> Rule: 1.1.6 - All IFRAME elements are required to contain element content.
> 
>     * Failure - IFRAME Element at Line: 362, Column: 1
> 
> I'm not very familiar with iframes.  What do you think it is asking for?
> 
> Here's a reference page
> http://v4.csatravelprotection.com/csa/twelcome.do
> 
> and the appropriate code:
> <iframe width="132" height="142" name="gToday:contrast:agenda.js"
> id="gToday:contrast:agenda.js" src="../js/cal/ipopeng.htm" scrolling="no"
> frameborder="0" style="visibility:visible; z-index:999; position:absolute;
> left:-500px; top:0px;" >
> </iframe>
> 
> There is a javascript that populates this iframe.  Do you think the validation
> engine would be happy with a simple comment tag inside the iframe before the
> javascript populates it?  I'll try for the heck of it.  Any other ideas?
> 
> Ted
>    
> ******************************************************
> The discussion list for  http://webstandardsgroup.org/
> 
> Proud presenters of Web Essentials 04 http://we04.com/
>  Web standards, accessibility, inspiration, knowledge
> To be held in Sydney, September 30 and October 1, 2004
> 
>  See http://webstandardsgroup.org/mail/guidelines.cfm
>  for some hints on posting to the list & getting help
> ******************************************************
> 
> ******************************************************
> The discussion list for  http://webstandardsgroup.org/
> 
> Proud presenters of Web Essentials 04 http://we04.com/
>  Web standards, accessibility, inspiration, knowledge
> To be held in Sydney, September 30 and October 1, 2004
> 
>  See http://webstandardsgroup.org/mail/guidelines.cfm
>  for some hints on posting to the list & getting help
> ******************************************************
> 
> 



******************************************************
The discussion list for  http://webstandardsgroup.org/

Proud presenters of Web Essentials 04 http://we04.com/
 Web standards, accessibility, inspiration, knowledge
To be held in Sydney, September 30 and October 1, 2004

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list & getting help
******************************************************

Reply via email to