DOCBOOK-APPS: Re: Docbook xsl stylesheets and accessibilityrequirements?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 / Billard, Trish [EMAIL PROTECTED] was heard to say: [...] | Is there any documentation out there about how these transformations | meet or don't meet these requirements? I'll need to create | configurations or customizations to ensure the requriements are met. I'm not aware of any comprehensive studies, but I've tried to make sure the transformations are accessible. If you find cases where they aren't, I'll make sure it gets fixed promptly. Be seeing you, norm - -- Norman Walsh [EMAIL PROTECTED] | Science is like sex: sometimes http://www.oasis-open.org/docbook/ | something useful comes out, but Chair, DocBook Technical Committee | that is not the reason we are | doing it.--Richard Feynman -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.7 http://mailcrypt.sourceforge.net/ iD8DBQE+UVzdOyltUcwYWjsRArsVAJ9EWFEIFWQ8m/OPchXwsbjs14j8AgCfZGGV Aysi+1DUwMiQsPd99sBoTmA= =qhkd -END PGP SIGNATURE-
DOCBOOK-APPS: Re: Docbook xsl stylesheets and accessibilityrequirements?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 / [EMAIL PROTECTED] was heard to say: | A general question for folks. If one is stylesheet agnostic, would DSSSL or | XSL be a better choice for a start toward producing XHTML Strict? I was a | LISP hacker in a previous life, and so find DSSSL appealing. Sigh. The easiest way to get XHTML strict out of the stylesheets is almost certainly to run tidy. I appreciate that people would like to be able to get strict output from the stylesheets for arbitrary DocBook, but it would be very, very hard. However, if you exercise some control in your DocBook sources, it should be fairly easy to get strict XHTML. If you find otherwise, I'd be interested in seeing the examples. Be seeing you, norm - -- Norman Walsh [EMAIL PROTECTED] | They that can give up essential http://www.oasis-open.org/docbook/ | liberty to obtain a little Chair, DocBook Technical Committee | temporary safety deserve neither | liberty nor safety.--Benjamin | Franklink -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.7 http://mailcrypt.sourceforge.net/ iD8DBQE+UV2QOyltUcwYWjsRAgokAJ4kFCwdiAAChXer0QgGO7t5unrfnwCdHALj fuBy3cr/4MlxlZCfU8Hnqo4= =03Me -END PGP SIGNATURE-
DOCBOOK-APPS: Re: Docbook xsl stylesheets and accessibilityrequirements?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 / Billard, Trish [EMAIL PROTECTED] was heard to say: | Wow, this started quite the thread. | But what I was really looking for is for the HTML (rather than the XHTML), what |things to meet accessibility requirements do Norm's stylesheets already provide? |Examples might be always supporting putting an alt attribute for all images, allowing |resizing of point sizes. That sort of thing. DocBook meets those requirements, I believe. Last time I reviewed the W3C XML Accessibility Guidelines, I thought DocBook passed. Dave Pawson might know better than I. Be seeing you, norm - -- Norman Walsh [EMAIL PROTECTED] | There are only 10 types of people http://www.oasis-open.org/docbook/ | in this world: those who Chair, DocBook Technical Committee | understand binary and those who | don't. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.7 http://mailcrypt.sourceforge.net/ iD8DBQE+UV3lOyltUcwYWjsRAvtgAJ978XeWNHYsHXAuk8m/kMvNTene1gCbBiIb LsOFGrZjq/qLzlZRHC6xGjI= =MQXV -END PGP SIGNATURE-
