Accessibility Report for 'XYZ' web site · Web view[14] 1.1.1 T1: The ALT attribute must be defined...

Accessibility Report for "XYZ" web site

Accessibility Report for Cisco TelePresence Conductor

Version of product: Cisco TelePresence Conductor

URL: https://10.50.154.83

Username: demo

Password: demo

Tester: Nadia Dabaie

Date: 4/21/2012

Summary:

1. Code Inspection: Fail

2. Keyboard Navigation: Fail

3. Visual Inspection: Fail

4. Screen Reader: Fail

5.

The Cisco Web ADRs Checklist

(More information can be found on “Accessibility Center” community on IWE)

Cisco Web ADRs

Description

Status (Pass,Fail,N/A)

Comments

ADR 1.1.1

Non text content

Fail

ADR 1.2.1

Audio-only and Video-only (Prerecorded)

N/A

ADR 1.2.2

Captions (Prerecorded)

N/A

ADR 1.2.3

Audio Description or Media Alternative (Prerecorded)

N/A

ADR 1.3.1

Info and Relationships

Fail

ADR 1.3.2

Meaningful Sequence

Pass

ADR 1.3.3

Sensory Characteristics

Pass

ADR 1.4.1

Use of Color

Pass

ADR 1.4.2

Audio Control

Pass

ADR 1.4.3

Contrast

Pass

ADR 2.1.1

Keyboard

Fail

ADR 2.1.2

No Keyboard Trap

Pass

ADR 2.2.1

Timing Adjustable

Pass

ADR 2.2.2

Pause, Stop, Hide

Pass

ADR 2.3.1

Three Flashes or Below Threshold

Pass

ADR 2.4.1

Bypass Blocks

Pass

ADR 2.4.2

Page Titled

Fail

ADR 2.4.3

Focus Order

Pass

ADR 2.4.4

Link Purpose (In Context)

Pass

ADR 3.1.1

Language of Page

Fail

ADR 3.2.1

On Focus

Pass

ADR 3.2.2

On Input

Pass

ADR 3.3.1

Error Identification

Pass

ADR 3.3.2

Labels or Instructions

Pass

ADR 4.1.1

Parsing

Fail

ADR 4.1.2

Name, Role, Value

Pass

I - Code Inspection

- Software: SOAtest version 9.0

- ACC Rule Set: Cisco ADRs

- This test identifies the coding scheme which

Test scenario:

Test Suite: Functional Tests

Scenario: TP-Conductor-1

Test 1: Navigate to ${10_50_154_83_BASE_URL} - success

Scenario: Form: login_form

Test 1: Type "demo" - success

Test 2: Type "****" - success

Test 3: Click "Login" - success

Test 3: Click "IPv4 address" - success

Test 4: Click "Alarms" - success

Test 5: Click "Conference bridges" - success

Test 6: Click "Conferences" - success

Test 7: Click "All events" - success

Test 8: Click "Conference creation events" - success

Test 9: Click "Administration" - success

Test 10: Click "Ethernet" - success

Test 11: Click "IP" - success

Test 12: Click "DNS" - success

Test 13: Click "Time" - success

Test 14: Click "SNMP" - success

Test 15: Click "Clustering" - success

Test 16: Click "Basic conference configuration wizard" - success

Test 17: Click "Creating conferences" - success

Test 18: Click "Conference bridge pools" - success

Test 19: Click "Conference bridge Service Preferences" - success

Test 20: Click "Conference templates" - success

Test 21: Click "Conference aliases" - success

Test 22: Click "Auto-dialed participants" - success

Test 23: Click "Call Policy" - success

Test 24: Click "Administrator accounts" - success

Test 25: Click "Administrator groups" - success

Test 26: Click "Upgrade" - success

Test 27: Click "Logging" - success

Test 28: Click "Check pattern" - success

Test 29: Click "Check dial plan" - success

Test 30: Click "Ping" - success

Test 31: Click "Tracepath" - success

Test 32: Click "Trusted CA certificate" - success

Test 33: Click "Server certificate" - success

Test 34: Click "Backup and restore" - success

Test 35: Click "System snapshot" - success

Test 36: Click "Configuration" - success

