- From: Pete Brunet <brunet@us.ibm.com>
- To: Robert Weir <robert_weir@us.ibm.com>
- Date: Wed, 20 Sep 2006 21:19:19 -0600
Rob, Attached is the update Hiro and I worked on to be submitted as a comment to the ODF 1.1 proposal.
Some history from the earlier parts of this thread...
From Rob Weir on 9/6:
Rich, has this change already been discussed & agreed on by the Accessibility Subcommittee?
If so, I'm fine with it. Since the changes are more extensive than a word or two, it is probably good if Pete can download the posted ODF 1.1 draft and apply the changes there. I can then propose it to the TC for inclusion.
Since ODF 1.1 is already out for public comment, we're somewhat limited in what kind of changes we can make. Additional explanatory text is fine, as well as errata. But we should not be introducing new markup or changing the defined behavior of existing markup.
From Hiro Takagi-san on 9/6:
We raised the issue to the SC two weeks ago, and submitted proposal last week.
http://lists.oasis-open.org/archives/office-accessibility/200608/msg00048.html
Our current recommendation is to classify the "is-subtable" attribute as a deprecated attribute in the ODF 1.2 timeline
Pete Brunet
IBM Accessibility Architecture and Development
11501 Burnet Road, MS 9022E004, Austin, TX 78758
Voice: (512) 838-4594, TL 678-4594, Fax: (512) 838-9666
Ionosphere: WS4G
| Hironobu Takagi/Japan/IBM@IBMJP
09/17/2006 01:56 AM |
|
Pete,
I am sorry for my slow response. My changes are indicated as red.
Thank you for the description about navigation issue.
I thought the description can be discussed in the contenxt of non-visual table navigation,
but I agree your explanation in the cell addresing contenxt is easy to understand for office developers.
I modified some wording, so please confirm them.
- It is recommend for standard authors to follow the RFC2119 in terms of usage of "must/should/may." (http://rfc.net/rfc2119.html)
So, I changed some "must" to "should." Are they appropriate? Please confirm these changes.
- In the ODF 1.1 spec, the term "office applications" is consistently used to indicate ODF editors.
- The term "cell addressing" is used to indicate cell numbering, and I could not find the term "cell number" in the spec.
If you have any question, please let me know.
Thank you.
Best Reagrds.
Hiro
---------------------
Hironobu Takagi, PhD.
User Experience and Accessibility Technology
Tokyo Research Laboratory
+81-46-215-4557
E-mail: takagih@jp.ibm.com
|
Hiro, The ODF 1.1 review period ends this week so I'd like to get this in to the system.
Pete Brunet
IBM Accessibility Architecture and Development
11501 Burnet Road, MS 9022E004, Austin, TX 78758
Voice: (512) 838-4594, TL 678-4594, Fax: (512) 838-9666
Ionosphere: WS4G
----- Forwarded by Pete Brunet/Austin/IBM on 09/16/2006 07:57 PM -----
| Pete Brunet/Austin/IBM
09/14/2006 02:04 AM |
|
Hiro, I took another shot at the paragraph. Please review.
In the OpenDocument schema, this
a subtable
can be represented in either of the ways as detailed in Sample 1 using
spans and Sample 2 using
table:is-subtable. The
semantics conveyed by cell addresses
are especially important to those who are using assistive technology such
as a person who is blind. Blind users cannot see the entire table.
Screen Readers (assistive
technologies for the blind)
only provide information about the cell which currently has focus. An
important piece of structural information is the cell name, e.g. A1, B2,
etc. The use of table:is-subtable results in a modified addressing
scheme and that addressing
scheme conveys important structural information to a blind user. For
example, in sample 2 there is a B2 (.B2.B1) under an C1. This will
be disorienting if table:is-subtable is used inappropriately. An
office
application should
allow the author to choose between spans or table:is-subtable as appropriate
to the document being authored. If it is important to maintain the
semantics conveyed by the subtable cell addressing
scheme so that it is clear that certain cells belong to a subtable then
an author would use table:is-subtable as shown in sample 2. If the
subtable cell addressing
scheme would be misleading, especially for a person using assistive technology,
then the author would use table:number-rows-spanned and table:number-rows-spanned
as shown in sample 1.
An example of why an office
application
should
not solely use table:is-subtable without author control is a table with
row and column headers. In sample 2, if the gray cells, i.e. cells
A1, B1, C1, and A2 are the row and column headers of the remaining cells,
then table:is-subtable should
not be used because its cell addressing
scheme is disjoint from the addressing
scheme of the row and column headers and the semantic relationship is broken.
For example, cell C1 should be the header of cell C2 as in sample
1, not the header of a B2 cell as in sample 2.
Pete Brunet
IBM Accessibility Architecture and Development
11501 Burnet Road, MS 9022E004, Austin, TX 78758
Voice: (512) 838-4594, TL 678-4594, Fax: (512) 838-9666
Ionosphere: WS4G
| Hironobu Takagi/Japan/IBM@IBMJP
09/07/2006 09:02 AM |
|
Pete,
I would like to recommend to include one description in the ODF 1.1 spec.
I inserted it in the attached mail and marked it in red.
Could review it and include it in your modified ODF 1.1 spec?
Talk to you later in the SC call.
Best Regards,
Hiro
--------------------
Hironobu Takagi, PhD.
User Experience and Accessibility Technology
Tokyo Research Laboratory
+81-46-215-4557
E-mail: takagih@jp.ibm.com
|
Rob,
We raised the issue to the SC two weeks ago, and submitted proposal last week.
http://lists.oasis-open.org/archives/office-accessibility/200608/msg00048.html
Our current recommendation is to classify the "is-subtable" attribute as a deprecated attribute in the ODF 1.2 timeline
Pete,
I am sorry for my slow response. I am still thinking the way to describe the navigation issue in the main spec, since navigation issue is difficult to describe in short sentences as you know...
It might be appropriate to describe the address issue only in the main spec and to describe navigation issue in the accessibility guideline.
I will decide before the tomorrow's SC call.
Best Regards,
Hiro
---------------------
Hironobu Takagi, PhD.
User Experience and Accessibility Technology
Tokyo Research Laboratory
+81-46-215-4557
E-mail: takagih@jp.ibm.com
|
Rich, has this change already been discussed & agreed on by the Accessibility Subcommittee?
If so, I'm fine with it. Since the changes are more extensive than a word or two, it is probably good if Pete can download the posted ODF 1.1 draft and apply the changes there. I can then propose it to the TC for inclusion.
Since ODF 1.1 is already out for public comment, we're somewhat limited in what kind of changes we can make. Additional explanatory text is fine, as well as errata. But we should not be introducing new markup or changing the defined behavior of existing markup.
Regards,
-Rob
___________________________
Rob Weir
Software Architect
Workplace, Portal and Collaboration Software
IBM Software Group
email: robert_weir@us.ibm.com
phone: 1-978-399-7122
blog: http://www.robweir.com/blog/
| Pete Brunet/Austin/IBM@IBMUS
09/01/2006 06:03 PM |
|
Hiro, Please review the following to verify my thinking. You may also want to update my proposed text if you think more needs to be said about use cases that need to use spanning instead of table:is-subtable.
I think 8.2.6 (Subtables) of the proposed ODF 1.1 spec is misleading. There are two samples; sample 1 uses spans; sample 2 uses table:is-subtable.
The use of spans does not result in something that has subtable style cell numbers, i.e. Sample 1 would have cell numbers as follows:
|
A1
|
B1
|
C1
| |
| A2 | B2 | C2 | |
| B3 | |||
The ODF 1.1 spec should be adjusted to included an additional image, the above image, and it should be placed just before the sample 1 (spanning) code and the example that is now above sample 1 should be moved to just above the sample 2 (is-subtable) code.
I marked up the following (including the code in the first sample) to show a proposed change to section 8.2.6.
8.2.6 Subtables
If a table cell only contains a single table but no paragraphs or other content, this table can be specified as subtable. It then occupies the whole cell and no other content can appear in this cell.
The borders of a subtable merge with the borders of the cell that it resides in. A subtable does not contain any formatting properties. A subtable is essentially a container for some additional table rows that integrate seamlessly with the parent table.
A nested table is turned into a subtable with the attribute table:is-subtable that is attached to the table element. A nested table that is not a specified to be a subtable appears as a table within a table, that is, it has borders distinct from those of the parent cell and respects the padding of the parent cell.
<define name="table-table-attlist"
combine="interleave">
<optional>
<attribute name="table:is-sub-table"
a:defaultValue="false">
<ref name="boolean"/>
</attribute>
</optional>
</define>
Example of Representation of subtable
In the OpenDocument schema, this
a subtable
can be represented in either of the ways as detailed in Sample 1 using
spans and Sample 2 using
table:is-subtable. The
semantics conveyed by cell numbers are especially important to those who
are using assistive technology such as a person who is blind because the
cell numbering provides information about the table structure, information
which cannot be obtained through sight. If it is important to maintain
the semantics conveyed by the cell numbering so that it is clear that certain
cells belong to a subtable then use table:is-subtable as shown in sample
2. If the subtable cell numbering would be misleading, especially
for a person using assitive technology, then use table:number-rows-spanned
and table:number-rows-spanned as shown in sample 1.
In addition each cell should be associated with a row-header and a column-header
to covey sufficient semantics. If a use of table:is-subtable breaks association
between a cell and headers, then use table:number-rows-spanned and table:number-rows-spanned
as shown in sample 1.
|
A1
|
B1
|
C1
| |
| A2 | B2 | C2 | |
| B3 | |||
Sample 1
Using cells that span several rows, the table is specified as follows:
<style:style style:name="Table
1" style:family="table">
<style:table-properties style:width="12cm"
fo:background-color="light-grey"/>
</style:style>
<style:style style:name="Col1"
style:family="table-column">
<style:table-column-properties style:column-width="2cm"/>
</style:style>
<style:style style:name="Col2"
style:family="table-column">
<style:table-column-properties style:column-width="4cm"/>
</style:style>
<style:style style:name="Col3"
style:family="table-column">
<style:table-column-properties style:column-width="6cm"/>
</style:style>
<style:style style:name="Row1"
style:family="table-row">
<style:table-row-properties fo:background-color="grey"/>
</style:style>
<style:style style:name="Cell1"
style:family="table-cell">
<style:table-cell-properties fo:background-color="grey"/>
</style:style>
<table:table table:name="Table
1" table:style-name="Table 1">
<table:table-columns>
<table:table-column table:style-name="Col1"/>
<table:table-column table:style-name="Col2"/>
<table:table-column table:style-name="Col3"/>
</table:table-columns>
<table:table-header-rows>
<table:table-row table:style-name="Row1">
<table:table-cell>
<text:p text:style="Table Caption">
A1
</text:p>
</table:table-cell>
<table:table-cell>
<text:p text:style="Table Caption">
B1
</text:p>
</table:table-cell>
<table:table-cell>
<text:p text:style="Table Caption">
C1
</text:p>
</table:table-cell>
</table:table-row>
</table:table-header-rows>
<table:table-rows>
<table:table-row>
<table:table-cell table:number-rows-spanned="2"
table:style-name="Cell1">
<text:p text:style="Table Body">
A2
</text:p>
</table:table-cell>
<table:table-cell>
<text:p text:style="Table Body">
.B2.A1
B2
</text:p>
</table:table-cell>
<table:table-cell>
<text:p text:style="Table Body">
.B2.B1
C2
</text:p>
</table:table-cell>
</table:table-row>
<table:table-row>
<table:covered-table-cell/>
<table:table-cell table:number-columns-spanned="2">
<text:p text:style="Table Body">
.B2.A2
B3
</text:p>
</table:table-cell>
<table:covered-table-cell/>
</table:table-row>
</table:table-rows>
</table:table>
|
A1
|
B1
|
C1
| |
| A2 | .B2.A1 | .B2.B1 | |
| .B2.A2 | |||
Sample 2
Using sub tables, the table is specified as follows:
<style:style style:name="Table
1" style:family="table">
<style:table-properties fo:width="12cm"
fo:background-color="light-grey"/>
</style:style>
<style:style style:name="Col1"
style:family="table-column">
<style:table-column-properties style:column-width="2cm"/>
</style:style>
<style:style style:name="Col2"
style:family="table-column">
<style:table-column-properties style:column-width="4cm"/>
</style:style>
<style:style style:name="Col3"
style:family="table-column">
<style:table-column-properties style:column-width="6cm"/>
</style:style>
<style:style style:name="Row1"
style:family="table-row">
<style:table-row-properties fo:background-color="grey"/>
</style:style>
<style:style style:name="Cell1"
style:family="table-cell">
<style:table-cell-properties fo:background-color="grey"/>
</style:style>
<table:table table:name="Table
1" table:style-name="Table 1">
<table:table-columns>
<table:table-column table:style-name="Col1"/>
<table:table-column table:style-name="Col2"/>
<table:table-column table:style-name="Col3"/>
</table:table-columns>
<table:table-header-rows>
<table:table-row table:style-name="Row1">
<table:table-cell>
<text:p text:style="Table Caption">
A1
</text:p>
</table:table.cell>
<table:table-cell>
<text:p text:style="Table Caption">
B1
</text:p>
</table:table-cell>
<table:table-cell>
<text:p text:style="Table Caption">
C1
</text:p>
</table:table-cell>
</table:table-row>
</table:table-header-rows>
<table:table-rows>
<table:table-row>
<table:table-cell table:style-name="Cell1">
<text:p text:style="Table Body">
A2
</text:p>
</table:table-cell>
<table:table-cell table:number-columns-spanned="2">
<table:table is-subtable="true">
<table:table-columns>
<table:table-column table:style-name="Col2"/>
<table:table-column table:style-name="Col3"/>
</table:table-columns>
<table:rows>
<table:row>
<table:table-cell>
<text:p text:style="Table Body">
.B2.A1
</text:p>
</table:table-cell>
<table:table-cell>
<text:p text:style="Table Body">
.B2.B1
</text:p>
</table:table-cell>
</table:table-row>
<table:table-row>
<table:table-cell
table:number-columns-spanned="2">
<text:p text:style="Table Body">
.B2.A2
</text:p>
</table:table-cell>
<table:covered-table-cell/>
</table:table-row>
</table:table-rows>
</table:table>
</table:table-cell>
<table:covered-table-cell/>
</table:table-row>
</table:table-rows>
</table:table>
Pete Brunet
IBM Accessibility Architecture and Development
11501 Burnet Road, MS 9022E004, Austin, TX 78758
Voice: (512) 838-4594, TL 678-4594, Fax: (512) 838-9666
Ionosphere: WS4G