-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy pathexcel2010-review.html
More file actions
333 lines (315 loc) · 16.4 KB
/
Copy pathexcel2010-review.html
File metadata and controls
333 lines (315 loc) · 16.4 KB
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
<!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: MS Excel 2010 | 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: MS Excel 2010</h2> <div class="clear-block">
<div id="node-39" 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/word2007-review">http://inclusivedesign.ca/accessible-office-documents/excel2010-review</a>
</p>
<p><strong>Contents</strong><br />
<a href="excel2010-review.html#_Toc285195701">Usage Notes</a> <br />
<a href="excel2010-review.html#_Toc285195702">Review Results</a><br />
<a href="excel2010-review.html#_Toc285195703">Screen Reader Test 1. Accessing an Existing Test Document</a><br />
<a href="excel2010-review.html#_Toc285195704">Screen Reader Test 2. Creating a New Document</a><br />
<a href="excel2010-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), Excel 2010 was found to be relatively accessible using keyboard navigation. In addition, screen reader testing appeared to show that use is possible with JAWS 11 and NVDA 2010.2 with some limitations. </p>
<h3><strong>Testing Details</strong></h3>
<p>Screen reader testing was performed using two popular screen readers for Windows 7, JAWS 11 and NVDA 2010.2.<br />
Keyboard navigation testing was performed on Windows 7.</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 />
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 “ADOD Assessment Framework: Success criteria for assessing the accessibility of office application user interfaces”</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 “high contrast” modes); and Providing documentation.</em></p>
</td>
<td width="319" valign="top">
<p><strong>Yes. </strong></p>
<ul>
<li>Screen reader support is confirmed by testing (see below).</li>
<li>Most features are keyboard accessible.</li>
<li>Provides keyboard shortcuts and when “alt” is pressed, the keyboard shortcuts appear displayed adjacent to the controls they will activate.</li>
<li>Respects platform settings including Windows “high contrast” 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>Yes.</strong> “Zoom” feature and support for Windows platform high contrast settings. </p>
</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>Mostly.</strong> Some inserted graphical objects (e.g., shapes) appear to require the mouse be used for editing. </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.</strong> Document can be navigated cell by cell, not by document structure alone. </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>Does not allow navigation via the structure alone. </p>
<ul>
<li>Shortcut keys moves to edge of data region or cell by cell.</li>
<li>Shortcut keys allow chart navigation via the structure of the chart.</li>
</ul>
</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>“Find and Replace” 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 “Authoring Techniques for Accessible Office Documents: Microsoft Excel 2010”. 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="213" valign="top">
<strong>Able to Access?</strong> </td>
<td width="213" valign="top">
<p align="center"><strong>JAWS 11</strong><strong> </strong></p>
</td>
<td width="213" valign="top">
<p align="center"><strong>NVDA 2010.2</strong><strong> </strong></p>
</td>
</tr>
<tr>
<td width="213" valign="top">
<p>Image with “alt” text</p>
</td>
<td width="213" valign="top">
<p><strong>Yes. </strong>The image was found with the JAWS object list (control + shift + o). </p>
</td>
<td width="213" valign="top">
<p><strong>No.</strong> NVDA did not recognize an image.</p>
</td>
</tr>
<tr>
<td width="213" valign="top">
<p>Data table</p>
</td>
<td width="213" valign="top">
<p><strong>Yes.</strong> </p>
</td>
<td width="213" valign="top">
<p><strong>Yes.</strong> </p>
</td>
</tr>
<tr>
<td width="213" valign="top">
<p>Bar chart with “alt” text </p>
</td>
<td width="213" valign="top">
<p><strong>Yes.</strong> The chart was found using the JAWS object list (control + shift + o).</p>
</td>
<td width="213" valign="top">
<p><strong>No.</strong> NVDA did not recognize a chart.</p>
</td>
</tr>
<tr height="49">
<td width="213" height="49" valign="top">
<p>Formatted text</p>
</td>
<td width="213" height="49" valign="top">
<p><strong>Yes.</strong> Using the JAWS text attributes command (JAWS key + f).</p>
</td>
<td width="213" height="49" valign="top">
<p><strong>Yes.</strong> Using the NVDA text attributes command (NVDAS key + f). Font color was not recognized.<strong> </strong></p>
</td>
</tr>
<tr height="49">
<td width="213" height="49" valign="top">
<p>Cell with a note on it</p>
</td>
<td width="213" height="49" valign="top">
<p><strong>Yes.</strong> JAWS announced the presence of the note, and it was discoverable using the JAWS comments list (control + shift + ‘).<strong> </strong></p>
</td>
<td width="213" height="49" valign="top">
<p><strong>No.</strong> The text was available, but NVDA did not announce or provide access to the comment.<strong> </strong></p>
</td>
</tr>
<tr>
<td width="213" valign="top">
<p>Search function</p>
</td>
<td width="213" valign="top">
<p><strong>Yes.</strong></p>
</td>
<td width="213" valign="top">
<p><strong>Yes.</strong></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="213" valign="top">
<strong>Able to accomplish?</strong> </td>
<td width="213" valign="top">
<p align="center"><strong>JAWS 11</strong></p>
</td>
<td width="213" valign="top">
<p align="center"><strong>NVDA 2010.2</strong></p>
</td>
</tr>
<tr>
<td width="213" valign="top">
<p>Add and then edit regular text (e.g. do a select-cut-paste) </p>
</td>
<td width="213" valign="top">
<p><strong>Yes. </strong>To cut and paste an entire cell of text it is necessary to select the cell, cut, move to the new cell, and then to paste. To cut a segment of text from the currently selected cell it is necessary to press F2 to focus on the cell edit control, to select the desired text, to cut, to find the new cell, and to paste.<strong> </strong></p>
</td>
<td width="213" valign="top">
<p><strong>Yes. </strong>To cut and paste an entire cell of text it is necessary to select the cell, cut, move to the new cell, and then to paste. To cut a segment of text from the currently selected cell it is necessary to press F2 to focus on the cell edit control, to select the desired text, to cut, to find the new cell, and to paste.<strong> </strong></p>
</td>
</tr>
<tr>
<td width="213" valign="top">
<p>Insert an image </p>
</td>
<td width="213" valign="top">
<p><strong>Yes.</strong> Using Insert > Picture. It did not appear possible to set alternative text.</p>
</td>
<td width="213" valign="top">
<p><strong>Yes.</strong> Using Insert > Picture. It did not appear possible to add Alternative text. Once focus was moved from the picture, pressing escape, it was not possible to get it back. </p>
</td>
</tr>
<tr>
<td width="213" valign="top">
<p>Insert a 3-by-3 table and fill it with content </p>
</td>
<td width="213" valign="top">
<p><strong>Yes.</strong> <strong> </strong></p>
</td>
<td width="213" valign="top">
<p><strong>Yes.</strong> </p>
</td>
</tr>
<tr>
<td width="213" valign="top">
<p>Create a chart from a data table </p>
</td>
<td width="213" valign="top">
<p><strong>Yes.</strong> Using Insert > (chart type).</p>
</td>
<td width="213" valign="top">
<p><strong>Yes. </strong>Using Insert > (chart type).<strong> </strong></p>
</td>
</tr>
<tr>
<td width="213" valign="top">
<p>Use text formatting (bold, text colour) </p>
</td>
<td width="213" valign="top">
<p><strong>Yes.</strong></p>
</td>
<td width="213" valign="top">
<p><strong>Yes.</strong> </p>
</td>
</tr>
<tr>
<td width="213" valign="top">
<p>Save document </p>
</td>
<td width="213" valign="top">
<p><strong>Yes.</strong></p>
</td>
<td width="213" valign="top">
<p><strong>Yes.</strong></p>
</td>
</tr>
<tr>
<td width="213" valign="top">
<p><strong>Other Comments by the Screen Reader Tester:</strong></p>
</td>
<td width="213" valign="top">
<p>JAWS provides good support for the ribbon. However, using the ribbon is very non-intuitive, as it is a unique user interface component. JAWS does provide help training for Office 2007 in the JAWS menu > Help > Training. Although the training is for Office 2007, it would be useful to an Office 2010 user as well.</p>
<p>Some documents open in Office 2010 in “Protected view”. From within the document press F6 to get to the Protected view toolbar and tab to get to the “Enable editing” button.</p>
</td>
<td width="213" valign="top">
<p>Using the ribbon is very non-intuitive, as it is a unique user interface component. <br />
Some documents open in Office 2010 in “Protected view”. From within the document press F6 to get to the Protected view toolbar and tab to get to the “Enable editing” button.</p>
</td>
</tr>
</table>
<p></p>
<h2> </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 © 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 "Version" section; and<br />
(c) the reproduction must preserve the "Acknowledgments" 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>