Test 37: Click "View" - success

Test 38: Click "Feedback receivers" - success

Test 39: Click "Restart" - success

Test 40: Click "Logout" - success

Accessibility Errors:

[1339] Cisco ADRs (Cisco ADRs)

· [14] 1.1.1 T1: The ALT attribute must be defined for an image (ImgMissingAlt_2-1)

· [1] 2.4.2 T1: A meaningful title must be provided for each page in TITLE element (TitleElement2_2-1)

· [1000] 1.3.1 T4 T5 T6: If data table, data cells should have HEADERS attribute to list the IDs of the header cells. Screen Reader test required (DataCellHeaders_2-2)

· [42] 1.3.1 T4 T5 T6: If data table, provide unique IDs in header cells and reference them in HEADER attribute of data cells. Screen Reader test required (HeaderScope_2-2)

· [13] 1.3.1 T4 T5 T6: If data table, provide a description via the SUMMARY attribute or CAPTION element. Screen Reader test required (TableSummary_2-2)

· [1] 3.1.1 T1: The value of the LANG attribute must be set to one of the ISO 639 language codes (LanguageISO639_2-3)

· [31] 4.1.1 T3: The ID attribute must be unique in a document (new_IDReporter2-3)

· [52] 1.3.1 T1 T2: Form controls and their labels should be explicitly associated with the LABEL element (new_form2-3)

· [95] 1.3.1 T4: If layout table, only use TABLE, TR, and TD elements. Screen Reader test required (LayoutTableTags_2-4)

· [59] 3.2.1 T1: onBlur and onFocus should not be used to initiate a major change of context. Keyboard test required (OnBlurOnFocus_2-4)

· [31] 2.1.1 T2: Mouse movement events might need to be paired with key events to be accessible. Keyboard test required (OnMouseMovement_2-4)

II - Keyboard Navigation

NOTE: This test is not using a screen reader. Users should be able to navigate and use the application without using the mouse.

- All keyboard navigation issues listed in this section are related to one or more of the ADRs listed below.

Related ADRs:

· ADR 2.1.1: Keyboard

· ADR 2.1.2: No Keyboard Trap

· ADR 2.4.3: Focus Order

General Navigation issues on all pages:

1) The main issue with kb navigation was in the drop down menus. When tabbing through the menu items, the focus moves from one menu item to the next. However, when reaching the last menu item on the last tab (Maintenance > Shutdown), the expanded menu stays visually in focus even when the actual focus (cursor) has moved to another element/control on the page. This behavior repeats when the actual focus is on the last page name of the first menu option and the kb user presses the keys to traverse the page elements preceding the cursor position, the expanded menu stays visually in focus even when the actual focus (cursor) moves to a higher location on the page.

2) Another important issue is not having a skip nav method which would allow the keyboard user to navigate directly and bring focus into the content of the page that was selected from the menu options. There are many links to navigate through before the intended content is reached.

3) Navigating through the Event Log table (Status > Even Log > All Events) is very problematic to the kb user as there is no tab order that would take focus off the table. The table is very expansive and kb users get trapped in the content and cannot take focus to another area on the page.

4) There is no keyboard focus to the DNS lookup utility link at the bottom of the DNS page: (Systems > DNS). The user cannot access the links without using the mouse.

III - Visual Inspection

The web UI was tested using a set of 3 high-contrast themes from Windows XP:

1) High Contrast Black (large)

2) High Contrast white (large)

3) High Contrast 1 (Large)

A sample set of screen shots with these themes applied can be found below. The application inherited most elements of color changes associated with the high contrast themes.

The application exhibited problems with inheriting the large font sizes. The product simply failed to change font size at all.

These issues can be filed under requirement ACC-SW-50.31: Contrast.

Sample Screenshots: High Contrast Black (large)

Note that the text size has not changed at all which makes it not accessible to users with low vision issues. The text size should have been increased to match the user’s pre-set OS settings for high contrast large font.

High Contrast White (large)

Application does not inherit change in font size in accordance with the large setting. Same issue repeats for the High Contrast 1 (large) setting.

IV - Screen Reader

