Doug,
well it's certainly exciting news that you intend to contribute.
in the meantime it is possible to write documents that work in both asv
and mozSVG.
including one that demonstrates tool tips! which may mean using
scripting in this instance.
A large part of accessibility is ensuring
Jim,
that's preposterous, in terms of accessibility the SVG1.1 spec is
broken. The chair and others have indicated that there is much work to
be done. for instance ASV3.1 doesn't support standard keyboard
accessibility any more than mozSVG, or any other UA afaik.
Following standards only
that's preposterous, in terms of accessibility the SVG1.1 spec is
broken.
Certainly, but you keep bringing back specific discussions, about specific
things, to the general SVG accessibility as a whole is broken. We were
specifically discussing tooltips, nothing more.
In no case does the
As promised, here is the sample I cooked up to demonstrate referencing
metadata elements:
http://svg-whiz.com/samples.html#trefMetadata
Regards-
Doug
doug . schepers @ vectoreal.com
www.vectoreal.com ...for scalable solutions.
Doug Schepers wrote:
|
| Hi, Ravi-
|
| That's because
Jim Schepers,
the SMIL tooltips example code uses mouseover and mouseout, almost by
definition that can't be good accessibility because it is device
dependent. please see hixie's bug #273197 where mozSVG may be
supporting tab.
assuming users can tab to these graphics, which is by no means
Jim,
perhaps you can enlighten me, what is the 'required information' that a
blind user or a user who prefers not to use a mouse will get from this
SMIL document?
regards
Jonathan Chetwynd
http://www.peepo.co.uk It's easy to use
irc://freenode/accessibility
On 5 Dec 2004, at 18:22, Jim
Hi, Jonathan-
Jonathan Chetwynd wrote:
|
| in the meantime it is possible to write documents that work
| in both asv and mozSVG.
| including one that demonstrates tool tips! which may mean
| using scripting in this instance.
Er... You mean like the scripted tooltip example on the same page,
Jim and Schepers,
well I agree it is possible, and even likely that future UA will
provide at least an option to view metadata such as title and desc in a
specific area of the screen such as perhaps the status bar. However in
that case Doug's example is redundant.
If you read the bug report
Jonathan Chetwynd [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
If you read the bug report which I drew your attention to it mentions
UAG:
http://www.w3.org/TR/UAAG10/guidelines.html#gl-device-independence
specifically the first guideline makes it clear, that if you choose to
URL for Slashdot article:
http://tinyurl.com/658z9
Weather Data Available in XML
Posted by michael on Sunday December 05, @06:21PM
from the stormy-weather dept.
wombatmobile writes Wired reports the National Oceanic and
Atmospheric Administration this week began providing weather
data in
Jim,
I refer you to WCAG 1.0 and WCAG 2.0
http://www.w3.org/TR/WCAG20/#keyboard-operation
Guideline 2.1 Make all functionality operable via a keyboard or a
keyboard interface.
http://www.w3.org/TR/WCAG10/#gl-device-independence ?
9.2 Ensure that any element that has its own interface can be
Mike,
thanks for pointing this up, if anyone is considering making a realtime
SVG application:
http://www.nws.noaa.gov/forecasts/xml/SOAP_server/ndfdXML.htm
it uses .jpg for the weather icons, SVG ones might be available, just
ask :-)
It's a great pity this is continental USA only, UKmet
12 matches
Mail list logo
