docbook-tc — archive

[Robert Stayton]

Hi Scott, I read through it all, and it seems the proposal is coming down to these changes: 1. Add @rowheader to the colspec element, with possible values 'yes' or 'no'. There is no default value, but absence of the attribute implies 'no'. 2. Add @ headers to entry, with allowed content being id values from within the table. Is that right? If these additions are sufficient to meet the accessibility requirements, then they seem fine to me. We would need to clarify how certain cases are to be handled. I can think of two: a. If a table has rowheader="firstcol" and the colspec for column1 in that table has an explicit rowheader="no", I presume the colspec has precedence? b. If an entry in a given row spans multiple columns, I presume the first column in the span determines whether the entry is a rowheader? Bob Stayton Sagehill Enterprises bobs@sagehill.net