- Tested with screen reader JAWS version 12 on Tested with FF 3.6.3 on Windows 8.0.600.

- Because of the issues found in “Code Inspection” and “Keyboard Navigation” tests, it is difficult to complete the “Screen Reader” test. Fixing these issues first would eliminate many related problems and would only focus on screen reader issues. Here are some issues that occur on many pages of the application:

1) Screen reader users cannot use a number of forms on the pages because they are not labeled correctly (See Code Inspection test above).

2) Screen reader users cannot understand many data tables because they are not coded correctly for accessibility (See Code Inspection test above).

3) Screen reader users cannot access and use all elements or controls that are not in the tab order or not in a logical navigation (See Keyboard Navigation test above).

Examples: The example provided below is merely an example to illustrate an issue. There are many examples but they are all listed in the report.

· On the Maintenance > Logging page the Form controls and their labels are not explicitly associated with the LABEL element. The screen reader does not announce the lables of the “Remote syslog servers” table.

· The “informational icons which are present on the “Users > LDAP configuration” page have an alt tag that is null ([ img alt="" ]). The textual information associated with each icon is only visible to users with vision. It is not exposed to assistive technologies like JAWS the screen reader. On the same page the “red astrik” which is an important piece of info is not announce by JAWS.

· If layout table, only use TABLE, TR, and TD elements: The table on Status > Overview > System Information page is a layout table and should not have the Headers element. When using JAWS keys to read the table, JAWS does not announce the headers of each row; instead it announces the Summary of the table. The following example is taken from the page referenced earlier in the paragraph and is illustrated in the next screenshot:

In the screenshot above JAWS announces the following when the tab order is on the text highlighted in red “paulVm” first row second column: “System information paulVm column two”. If that was a data table, this test should have been announced as follow: “System Information System host name paulVm first row second column”. However, in this scenario it is best to keep this table as layout table. ACC-Web-1.3.1

CDATA

Defines where administrator login credentials are authenticated against an external credentials directory such as Active Directory.

Local only: credentials are verified against a local database stored on the system.

Remote only: credentials are verified against an external credentials directory.

Both: credentials are verified first against a local database stored on the system, and then if no matching account is found the external credentials directory is used instead.

Default: Local only

04/19/12 16:22:30

Results from:Cisco Accessibility Test

STATIC ANALYSIS

FUNCTIONAL TESTS

STATIC ANALYSIS

Project Name

Tasks suppressed / qfix / total / per 10,000 lines

Files checked / total

Lines checked / total

TP-Conductor-firefox-test

0

|

0

|

1339

|

0

0

|

0

0

|

0

Total [2:49:31]

0

|

0

|

1339

|

0

0

|

0

0

|

0

All Tasks by Category

All Tasks by Severity

by:

Category

Severity

[1339] Cisco ADRs (Cisco ADRs)

[14] 1.1.1 T1: The ALT attribute must be defined for an image (ImgMissingAlt_2-1)

[1] 2.4.2 T1: A meaningful title must be provided for each page in TITLE element (TitleElement2_2-1)

[1000] 1.3.1 T4 T5 T6: If data table, data cells should have HEADERS attribute to list the IDs of the header cells. Screen Reader test required (DataCellHeaders_2-2)

[42] 1.3.1 T4 T5 T6: If data table, provide unique IDs in header cells and reference them in HEADER attribute of data cells. Screen Reader test required (HeaderScope_2-2)

[13] 1.3.1 T4 T5 T6: If data table, provide a description via the SUMMARY attribute or CAPTION element. Screen Reader test required (TableSummary_2-2)

[1] 3.1.1 T1: The value of the LANG attribute must be set to one of the ISO 639 language codes (LanguageISO639_2-3)

[31] 4.1.1 T3: The ID attribute must be unique in a document (new_IDReporter2-3)

[52] 1.3.1 T1 T2: Form controls and their labels should be explicitly associated with the LABEL element (new_form2-3)

[95] 1.3.1 T4: If layout table, only use TABLE, TR, and TD elements. Screen Reader test required (LayoutTableTags_2-4)

[59] 3.2.1 T1: onBlur and onFocus should not be used to initiate a major change of context. Keyboard test required (OnBlurOnFocus_2-4)

[31] 2.1.1 T2: Mouse movement events might need to be paired with key events to be accessible. Keyboard test required (OnMouseMovement_2-4)

[15] Severity 1 - Highest

[14] 1.1.1 T1: The ALT attribute must be defined for an image (ImgMissingAlt_2-1)

[1] 2.4.2 T1: A meaningful title must be provided for each page in TITLE element (TitleElement2_2-1)

[1055] Severity 2 - High

[1000] 1.3.1 T4 T5 T6: If data table, data cells should have HEADERS attribute to list the IDs of the header cells. Screen Reader test required (DataCellHeaders_2-2)

[42] 1.3.1 T4 T5 T6: If data table, provide unique IDs in header cells and reference them in HEADER attribute of data cells. Screen Reader test required (HeaderScope_2-2)

[13] 1.3.1 T4 T5 T6: If data table, provide a description via the SUMMARY attribute or CAPTION element. Screen Reader test required (TableSummary_2-2)

[84] Severity 3 - Medium

[1] 3.1.1 T1: The value of the LANG attribute must be set to one of the ISO 639 language codes (LanguageISO639_2-3)

[31] 4.1.1 T3: The ID attribute must be unique in a document (new_IDReporter2-3)

[52] 1.3.1 T1 T2: Form controls and their labels should be explicitly associated with the LABEL element (new_form2-3)

[185] Severity 4 - Low

[95] 1.3.1 T4: If layout table, only use TABLE, TR, and TD elements. Screen Reader test required (LayoutTableTags_2-4)

[59] 3.2.1 T1: onBlur and onFocus should not be used to initiate a major change of context. Keyboard test required (OnBlurOnFocus_2-4)

[31] 2.1.1 T2: Mouse movement events might need to be paired with key events to be accessible. Keyboard test required (OnMouseMovement_2-4)

Author

Taskssuppressed/ total / recommended

ndabaie

0

1339

50

Total Tasks: 1339

ndabaie [1339] ^

-

Browser-Constructed HTML (Firefox 3.6)

2:

3.1.1 T1: The value of the LANG attribute must be set to one of the ISO 639 language codes

LanguageISO639_2-3

5:

2.4.2 T1: A meaningful title must be provided for each page in TITLE element

TitleElement2_2-1

60:

1.3.1 T4: If layout table,

should not be used. Only use TABLE, TR, and TD elements in layout tables. Screen Reader test required

LayoutTableTags_2-4

61:



LayoutTableTags_2-4

62:



LayoutTableTags_2-4

63:



LayoutTableTags_2-4

70:



LayoutTableTags_2-4

71:



LayoutTableTags_2-4

72:



LayoutTableTags_2-4

73:



LayoutTableTags_2-4

74:



LayoutTableTags_2-4

75:



LayoutTableTags_2-4

76:



LayoutTableTags_2-4

77:



LayoutTableTags_2-4

81:



LayoutTableTags_2-4

82:



LayoutTableTags_2-4

83:



LayoutTableTags_2-4

84:



LayoutTableTags_2-4

85:



LayoutTableTags_2-4

86:



LayoutTableTags_2-4

93:



LayoutTableTags_2-4

94:



LayoutTableTags_2-4

95:



LayoutTableTags_2-4

96:



LayoutTableTags_2-4

97:



LayoutTableTags_2-4

98:



LayoutTableTags_2-4

99:



LayoutTableTags_2-4

100:



LayoutTableTags_2-4

101:



LayoutTableTags_2-4

102:



LayoutTableTags_2-4

103:



LayoutTableTags_2-4

114:



LayoutTableTags_2-4

115:



LayoutTableTags_2-4

116:



LayoutTableTags_2-4

117:



LayoutTableTags_2-4

124:



LayoutTableTags_2-4

125:



LayoutTableTags_2-4

126:



LayoutTableTags_2-4

127:



LayoutTableTags_2-4

128:



LayoutTableTags_2-4

129:



LayoutTableTags_2-4

141:



LayoutTableTags_2-4

142:



LayoutTableTags_2-4

143:



LayoutTableTags_2-4

144:



LayoutTableTags_2-4

145:



