[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: DOCBOOK-APPS: Docbook xsl stylesheets and accessibilityrequirements?
Adam DiCarlo wrote:
> Personally I think accessability concerns should be part of what is
> produced by default by docbook-xsl (and dsssl). Depending on the
> scope of the changes needed, it could be setting that can be turned
> on.
>
> Someone just needs to work out what accessbaility problems the
> XSL/DSSSL has an file bugs on them.
>
I guess we could think of it as a two stage question: a) the machine or
processing level compliance and b) the user check level; this is the way
Bobby, for example, reports. Processing level compliance is pretty
mechanical and may be a reasonable thing to seek on behalf of the
stylesheets; user level, obviously, another question.
An example: my experience, which is limited at this point, is that the
html xsl stylesheets will produce valid, say 4.01 Strict, if the
xsl:output is properly set up and the <body> attributes are turned off.
This is simple and straightforward but, I think, requires a
customization template for body attributes; if I'm right, I guess this
could be parameterized? This is a single run, no post-processing
scenario; I think that should be a goal, rather than multi-stage scenarios.
On the other hand, for reasons that I don't yet understand, I'm finding
that the xhtml xsl stylesheets, particularly when a customization
template is introduced, insert non-valide xmlns attributes in the
customized output. But, I may be misssing something in my setup or
configuration. I bugged Daniel about this, but have had similar
experience with Instant Saxon.
Other accessibility targets, e.g. ALT and LONGDESC attribute values, are
supported by the stylesheets but depend on the author's setting
attribute values in DocBook instance. Call this, "user check".
I'm not sure about TITLE attribute values for images and links.
And then there are TABLEs for the purposes of layout. I don't think
there is anything in the stylesheets that requires table use. The only
parameter controlled table layout feature that comes off the top of my
head is variablelist/definitionlist, I think. I can stand corrected,
however.
TAB sequences and TAB key navigation strike me as "imponderable" at the
moment.
I suppose we are looking at setting a baseline? Maybe we should look at
the Level 1 WAI guidelines and see where we stand? Has anyone done any
tick mark work with the checklists in relation to DB/DBXSL? How do they
align with the 508? And, I'm not secure at all on the DSSSL side, I'm
afraid.
Regards. ...edN
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC