website-adod/googledocument-review.html at main · inclusive-design/website-adod · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en" dir="ltr">
  <head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<link rel="shortcut icon" href="misc/favicon.ico" type="image/x-icon" />

    <title>Office Application Accessibility Review: Google docs: Document | Accessible Digital Office Document (ADOD) Project</title>
    <link type="text/css" rel="stylesheet" media="all" href="sites/adod.idrc.ocad.ca/files/css/css_f227edaa08468efc78f9ba2d884f9b5e.css" />
<link type="text/css" rel="stylesheet" media="print" href="sites/adod.idrc.ocad.ca/files/css/css_24d907fbbd309d49286f16c0b240a2d1.css" />
        <!--[if lt IE 7]>
      <link type="text/css" rel="stylesheet" media="all" href="/themes/garland/fix-ie.css" />    <![endif]-->
  </head>
  <body>

<!-- Layout -->
  <div id="header-region" class="clear-block"></div>

    <div id="wrapper">
    <div id="container" class="clear-block">

      <div id="header">
        <div id="logo-floater">
        <h1><a href="index.html" title="Accessible Digital Office Document (ADOD) Project"><span>Accessible Digital Office Document (ADOD) Project</span></a></h1>        </div>


      </div> <!-- /header -->


      <div id="center"><div id="squeeze"><div class="right-corner"><div class="left-corner">
          <div class="breadcrumb"><a href="index.html">Home</a></div>                              <h2>Office Application Accessibility Review: Google docs: Document</h2>                                                  <div class="clear-block">
            <div id="node-34" class="node">


  <div class="content clear-block">
    <p><strong>Version</strong><br />
          Date of Current Version: 16  February 2011<br />
          Latest Version (HTML): <a href="http://inclusivedesign.ca/accessible-office-documents/googledocument-review">http://inclusivedesign.ca/accessible-office-documents/googledocument-review</a>
  </p>
<p><strong>Contents</strong><br />
          <a href="googledocument-review.html#_Toc285195701">Usage Notes</a> <br />
          <a href="googledocument-review.html#_Toc285195702">Review  Results</a><br />
          <a href="googledocument-review.html#_Toc285195703">Screen  Reader Test 1. Accessing an Existing Test Document</a><br />
          <a href="googledocument-review.html#_Toc285195704">Screen  Reader Test 2. Creating a New Document</a><br />
          <a href="googledocument-review.html#_Toc285195705">Acknowledgments</a></p>
<h2><a name="_Toc285195701" id="_Toc285195701"><strong>Usage Notes</strong></a> </h2>
<p></p>
<h3><strong>Overview</strong><strong><strong> </strong></strong></h3>
<p>At the time of testing (February, 2011), Google  docs: Document was found not to be very accessible using keyboard navigation. In  addition, screen reader testing appeared to show important limitations.</p>
<h3><strong>Testing Details</strong></h3>
<p>Screen reader testing was performed on Firefox  3.6.13 using two popular screen readers for Windows 7, JAWS 11 and NVDA 2010.2. <br />
          Keyboard navigation testing was performed on Windows  7 using Opera 11.01.</p>
<h3><strong>Disclaimer</strong></h3>
<p><strong>This  document is provided for information purposes only and is neither a  recommendation nor a guarantee of results.</strong><br />
  &nbsp;If errors are found, please report them to: <a href="mailto:adod-comments@idrc.ocad.ca">adod-comments@idrc.ocad.ca</a>. </p>
<h2><a name="_Toc285195702" id="_Toc285195702"><strong>Review Results</strong></a> </h2>
<p>This  table summarizes the result of our reviews using the &ldquo;ADOD Assessment  Framework: Success criteria for assessing the accessibility of office  application user interfaces&rdquo;</p>
<table border="1" cellspacing="0" cellpadding="0">
<tr>
<td width="319" valign="top">
                <strong>ADOD     Assessment Framework: Success criteria for assessing the accessibility of     office application user interfaces </strong> </td>
<td width="319" valign="top">
<p align="center"><strong>Result</strong></p>
</td>
</tr>
<tr>
<td width="319" valign="top">
<p><strong><strong>[ADOD-Office-Applications-UI </strong></strong><strong><strong>7.1] Use all applicable    operating system and accessibility standards and conventions that are    important or essential to accessibility. The techniques for this checkpoint    include references to checklists and guidelines for a number of platforms and    to general guidelines for accessible applications.</strong></strong><strong><strong> </strong></strong><br />
                    <em>ADOD    Note: The Checkpoint is very general, and includes: Supporting relevant    accessibility API(s); Web-based tools conforming to WCAG; Keyboard access;    Providing keyboard shortcuts where recommended for a platform; Respecting    platform settings (such as &ldquo;high contrast&rdquo; modes); and Providing    documentation.</em></p>
</td>
<td width="319" valign="top">
<p><strong>No. </strong></p>
<ul>
<li>Screen reader support is confirmed by    testing (see below).</li>
<li>Only select features are keyboard    accessible.</li>
<li>Does not respect platform settings    including Windows &ldquo;high contrast&rdquo; mode.</li>
</ul>
</td>
</tr>
<tr>
<td width="319" valign="top">
<p><strong><strong>[ADOD-Office-Applications-UI </strong></strong><strong><strong>7.2] Allow the author    to change the presentation within editing views without affecting the [office    document]. This allows the author to edit the document according to personal    requirements, without changing the way the document is rendered when    published.</strong></strong> </p>
</td>
<td width="319" valign="top">
<p><strong>No.</strong></p>
<ul>
<li>Does not support Windows platform &ldquo;high    contrast&rdquo; settings.<strong> </strong></li>
<li>No magnification or &ldquo;Zoom&rdquo; feature.<strong> </strong></li>
</ul>
</td>
</tr>
<tr>
<td width="319" valign="top">
<p><strong><strong>[ADOD-Office-Applications-UI </strong></strong><strong><strong>7.3] Allow the author    to edit all properties of each element and object in an accessible fashion.</strong></strong><strong> </strong></p>
</td>
<td width="319" valign="top">
<p><strong>No.</strong> Main menu options are not accessible via keyboard shortcuts. Keyboard    shortcuts do exist for some of the menu commands, but not for many others. </p>
</td>
</tr>
<tr>
<td width="319" valign="top">
<p><strong><strong>[ADOD-Office-Applications-UI </strong></strong><strong><strong>7.4] Ensure that the    editing view allows navigation via the structure of the document in an    accessible fashion.</strong></strong> </p>
</td>
<td width="319" valign="top">
<p><strong>No.&nbsp; </strong>&nbsp;No view available that allows navigation via    document structure. </p>
</td>
</tr>
<tr>
<td width="319" valign="top">
<p><strong><strong>[ADOD-Office-Applications-UI </strong></strong><strong><strong>7.5] Enable editing of    the structure of the document in an accessible fashion.</strong></strong> </p>
</td>
<td width="319" valign="top">
<p><strong>No.</strong> No view available that allows editing of the document structure,    document structure can be edited by editing the document content itself. </p>
</td>
</tr>
<tr>
<td width="319" valign="top">
<p><strong><strong>[ADOD-Office-Applications-UI </strong></strong><strong><strong>7.6] Allow the author    to search within editing views.</strong></strong><a name="sc_a324" id="sc_a324"></a><a name="sc_a331" id="sc_a331"></a> </p>
</td>
<td width="319" valign="top">
<p><strong>Yes. </strong>Via the<strong> </strong>&ldquo;Find and Replace&rdquo; feature.<strong> </strong></p>
</td>
</tr>
</table>
<h2><a name="_Toc285195703" id="_Toc285195703"><strong>Screen Reader Test  1. Accessing an Existing Test Document</strong></a> </h2>
<p>In this test, the evaluator used a screen  reader to explore a pre-existing test document that had been created by a  sighted colleague, following the &ldquo;Authoring Techniques for Accessible Office  Documents: Google docs: Document&rdquo;. The test document included the elements in  the left-hand column (i.e., heading, table of contents, etc.).</p>
<table border="1" cellspacing="0" cellpadding="0">
<tr>
<td width="319" valign="top">
                <strong>Able to Access?</strong> </td>
<td width="319" valign="top">
<p align="center"><strong>JAWS 11</strong><strong> </strong></p>
</td>
</tr>
<tr>
<td width="319" valign="top">
<p>Headings</p>
</td>
<td width="319" valign="top">
<p><strong>No.</strong></p>
</td>
</tr>
<tr>
<td width="319" valign="top">
<p>Table of contents</p>
</td>
<td width="319" valign="top">
<p><strong>Yes.&nbsp; </strong>Links were not indicated.</p>
</td>
</tr>
<tr>
<td width="319" valign="top">
<p>Image with &ldquo;alt&rdquo; text</p>
</td>
<td width="319" valign="top">
<p><strong>No.</strong> </p>
</td>
</tr>
<tr>
<td width="319" valign="top">
<p>Table</p>
</td>
<td width="319" valign="top">
<p><strong>No. </strong>The table    contents were available, but they were not in a table. Note: viewing the page    with ARIA application mode disabled there was a table containing the same    content.<strong> </strong></p>
</td>
</tr>
<tr>
<td width="319" valign="top">
<p>Formatted    text </p>
</td>
<td width="319" valign="top">
<p><strong>Yes.</strong> Not    all attributes were announced. For example, JAWS did not read the 2 in    superscript.<strong> </strong></p>
</td>
</tr>
<tr height="49">
<td width="319" height="49" valign="top">
<p>Change    tracking</p>
</td>
<td width="319" height="49" valign="top">
<p><strong>No.</strong> The    text was available, but no changes were announced.</p>
</td>
</tr>
<tr height="49">
<td width="319" height="49" valign="top">
<p>Numbered    pages</p>
</td>
<td width="319" height="49" valign="top">
<p><strong>No.</strong> There    did not appear to be a way to access the headers and footers for the document.<strong> </strong></p>
</td>
</tr>
<tr>
<td width="319" valign="top">
<p>Search    function</p>
</td>
<td width="319" valign="top">
<p><strong>No.&nbsp; </strong>The Find and Replace dialog was accessible, but the document frame    was not reliably accessible enough to assess if the search had been    successful.</p>
</td>
</tr>
</table>
<h2><a name="_Toc285195704" id="_Toc285195704"><strong>Screen Reader Test  2. Creating a New Document</strong></a> </h2>
<p>In this test, the evaluator used a screen  reader to create a new test document which was to include the elements in the  left-hand column (i.e., two levels of heading, an image, etc.).</p>
<table border="1" cellspacing="0" cellpadding="0">
<tr>
<td width="319" valign="top">
                <strong>Able to accomplish?</strong> </td>
<td width="319" valign="top">
<p align="center"><strong>JAWS 11</strong></p>
</td>
</tr>
<tr>
<td width="319" valign="top">
<p>Create    a new document </p>
</td>
<td width="319" valign="top">
<p><strong>Yes.&nbsp; </strong>From File &gt; New &gt; Document.<strong> </strong></p>
</td>
</tr>
<tr>
<td width="319" valign="top">
<p>Create two    levels of headings </p>
</td>
<td width="319" valign="top">
<p><strong>No.</strong><strong> </strong></p>
</td>
</tr>
<tr>
<td width="319" valign="top">
<p>Add and then    edit paragraph text (e.g. do a select-cut-paste) </p>
</td>
<td width="319" valign="top">
<p><strong>No.&nbsp; </strong>The editor frame was not reliably accessible enough to perform    this task.</p>
</td>
</tr>
<tr>
<td width="319" valign="top">
<p>Insert an    image </p>
</td>
<td width="319" valign="top">
<p><strong>No. </strong>It was    possible to access Insert &gt; Image, but the Insert Image dialog was not    accessible enough to complete the task of inserting the image.&nbsp; After selecting the button to browse for an    image to be uploaded, and selecting the local file, the dialog disappeared.</p>
</td>
</tr>
<tr>
<td width="319" valign="top">
<p>Insert a    3-by-3 table and fill it with content </p>
</td>
<td width="319" valign="top">
<p><strong>No. </strong>It was    possible to select Table &gt; Insert Table, but the Insert Table sub menu was    not accessible.</p>
</td>
</tr>
<tr>
<td width="319" valign="top">
<p>Create a    bullet list </p>
</td>
<td width="319" valign="top">
<p><strong>No. </strong>The    editor frame was not reliably accessible enough to complete this task.&nbsp; The Bullets button did appear to be accessible    from the toolbar.<strong> </strong></p>
</td>
</tr>
<tr>
<td width="319" valign="top">
<p>Use text    formatting (bold, text colour) </p>
</td>
<td width="319" valign="top">
<p><strong>No. </strong>The    editor frame was not reliably accessible enough to complete this task. Both    the Format menu and options on the toolbar appeared to be accessible.</p>
</td>
</tr>
<tr>
<td width="319" valign="top">
<p>Add page    numbering </p>
</td>
<td width="319" valign="top">
<p><strong>No. </strong>This    did not appear to be accessible from the menus or toolbar.</p>
</td>
</tr>
<tr>
<td width="319" valign="top">
<p>Insert a    table of contents </p>
</td>
<td width="319" valign="top">
<p><strong>Yes. </strong>Although    there were no headings in the document to populate the table of contents with    content. When the document was downloaded and opened in Word 2003 the    following text was in the document &ldquo;Add Headings (Format &gt; Paragraph styles) and they will appear    in your table of contents.&rdquo; </p>
</td>
</tr>
<tr>
<td width="319" valign="top">
<p>Save    document </p>
</td>
<td width="319" valign="top">
<p><strong>Yes. </strong>Using    the &ldquo;Save&rdquo; button.<strong> </strong></p>
</td>
</tr>
<tr>
<td width="319" valign="top">
<p><strong>Other Comments by the Screen Reader Tester:</strong></p>
</td>
<td width="319" valign="top">
<p>The    documentation for using Document with a screen-reader states that when a    document loads ARIA application mode will be enabled and you will be in the    editor frame. You should be able to edit and read the document by using arrow    keys and standard keyboard commands.&nbsp;    This was very inconsistent.&nbsp; There    were times that the document would read, other times that it would not, times    that edits took effect, and times that they did not. When reading the reading    was not consistent, lines were often read out of order, when using left or    right arrows to read by character some characters would repeat or not be    spoken at all.<br />
              The    documentation also states that pressing the escape key from the editor frame    would activate the Document menu, this never worked. It was necessary to    toggle ARIA application mode on and off (JAWS key + z) to move in and out of    the editor frame to other controls on the page.&nbsp; The toggling of application mode rarely    worked as it should.&nbsp; It was necessary    to open a second Firefox window and to move to that window and then back to    Document to escape application mode.<br />
              See also    Google Apps accessibility documentation at    <a href="http://www.google.com/accessibility/resources.html" title="http://www.google.com/accessibility/resources.html">http://www.google.com/accessibility/resources.html</a></p>
</td>
</tr>
</table>
<p></p>
<h2>&nbsp;</h2>
<h4><a name="_Toc285621609" id="_Toc285621609"><strong>Acknowledgments</strong></a> </h4>
<p>This document was produced as part of the  Accessible Digital Office Document (ADOD) Project (<a href="http://inclusivedesign.ca/accessible-office-documents" title="http://inclusivedesign.ca/accessible-office-documents">http://inclusivedesign.ca/accessible-office-documents</a>).<br />
  This project has been developed by the  Inclusive Design Research Centre, OCAD University as part of an EnAbling Change  Partnership project with the Government of Ontario and UNESCO (United Nations  Educational, Scientific and Cultural Organization).</p>
<p><img src="sites/adod.idrc.ocad.ca/files/partners.png" alt="Partner logos: UNESCO-United Nations Educational, Scientific and Cultural Organization, the Government of Ontario and the Inclusive Design Research Centre (OCAD University)" width="626" height="166" /></p>
<p>Copyright &copy; 2011 Inclusive Design Research  Centre, OCAD University<br />
  This material may be reproduced and distributed in print or electronic  format only as long as: </p>
<p>(a) the reproduction is offered at no cost to the recipients; and<br />
  (b) the reproduction must  preserve the &quot;Version&quot; section; and<br />
  (c) the reproduction must  preserve the &quot;Acknowledgments&quot; section; and<br />
  (d) the reproduction must  preserve this copyright notice.</p>
  </div>

  <div class="clear-block">
    <div class="meta">
        </div>

      </div>

</div>
          </div>
                    <div id="footer">Copyright 2010, IDRC</div>
      </div></div></div></div> <!-- /.left-corner, /.right-corner, /#squeeze, /#center -->


    </div> <!-- /container -->
  </div>
<!-- /layout -->

    </body>
</html>