LayoutTableTags_2-4

147:



LayoutTableTags_2-4

148:



LayoutTableTags_2-4

149:



LayoutTableTags_2-4

150:



LayoutTableTags_2-4

156:



LayoutTableTags_2-4

157:



LayoutTableTags_2-4

158:



LayoutTableTags_2-4

159:



LayoutTableTags_2-4

167:



LayoutTableTags_2-4

168:



LayoutTableTags_2-4

169:



LayoutTableTags_2-4

170:



LayoutTableTags_2-4

177:



LayoutTableTags_2-4

178:



LayoutTableTags_2-4

179:



LayoutTableTags_2-4

180:



LayoutTableTags_2-4

182:

1.3.1 T4 T5 T6: If data table, provide a description via the SUMMARY attribute or CAPTION element. Screen Reader test required

TableSummary_2-2

185:

1.3.1 T4 T5 T6: If data table, provide unique IDs in header cells and reference them in HEADER attribute of data cells. Screen Reader test required

HeaderScope_2-2

185:



LayoutTableTags_2-4

189:

1.3.1 T4 T5 T6: If data table, data cells should have HEADERS attribute to list the IDs of the header cells. Screen Reader test required

DataCellHeaders_2-2

190:


DataCellHeaders_2-2

191:


DataCellHeaders_2-2

192:

1.1.1 T1: The ALT attribute must be defined for image "/inc/close.gif?etag=538-1329412461"

ImgMissingAlt_2-1

192:


DataCellHeaders_2-2

192:

3.2.1 T1: onBlur and onFocus should not be used to initiate a major change of context. Keyboard test required

OnBlurOnFocus_2-4

193:


ImgMissingAlt_2-1

193:


DataCellHeaders_2-2

193:


OnBlurOnFocus_2-4

194:

1.3.1 T1 T2: Form controls and their labels should be explicitly associated with the LABEL element

new_form2-3

194:


DataCellHeaders_2-2

195:


ImgMissingAlt_2-1

195:


DataCellHeaders_2-2

196:


DataCellHeaders_2-2

197:


DataCellHeaders_2-2

198:


DataCellHeaders_2-2

198:

4.1.1 T3: The ID attribute must be unique in a document

new_IDReporter2-3

202:


new_IDReporter2-3

204:


TableSummary_2-2

206:


OnBlurOnFocus_2-4

207:


HeaderScope_2-2

208:


HeaderScope_2-2

208:



LayoutTableTags_2-4

208:


new_IDReporter2-3

209:


HeaderScope_2-2

209:



LayoutTableTags_2-4

210:


HeaderScope_2-2

210:



LayoutTableTags_2-4

211:


HeaderScope_2-2

211:



LayoutTableTags_2-4

212:


HeaderScope_2-2

212:



LayoutTableTags_2-4

212:


new_IDReporter2-3

213:


HeaderScope_2-2

213:



LayoutTableTags_2-4

214:


HeaderScope_2-2

214:



LayoutTableTags_2-4

215:


HeaderScope_2-2

215:



LayoutTableTags_2-4

216:


HeaderScope_2-2

216:



LayoutTableTags_2-4

216:


OnBlurOnFocus_2-4

217:



LayoutTableTags_2-4

218:



LayoutTableTags_2-4

219:



LayoutTableTags_2-4

220:



LayoutTableTags_2-4

221:


new_form2-3

221:


DataCellHeaders_2-2

221:



LayoutTableTags_2-4

221:


new_IDReporter2-3

222:


DataCellHeaders_2-2

223:


new_form2-3

223:


DataCellHeaders_2-2

224:


ImgMissingAlt_2-1

224:


DataCellHeaders_2-2

224:

2.1.1 T2: Mouse movement events might need to be paired with key events to be accessible. Keyboard test required

OnMouseMovement_2-4

224:


OnBlurOnFocus_2-4

225:


DataCellHeaders_2-2

225:


OnMouseMovement_2-4

225:


new_IDReporter2-3

226:


DataCellHeaders_2-2

226:


OnMouseMovement_2-4

226:


OnBlurOnFocus_2-4

227:


ImgMissingAlt_2-1

227:


DataCellHeaders_2-2

227:


OnMouseMovement_2-4

227:


OnBlurOnFocus_2-4

228:


ImgMissingAlt_2-1

228:


DataCellHeaders_2-2

228:


OnMouseMovement_2-4

228:


OnBlurOnFocus_2-4

229:


ImgMissingAlt_2-1

229:


OnMouseMovement_2-4

230:


new_form2-3

230:


DataCellHeaders_2-2

230:


OnMouseMovement_2-4

231:


ImgMissingAlt_2-1

231:


DataCellHeaders_2-2

231:


OnBlurOnFocus_2-4

232:


DataCellHeaders_2-2

233:


DataCellHeaders_2-2

234:


DataCellHeaders_2-2

234:


new_IDReporter2-3

235:


DataCellHeaders_2-2

236:


new_form2-3

236:


DataCellHeaders_2-2

236:


TableSummary_2-2

237:


DataCellHeaders_2-2

238:


OnBlurOnFocus_2-4

239:


new_form2-3

239:


DataCellHeaders_2-2

239:


HeaderScope_2-2

239:


OnBlurOnFocus_2-4

240:


DataCellHeaders_2-2

240:


HeaderScope_2-2

240:



LayoutTableTags_2-4

240:


OnBlurOnFocus_2-4

241:


DataCellHeaders_2-2

241:


HeaderScope_2-2

241:


OnBlurOnFocus_2-4

242:


DataCellHeaders_2-2

242:


OnBlurOnFocus_2-4

243:


DataCellHeaders_2-2

243:


TableSummary_2-2

243:


new_IDReporter2-3

244:


DataCellHeaders_2-2

245:


DataCellHeaders_2-2

245:


new_IDReporter2-3

246:


DataCellHeaders_2-2

246:


HeaderScope_2-2

248:


new_form2-3

248:


DataCellHeaders_2-2

249:


DataCellHeaders_2-2

249:


OnBlurOnFocus_2-4

250:


DataCellHeaders_2-2

250:


OnBlurOnFocus_2-4

251:


DataCellHeaders_2-2

251:


OnBlurOnFocus_2-4

252:


DataCellHeaders_2-2

252:


OnBlurOnFocus_2-4

253:


DataCellHeaders_2-2

254:


DataCellHeaders_2-2

255:


ImgMissingAlt_2-1

255:


DataCellHeaders_2-2

255:


OnBlurOnFocus_2-4

255:


new_IDReporter2-3

257:


new_form2-3

257:


DataCellHeaders_2-2

257:


OnBlurOnFocus_2-4

258:


DataCellHeaders_2-2

259:


DataCellHeaders_2-2

259:


OnBlurOnFocus_2-4

260:


DataCellHeaders_2-2

261:


DataCellHeaders_2-2

262:


ImgMissingAlt_2-1

262:


DataCellHeaders_2-2

262:


TableSummary_2-2

262:


OnBlurOnFocus_2-4

263:


DataCellHeaders_2-2

264:


DataCellHeaders_2-2

264:


TableSummary_2-2

264:


OnBlurOnFocus_2-4

264:


new_IDReporter2-3

265:


HeaderScope_2-2

266:


new_form2-3

266:


DataCellHeaders_2-2

266:


OnBlurOnFocus_2-4

267:


DataCellHeaders_2-2

267:


HeaderScope_2-2

267:



LayoutTableTags_2-4

268:


DataCellHeaders_2-2

268:


HeaderScope_2-2

268:



LayoutTableTags_2-4

269:


DataCellHeaders_2-2

269:


TableSummary_2-2

269:


HeaderScope_2-2

269:



LayoutTableTags_2-4

269:


new_IDReporter2-3

270:


new_form2-3

270:


DataCellHeaders_2-2

270:


HeaderScope_2-2

270:



LayoutTableTags_2-4

271:


ImgMissingAlt_2-1

271:


DataCellHeaders_2-2

271:


HeaderScope_2-2

272:


DataCellHeaders_2-2

272:


HeaderScope_2-2

273:


DataCellHeaders_2-2

273:


HeaderScope_2-2

273:


OnBlurOnFocus_2-4

274:


TableSummary_2-2

