RE: SVGAccessibilityWG: has-been-clicked or a:visited

That's not a problem. SVG can be used for many different purposes.

In any case, if you are only talking about different visual depictions of an
interface, or simple extensions to the funtionality or interface of a
widget, that's something that can be done easily with sXBL. You can separate
out the appearance, and even to a degree, the behavior, of a GUI widget from
the model of the widegt (see XForms).

What Jonathan is proposing is a model view of a GUI that pays attention to
accessibility, and I think it's a good idea; if it's done right, it'll be
compatible with a variety of implementations.

Regards-
Doug

David Woolley wrote:
| 
| 
| > there may be a need for another layer of language, for instance a 
| > standardised graphical user interface schema.
| > however perhaps you have ideas of your own to describe?
| 
| I think the problem here is that you see SVG as an 
| application platform on which to produce your idea of good 
| tools, but the reason that most commercial artists want to 
| use SVG is that it has the flexibility to produce interfaces 
| that are completely different from their competitors, for 
| branding purposes.  They may also think that their interfaces 
| are easier to use, but ability to transfer to a competitor's 
| interface is not something they consider desirable.
|

Received on Friday, 12 November 2004 14:04:45 UTC