W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > July to September 2014

Re: Question about page title and @lang on pages within iframes

From: Mark Rogers <mark.rogers@powermapper.com>
Date: Sat, 20 Sep 2014 14:58:54 -0500
To: "w3c-wai-gl@w3.org" <w3c-wai-gl@w3.org>
Message-ID: <1F68EA0E0CBFBE44A9A64274E1AC01A122F096ECD3@DFW1MBX23.mex07a.mlsrvr.com>
>> However, the iframe itself can have a title (attribute), so I don't
>> think another title (element) in the iframe source page will help
>> particularly.
>>
>Agree - I have no idea how a title element in an iframe would ever get
>communicated to a user.

I think you do need titles on IFRAMEs because WindowEyes, JAWS 14 with FF, and VoiceOver on OSX read gibberish to varying degrees if you don't have a title.

The following browser / screen reader combinations do read out iframe title in browse mode:

JAWS 13 - 15 with Firefox
Window-Eyes 8.4 with IE11
VoiceOver on OSX 10.9

The following combinations don't read out iframe titles:
NVDA 2014.1 with IE11 and Firefox
JAWS 13-15 with IE11
VoiceOver on iOS when used with touch
SaToGo 3.4.96.0 with IE 11

For this code without a title:
<iframe src="1234.html" width="100" height="100"></iframe>

JAWS 14 with FF29 says: "Twelve thirty four frame. This is an, link, example hyperlink, in the target page. Twelve thirty four frame end."
WindowEyes 8.4 says "Untitled iframe. This is an, link, example hyperlink, in the target page. End frame."
VoiceOver on OSX says: "Frame zero" (the number read out is different for each frame, second frame is "Frame one" etc)


1)      The above examples are for reading/browse mode. There are no problems when tabbing through content, because different stuff is read out.

2)      VoiceOver on iOS doesn't have this problem when used with touch (it might have the problem when using a Bluetooth keyboard, but we haven't tested that yet)

3)      The JAWS problem only happens in JAWS 14 with Firefox, it doesn't happen in JAWS 14 with IE, and doesn't happen in JAWS 13 or 15.

4)      Tests were done with screen reader factory settings (JAWS in particular has lots of options that change how things are read out).


Best Regards
Mark

Mark Rogers - mark.rogers@powermapper.com<mailto:mark.rogers@powermapper.com>
PowerMapper Software Ltd - www.powermapper.com<http://www.powermapper.com>
Registered in Scotland No 362274 Quartermile 2 Edinburgh EH3 9GL
Received on Saturday, 20 September 2014 19:59:12 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 16 January 2018 15:34:16 UTC