274:


HeaderScope_2-2

275:


new_form2-3

275:


DataCellHeaders_2-2

275:


HeaderScope_2-2

276:


new_form2-3

276:


DataCellHeaders_2-2

276:


HeaderScope_2-2

276:


OnBlurOnFocus_2-4

277:


DataCellHeaders_2-2

277:


HeaderScope_2-2

277:


new_IDReporter2-3

278:


new_form2-3

278:


DataCellHeaders_2-2

278:


TableSummary_2-2

278:


new_IDReporter2-3

279:


DataCellHeaders_2-2

280:


DataCellHeaders_2-2

281:


DataCellHeaders_2-2

281:


HeaderScope_2-2

282:


new_form2-3

282:


DataCellHeaders_2-2

282:


HeaderScope_2-2

282:


OnMouseMovement_2-4

283:


new_form2-3

283:


OnMouseMovement_2-4

283:


OnBlurOnFocus_2-4

283:


new_IDReporter2-3

284:


ImgMissingAlt_2-1

284:


new_form2-3

284:


DataCellHeaders_2-2

284:


OnMouseMovement_2-4

285:


DataCellHeaders_2-2

286:


new_form2-3

286:


DataCellHeaders_2-2

286:


OnBlurOnFocus_2-4

287:


DataCellHeaders_2-2

287:


new_IDReporter2-3

288:


new_form2-3

288:


DataCellHeaders_2-2

289:


new_form2-3

289:


DataCellHeaders_2-2

290:


DataCellHeaders_2-2

291:


DataCellHeaders_2-2

293:


new_form2-3

293:


DataCellHeaders_2-2

293:


OnBlurOnFocus_2-4

293:


new_IDReporter2-3

294:


new_form2-3

294:


DataCellHeaders_2-2

295:


DataCellHeaders_2-2

295:


OnBlurOnFocus_2-4

296:


new_form2-3

296:


DataCellHeaders_2-2

297:


DataCellHeaders_2-2

298:


ImgMissingAlt_2-1

298:


new_form2-3

298:


DataCellHeaders_2-2

298:


OnBlurOnFocus_2-4

299:


DataCellHeaders_2-2

299:


OnBlurOnFocus_2-4

300:


new_form2-3

300:


DataCellHeaders_2-2

302:


new_form2-3

302:


DataCellHeaders_2-2

303:


new_form2-3

303:


DataCellHeaders_2-2

303:


OnBlurOnFocus_2-4

304:


DataCellHeaders_2-2

305:


DataCellHeaders_2-2

305:


new_IDReporter2-3

306:


new_form2-3

306:


DataCellHeaders_2-2

307:


DataCellHeaders_2-2

308:


ImgMissingAlt_2-1

308:


new_form2-3

308:


DataCellHeaders_2-2

308:


OnBlurOnFocus_2-4

309:


new_form2-3

309:


DataCellHeaders_2-2

309:


OnBlurOnFocus_2-4

310:


new_form2-3

310:


new_IDReporter2-3

311:


DataCellHeaders_2-2

313:


new_form2-3

313:


OnBlurOnFocus_2-4

316:


new_form2-3

316:


OnBlurOnFocus_2-4

316:


new_IDReporter2-3

317:


new_form2-3

318:


new_form2-3

318:


OnMouseMovement_2-4

319:


OnMouseMovement_2-4

319:


OnBlurOnFocus_2-4

320:


OnMouseMovement_2-4

321:


OnMouseMovement_2-4

322:


OnMouseMovement_2-4

323:


new_IDReporter2-3

326:


new_form2-3

326:


OnBlurOnFocus_2-4

329:


OnBlurOnFocus_2-4

329:


new_IDReporter2-3

330:


new_form2-3

330:


OnBlurOnFocus_2-4

331:


OnMouseMovement_2-4

332:


new_form2-3

332:


OnMouseMovement_2-4

332:


OnBlurOnFocus_2-4

333:


new_form2-3

333:


OnMouseMovement_2-4

333:


OnBlurOnFocus_2-4

334:


OnMouseMovement_2-4

337:


TableSummary_2-2

337:


new_IDReporter2-3

339:


