Weird. Looking at the HTML it's all very clean and nice. It even
validates with no errors on the w3c checker here:
http://validator.w3.org/
Only thing a bit unusual was that its doctype declaration was XHTML
Strict which is a bit unusual. Most sites that do good web standards are
using XHTML Transitional which is a little more lax. They seem to have
gone a bit out of their way to make this thing compliant. Maybe VO has
issues with XHTML Strict pages?
CB
Jacob Schmude wrote:
HiGreg
Well, this is most interesting indeed. It appears at first glance that
the content area is invisible to Voiceover. This is true, up to a
point. However, if I tab a few times, bringing keyboard focus to one
of the links in the content area, voiceover is able to see everything
fine until I stop interacting with the html content area. This holds
true for both group navigation (my preference) and dom navigation. I
don't see anything that looks as if it would cause this in the page
source I can view, but given the external scripts and references, that
doesn't mean anything. This behavior does not appear confined to
Safari, as Omniweb exhibits the same issue and it also uses Webkit as
its underlying rendering engine. Opera, however, does not seem to have
the problem, and is not based on Webkit.
Just my observations
On Mar 14, 2008, at 7:52 PM, Greg Kearney wrote:
Go to the following URL: http://www.vic.gov.au/
For reasons that I am unable to determine the content area of the
site is not reachable with VoiceOver. Neither VO find nor Item
chooser will locate any thing in the content area. Navigation take
you to the header and footer but never to the content. Am I doing
something wrong or is it the site? And if it is the site what have
they done to make the content area invisible to VoiceOver?
Greg Kearney
535 S. Jackson St.
Casper, Wyoming 82601
307-224-4022
[EMAIL PROTECTED]
