Difference between revisions of "Hornbill WCAG 2.0 Status"

From Hornbill
Jump to navigation Jump to search
(Created page with " = Accessibility Evaluation Report for WCAG 2.0 = == 1. Executive Summary == This report describes the conformance of the Hornbill Collaboration Core and its applications...")
 
 
(7 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 +
This document can now be found at its new location in the [https://docs.hornbill.com/esp-fundamentals/about/accessibility-report-wcag-2-2 Hornbill Document Library].
  
−
= Accessibility Evaluation Report for WCAG 2.0 =
+
[[file:hornbill-document-library.png|Latest WCAG Report|link=https://docs.hornbill.com/esp-fundamentals/about/accessibility-report-wcag-2-2]]
−
 
+
<!--
−
== 1. Executive Summary ==
 
−
 
−
This report describes the conformance of the Hornbill Collaboration Core and its applications with W3C&#39;s Web Content Accessibility Guidelines (WCAG) 2.0. The Success Criteria (checklist) is described in Section 5 bellow and is based on the Success Criteria check list provided by W3C ( https://www.w3.org/TR/2006/WD-WCAG20-20060427/appendixB.html )
 
  
−
 
+
Click on the following link to read our latest WCAG Report: https://docs.hornbill.com/esp-fundamentals/about/accessibility-report-wcag-2-2
−
== 2. Web Site Reviewed ==
 
−
 
−
* http://live.hornbill.com/INSTANCE_NAME/
 
−
* November 22, 2017
 
−
* English
 
−
 
 
−
== 3. Reviewer ==
 
−
 
−
* Daniel Dekel - Principal Web Developer
 
−
* Hornbill Technologies Limited
 
−
 
 
−
== 4. Review Process ==
 
−
 
−
* WCAG 2.0 Level 1 (A), Level 2 (AA) and Level 3 (AAA)
 
−
* Used HTMLHint (http://htmlhint.com/) to validate the HTML Content of all our source code
 
−
* Used W3C Checklist and Overview (https://www.w3.org/TR/UNDERSTANDING-WCAG20/) (Section 5)
 
−
* Made a manual review to our source code and our run-time environment
 
−
 
 
−
== 5. Check List ==
 
−
 
−
=== Level 1 (A) ===
 
−
 
−
=== Guide 1.1: Provide text alternatives for all non-text content ===
 
−
 
−
1.1.1 For all non-text content:
 
  
−
+
<h1>Accessibility Evaluation Report for WCAG 2.0</h1>
−
* Non-text content presents information or responds to user input, text alternatives serve the same purpose and present the same information as the non-text content. If text alternatives cannot serve the same purpose, then text alternatives at least identify the purpose of the non-text content.
 
−
* Non-text content is pure decoration, or used only for visual formatting, or if it is not presented to users, it is implemented such that it can be ignored by assistive technology
 
−
 
−
=== Guideline 1.2 : Provide synchronized alternatives for multimedia ===
 
−
 
−
1.2.1 - Captions are provided for prerecorded multimedia
 
  
−
+
<h2>&nbsp;</h2>
−
''Youtube videos are provided with captions''
 
  
−
+
<h2>1. Executive Summary</h2>
−
1.2.2 - Audio descriptions of video, or a full multimedia text alternative including any interaction, are provided for prerecorded multimedia
 
  
−
+
<p>This report describes the conformance of the Hornbill Collaboration Core and its applications with W3C&#39;s Web Content Accessibility Guidelines (WCAG) 2.0. The Success Criteria (checklist) is described in Section 5 bellow and is based on the Success Criteria check list provided by W3C (&nbsp;https://www.w3.org/TR/2006/WD-WCAG20-20060427/appendixB.html )</p>
−
''Most videos are tutorial videos showing screen captures that about new features. These can be easily understood without audio.''
 
  
−
+
<h2>&nbsp;</h2>
−
=== Guideline 1.3 : Ensure that information and structure can be separated from presentation ===
 
−
 
−
1.3.1 Information and relationships conveyed through presentation can be programmatically determined, and notification of changes to these is available to user agents, including assistive technologies
 
  
−
+
<h2>2. Last Reviewed</h2>
−
''We use basic html markup including headings, hyperlinks and logical DOM structure flow so that the screen reader will follow that easily.''
 
  
−
+
<ul>
−
1.3.2 Any information that is conveyed by color is also visually evident without color
+
<li>http://live.hornbill.com/INSTANCE_NAME/</li>
 +
<li>January 4, 2018</li>
 +
<li>English</li>
 +
</ul>
  
−
+
<h2>&nbsp;</h2>
−
''In most cases it is true however sin some scenarios like background colours to show a status in a row for example, there is no alternative.''
 
  
−
+
<h2>3. Reviewer</h2>
−
1.3.3 When the sequence of the content affects its meaning, that sequence can be programmatically determined.
 
  
−
+
<ul>
−
''In some cases we have information and actions that are aligned to the right for example, that will be sill available for screen readers, however, we do not provide a context for these actions and for the visually impaired person it will look the same.''
+
<li>Daniel Dekel -&nbsp;Principal Web Developer</li>
 +
<li>Hornbill Technologies Limited</li>
 +
</ul>
  
−
+
<h2>&nbsp;</h2>
−
=== Guideline 2.1 : Make all functionality operable via a keyboard interface ===
 
−
 
−
2.1.1 All functionality of the content is operable in a non-time-dependent manner through a keyboard interface, except where the task requires analog, time-dependent input.
 
  
−
+
<h2>4. Review Process</h2>
−
Note: This does not preclude and should not discourage the support of other input methods (such as a mouse) in addition to keyboard operation.
 
  
−
+
<ul>
−
''We do have shortcuts to access specific areas, to focus on common elements and focusable elements that allows easy navigation. There are sill areas in the product that are not very easy to navigate and these can be improved.''
+
<li>WCAG 2.0 Level 1 (A), Level 2 (AA)&nbsp;and Level 3 (AAA)</li>
 +
<li>Used HTMLHint (http://htmlhint.com/) to validate the HTML Content of all our source code</li>
 +
<li>Used W3C Checklist and Overview (https://www.w3.org/TR/UNDERSTANDING-WCAG20/) (Section 5)</li>
 +
<li>Made a manual review to our source code and our run-time environment</li>
 +
</ul>
  
−
+
<h2>&nbsp;</h2>
−
=== Guideline 2.2 : Allow users to control time limits on their reading or interaction ===
 
−
 
−
2.2.1 For each time-out that is a function of the content
 
  
−
+
<h2>5. Summary&nbsp;and Recommended Actions</h2>
−
''The time-out is set to a high number in the server. It can not be changed but it is sufficient for anyone to work without risk of loosing data.''
 
  
−
+
<h3><strong>Results for Level 1 (A):</strong></h3>
−
=== Guideline 2.3 : Allow users to avoid content that could cause seizures due to photosensitivity ===
 
−
 
−
2.3.1 Content does not violate the general flash threshold or the red flash threshold
 
  
−
+
<p>There are <strong>18</strong> checks in total for Level 1</p>
−
''The application does not display flashing elements on the screen. Popups are used with low contrasts and no red colours are used as a popup.''
 
  
−
+
<p><span style="color:#008000"><strong>14</strong></span> are fully met. <span style="color:#daa520"><strong>4</strong></span> are partially met.</p>
−
=== Guideline 2.4 : Provide mechanisms to help users find content, orient themselves within it, and navigate through it ===
 
−
 
−
2.4.1 A mechanism is available to bypass blocks of content that are repeated on multiple Web units
 
  
−
+
<p>In all the 5 cases that are partially or not meeting the success criteria, can be easily implemented.</p>
−
''There is a common menu that is available in all Web Units as well as shortcuts to navigate to that menu.''
 
  
−
+
<h3><strong>Results for Level 2 (AA):</strong></h3>
−
=== Guideline 2.5 : Help users avoid mistakes and make it easy to correct mistakes that do occur ===
 
−
 
−
2.5.1 If an input error is detected, the error is identified and described to the user in text
 
  
−
+
<p>There are <strong>15</strong> checks in total for Level 2</p>
−
''Errors are displayed to the user if occur. ''
 
  
−
+
<p><span style="color:#008000"><strong>9</strong></span> are fully met. <span style="color:#daa520"><strong>5</strong></span> are partially met and <span style="color:#a52a2a"><strong>1</strong></span>&nbsp;is not.</p>
−
=== Guideline 3.1 : Make text content readable and understandable. ===
 
−
 
−
3.1.1 The primary natural language or languages of the Web unit can be programmatically determined
 
  
−
+
<p>In <span style="color:#daa520">4</span> cases that are partially meeting the success criteria can be easily implemented.</p>
−
''Not possible, but it should be simple to implement''
 
  
−
+
<h3><strong>Results for Level 3 (AAA):</strong></h3>
−
=== Guideline 3.2 : Make the placement and functionality of content predictable. ===
 
−
 
−
3.2.1 When any component receives focus, it does not cause a change of context.
 
  
−
+
<p>There are <strong>21</strong>&nbsp;checks in total for Level 3</p>
−
''No components change context when setting focus.''
 
  
−
+
<p><span style="color:#008000"><strong>6</strong></span> are fully met. <span style="color:#daa520"><strong>4</strong></span> are partially met and <span style="color:#a52a2a"><strong>11</strong></span>&nbsp;are not.</p>
−
3.2.2 Changing the setting of any form control or field does not automatically cause a change of context (beyond moving to the next field in tab order), unless the authored unit contains instructions before the control that describe the behavior.
 
  
−
+
<p>In most cases of the partially or not meeting the success criteria&nbsp;will be difficult to implement.</p>
−
''I general the context of a form is not changed, however there are a few exceptions in Service Manager when filling fields in a progressive capture depending on the selected input, the form can switch to a different form. This has been changed and new forms are not doing this any more. New forms are now adding fields but the context of the form remains the same.''
 
  
−
+
<h3>&nbsp;</h3>
−
=== Guideline 4.1 : Support compatibility with current and future user agents (including assistive technologies) ===
 
−
 
−
4.1.1 Web units or authored components can be parsed unambiguously, and the relationships in the resulting data structure are also unambiguous
 
  
−
+
<h3><strong>General</strong></h3>
−
''We have a very well defined and valid markup content. We use automated tools to make sure these are valid.''
 
  
−
+
<p>Markup changes are relatively easy to improve. Multi-Language requirements can also be easily improved.</p>
−
4.1.2 For all user interface components, the name and role can be programmatically determined, 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
 
  
−
+
<p>Colour restrictions (like Luminosity Contrast Ratio) can be implemented by adding an extra style for people with partial sight allowing then to use that style in their profile settings (acceptance 4.2.1 and 4.2.3)</p>
−
''We use standard libraries to display more sophisticated controls therefore in most cases these controls will have proper role and naming identifications. There can be some components that are not properly defined and when these are identified we can add the extra information to meet this requirement.''
 
  
−
+
<p>Supplementary linguistic or illustrative help will be difficult to implement as it requires an addition of manpower time to each one of the new and old tasks.</p>
−
=== Guideline 4.2 : Ensure that content is accessible or provide an accessible alternative ===
 
−
 
−
4.2.1 At least one version of the content meets all level 1 success criteria, but alternate version(s) that do not meet all level 1 success criteria may be available from the same URI.
 
  
−
+
<p>&nbsp;</p>
−
''We have one version that meets all Level 1 success criteria''
 
  
−
+
<h2>7. Summary Check List</h2>
−
4.2.2 Content meets the following criteria even if the content uses a technology that is not in the chosen baseline:
 
  
−
+
<table border="0" cellpadding="1" cellspacing="1" style="width:500px">
−
* If content can be entered using the keyboard, then the content can be exited using the keyboard.
+
<tr>
−
* Content conforms to success criterion 2.3.1 (general and red flash).
+
<td style="background-color:#c6eed3; text-align:center; width:90px"><span style="font-size:11px">Fully Met</span></td>
−
+
<td style="background-color:#dba828; text-align:center; width:90px"><span style="font-size:11px">Partially Met</span></td>
−
''Both criteria is meet.''
+
<td style="background-color:#ff8c76; text-align:center; width:90px"><span style="font-size:11px">Not Met</span></td>
 +
</tr>
 +
</table>
  
−
 
+
<table border="0" cellpadding="1" cellspacing="3" style="width:100%">
−
=== Level 2 (AA) ===
+
<tr>
−
+
<th scope="col" style="background-color:#a0a0a0; vertical-align:middle">
−
=== Guideline 1.2 : Provide synchronized alternatives for multimedia ===
+
<h3><span style="color:#ffffff"><strong><span style="font-size:11px">Principles</span></strong></span></h3>
−
+
</th>
−
1.2.3 Audio descriptions of video are provided for prerecorded multimedia.
+
<th scope="col" style="background-color:#a0a0a0; vertical-align:middle">
 +
<h3><span style="color:#ffffff"><strong><span style="font-size:11px">Guidelines</span></strong></span></h3>
 +
</th>
 +
<th scope="col" style="background-color:#a0a0a0; vertical-align:middle; white-space:nowrap">
 +
<h3><span style="color:#ffffff"><strong><span style="font-size:11px">Level A</span></strong></span></h3>
 +
</th>
 +
<th scope="col" style="background-color:#a0a0a0; vertical-align:middle; white-space:nowrap">
 +
<h3><span style="color:#ffffff"><strong><span style="font-size:11px">Level AA</span></strong></span></h3>
 +
</th>
 +
<th scope="col" style="background-color:#a0a0a0; vertical-align:middle; white-space:nowrap">
 +
<h3><span style="color:#ffffff"><strong><span style="font-size:11px">Level AAA</span></strong></span></h3>
 +
</th>
 +
</tr>
 +
<tr>
 +
<td colspan="1" rowspan="6" style="background-color:#c6c6c8; text-align:center"><span style="font-size:11px">1</span></td>
 +
<td style="background-color:#eeeeee">
 +
<p><span style="font-size:11px">1.1: Provide text alternatives for all non-text content</span></p>
 +
</td>
 +
<td style="background-color:#c6eed3"><span style="font-size:11px">1.1.1</span></td>
 +
<td>&nbsp;</td>
 +
<td>&nbsp;</td>
 +
</tr>
 +
<tr>
 +
<td style="background-color:#eeeeee">
 +
<p><span style="font-size:11px">1.2&nbsp;: Provide synchronized alternatives for multimedia</span></p>
 +
</td>
 +
<td style="background-color:#c6eed3; white-space:nowrap"><span style="font-size:11px">1.2.1-1.2.2</span></td>
 +
<td style="background-color:#ff8c76"><span style="font-size:11px">1.2.3</span></td>
 +
<td style="background-color:#ff8c76; white-space:nowrap"><span style="font-size:11px">1.2.5-1.2.7</span></td>
 +
</tr>
 +
<tr>
 +
<td colspan="1" rowspan="2" style="background-color:#eeeeee">
 +
<p><span style="font-size:11px">1.3&nbsp;: Ensure that information and structure can be separated from presentation</span></p>
 +
</td>
 +
<td style="background-color:#c6eed3"><span style="font-size:11px">1.3.1</span></td>
 +
<td style="background-color:#c6eed3; white-space:nowrap"><span style="font-size:11px">1.3.4-1.3.5</span></td>
 +
<td>&nbsp;</td>
 +
</tr>
 +
<tr>
 +
<td style="background-color:#dba828"><span style="font-size:11px">1.3.2-1.3.3</span></td>
 +
<td>&nbsp;</td>
 +
<td>&nbsp;</td>
 +
</tr>
 +
<tr>
 +
<td colspan="1" rowspan="2" style="background-color:#eeeeee">
 +
<p><span style="font-size:11px">1.4&nbsp;: Make it easy to distinguish foreground information from its background</span></p>
 +
</td>
 +
<td>&nbsp;</td>
 +
<td style="background-color:#dba828"><span style="font-size:11px">1.4.1</span></td>
 +
<td style="background-color:#ff8c76"><span style="font-size:11px">1.4.3</span></td>
 +
</tr>
 +
<tr>
 +
<td>&nbsp;</td>
 +
<td style="background-color:#c6eed3"><span style="font-size:11px">1.4.2</span></td>
 +
<td style="background-color:#c6eed3"><span style="font-size:11px">1.4.4</span></td>
 +
</tr>
 +
<tr>
 +
<td colspan="1" rowspan="8" style="background-color:#c6c6c8; text-align:center"><span style="font-size:11px">2</span></td>
 +
<td style="background-color:#eeeeee">
 +
<p><span style="font-size:11px">2.1&nbsp;: Make all functionality operable via a keyboard interface</span></p>
 +
</td>
 +
<td style="background-color:#dba828"><span style="font-size:11px">2.1.1</span></td>
 +
<td>&nbsp;</td>
 +
<td style="background-color:#ff8c76"><span style="font-size:11px">2.1.2</span></td>
 +
</tr>
 +
<tr>
 +
<td colspan="1" rowspan="2" style="background-color:#eeeeee">
 +
<p><span style="font-size:11px">2.2&nbsp;: Allow users to control time limits on their reading or interaction</span></p>
 +
</td>
 +
<td style="background-color:#c6eed3"><span style="font-size:11px">2.2.1</span></td>
 +
<td style="background-color:#c6eed3"><span style="font-size:11px">2.2.2</span></td>
 +
<td style="background-color:#c6eed3"><span style="font-size:11px">2.2.4</span></td>
 +
</tr>
 +
<tr>
 +
<td>&nbsp;</td>
 +
<td style="background-color:#dba828"><span style="font-size:11px">2.2.3</span></td>
 +
<td style="background-color:#ff8c76"><span style="font-size:11px">2.2.5-2.2.6</span></td>
 +
</tr>
 +
<tr>
 +
<td style="background-color:#eeeeee">
 +
<p><span style="font-size:11px">2.3&nbsp;: Allow users to avoid content that could cause seizures due to photosensitivity</span></p>
 +
</td>
 +
<td style="background-color:#c6eed3"><span style="font-size:11px">2.3.1</span></td>
 +
<td>&nbsp;</td>
 +
<td style="background-color:#c6eed3"><span style="font-size:11px">2.3.2</span></td>
 +
</tr>
 +
<tr>
 +
<td colspan="1" rowspan="3" style="background-color:#eeeeee">
 +
<p><span style="font-size:11px">2.4&nbsp;: Provide mechanisms to help users find content, orient themselves within it, and navigate through it</span></p>
 +
</td>
 +
<td style="background-color:#c6eed3">
 +
<p><span style="font-size:11px">2.4.1</span></p>
 +
</td>
 +
<td style="background-color:#c6eed3">
 +
<p><span style="font-size:11px">2.4.3-2.4.4</span></p>
 +
</td>
 +
<td style="background-color:#c6eed3">
 +
<p><span style="font-size:11px">2.4.5</span></p>
 +
</td>
 +
</tr>
 +
<tr>
 +
<td>&nbsp;</td>
 +
<td>&nbsp;</td>
 +
<td style="background-color:#dba828"><span style="font-size:11px">2.4.6-2.4.7</span></td>
 +
</tr>
 +
<tr>
 +
<td>&nbsp;</td>
 +
<td>&nbsp;</td>
 +
<td style="background-color:#ff8c76"><span style="font-size:11px">2.4.8</span></td>
 +
</tr>
 +
<tr>
 +
<td style="background-color:#eeeeee">
 +
<p><span style="font-size:11px">2.5&nbsp;: Help users avoid mistakes and make it easy to correct mistakes that do occur</span></p>
 +
</td>
 +
<td style="background-color:#c6eed3">
 +
<p><span style="font-size:11px">2.5.1</span></p>
 +
</td>
 +
<td style="background-color:#c6eed3">
 +
<p><span style="font-size:11px">2.5.2-2.5.3</span></p>
 +
</td>
 +
<td style="background-color:#dba828">
 +
<p><span style="font-size:11px">2.5.4</span></p>
 +
</td>
 +
</tr>
 +
<tr>
 +
<td colspan="1" rowspan="5" style="background-color:#c6c6c8">
 +
<p style="text-align:center"><span style="font-size:11px">3</span></p>
 +
</td>
 +
<td colspan="1" rowspan="3" style="background-color:#eeeeee">
 +
<p><span style="font-size:11px">3.1&nbsp;: Make text content readable and understandable.</span></p>
 +
</td>
 +
<td style="background-color: rgb(198, 238, 211);">
 +
<p><span style="font-size:11px">3.1.1</span></p>
 +
</td>
 +
<td style="background-color:#dba828">
 +
<p><span style="font-size:11px">3.1.2</span></p>
 +
</td>
 +
<td style="background-color:#dba828">
 +
<p><span style="font-size:11px">3.1.3</span></p>
 +
</td>
 +
</tr>
 +
<tr>
 +
<td>&nbsp;</td>
 +
<td>&nbsp;</td>
 +
<td style="background-color:#c6eed3"><span style="font-size:11px">3.1.4</span></td>
 +
</tr>
 +
<tr>
 +
<td>&nbsp;</td>
 +
<td>&nbsp;</td>
 +
<td style="background-color:#ff8c76"><span style="font-size:11px">3.1.5-3.1.6</span></td>
 +
</tr>
 +
<tr>
 +
<td colspan="1" rowspan="2" style="background-color:#eeeeee">
 +
<p><span style="font-size:11px">3.2&nbsp;: Make the placement and functionality of content predictable</span></p>
 +
</td>
 +
<td style="background-color:#c6eed3">
 +
<p><span style="font-size:11px">3.2.1-3.2.2</span></p>
 +
</td>
 +
<td style="background-color:#c6eed3">
 +
<p><span style="font-size:11px">3.2.3</span></p>
 +
</td>
 +
<td style="background-color:#c6eed3">
 +
<p><span style="font-size:11px">3.2.5</span></p>
 +
</td>
 +
</tr>
 +
<tr>
 +
<td>&nbsp;</td>
 +
<td style="background-color:#dba828"><span style="font-size:11px">3.2.4</span></td>
 +
<td>&nbsp;</td>
 +
</tr>
 +
<tr>
 +
<td colspan="1" rowspan="3" style="background-color:#c6c6c8">
 +
<p style="text-align:center"><span style="font-size:11px">4</span></p>
 +
</td>
 +
<td colspan="1" rowspan="2" style="background-color:#eeeeee">
 +
<p><span style="font-size:11px">4.1&nbsp;: Support compatibility with current and future user agents (including assistive technologies)</span></p>
 +
</td>
 +
<td style="background-color:#c6eed3">
 +
<p><span style="font-size:11px">4.1.1</span></p>
 +
</td>
 +
<td>
 +
<p>&nbsp;</p>
 +
</td>
 +
<td>
 +
<p>&nbsp;</p>
 +
</td>
 +
</tr>
 +
<tr>
 +
<td style="background-color:#dba828">
 +
<p><span style="font-size:11px">4.1.2</span></p>
 +
</td>
 +
<td>
 +
<p>&nbsp;</p>
 +
</td>
 +
<td>
 +
<p>&nbsp;</p>
 +
</td>
 +
</tr>
 +
<tr>
 +
<td style="background-color:#eeeeee">
 +
<p><span style="font-size:11px">4.2&nbsp;: Ensure that content is accessible or provide an accessible alternative</span></p>
 +
</td>
 +
<td style="background-color:#c6eed3"><span style="font-size:11px">4.2.1-4.2.2</span></td>
 +
<td style="background-color:#dba828"><span style="font-size:11px">4.2.3</span></td>
 +
<td style="background-color:#dba828"><span style="font-size:11px">4.2.4</span></td>
 +
</tr>
 +
</table>
  
−
+
<p>&nbsp;</p>
−
''No''
 
  
−
+
<h2>7. Detailed Check List</h2>
−
=== Guideline 1.3 : Ensure that information and structure can be separated from presentation ===
 
−
 
−
1.3.4 Information that is conveyed by variations in presentation of text is also conveyed in text, or the variations in presentation of text can be programmatically determined.
 
  
−
+
<h3><strong><u>Level 1 (A)</u></strong></h3>
−
''Textual information can be programmatically determined by the markup language.''
 
  
−
+
<h3><strong>Guide 1.1: Provide text alternatives for all non-text content</strong></h3>
−
1.3.5 Information required to understand and operate content does not rely on shape, size, visual location, or orientation of components.
 
  
−
+
<p>1.1.1&nbsp;For all&nbsp;non-text content:</p>
−
''We use markup to define importance in the content as H1, H2, Strong, etc... ''
 
  
−
+
<ul>
−
=== Guideline 1.4 : Make it easy to distinguish foreground information from its background ===
+
<li>Non-text content presents information or responds to user input,&nbsp;text alternatives&nbsp;serve the same purpose and present the same information as the non-text content. If text alternatives cannot serve the same purpose, then text alternatives at least identify the purpose of the non-text content.</li>
−
+
<li>Non-text content is&nbsp;pure decoration, or used only for visual formatting, or if it is not presented to users, it is implemented such that it can be ignored by&nbsp;assistive technology</li>
−
1.4.1 Text or diagrams, and their background, have a luminosity contrast ratio of at least 5:1
+
</ul>
  
−
+
<h3><strong>Guideline 1.2&nbsp;: Provide synchronized alternatives for multimedia</strong></h3>
−
''It passes in most cases except in some hyperlinks where the background colour is light grey the ratio is 4.18:1''
 
  
−
+
<p>1.2.1 -&nbsp;Captions&nbsp;are provided for prerecorded&nbsp;multimedia</p>
−
1.4.2 A mechanism is available to turn off background audio that plays automatically, without requiring the user to turn off all audio.
 
  
−
+
<p><span style="color:#008000"><em>Youtube videos are provided with captions</em></span></p>
−
''It is possible to turn the Notifications sound off leaving other audio running without disturbance.''
 
  
−
+
<p>1.2.2 -&nbsp;Audio descriptions&nbsp;of video, or a&nbsp;full multimedia text alternative including any interaction, are provided for prerecorded&nbsp;multimedia</p>
−
=== Guideline 2.2 : Allow users to control time limits on their reading or interaction ===
 
−
 
−
2.2.2 Content does not blink for more than three seconds, or a method is available to stop all blinking content in the Web unit or authored component.
 
  
−
+
<p><span style="color:#008000"><em>Most videos are tutorial videos showing screen captures that about new features. These can be easily understood without audio.</em></span></p>
−
Note: For requirements related to flickering or flashing content, refer to Guideline 2.3 Allow users to avoid content that could cause seizures due to photosensitivity.
 
  
−
+
<h3><strong>Guideline 1.3&nbsp;: Ensure that information and structure can be separated from presentation</strong></h3>
−
''Content does not blink''
 
  
−
+
<p>1.3.1&nbsp;Information and relationships conveyed through&nbsp;presentation&nbsp;can be&nbsp;programmatically determined, and notification of changes to these is available to&nbsp;user agents, including&nbsp;assistive technologies</p>
−
2.2.3 Content can be paused by the user unless the timing or movement is part of an activity where timing or movement is essential.
 
  
−
+
<p><span style="color:#008000"><em>We use basic html markup including headings, hyperlinks and&nbsp; logical DOM structure flow so that the screen reader will follow that&nbsp; easily.</em></span></p>
−
''No - Content is automatically updated in real time and there is no option to stop that update. Pausing or stopping can result in out of date details escential for the flow. For example Activity Streams or Chat.''
 
  
−
+
<p>1.3.2&nbsp;Any&nbsp;information that is conveyed by color&nbsp;is also visually evident without color</p>
−
=== Guideline 2.4 : Provide mechanisms to help users find content, orient themselves within it, and navigate through it ===
 
−
 
−
2.4.3 Web units have titles.
 
  
−
+
<p><span style="color:#daa520"><em>In most cases it is true however sin some scenarios like background colours to show a status in a row for example, there is no alternative.</em></span></p>
−
''Yes - All our Web Units have a meaningful title''
 
  
−
+
<p>1.3.3&nbsp;When the sequence of the content affects its meaning, that sequence can be&nbsp;programmatically determined.</p>
−
2.4.4 Each link is programmatically associated with text from which its purpose can be determined.
 
  
−
+
<p><span style="color:#daa520"><em>In some cases we have information and actions that are aligned to the right for example, that will be sill available for screen readers, however, we do not provide a context for these actions and for the visually impaired person it will look the same.</em></span></p>
−
''Yes - Our links are related to text and if an image is used it will usually have a related text.''
 
  
−
+
<h3><strong>Guideline 2.1&nbsp;: Make all functionality operable via a keyboard interface</strong></h3>
−
=== Guideline 2.5 : Help users avoid mistakes and make it easy to correct mistakes that do occur ===
 
−
 
−
2.5.2 If an input error is detected and suggestions for correction are known and can be provided without jeopardizing the security or purpose of the content, the suggestions are provided to the user.
 
  
−
+
<p>2.1.1&nbsp;All&nbsp;functionality&nbsp;of the content is operable in a non-time-dependent manner through a&nbsp;keyboard interface, except where the task requires&nbsp;analog, time-dependent input.</p>
−
''Yes - Usually all forms will give a warning before submitting the data and and sometimes an error message after the submit, but in that case it will allow the user to correct without loosing the data.''
 
  
−
+
<p>Note:&nbsp;This does not preclude and should not discourage the support of other input methods (such as a mouse) in addition to keyboard operation.</p>
−
2.5.3 For forms that cause legal or financial transactions to occur, that modify or delete data in data storage systems, or that submit test responses, at least one of the following is true:
 
  
−
+
<p><span style="color:#daa520"><em>We do have shortcuts to access specific areas, to focus on common elements and focusable elements that allows easy navigation. There are sill areas in the product that are not very easy to navigate and these can be improved.</em></span></p>
−
* Actions are reversible.
 
−
* Actions are checked for input errors before going on to the next step in the process.
 
−
* The user is able to review and confirm or correct information before submitting it.
 
−
 
−
''Yes - Sometimes the action is reversible, there are input error checks and a in some cases the user is requested to confirm before performing the action''
 
  
−
+
<h3><strong>Guideline 2.2&nbsp;: Allow users to control time limits on their reading or interaction</strong></h3>
−
=== Guideline 3.1 : Make text content readable and understandable. ===
 
−
 
−
3.1.2 The natural language of each passage or phrase in the Web unit can be programmatically determined.
 
  
−
+
<p>2.2.1&nbsp;For each time-out that is a function of the content</p>
−
Note: This requirement does not apply to individual words or phrases that have become part of the primary language of the content.
 
  
−
+
<p><span style="color:#008000"><em>The time-out is set to a high number in the server. It can not be changed but it is sufficient for anyone to work without risk of loosing data.</em></span></p>
−
''Usually the entire UI is translated to the same language, however there are some exceptions:''
 
  
−
+
<h3><strong>Guideline 2.3&nbsp;: Allow users to avoid content that could cause seizures due to photosensitivity</strong></h3>
−
* ''Real time translations like in Activity Streams do not declare a lang attribute. ''
 
−
* ''Translations for that language could be missing, in that case the default language will be displayed instead.''
 
−
 
−
''When Level 1 requirement 3.1.1 is met, it should be simple to fully implement this one.''
 
  
−
+
<p>2.3.1&nbsp;Content does not violate the&nbsp;general flash threshold&nbsp;or the&nbsp;red flash threshold</p>
−
=== Guideline 3.2 : Make the placement and functionality of content predictable. ===
 
−
 
−
3.2.3 Navigational mechanisms that are repeated on multiple Web units within a set of Web units or other primary resources occur in the same relative order each time they are repeated, unless a change is initiated by the user.
 
  
−
+
<p><span style="color:#008000"><em>The application does not display flashing elements on the screen. Popups are used with low contrasts and no red colours are used as a popup.</em></span></p>
−
''The same navigation window is presented on each Web unit''
 
  
−
+
<h3><strong>Guideline 2.4&nbsp;: Provide mechanisms to help users find content, orient themselves within it, and navigate through it</strong></h3>
−
3.2.4 Components that have the same functionality within a set of Web units are identified consistently.
 
  
−
+
<p>&nbsp;2.4.1&nbsp;A mechanism is available to bypass blocks of content that are repeated on multiple&nbsp;Web units</p>
−
''Menu items have a consistent markup however, not all have a proper alt, name or role attributes''
 
  
−
+
<p><span style="color:#008000"><em>There is a common menu that is available in all Web Units as well as shortcuts to navigate to that menu.</em></span></p>
−
=== Guideline 4.2 : Ensure that content is accessible or provide an accessible alternative ===
 
−
 
−
4.2.3 At least one version of the content meets all level 2 success criteria, but alternate version(s) that do not meet all level 2 success criteria may be available from the same URI.
 
  
−
+
<h3><strong>Guideline 2.5&nbsp;: Help users avoid mistakes and make it easy to correct mistakes that do occur</strong></h3>
−
We use standard libraries that do provide support for assistive technologies (AT), however, in some cases we do create our own controls and not all support AT
 
  
−
 
+
<p>2.5.1&nbsp;If an&nbsp;input error&nbsp;is detected, the error is identified and described to the user in text</p>
−
=== Level 3 (AAA) ===
 
−
 
−
=== Guideline 1.2 : Provide synchronized alternatives for multimedia ===
 
−
 
−
1.2.5 Sign language interpretation is provided for multimedia.
 
  
−
+
<p><span style="color:#008000"><em>Errors are displayed to the user if occur.&nbsp;</em></span></p>
−
''Not available''
 
  
−
+
<h3><strong>Guideline 3.1&nbsp;: Make text content readable and understandable.</strong></h3>
−
1.2.6 Extended audio descriptions of video are provided for prerecorded multimedia.
 
  
−
+
<p>3.1.1&nbsp;The primary&nbsp;natural language&nbsp;or languages of the&nbsp;Web unit&nbsp;can be&nbsp;programmatically determined</p>
−
''Not available''
 
  
−
+
<p><span style="color:#008000"><em>Primary language is set in the document&#39;s body</em></span></p>
−
1.2.7 For prerecorded multimedia, a full multimedia text alternative including any interaction is provided.
 
  
−
+
<h3><strong>Guideline 3.2&nbsp;: Make the placement and functionality of content predictable.</strong></h3>
−
''Not available''
 
  
−
+
<p>3.2.1&nbsp;When any component receives focus, it does not cause a&nbsp;change of context.</p>
−
=== Guideline 1.4 : Make it easy to distinguish foreground information from its background ===
 
−
 
−
1.4.3 Text or diagrams, and their background, have a luminosity contrast ratio of at least 10:1
 
  
−
+
<p><span style="color:#008000"><em>No components change context when setting focus.</em></span></p>
−
''Not available''
 
  
−
+
<p>3.2.2&nbsp;Changing the setting of any form control or field does not automatically cause a&nbsp;change of context&nbsp;(beyond moving to the next field in tab order), unless the authored unit contains instructions before the control that describe the behavior.</p>
−
1.4.4 Audio content does not contain background sounds, background sounds can be turned off, or background sounds are at least 20 decibels lower than the foreground audio content, with the exception of occasional sound effects
 
  
−
+
<p><span style="color:#008000"><em>I general the context of a form is not changed, however there are a few exceptions in Service Manager when filling fields in a progressive capture depending on the selected input, the form can switch to a different form. This has been changed and new forms are not doing this any more. New forms are now adding fields but the context of the form remains the same.</em></span></p>
−
''Our audio recordings are done in an isolated environment. No background sound is recorder.''
 
  
−
+
<h3><strong>Guideline 4.1&nbsp;: Support compatibility with current and future user agents (including assistive technologies)</strong></h3>
−
=== Guideline 2.1 : Make all functionality operable via a keyboard interface ===
 
−
 
−
2.1.2 All functionality of the content is operable in a non-time-dependent manner through a keyboard interface
 
  
−
+
<p>4.1.1&nbsp;Web units&nbsp;or&nbsp;authored components&nbsp;can be&nbsp;parsed unambiguously, and the relationships in the resulting data structure are also unambiguous</p>
−
''Not all areas are reachable using the keyboard''
 
  
−
+
<p><span style="color:#008000"><em>We have a very well defined and valid markup content. We use automated tools to make sure these are valid.</em></span></p>
−
=== Guideline 2.2 : Allow users to control time limits on their reading or interaction ===
 
−
 
−
2.2.1 For each time-out that is a function of the content
 
  
−
+
<p>4.1.2&nbsp;For all user interface components, the&nbsp;name&nbsp;and&nbsp;role&nbsp;can be&nbsp;programmatically determined, values that can be set by the user can be&nbsp;programmatically set, and notification of changes to these items is available to&nbsp;user agents, including&nbsp;assistive technologies</p>
−
''The time-out is set to a high number in the server. It can not be changed but it is sufficient for anyone to work without risk of loosing data.''
 
  
−
+
<p><span style="color:#daa520"><em>We use standard libraries to display more sophisticated controls therefore in most cases these controls will have proper role and naming identifications. There can be some components that are not properly defined and when these are identified we can add the extra information to meet this requirement.</em></span></p>
−
=== Guideline 2.3 : Allow users to avoid content that could cause seizures due to photosensitivity ===
 
−
 
−
2.3.1 Content does not violate the general flash threshold or the red flash threshold
 
  
−
+
<h3><strong>Guideline 4.2&nbsp;: Ensure that content is accessible or provide an accessible alternative</strong></h3>
−
''The application does not display flashing elements on the screen. Popups are used with low contrasts and no red colours are used as a popup.''
 
  
−
+
<p>4.2.1&nbsp;At least one version of the&nbsp;content&nbsp;meets all level 1 success criteria, but&nbsp;alternate version(s)&nbsp;that do not meet all level 1 success criteria may be available from the same URI.</p>
−
=== Guideline 2.4 : Provide mechanisms to help users find content, orient themselves within it, and navigate through it ===
 
−
 
−
2.2.4 Except for real-time events, timing is not an essential part of the event or activity presented by the content.
 
  
−
+
<p><span style="color:#008000"><em>We have one version that meets all Level 1 success criteria</em></span></p>
−
''Apart of real-time events, there is no mechanism that will update based on an interval or that will require the user to meet a task in a specific time ''
 
  
−
+
<p>4.2.2&nbsp;Content&nbsp;meets the following criteria even if the content uses a technology that is not in the chosen&nbsp;baseline:</p>
−
2.2.5 Interruptions, such as updated content, can be postponed or suppressed by the user, except interruptions involving an emergency.
 
  
−
+
<ul>
−
''System auto-updates. there is no mechanism to stop events updating the interface.''
+
<li>If content can be entered using the keyboard, then the content can be exited using the keyboard.</li>
 +
<li>Content conforms to&nbsp;success criterion 2.3.1&nbsp;(general and red flash).</li>
 +
</ul>
  
−
+
<p><span style="color:#008000"><em>Both criteria is meet.</em></span></p>
−
2.2.6 When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating.
 
  
−
+
<h3>&nbsp;</h3>
−
''Not available, however, the timeout time is very long and there should be enough time to finish the task''
 
  
−
+
<h3><u><strong>Level 2 (AA)</strong></u></h3>
−
=== Guideline 2.3 : Allow users to avoid content that could cause seizures due to photosensitivity ===
 
−
 
−
2.3.2 Web units do not contain any components that flash more than three times in any 1-second period
 
  
−
+
<h3><strong>Guideline 1.2&nbsp;: Provide synchronized alternatives for multimedia</strong></h3>
−
''We do not provide any flashing components''
 
  
−
+
<p>1.2.3&nbsp;Audio descriptions&nbsp;of video are provided for prerecorded&nbsp;multimedia.</p>
−
=== Guideline 2.4 : Provide mechanisms to help users find content, orient themselves within it, and navigate through it ===
 
−
 
−
2.4.5 Titles, headings, and labels are descriptive.
 
  
−
+
<p><span style="color:#a52a2a"><em>No</em></span></p>
−
''Our titles, headings and labels are descriptive and in relation to the context''
 
  
−
+
<h3><strong>Guideline 1.3&nbsp;: Ensure that information and structure can be separated from presentation</strong></h3>
−
2.4.6 When a Web unit or authored component is navigated sequentially, components receive focus in an order that follows relationships and sequences in the content.
 
  
−
+
<p>1.3.4&nbsp;Information that is conveyed by&nbsp;variations in presentation of text&nbsp;is also conveyed in text, or the variations in presentation of text can be&nbsp;programmatically determined.</p>
−
''In most cases accessing a web units triggers a focus in an element. The element is also visually detectable. ''
 
  
−
+
<p><span style="color:#008000"><em>Textual information can be programmatically determined by the markup language.</em></span></p>
−
2.4.7 Information about the user&#39;s location within a set of Web units is available.
 
  
−
+
<p>1.3.5&nbsp;Information required to understand and operate content does not rely on shape, size, visual location, or orientation of components.</p>
−
''Despite the fact that there are no breadcrumbs, each unit has its own icon and sub-units will use the same icon to indicate the location. Also a sub-menu indicates the internal options for that unit.''
 
  
−
+
<p><span style="color:#008000"><em>We use markup to define importance in the content as H1, H2, Strong, etc...&nbsp;</em></span></p>
−
2.4.8 The purpose of each link can be programmatically determined from the link.
 
  
−
+
<h3><strong>Guideline 1.4&nbsp;: Make it easy to distinguish foreground information from its background</strong></h3>
−
''We sometimes have non-specific links saying &ldquo;click here&rdquo; or &ldquo;more&rdquo;.''
 
  
−
+
<p>1.4.1&nbsp;Text or diagrams, and their background, have a&nbsp;luminosity contrast ratio&nbsp;of at least 5:1</p>
−
=== Guideline 2.5 : Help users avoid mistakes and make it easy to correct mistakes that do occur ===
 
−
 
−
2.5.4 Context-sensitive help is available for text input.
 
  
−
+
<p><span style="color:#daa520"><em>It passes in most cases except in some hyperlinks where the background colour is light grey the ratio is 4.18:1</em></span></p>
−
''We usually display expected data format and description for the expected input.''
 
  
−
+
<p>1.4.2&nbsp;A mechanism is available to turn off background audio that plays automatically, without requiring the user to turn off all audio.</p>
−
=== Guideline 3.1 : Make text content readable and understandable. ===
 
−
 
−
3.1.3 A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon.
 
  
−
+
<p><span style="color:#008000"><em>It is possible to turn the Notifications sound off leaving other audio running without disturbance.</em></span></p>
−
''We do not provide alternative list of definitions for words or phrases''
 
  
−
+
<h3><strong>Guideline 2.2&nbsp;: Allow users to control time limits on their reading or interaction</strong></h3>
−
3.1.4 A mechanism for finding the expanded form of abbreviations is available.
 
  
−
+
<p>2.2.2&nbsp;Content does not&nbsp;blink&nbsp;for more than three seconds, or a method is available to stop all blinking content in the&nbsp;Web unit&nbsp;or&nbsp;authored component.</p>
−
''Usually if there is an abbreviation we provide titles in case the user is not familiar with it.''
 
  
−
+
<p>Note:&nbsp;For requirements related to flickering or flashing content, refer to&nbsp;Guideline 2.3 Allow users to avoid content that could cause seizures due to photosensitivity.</p>
−
3.1.5 When text requires reading ability more advanced than the lower secondary education level, supplemental content is available that does not require reading ability more advanced than the lower secondary education level
 
  
−
+
<p><span style="color:#008000"><em>Content does not blink</em></span></p>
−
''We do not provide illustrations or supplementary content to the provided one''
 
  
−
+
<p>2.2.3&nbsp;Content can be&nbsp;paused&nbsp;by the user unless the timing or movement is part of an&nbsp;activity where timing or movement is essential.</p>
−
3.1.6 A mechanism is available for identifying specific pronunciation of words where meaning cannot be determined without pronunciation.
 
  
−
+
<p><span style="color:#daa520"><em>No - Content is automatically updated in real time and there is no option to stop that update. Pausing or stopping can result in out of date details escential for the flow. For example Activity Streams or Chat.</em></span></p>
−
''We do not provide any type of glossary or voice recordings for pronunciation for words''
 
  
−
+
<h3><strong>Guideline 2.4&nbsp;: Provide mechanisms to help users find content, orient themselves within it, and navigate through it</strong></h3>
−
=== Guideline 3.2 : Make the placement and functionality of content predictable. ===
 
−
 
−
3.2.5 Changes of context are initiated only by user request
 
  
−
+
<p>2.4.3&nbsp;Web units&nbsp;have titles.</p>
−
''We do not change context without the user requesting. Context is opened in the same window unless the user requests.''
 
  
−
+
<p><span style="color:#008000"><em>Yes - All our Web Units have a meaningful&nbsp;title</em></span></p>
−
=== Guideline 4.2 : Ensure that content is accessible or provide an accessible alternative ===
 
−
 
−
4.2.4 Content implemented using technologies outside of the chosen baseline satisfies all Level 1 and Level 2 requirements supported by the technologies.
 
  
−
+
<p>2.4.4&nbsp;Each link is programmatically associated with text from which its purpose can be determined.</p>
−
We use standard libraries, however, in some cases we do create our own controls and not all satisfies Level 2 requirements.
 
  
−
 
+
<p><span style="color:#008000"><em>Yes - Our links are related to text and if an image is used it will usually have a related text.</em></span></p>
−
== 6. Results and Recommended Actions ==
 
−
 
−
=== Results for Level 1 (A): ===
 
−
 
−
There are '''18''' checks in total for Level 1
 
  
−
+
<h3><strong>Guideline 2.5&nbsp;: Help users avoid mistakes and make it easy to correct mistakes that do occur</strong></h3>
−
'''13''' are fully met. '''4''' are partially met and '''1''' is not met.
 
  
−
+
<p>2.5.2&nbsp;If an&nbsp;input error&nbsp;is detected and suggestions for correction are known and can be provided without jeopardizing the security or purpose of the content, the suggestions are provided to the user.</p>
−
In all the 5 cases that are partially or not meeting the success criteria, can be easily implemented.
 
  
−
+
<p><span style="color:#008000"><em>Yes - Usually all forms will give a warning before submitting the data and and sometimes an&nbsp;error message after the submit, but in that case it will allow the user to correct without loosing the data.</em></span></p>
−
=== Results for Level 2 (AA): ===
 
−
 
−
There are '''15''' checks in total for Level 2
 
  
−
+
<p>2.5.3&nbsp;For forms that cause legal or financial transactions to occur, that modify or delete data in data storage systems, or that submit test responses, at least one of the following is true:</p>
−
'''9''' are fully met. '''5''' are partially met and '''1''' is not.
 
  
−
+
<ul>
−
In 4 cases that are partially meeting the success criteria can be easily implemented.
+
<li>Actions are reversible.</li>
 +
<li>Actions are checked for&nbsp;input errors&nbsp;before going on to the next step in the process.</li>
 +
<li>The user is able to review and confirm or correct information before submitting it.</li>
 +
</ul>
  
−
+
<p><span style="color:#008000"><em>Yes - Sometimes the action is reversible, there are input error checks and a in some cases the user is requested to confirm before performing the action</em></span></p>
−
=== Results for Level 3 (AAA): ===
 
−
 
−
There are '''23''' checks in total for Level 3
 
  
−
+
<h3><strong>Guideline 3.1&nbsp;: Make text content readable and understandable.</strong></h3>
−
'''8''' are fully met. '''5''' are partially met and '''10''' are not.
 
  
−
+
<p>3.1.2&nbsp;The natural language of each passage or phrase in the&nbsp;Web unit&nbsp;can be&nbsp;programmatically determined.</p>
−
In most cases of the partially or not meeting the success criteria will be difficult to implement.
 
  
−
 
+
<p>Note:&nbsp;This requirement does not apply to individual words or phrases that have become part of the primary language of the content.</p>
−
=== General ===
 
−
 
−
Markup changes are relatively easy to improve. Multi-Language requirements can also be easily improved.
 
  
−
+
<p><em><span style="color:#daa520">Usually the entire UI is translated to the same language, however there are some exceptions:</span></em></p>
−
Colour restrictions (like Luminosity Contrast Ratio) can be implemented by adding an extra style for people with partial sight allowing then to use that style in their profile settings (acceptance 4.2.1 and 4.2.3)
 
  
−
+
<ul>
−
Supplementary linguistic or illustrative help will be difficult to implement as it requires an addition of manpower time to each one of the new and old tasks.
+
<li><em><span style="color:#daa520">Real time translations like in Activity Streams do not declare a lang attribute.&nbsp;</span></em></li>
 +
<li><em><span style="color:#daa520">Translations for that language could be missing, in that case the default language will be displayed instead.</span></em></li>
 +
</ul>
  
−
 
+
<p><em><span style="color:#daa520">It should be simple to fully implement this one.</span></em></p>
−
== 7. References ==
+
 
−
+
<h3><strong>Guideline 3.2&nbsp;: Make the placement and functionality of content predictable.</strong></h3>
−
* https://www.w3.org/TR/WCAG20/
+
 
−
* https://www.w3.org/TR/UNDERSTANDING-WCAG20/
+
<p>3.2.3&nbsp;Navigational mechanisms that are repeated on multiple&nbsp;Web units&nbsp;within a set of Web units or other primary resources occur in the&nbsp;same relative order&nbsp;each time they are repeated, unless a change is initiated by the user.</p>
−
* https://www.w3.org/TR/2006/WD-WCAG20-20060427/appendixB.html
+
 
 +
<p><span style="color:#008000"><em>The same navigation window is presented on each Web unit</em></span></p>
 +
 
 +
<p>3.2.4&nbsp;Components that have the&nbsp;same functionality&nbsp;within a set of&nbsp;Web units&nbsp;are identified consistently.</p>
 +
 
 +
<p><span style="color:#daa520"><em>Menu items have a&nbsp;consistent markup however, not all have a proper alt, name or role attributes</em></span></p>
 +
 
 +
<h3><strong>Guideline 4.2&nbsp;: Ensure that content is accessible or provide an accessible alternative</strong></h3>
 +
 
 +
<p>4.2.3&nbsp;At least one version of the&nbsp;content&nbsp;meets all level 2 success criteria, but&nbsp;alternate version(s)&nbsp;that do not meet all level 2 success criteria may be available from the same URI.</p>
 +
 
 +
<p><span style="color:#daa520">We use standard libraries that do provide support for assistive technologies (AT), however, in some cases we do create our own controls and not all support AT</span></p>
 +
 
 +
<h3>&nbsp;</h3>
 +
 
 +
<h3><strong><u>Level 3 (AAA)</u></strong></h3>
 +
 
 +
<h3><strong>Guideline 1.2&nbsp;: Provide synchronized alternatives for multimedia</strong></h3>
 +
 
 +
<p>1.2.5 Sign language interpretation is provided for multimedia.</p>
 +
 
 +
<p><span style="color:#b22222"><em>Not available</em></span></p>
 +
 
 +
<p>1.2.6 Extended audio descriptions of video are provided for prerecorded multimedia.</p>
 +
 
 +
<p><span style="color:#b22222"><em>Not available</em></span></p>
 +
 
 +
<p>1.2.7 For prerecorded multimedia, a full multimedia text alternative including any interaction is provided.</p>
 +
 
 +
<p><span style="color:#b22222"><em>Not available</em></span></p>
 +
 
 +
<h3><strong>Guideline 1.4&nbsp;: Make it easy to distinguish foreground information from its background</strong></h3>
 +
 
 +
<p>1.4.3 Text or diagrams, and their background, have a luminosity contrast ratio of at least 10:1</p>
 +
 
 +
<p><span style="color:#b22222"><em>Not available</em></span></p>
 +
 
 +
<p>1.4.4 Audio content does not contain background sounds, background sounds can be turned off, or background sounds are at least 20 decibels lower than the foreground audio content, with the exception of occasional sound effects</p>
 +
 
 +
<p><em><span style="color:#008000">Our audio recordings are done in an isolated environment. No background sound is recorder.</span></em></p>
 +
 
 +
<h3><strong>Guideline 2.1&nbsp;: Make all functionality operable via a keyboard interface</strong></h3>
 +
 
 +
<p>2.1.2 All functionality of the content is operable in a non-time-dependent manner through a keyboard interface</p>
 +
 
 +
<p><span style="color:#a52a2a"><em>Not all areas are reachable using the keyboard</em></span></p>
 +
 
 +
<h3><strong>Guideline 2.2&nbsp;: Allow users to control time limits on their reading or interaction</strong></h3>
 +
 
 +
<p>2.2.4&nbsp;Except for&nbsp;real-time events, timing is not an essential part of the event or activity presented by the content</p>
 +
 
 +
<p><span style="color:#008000"><em>Correct, timing&nbsp;is not necessary to perform an action</em></span></p>
 +
 
 +
<p>2.2.5&nbsp;Interruptions, such as updated content, can be postponed or suppressed by the user, except interruptions involving an&nbsp;emergency</p>
 +
 
 +
<p><span style="color:#b22222"><em>No, the user can not postpone an update coming from an event</em></span></p>
 +
 
 +
<p>2.2.6&nbsp;When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating</p>
 +
 
 +
<p><span style="color:#b22222"><em>No, the data will be lost but the timeout is very long, so there is a very small chance for data lost.</em></span></p>
 +
 
 +
<h3><strong>Guideline 2.3&nbsp;: Allow users to avoid content that could cause seizures due to photosensitivity</strong></h3>
 +
 
 +
<p>2.3.2 Web units do not contain any components that flash more than three times in any 1-second period</p>
 +
 
 +
<p><span style="color:#008000"><em>We do not provide any flashing components</em></span></p>
 +
 
 +
<h3><strong>Guideline 2.4&nbsp;: Provide mechanisms to help users find content, orient themselves within it, and navigate through it</strong></h3>
 +
 
 +
<p>2.4.5 Titles, headings, and labels are descriptive.</p>
 +
 
 +
<p><span style="color:#008000"><em>Our titles, headings and labels are descriptive and in relation to the context</em></span></p>
 +
 
 +
<p>2.4.6 When a Web unit or authored component is navigated sequentially, components receive focus in an order that follows relationships and sequences in the content.</p>
 +
 
 +
<p><span style="color:#daa520"><em>In most cases accessing a web units triggers a focus in an element. The element is also visually detectable. </em></span></p>
 +
 
 +
<p>2.4.7 Information about the user&#39;s location within a set of Web units is available.</p>
 +
 
 +
<p><span style="color:#daa520"><em>Despite the fact that there are no breadcrumbs, each unit has its own icon and sub-units will use the same icon to indicate the location. Also a sub-menu indicates the internal options for that unit.</em></span></p>
 +
 
 +
<p>2.4.8 The purpose of each link can be programmatically determined from the link.</p>
 +
 
 +
<p><span style="color:#a52a2a"><em>We sometimes have non-specific links saying &ldquo;click here&rdquo; or &ldquo;more&rdquo;.</em></span></p>
 +
 
 +
<h3><strong>Guideline 2.5&nbsp;: Help users avoid mistakes and make it easy to correct mistakes that do occur</strong></h3>
 +
 
 +
<p>2.5.4 Context-sensitive help is available for text input.</p>
 +
 
 +
<p><span style="color:#daa520"><em>We usually display expected data format and description for the expected input.</em></span></p>
 +
 
 +
<h3><strong>Guideline 3.1&nbsp;: Make text content readable and understandable.</strong></h3>
 +
 
 +
<p>3.1.3 A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon.</p>
 +
 
 +
<p><span style="color:#a52a2a"><em>We do not provide alternative list of definitions for words or phrases</em></span></p>
 +
 
 +
<p>3.1.4 A mechanism for finding the expanded form of abbreviations is available.</p>
 +
 
 +
<p><span style="color:#008000"><em>Usually if there is an abbreviation we provide titles in case the user is not familiar with it.</em></span></p>
 +
 
 +
<p>3.1.5 When text requires reading ability more advanced than the lower secondary education level, supplemental content is available that does not require reading ability more advanced than the lower secondary education level</p>
 +
 
 +
<p><em><span style="color:#a52a2a">We do not provide illustrations or supplementary content to the provided one</span></em></p>
 +
 
 +
<p>3.1.6 A mechanism is available for identifying specific pronunciation of words where meaning cannot be determined without pronunciation.</p>
 +
 
 +
<p><span style="color:#a52a2a"><em>We do not provide any type of glossary or voice recordings for pronunciation for words</em></span></p>
 +
 
 +
<h3><strong>Guideline 3.2&nbsp;: Make the placement and functionality of content predictable.</strong></h3>
 +
 
 +
<p>3.2.5 Changes of context are initiated only by user request</p>
 +
 
 +
<p><span style="color:#008000"><em>We do not change context without the user requesting. Context is opened in the same window unless the user requests.</em></span></p>
 +
 
 +
<h3><strong>Guideline 4.2&nbsp;: Ensure that content is accessible or provide an accessible alternative</strong></h3>
 +
 
 +
<p>4.2.4&nbsp;Content implemented using technologies outside of the chosen&nbsp;baseline&nbsp;satisfies all Level 1 and Level 2 requirements supported by the technologies.</p>
 +
 
 +
<p><em><span style="color:#daa520">We use standard libraries, however, in some cases we do create our own controls and not all satisfies Level 2 requirements.</span></em></p>
 +
 
 +
<p>&nbsp;</p>
 +
 
 +
<h2>8. References</h2>
 +
 
 +
<ul>
 +
<li>https://www.w3.org/TR/WCAG20/</li>
 +
<li>https://www.w3.org/TR/UNDERSTANDING-WCAG20/</li>
 +
<li>https://www.w3.org/TR/2006/WD-WCAG20-20060427/appendixB.html</li>
 +
</ul>
 +
-->
 +
[[Category:HDOC]]

Latest revision as of 15:32, 16 April 2024

This document can now be found at its new location in the Hornbill Document Library.

Latest WCAG Report

Retrieved from "https://wiki.hornbill.com/index.php?title=Hornbill_WCAG_2.0_Status&oldid=32367"