OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-tc message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: Table accessibility, summary and HTML5

Hi Jirka,

I agree with your assessment. We also have the alt element that should be used for a table summary (http://www.docbook.org/tdg51/en/html/alt.html).

We could probably remove the section about table caption from the Publishers v1.1 and from DocBook v5.1 specs and provide the documentation for use of alt for table summary. The other items in the Table Accessibility are still needed (scope, rowheader, headers).

Thanks and best regards,

Scott Hudson   |   PELCO  by Schneider Electric   |   United States  |   Standards Lead 
 +1 970 282 1952  |  Mobile: +1 720 369 2433 
 | Email: scott.hudson@schneider-electric.com

On Jul 12, 2013, at 6:10 AM, Jirka Kosek <jirka@kosek.cz> wrote:

On 21.6.2013 17:50, Scott Hudson wrote:

I did find this:

which suggests using <table><caption><details><summary/>...

If we did that, it would mean adding a details and summary element to
CALS? I'm not sure that's a good way to go. We could just add an
@summary, and then rely on the output processors/transforms to take
the @summary and populate it appropriately?

I think that we shouldn't use attribute like @summary. The reason is
that content in attribute is hard to localize (you can't change
directionality here) and you can't use embeded markup.

I think that actually there is no need to invent any new markup. DocBook
5 offers annotations (http://docbook.org/tdg51/en/html/annotation.html)
and we can use just them:

<annotation xml:id="summary">
<para>In the following table, characteristics are
given in the second column, with the negative side in the left column
and the positive
side in the right column.</para>

<table annotations="summary">

With such approach there is no need to invent new accessibility markup
for DocBook, solution will work for both HTML and CALS tables. Moreover
summary can be longer, use markup, links, ...

I think that just documenting this approach in TDG should be sufficient,
or have I missed something?

Have a nice weekend,


 Jirka Kosek      e-mail: jirka@kosek.cz      http://xmlguru.cz
      Professional XML consulting and training services
 DocBook customization, custom XSLT/XSL-FO document processing
OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep.
   Bringing you XML Prague conference    http://xmlprague.cz

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]