thanks for that Stuart.

We have already implemented frame titles, we were actually referring to the 
page titles (found within the HEAD) of the html that makes up the page within 
the frame.  If these were left blank would it cause a problem???

Frame:
<frame src="page.html" name="BodyContent" id="BodyContent" title="Main Content" 
longdesc="frameset-desc.html#BodyContent" noresize="noresize" />
 
page.html:
<HEAD>
    <TITLE>???</TITLE>
</HEAD>

Cheers,

Anat

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Stuart Foulstone
Sent: Wednesday, 2 April 2008 8:43 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Frames and title relevance to screen readers....


Hi,

You might find the following link useful:

See http://www.webaim.org/techniques/frames/

Stuart

On Wed, April 2, 2008 1:13 am, Anat Katz wrote:
>
> Hi team,
>
> Just a general question - is there any value from a screen reader point of
> view, to have a specific title to the actual pages that were build /called
> by the frameset.
> Is there any value for screen reader's users?
> I.e.: the page that contains the main content, should have a specific
> /relevant page title? Do screen readers read the page title of each one of
> the pages of the frameset? Or do they only read the one frameset page
> title?
> Example: "Recipes" page title as opposed to "main content" page title.
> (please note I am not referring to the titles of the frames in the
> frameset, see example below)
> <frame src="page.html" name="BodyContent" id="BodyContent" title="Main
> Content" longdesc="frameset-desc.html#BodyContent" noresize="noresize" />
>
> Cheers,
> Anat
>
>
> This email and any attachments may contain privileged and confidential
> information and are intended for the named addressee only. If you have
> received this e-mail in error, please notify the sender and delete this
> e-mail immediately. Any confidentiality, privilege or copyright is not
> waived or lost because this e-mail has been sent to you in error. It is
> your responsibility to check this e-mail and any attachments for viruses.
> No warranty is made that this material is free from computer virus or any
> other defect or error.  Any loss/damage incurred by using this material is
> not the sender's responsibility.  The sender's entire liability will be
> limited to resupplying the material.
>
> *******************************************************************
> 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]
*******************************************************************


This email and any attachments may contain privileged and confidential 
information and are intended for the named addressee only. If you have received 
this e-mail in error, please notify the sender and delete this e-mail 
immediately. Any confidentiality, privilege or copyright is not waived or lost 
because this e-mail has been sent to you in error. It is your responsibility to 
check this e-mail and any attachments for viruses.  No warranty is made that 
this material is free from computer virus or any other defect or error.  Any 
loss/damage incurred by using this material is not the sender's responsibility. 
 The sender's entire liability will be limited to resupplying the material.


*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************

Reply via email to