new_IDReporter2-3

340:


TableSummary_2-2

340:


HeaderScope_2-2

340:


new_IDReporter2-3

341:


HeaderScope_2-2

341:


OnMouseMovement_2-4

342:


new_form2-3

342:


HeaderScope_2-2

342:


OnMouseMovement_2-4

342:


OnBlurOnFocus_2-4

343:


new_form2-3

343:


HeaderScope_2-2

343:


OnMouseMovement_2-4

343:


OnBlurOnFocus_2-4

344:


HeaderScope_2-2

344:


OnMouseMovement_2-4

345:


HeaderScope_2-2

346:


HeaderScope_2-2

347:


new_form2-3

347:


HeaderScope_2-2

347:


OnBlurOnFocus_2-4

348:


HeaderScope_2-2

349:


HeaderScope_2-2

349:


new_IDReporter2-3

350:


new_form2-3

350:


TableSummary_2-2

350:


HeaderScope_2-2

350:


OnBlurOnFocus_2-4

350:


new_IDReporter2-3

352:


new_form2-3

352:


OnBlurOnFocus_2-4

353:


HeaderScope_2-2

355:


new_form2-3

355:


OnBlurOnFocus_2-4

355:


new_IDReporter2-3

357:


new_IDReporter2-3

360:


new_form2-3

360:


OnBlurOnFocus_2-4

361:


new_form2-3

364:


new_form2-3

364:


OnBlurOnFocus_2-4

367:


new_form2-3

367:


OnBlurOnFocus_2-4

368:


OnBlurOnFocus_2-4

370:


OnMouseMovement_2-4

371:


DataCellHeaders_2-2

371:


OnMouseMovement_2-4

372:


OnMouseMovement_2-4

373:


OnMouseMovement_2-4

374:


new_IDReporter2-3

375:


DataCellHeaders_2-2

377:


new_form2-3

377:


OnMouseMovement_2-4

377:


OnBlurOnFocus_2-4

378:


OnMouseMovement_2-4

379:


DataCellHeaders_2-2

379:


OnMouseMovement_2-4

380:


OnMouseMovement_2-4

381:


new_form2-3

381:


OnBlurOnFocus_2-4

383:


DataCellHeaders_2-2

384:


new_form2-3

384:


OnBlurOnFocus_2-4

387:


DataCellHeaders_2-2

391:


DataCellHeaders_2-2

395:


DataCellHeaders_2-2

397:


OnBlurOnFocus_2-4

399:


DataCellHeaders_2-2

403:


DataCellHeaders_2-2

407:


DataCellHeaders_2-2

407:


OnBlurOnFocus_2-4

411:


DataCellHeaders_2-2

414:


new_IDReporter2-3

415:


DataCellHeaders_2-2

419:


new_form2-3

419:


DataCellHeaders_2-2

423:


DataCellHeaders_2-2

427:


DataCellHeaders_2-2

431:


DataCellHeaders_2-2

433:


OnBlurOnFocus_2-4

435:


DataCellHeaders_2-2

439:


DataCellHeaders_2-2

443:


DataCellHeaders_2-2

447:


DataCellHeaders_2-2

451:


DataCellHeaders_2-2

455:


DataCellHeaders_2-2

459:


DataCellHeaders_2-2

463:


DataCellHeaders_2-2

467:


DataCellHeaders_2-2

471:


DataCellHeaders_2-2

475:


DataCellHeaders_2-2

479:


DataCellHeaders_2-2

483:


DataCellHeaders_2-2

487:


DataCellHeaders_2-2

491:


DataCellHeaders_2-2

495:


DataCellHeaders_2-2

499:


DataCellHeaders_2-2

503:


DataCellHeaders_2-2

507:


DataCellHeaders_2-2

511:


DataCellHeaders_2-2

515:

1.3.1 T4 T5 T6: If data table, data cells should have HEADERS attribute to list the IDs of the header cells. Screen Reader test re

Date post:	25-Jan-2021
Category:	Documents
Upload:	others
View:	1 times
Download:	0 times

Accessibility Report for 'XYZ' web site · Web view[14] 1.1.1 T1: The ALT attribute must be defined...

Documents