UNICOM Intelligence web player and W3C compliance
World Wide Web Consortium (W3C) compliance guidelines covers a wide range of recommendations for making Web content more accessible. Following these guidelines will make content accessible to a wider range of people with disabilities, including blindness and low vision, deafness and hearing loss, learning disabilities, cognitive limitations, limited movement, speech disabilities, photo-sensitivity, and combinations of these. Following these guidelines will also often make Web content generally more usable.
Test objective
Run tests against the UNICOM Intelligence Web player, check for current W3C compliance, and determine the level of W3C compliance.
Testing tools
The following test tools were used to perform tests.
▪Eclipse ACTF aDesigner: After each Web page has loaded, the Visualize blind usability is used to view the Web page errors.
▪Axe DevTools browser extension: After each Web page is loaded, the browser’s Developer Tools are loaded to view the issues.
Test environment
Server
Operating system: Microsoft Windows Server Data Center 2016 (x64 64-bit)
Desktop
Operating system: Microsoft Windows 10 64-bit
aDesigner 1.4.0
axe Version 4.20.2
Test data
A test project named ALLTYPE.mdd was use for testing. The test project covered most UNICOM Intelligence question types and Web page controls. The UNICOM Intelligence generated Web controls and elements were tested. As a result, no question or layout templates were used for the test project.
Test approach
The test project consisted of 22 pages (include Authentication and End pages). Each page displayed one question or question group (such as loop, compound, and page). The project was activated against a UNICOM Intelligence 7.5.1 server with sample management. Eclipse ACTF aDesigner was used to analyze the Web survey and record all errors in each page. Each page contained all possible options for the particular question or page type (for example, controls for Previous, Next, First, Last, Goto, Stop, and so on). The following pages were analyzed:
|
Authentication
|
Date and time question
|
|
Single response question
|
Display
|
|
Multiple response question
|
Loop (mixed question types)
|
|
Single response grid
|
Block
|
|
Multiple response grid
|
Single response (multiple columns)
|
|
Numeric response grid
|
Multiple response (multiple columns)
|
|
Multiple response grid
|
Single response (dropdown list)
|
|
Text response grid
|
Multiple response (list box)
|
|
True or false question
|
Text question (multiple line)
|
|
Numeric question
|
Page
|
|
Text question
|
End
|
Test results
Six issues were discovered after testing. The issues will be addressed in a future UNICOM Intelligence release.
1 There is no associated label element or title attribute to identify the form control.
Error page: All pages
Against guidelines:
WCAG 2.0: 1.1.1 – All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below. (Level A)
WCAG 2.0: 1.3.1 – Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A)
WCAG 2.0: 3.3.2 – Labels or instructions are provided when content requires user input. (Level A)
WCAG 2.0: 4.1.2 – For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. (Level A)
2 Identify the human language of the content by providing xml:lang attribute (for example, <html xml:lang="en">)
Error pages: All pages
Against guideline:
WCAG 2.0: 3.1.1 – The default human language of each Web page can be programmatically determined. (Level A)
3 Make sure that any group of input elements of type="radio" or type="checkbox" with the same name attribute is contained within a fieldset element.
Error pages: Single Response Question, Multiple Response Question, Single Response Grid Question, Multiple Response Grid Question, True Or False Question, Compound, Loop, Block, Page
Against guidelines:
WCAG 2.0: 1.3.1 – Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A)
WCAG 2.0: 3.3.2 – Labels or instructions are provided when content requires user input. (Level A)
4 Use measurements that are relative to other measurements in the content for the font size.
Error page: Authentication
Against guideline:
WCAG 2.0: 1.4.4 – Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality. (Level AA)
5 Provide skip-links such as “skip to main”.
Error page: Compound
Against guideline:
WCAG 2.0: 2.4.1 – A mechanism is available to bypass blocks of content that are repeated on multiple Web pages. (Level A)
6 Include a document title that is non‑empty.
Error page: End
Against guideline:
WCAG 2.0: 2.4.2 – Web pages have titles that describe topic or purpose. (Level A)
See