E-mail List Archives
Thread: Word documents and tables
Number of posts in this thread: 12 (In chronological order)
From: Jeremy Merritt
Date: Tue, Oct 26 2010 7:57AM
Subject: Word documents and tables
No previous message | Next message →
Hi all,
In the WebAIM article on creating Word documents:
http://webaim.org/techniques/word/
It mentions two key points:
1. There is no way to assign table headers or <th> elements to a table created in Word.
2. There is no way to add row headers (headers across the side of a table) in Word.
The article suggests that the user mark that Word "Repeat as header row at the top of each page." But there is no fix for row headers.
So, are one-dimensional tables OK in Word, but if a document contains a 2-dimensional table (or a more complex table) that contains row headers, is the suggestion to only provide that document in PDF/HTML format with the tables properly tagged? Does WebAIM have an "official" suggestion on this?
Thanks,
Jeremy
From: Cliff Tyllick
Date: Tue, Oct 26 2010 9:18AM
Subject: Re: Word documents and tables
← Previous message | Next message →
Jeremy, I don't know about WebAIM's official position, but I do know the experience our authors have had with Word and tables. I first learned this approach from another participant (whose name I didn't catch) in a class at Knowbility's John Slatin Access U in May.
You can designate column and row headings in Word documents, and JAWS (and, I assume, other screen readers) will pick it up. But nowhere in Word's documentation have I found this procedure. Here's how you do it:
To make it possible for screen readers to recognize the headings in your table, add a bookmark to the first cell of each table:
- If the first row contains column headings *and* the first column contains row headings, name the bookmark "Title#," where "#" is the number of the table.
- If the first row contains column headings but the rest of the first column is data, not row headings, name the bookmark "ColumnTitle#," where # is the number of the table. (A decision table might be formatted this way.)
- If the first column contains row headings but the rest of the first row is data, not column headings, name the bookmark "RowTitle#," where # is the number of the table.
When JAWS encounters such a table, it will, at the appropriate verbosity setting, behave just like it does in a properly tagged table in an html or PDF document. For example, if the bookmark is a "Title" bookmark:
- If you move the cursor directly into a data cell, you will hear JAWS announce the column heading and then the row heading, followed in a different tone of voice by the contents of that cell.
- Move the cursor to the next row (same column), and JAWS will announce the new row heading and, in the different tone of voice, the contents of that cell.
- Move the cursor to the next column (same row), and JAWS will announce the new column heading and, in the different tone of voice, the contents of that cell.
All the "Repeat as header row" does is display (to people who can see) the header row on each new page when the table extends across more than one page. It does not affect what JAWS announces -- at least, it hasn't in any demonstration that I have witnessed. But, of course, redisplaying the header row is important for cognitive accessibility, even for people whose only "impairment" is a moment's distraction as they flipped the page.
I do know that it is possible to make Word accept multiple rows as the header row to be repeated across each page, but in my limited success with this I have also noticed that it makes the document in question much less stable. Save early, save often, and make backup copies if you do this. I don't have ready access to JAWS and have not tested whether the bookmark method will work with complex header rows or columns.
Oh, and one other thing: Although JAWS does interpret these bookmarks to mean that header cells are present, Acrobat 9 does not. In other words, when you convert the document to PDF, you will have to go in and tag the table's header columns and rows just as you always have. We don't have Acrobat X yet; maybe Andrew Kirkpatrick can let us know whether it will detect this device.
Finally, when a table is extensive, even if it isn't complex, I think it's good practice in any document that could end up in print to add a note that displays the url of the table in html. You don't have to be blind to appreciate having the ability to navigate a large or complex table in a browser.
Cliff
Cliff Tyllick
Usability assessment coordinator
Agency Communications Division
Texas Commission on Environmental Quality
512-239-4516
= EMAIL ADDRESS REMOVED =
>>> On 10/26/2010 at 8:54 AM, in message < = EMAIL ADDRESS REMOVED = >, Jeremy Merritt < = EMAIL ADDRESS REMOVED = > wrote:
Hi all,
In the WebAIM article on creating Word documents:
http://webaim.org/techniques/word/
It mentions two key points:
1. There is no way to assign table headers or <th> elements to a table created in Word.
2. There is no way to add row headers (headers across the side of a table) in Word.
The article suggests that the user mark that Word "Repeat as header row at the top of each page." But there is no fix for row headers.
So, are one-dimensional tables OK in Word, but if a document contains a 2-dimensional table (or a more complex table) that contains row headers, is the suggestion to only provide that document in PDF/HTML format with the tables properly tagged? Does WebAIM have an "official" suggestion on this?
Thanks,
Jeremy
From: Christophe Strobbe
Date: Tue, Oct 26 2010 11:03AM
Subject: Re: Word documents and tables
← Previous message | Next message →
Hi Cliff,
At 16:55 26/10/2010, Cliff Tyllick wrote:
>(...)
>You can designate column and row headings in Word documents, and
>JAWS (and, I assume, other screen readers) will pick it up. But
>nowhere in Word's documentation have I found this procedure. Here's
>how you do it:
>
>To make it possible for screen readers to recognize the headings in
>your table, add a bookmark to the first cell of each table:
>- If the first row contains column headings *and* the first column
>contains row headings, name the bookmark "Title#," where "#" is the
>number of the table.
>- If the first row contains column headings but the rest of the
>first column is data, not row headings, name the bookmark
>"ColumnTitle#," where # is the number of the table. (A decision
>table might be formatted this way.)
>- If the first column contains row headings but the rest of the
>first row is data, not column headings, name the bookmark
>"RowTitle#," where # is the number of the table.
I once used a similar bookmark technique, but with a bookmark in
every column header cell and every row header cell. I can't remember
where that advice came from, and maybe that is a good thing because
it did not work. A blind trainee who used the document complained
that the tables were still not accessible. However, transferring
those tables to Microsoft Excel turned out to be much better, even
though the tables contain a header row with merged cells. (I am
referring to the tables in Clause 7 of CEN/CENELEC Guide 6:
<ftp://ftp.cen.eu/BOSS/Reference_Documents/Guides/CEN_CLC/CEN_CLC_6.pdf>;.
Guide 6 contains "Guidelines for standards developers to address the
needs of older persons and persons with disabilities" but is not accessible...)
>
>When JAWS encounters such a table, it will, at the appropriate
>verbosity setting, behave just like it does in a properly tagged
>table in an html or PDF document. For example, if the bookmark is a
>"Title" bookmark:
>- If you move the cursor directly into a data cell, you will hear
>JAWS announce the column heading and then the row heading, followed
>in a different tone of voice by the contents of that cell.
>- Move the cursor to the next row (same column), and JAWS will
>announce the new row heading and, in the different tone of voice,
>the contents of that cell.
>- Move the cursor to the next column (same row), and JAWS will
>announce the new column heading and, in the different tone of voice,
>the contents of that cell.
>All the "Repeat as header row" does is display (to people who can
>see) the header row on each new page when the table extends across
>more than one page. It does not affect what JAWS announces -- at
>least, it hasn't in any demonstration that I have witnessed. But, of
>course, redisplaying the header row is important for cognitive
>accessibility, even for people whose only "impairment" is a moment's
>distraction as they flipped the page.
>(...)
Best regards,
Christophe
--
Christophe Strobbe
K.U.Leuven - Dept. of Electrical Engineering - SCD
Research Group on Document Architectures
Kasteelpark Arenberg 10 bus 2442
B-3001 Leuven-Heverlee
BELGIUM
tel: +32 16 32 85 51
http://www.docarch.be/
Twitter: @RabelaisA11y
---
"Better products and services through end-user empowerment"
www.usem-net.eu - www.stand4all.eu
---
Please don't invite me to Facebook, Quechup or other "social
networks". You may have agreed to their "privacy policy", but I haven't.
From: Cliff Tyllick
Date: Tue, Oct 26 2010 12:06PM
Subject: Re: Word documents and tables
← Previous message | Next message →
Hi, Chris.
When this was mentioned at Access U, we were in a class on how to make
Word documents accessible. We tested it immediately with Word 2007 or
2010 and, I believe, JAWS 11. The instructor added the bookmark, turned
JAWS on, and clicked into a cell in the middle of the table. The whole
class cheered on hearing JAWS read the two headings and then the cell
data.
I really do like your sample document. I scrolled until I saw a table
and found this:
"Table 1 * Factors to consider in clauses on information
The best designed products or services avoid the need for any
explanatory information, signalling the way they should be used by form
and appearance."
And, below this introduction, Table 1 has column headings, row
headings, and empty cells. Some of the cells are shaded gray; others are
white.
No explanatory information needed there, eh?
Cliff
Cliff Tyllick
Usability assessment coordinator
Agency Communications Division
Texas Commission on Environmental Quality
512-239-4516
= EMAIL ADDRESS REMOVED =
>>> On 10/26/2010 at 12:02 PM, in message
< = EMAIL ADDRESS REMOVED = >, Christophe
Strobbe < = EMAIL ADDRESS REMOVED = > wrote:
Hi Cliff,
At 16:55 26/10/2010, Cliff Tyllick wrote:
>(...)
>You can designate column and row headings in Word documents, and
>JAWS (and, I assume, other screen readers) will pick it up. But
>nowhere in Word's documentation have I found this procedure. Here's
>how you do it:
>
>To make it possible for screen readers to recognize the headings in
>your table, add a bookmark to the first cell of each table:
>- If the first row contains column headings *and* the first column
>contains row headings, name the bookmark "Title#," where "#" is the
>number of the table.
>- If the first row contains column headings but the rest of the
>first column is data, not row headings, name the bookmark
>"ColumnTitle#," where # is the number of the table. (A decision
>table might be formatted this way.)
>- If the first column contains row headings but the rest of the
>first row is data, not column headings, name the bookmark
>"RowTitle#," where # is the number of the table.
I once used a similar bookmark technique, but with a bookmark in
every column header cell and every row header cell. I can't remember
where that advice came from, and maybe that is a good thing because
it did not work. A blind trainee who used the document complained
that the tables were still not accessible. However, transferring
those tables to Microsoft Excel turned out to be much better, even
though the tables contain a header row with merged cells. (I am
referring to the tables in Clause 7 of CEN/CENELEC Guide 6:
<ftp://ftp.cen.eu/BOSS/Reference_Documents/Guides/CEN_CLC/CEN_CLC_6.pdf>;.
Guide 6 contains "Guidelines for standards developers to address the
needs of older persons and persons with disabilities" but is not
accessible...)
>
>When JAWS encounters such a table, it will, at the appropriate
>verbosity setting, behave just like it does in a properly tagged
>table in an html or PDF document. For example, if the bookmark is a
>"Title" bookmark:
>- If you move the cursor directly into a data cell, you will hear
>JAWS announce the column heading and then the row heading, followed
>in a different tone of voice by the contents of that cell.
>- Move the cursor to the next row (same column), and JAWS will
>announce the new row heading and, in the different tone of voice,
>the contents of that cell.
>- Move the cursor to the next column (same row), and JAWS will
>announce the new column heading and, in the different tone of voice,
>the contents of that cell.
>All the "Repeat as header row" does is display (to people who can
>see) the header row on each new page when the table extends across
>more than one page. It does not affect what JAWS announces -- at
>least, it hasn't in any demonstration that I have witnessed. But, of
>course, redisplaying the header row is important for cognitive
>accessibility, even for people whose only "impairment" is a moment's
>distraction as they flipped the page.
>(...)
Best regards,
Christophe
--
Christophe Strobbe
K.U.Leuven - Dept. of Electrical Engineering - SCD
Research Group on Document Architectures
Kasteelpark Arenberg 10 bus 2442
B-3001 Leuven-Heverlee
BELGIUM
tel: +32 16 32 85 51
http://www.docarch.be/
Twitter: @RabelaisA11y
---
"Better products and services through end-user empowerment"
www.usem-net.eu - www.stand4all.eu
---
Please don't invite me to Facebook, Quechup or other "social
networks". You may have agreed to their "privacy policy", but I
haven't.
From: Christophe Strobbe
Date: Tue, Oct 26 2010 12:54PM
Subject: Re: Word documents and tables
← Previous message | Next message →
Hi,
At 20:06 26/10/2010, Cliff Tyllick wrote:
>Hi, Chris.
>
>When this was mentioned at Access U, we were in a class on how to make
>Word documents accessible. We tested it immediately with Word 2007 or
>2010 and, I believe, JAWS 11. The instructor added the bookmark, turned
>JAWS on, and clicked into a cell in the middle of the table. The whole
>class cheered on hearing JAWS read the two headings and then the cell
>data.
Excellent.
The bookmark technique for table headings is not mentioned in the
"Accessible Digital Office Documents (ADOD) Guidance" for MS Word or
OpenOffice at <http://adod.idrc.ocad.ca/node/1>;.
I should test how screenreaders deal with tables in OpenOffice.org /
LibreOffice, but if anyone else has experience with this, please send
a comment to = EMAIL ADDRESS REMOVED = .
>I really do like your sample document.
Before anyone gets a wrong impression I would like to add that I did
not create that document, CEN did.
Last year I sent CEN instructions on how to create a more accessible
version of Guide 6; instead of doing that, they just sent me a
Microsoft Word version of the document.
>I scrolled until I saw a table and found this:
>
>"Table 1 * Factors to consider in clauses on information
>The best designed products or services avoid the need for any
>explanatory information, signalling the way they should be used by form
>and appearance."
>
>And, below this introduction, Table 1 has column headings, row
>headings, and empty cells. Some of the cells are shaded gray; others are
>white.
>
>No explanatory information needed there, eh?
Precisely. Convincing standards bodies to create accessible documents
is an uphill battle.
Best regards,
Christophe
>
>Cliff
>
>Cliff Tyllick
>Usability assessment coordinator
>Agency Communications Division
>Texas Commission on Environmental Quality
>512-239-4516
> = EMAIL ADDRESS REMOVED =
>
>
> >>> On 10/26/2010 at 12:02 PM, in message
>< = EMAIL ADDRESS REMOVED = >, Christophe
>Strobbe < = EMAIL ADDRESS REMOVED = > wrote:
>Hi Cliff,
>
>
>At 16:55 26/10/2010, Cliff Tyllick wrote:
> >(...)
> >You can designate column and row headings in Word documents, and
> >JAWS (and, I assume, other screen readers) will pick it up. But
> >nowhere in Word's documentation have I found this procedure. Here's
> >how you do it:
> >
> >To make it possible for screen readers to recognize the headings in
> >your table, add a bookmark to the first cell of each table:
> >- If the first row contains column headings *and* the first column
> >contains row headings, name the bookmark "Title#," where "#" is the
> >number of the table.
> >- If the first row contains column headings but the rest of the
> >first column is data, not row headings, name the bookmark
> >"ColumnTitle#," where # is the number of the table. (A decision
> >table might be formatted this way.)
> >- If the first column contains row headings but the rest of the
> >first row is data, not column headings, name the bookmark
> >"RowTitle#," where # is the number of the table.
>
>I once used a similar bookmark technique, but with a bookmark in
>every column header cell and every row header cell. I can't remember
>where that advice came from, and maybe that is a good thing because
>it did not work. A blind trainee who used the document complained
>that the tables were still not accessible. However, transferring
>those tables to Microsoft Excel turned out to be much better, even
>though the tables contain a header row with merged cells. (I am
>referring to the tables in Clause 7 of CEN/CENELEC Guide 6:
><ftp://ftp.cen.eu/BOSS/Reference_Documents/Guides/CEN_CLC/CEN_CLC_6.pdf>;.
>
>Guide 6 contains "Guidelines for standards developers to address the
>needs of older persons and persons with disabilities" but is not
>accessible...)
>
>
> >
> >When JAWS encounters such a table, it will, at the appropriate
> >verbosity setting, behave just like it does in a properly tagged
> >table in an html or PDF document. For example, if the bookmark is a
> >"Title" bookmark:
> >- If you move the cursor directly into a data cell, you will hear
> >JAWS announce the column heading and then the row heading, followed
> >in a different tone of voice by the contents of that cell.
> >- Move the cursor to the next row (same column), and JAWS will
> >announce the new row heading and, in the different tone of voice,
> >the contents of that cell.
> >- Move the cursor to the next column (same row), and JAWS will
> >announce the new column heading and, in the different tone of voice,
> >the contents of that cell.
> >All the "Repeat as header row" does is display (to people who can
> >see) the header row on each new page when the table extends across
> >more than one page. It does not affect what JAWS announces -- at
> >least, it hasn't in any demonstration that I have witnessed. But, of
> >course, redisplaying the header row is important for cognitive
> >accessibility, even for people whose only "impairment" is a moment's
> >distraction as they flipped the page.
> >(...)
>
>Best regards,
>
>Christophe
>
>
>--
>Christophe Strobbe
>K.U.Leuven - Dept. of Electrical Engineering - SCD
>Research Group on Document Architectures
>Kasteelpark Arenberg 10 bus 2442
>B-3001 Leuven-Heverlee
>BELGIUM
>tel: +32 16 32 85 51
>http://www.docarch.be/
>Twitter: @RabelaisA11y
>---
>"Better products and services through end-user empowerment"
>www.usem-net.eu - www.stand4all.eu
>---
>Please don't invite me to Facebook, Quechup or other "social
>networks". You may have agreed to their "privacy policy", but I
>haven't.
>
>
From: Michael.Moore
Date: Tue, Oct 26 2010 2:09PM
Subject: Re: Word documents and tables
← Previous message | Next message →
Just a word of caution - pun intended. The use of bookmarks to add table header support in Word is a JAWS specific hack. It does not work with other screen readers and is very fragile. You must name the bookmark "Title, RowTitle, or ColumnTitle" If you change the table or add additional tables you may need to redo the bookmarks. You will definitely need the version of JFW that your JAWS users will be working with to test and make sure things are working. Freedom Scientific has information in the release notes for JFW 6 http://www.freedomscientific.com/fs_products/software_jaws60fea.asp What is left out in that documentation is how to deal with multiple tables in a document. Bookmarks must all be unique so adding a .1, .2 will usually keep things working, at least in JFW 9, 10, and 11. We have not tested in JFW 12 yet.
The basics of MS Word table accessibility are: Use the insert table command to create the table, keep the tables simple, one row of column headings and one column of row headings is preferred. Do not use merged cells. Uncheck allow rows to break across columns, and check repeat as header row for the header row(s). This second item will provide the column headers when you convert the document to PDF or HTML. Most screen readers allow their users a method to mark rows and columns as headers but many screen reader users do not know how to do this. If you are planning for public distribution of the document, HTML and PDF offer much more robust support for tables. You cannot make complex tables directly accessible in Word. At least not to my knowledge.
If you have Office 2007 or 2010 you can use more than one row of column headers and these will transfer to PDF or to HTML using Adobe's Acrobat Pro or Dreamweaver products. You will need to add the row headers once the conversion is complete. You can also add headers and IDs to support complex tables.
Mike Moore
From: Cliff Tyllick
Date: Tue, Oct 26 2010 3:24PM
Subject: Re: Word documents and tables
← Previous message | Next message →
Mike, thanks for the additional information. I'm always eager to learn more.
To clarify, your last sentence, "You can also add headers and IDs to support complex tables," refers to what can be done in Acrobat Pro or Dreamweaver, not what can be done in Office 2007 and 2010, right?
Cliff
>>> On 10/26/2010 at 3:05 PM, in message < = EMAIL ADDRESS REMOVED = >, < = EMAIL ADDRESS REMOVED = > wrote:
Just a word of caution - pun intended. The use of bookmarks to add table header support in Word is a JAWS specific hack. It does not work with other screen readers and is very fragile. You must name the bookmark "Title, RowTitle, or ColumnTitle" If you change the table or add additional tables you may need to redo the bookmarks. You will definitely need the version of JFW that your JAWS users will be working with to test and make sure things are working. Freedom Scientific has information in the release notes for JFW 6 http://www.freedomscientific.com/fs_products/software_jaws60fea.asp What is left out in that documentation is how to deal with multiple tables in a document. Bookmarks must all be unique so adding a .1, .2 will usually keep things working, at least in JFW 9, 10, and 11. We have not tested in JFW 12 yet.
The basics of MS Word table accessibility are: Use the insert table command to create the table, keep the tables simple, one row of column headings and one column of row headings is preferred. Do not use merged cells. Uncheck allow rows to break across columns, and check repeat as header row for the header row(s). This second item will provide the column headers when you convert the document to PDF or HTML. Most screen readers allow their users a method to mark rows and columns as headers but many screen reader users do not know how to do this. If you are planning for public distribution of the document, HTML and PDF offer much more robust support for tables. You cannot make complex tables directly accessible in Word. At least not to my knowledge.
If you have Office 2007 or 2010 you can use more than one row of column headers and these will transfer to PDF or to HTML using Adobe's Acrobat Pro or Dreamweaver products. You will need to add the row headers once the conversion is complete. You can also add headers and IDs to support complex tables.
Mike Moore
From: Michael.Moore
Date: Wed, Oct 27 2010 7:00AM
Subject: Re: Word documents and tables
← Previous message | Next message →
That is correct, you can only provide support for complex tables in HTML and PDF and PDF has a serious resource issue when using JFW which can cause a lot of lag time. We are currently experimenting with changes in the tag tree and the content tree to see if we can find a way to reduce this but it is a very time consuming process. Best practice is still to keep all tables as simple as possible since it makes the information more understandable for everyone. We plan to present our findings and any new techniques that we have learned at AccessU in May.
Mike Moore
From: Cliff Tyllick
Date: Wed, Oct 27 2010 12:18PM
Subject: Re: Word documents and tables
← Previous message | Next message →
One other thought, Mike. You said:
>The use of bookmarks to add table header support in Word is a JAWS-specific hack. It does not work with other screen readers and is very fragile. You must name the bookmark "Title", "RowTitle", or "ColumnTitle" [plus a number, if more than one bookmark of that type]. If you change the table or add additional tables you may need to redo the bookmarks.
My thought:
What's the difference between a hack and standard practice? Sometimes, it's the level of acceptance and the robustness of support.
What would it take to get other screen readers to follow JAWS in this respect? That would address acceptance.
And what would it take to get Word and other word processing applications to robustly support this technique?
Ideally, creation of the bookmark would trigger from a setting in the Table Properties. The author could check off whether the table has a header row, header column, or both, and the bookmark would be created accordingly. The number in each bookmark's name could match the table number, and the bookmark names could be updated either dynamically as tables are added and removed or on command -- for example, as part of "Update all fields."
And when a PDF is created, Acrobat Pro could read that property and tag not only the header row but also a header column when appropriate.
Even without these suggested improvements, and in spite of its problems and limitations, this strikes me as an elegant solution to the problem of tagging table structure in word processing documents.
Cliff
>>> On 10/27/2010 at 8:00 AM, in message < = EMAIL ADDRESS REMOVED = >, < = EMAIL ADDRESS REMOVED = > wrote:
That is correct, you can only provide support for complex tables in HTML and PDF and PDF has a serious resource issue when using JFW which can cause a lot of lag time. We are currently experimenting with changes in the tag tree and the content tree to see if we can find a way to reduce this but it is a very time consuming process. Best practice is still to keep all tables as simple as possible since it makes the information more understandable for everyone. We plan to present our findings and any new techniques that we have learned at AccessU in May.
Mike Moore
From: Michael.Moore
Date: Wed, Oct 27 2010 12:57PM
Subject: Re: Word documents and tables
← Previous message | Next message →
Hi Cliff,
Thanks for the questions, also I need to clear up one item that I got wrong yesterday.
Clearing up the mistake: If you have more than one table in work then you need to use "Title1, Title2..." I added a dot between the bookmark name and the number yesterday, which will not work. It is something that you do with cell names in Excel when you have multiple worksheets in a workbook. The differences between the programs can get confusing, which is why we have to test every document after we implement the hacks.
Now to answer your questions.
What's the difference between a hack and standard practice?
In my mind a hack is taking advantage of a feature or a bug to accomplish something that is not supported natively. Bookmarks and named cells which can be exploited to make JAWS recognize row and column headings in Word and Excel are intended to provide support for formulas and hyperlink anchors. A standard practice would be for Word and Excel provide a programmatic method of identifying table headers similar to the TH tag in HTML and PDF preferably with header and id support as well. In word styles are used to identify heading elements and this works well with most commercial screen readers and it makes semantic sense.
What would it take to get other screen readers to follow JAWS in this respect?
The other screen reader manufacturers would probably need to make sure that implementing that feature would not violate a Freedom Scientific patent or license the feature from Freedom Scientific. If you don't think this is an issue read article linked below from NFB. <http://www.nfb.org/images/nfb/Publications/bm/bm09/bm0911/bm091107.htm>; Even if this were implemented it does not get around the hack issue. Bookmarks and Cell names are just not semantically correct elements for creating row and column headers.
What would it take to get Word and other word processing applications to robustly support this technique?
Implementing the bookmarks and cell names in the same manner that they are implemented in Word would probably involve software patent issues. Perhaps someone from MS could speak up about this. Much better would be to extend the XML specifications for MS Office docs and Open Office docs to support semantic tags that differentiated between data cells and header cells and provide support for header and id attributes. Implementation for the AT developers would then be similar to support in PDF and HTML.
Mike Moore
(512) 424-4159
From: Paul.Adam
Date: Wed, Oct 27 2010 1:06PM
Subject: Re: Word documents and tables
← Previous message | Next message →
To clarify, it's Title_1, Title_2, etc. for making multiple tables in word accessible to JAWS users. In our office accessibility classes I teach this technique since JAWS is the agency standard used by employees needing a screen reader. You can also do a similar technique for Excel tables but it's with defined names instead of bookmarks.
I couldn't find the URL explaining the process so the best place to find it is within the JAWS help under "Tables in Word". I've pasted the info on how to do it below, and below that the link to the Excel process:
--------------------------
Creating Accessible Tables
You can create accessible tables for JAWS using functionality available in Microsoft Word. This means that even those who do not use JAWS can mark table row and column headings for JAWS users.
To make a table accessible, start Microsoft Word and open the document containing your table(s). If the table has both row and column headings, place the insertion point in a cell where the row and column containing the headings meet. Then, open the Insert menu and choose Bookmark. Type "Title" and press ENTER.
If the table has only row headings, place the insertion point in any cell within the column containing the headings. Then, open the Insert menu and choose Bookmark. Type "RowTitle" and press ENTER.
If the table has only column headings, place the insertion point in any cell within the row containing the headings. Then, open the Insert menu and choose Bookmark. Type "ColumnTitle" and press ENTER.
Tip: Do not place a bookmark in each cell that contains a heading. JAWS recognizes all cells in the marked row or column as a heading.
Microsoft Word does not allow two bookmarks to use the same name. If there is more than one table in your document, add a number or descriptive word to the end of the bookmark text used to indicate headings. For example, "Title_1," "RowTitle_Revenue," or "ColumnTitle_Expenses."
--------------------------
Creating Accessible Ranges in Microsoft Excel
http://easi.cc/archive/tables1/03_CreatingAccessibleRangesInMicrosoftExcel.htm
Paul Adam
Accessibility Specialist
Department of Assistive and Rehabilitative Services
= EMAIL ADDRESS REMOVED =
From: Langum, Michael J
Date: Wed, Oct 27 2010 1:12PM
Subject: Re: Word documents and tables
← Previous message | No next message
Wouldn't it be more productive to get word processors to simply add an attribute comparable to the HTML "scope" attribute. That way, it would easy (I think) to pass this information from WORD to MSAA.
It would also be easy (at least for simple tables) to automatically convert to valid PDF or HTML when desired.
Are there any Microsoft programmers out there?
-- Mike