MHonArc v2.5.0b2 -->
office message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Question on table headers
A received a question from Rich on the
Accessibility SC, but I didn't have a good answer for him. Table
headers -- the grammar we specify now is:<define name="table-rows-no-group"> <choice>
<group>
<ref
name="table-rows"/>
<optional>
<ref name="table-table-header-rows"/>
<optional>
<ref
name="table-rows"/>
</optional>
</optional>
</group>
<group>
<ref
name="table-table-header-rows"/>
<optional>
<ref name="table-rows"/>
</optional>
</group> </choice></define>The first group in the choice seems
to allow table rows, followed by an optional table header, followed by
optionally more table rows. Does anyone know what that is allowed?
Are there any implementations that allow you to define a table header
in the middle of a table? What am I missing? We're trying to
figure out 1) how this would be rendered if it is allowed, especially when
it flows onto a second page and you repeat the headers, and 2) how to expose
this for accessibility. Certainly it would be unkind to start reading
the table rows and then start reading the headers only later.The more typical option is the 2nd group
in the choice, where the table header comes first, optionally followed
by more table rows. Column headers are parallel to this and allow
the same two options.-Rob
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]