W3C home > Mailing lists > Public > public-svg-wg@w3.org > July to September 2008

Re: Agenda Request: SVG WG Review of XHTML Access Module

From: Doug Schepers <schepers@w3.org>
Date: Sat, 05 Jul 2008 04:51:54 -0700
Message-ID: <486F605A.6080909@w3.org>
To: Doug Schepers <schepers@w3.org>
Cc: W3C SVG Public Working Group <public-svg-wg@w3.org>

Hi, SVG-

And another thing...

Doug Schepers wrote (on 7/5/08 4:43 AM):
> 
> * "Finally, XHTML Access requires the availability of the XHTML Role 
> Attribute Module ... and of the Core Attribute Collection as defined in 
> XHTML Modularization."  This is a problem, since the Core Attribute 
> Collection [2] lists:
>  xml:space ("default"* | "preserve"), class (NMTOKENS), id (ID), title 
> (CDATA)
> 
> SVG doesn't have a 'title' attribute, and in fact, that is a less 
> accessible option than what SVG does have, which is the <title> element.

The Access spec doesn't provide any means for the author to provide a 
title for the 'access' element itself, other than the implicit 'title' 
attribute in XHTML modularization itself.  SVG should be allowed to 
provide a child title, desc, and tip element.  Dunno if that would 
conflict with the DTD/Schema they provide, but if so, it should be relaxed.

I would go so far as to say that the 'access' element should explicitly 
allow child content elements, and that the host language should be able 
to specify their nature.  It would be even better if title and desc were 
part of the model.

Being able to give an explicit explanation of the use of the element 
would be very important for accessibility, I think.

Regards-
-Doug Schepers
W3C Team Contact, WebApps, SVG, and CDF
Received on Saturday, 5 July 2008 11:52:30 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:20:09 UTC