Hornbill WCAG 2.0 Status

From Hornbill
Jump to navigation Jump to search

Accessibility Evaluation Report for WCAG 2.0

 

1. Executive Summary

This report describes the conformance of the Hornbill Collaboration Core and its applications with W3C'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 )

 

2. Last Reviewed

 

3. Reviewer

  • Daniel Dekel - Principal Web Developer
  • Hornbill Technologies Limited

 

4. Review Process

 

5. Summary and Recommended Actions

Results for Level 1 (A):

There are 18 checks in total for Level 1

14 are fully met. 4 are partially met.

In all the 5 cases that are partially or not meeting the success criteria, can be easily implemented.

Results for Level 2 (AA):

There are 15 checks in total for Level 2

9 are fully met. 5 are partially met and 1 is not.

In 4 cases that are partially meeting the success criteria can be easily implemented.

Results for Level 3 (AAA):

There are 21 checks in total for Level 3

6 are fully met. 4 are partially met and 11 are not.

In most cases of the partially or not meeting the success criteria will be difficult to implement.

 

General

Markup changes are relatively easy to improve. Multi-Language requirements can also be easily improved.

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)

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.

 

7. Summary Check List

Fully Met Partially Met Not Met

Principles

Guidelines

Level A

Level AA

Level AAA
1

1.1: Provide text alternatives for all non-text content

 1.1.1    

1.2 : Provide synchronized alternatives for multimedia

 1.2.1-1.2.2 1.2.3 1.2.5-1.2.7

1.3 : Ensure that information and structure can be separated from presentation

 1.3.1 1.3.4-1.3.5  
1.3.2-1.3.3    

1.4 : Make it easy to distinguish foreground information from its background

   1.4.1 1.4.3
  1.4.2 1.4.4
2

2.1 : Make all functionality operable via a keyboard interface

 2.1.1   2.1.2

2.2 : Allow users to control time limits on their reading or interaction

 2.2.1 2.2.2 2.2.4
  2.2.3 2.2.5-2.2.6

2.3 : Allow users to avoid content that could cause seizures due to photosensitivity

 2.3.1   2.3.2

2.4 : Provide mechanisms to help users find content, orient themselves within it, and navigate through it

2.4.1

2.4.3-2.4.4

2.4.5
    2.4.6-2.4.7
    2.4.8

2.5 : Help users avoid mistakes and make it easy to correct mistakes that do occur

2.5.1

2.5.2-2.5.3

2.5.4

3

3.1 : Make text content readable and understandable.

3.1.1

3.1.2

3.1.3
    3.1.4
    3.1.5-3.1.6

3.2 : Make the placement and functionality of content predictable

3.2.1-3.2.2

3.2.3

3.2.5
  3.2.4  

4

4.1 : Support compatibility with current and future user agents (including assistive technologies)

4.1.1

 

 

4.1.2

 

 

4.2 : Ensure that content is accessible or provide an accessible alternative

 4.2.1-4.2.2 4.2.3 4.2.4

 

7. Detailed Check List

Level 1 (A)

Guide 1.1: Provide text alternatives for all non-text content

1.1.1 For all non-text content:

  • 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

Youtube videos are provided with captions

1.2.2 - Audio descriptions of video, or a full multimedia text alternative including any interaction, are provided for prerecorded multimedia

Most videos are tutorial videos showing screen captures that about new features. These can be easily understood without audio.

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

We use basic html markup including headings, hyperlinks and  logical DOM structure flow so that the screen reader will follow that  easily.

1.3.2 Any information that is conveyed by color is also visually evident without color

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.

1.3.3 When the sequence of the content affects its meaning, that sequence can be programmatically determined.

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.

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.

Note: This does not preclude and should not discourage the support of other input methods (such as a mouse) in addition to keyboard operation.

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.

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

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.

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

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.

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

There is a common menu that is available in all Web Units as well as shortcuts to navigate to that menu.

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

Errors are displayed to the user if occur. 

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

Primary language is set in the document's body

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.

No components change context when setting focus.

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.

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.

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

We have a very well defined and valid markup content. We use automated tools to make sure these are valid.

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

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.

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.

We have one version that meets all Level 1 success criteria

4.2.2 Content meets the following criteria even if the content uses a technology that is not in the chosen baseline:

  • If content can be entered using the keyboard, then the content can be exited using the keyboard.
  • Content conforms to success criterion 2.3.1 (general and red flash).

Both criteria is meet.

 

Level 2 (AA)

Guideline 1.2 : Provide synchronized alternatives for multimedia

1.2.3 Audio descriptions of video are provided for prerecorded multimedia.

No

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.

Textual information can be programmatically determined by the markup language.

1.3.5 Information required to understand and operate content does not rely on shape, size, visual location, or orientation of components.

We use markup to define importance in the content as H1, H2, Strong, etc... 

Guideline 1.4 : Make it easy to distinguish foreground information from its background

1.4.1 Text or diagrams, and their background, have a luminosity contrast ratio of at least 5:1

It passes in most cases except in some hyperlinks where the background colour is light grey the ratio is 4.18:1

1.4.2 A mechanism is available to turn off background audio that plays automatically, without requiring the user to turn off all audio.

It is possible to turn the Notifications sound off leaving other audio running without disturbance.

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.

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.

Content does not blink

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.

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.

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.

Yes - All our Web Units have a meaningful title

2.4.4 Each link is programmatically associated with text from which its purpose can be determined.

Yes - Our links are related to text and if an image is used it will usually have a related text.

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.

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.

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:

  • 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

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.

Note: This requirement does not apply to individual words or phrases that have become part of the primary language of the content.

Usually the entire UI is translated to the same language, however there are some exceptions:

  • 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.

It should be simple to fully implement this one.

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.

The same navigation window is presented on each Web unit

3.2.4 Components that have the same functionality within a set of Web units are identified consistently.

Menu items have a consistent markup however, not all have a proper alt, name or role attributes

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.

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

 

Level 3 (AAA)

Guideline 1.2 : Provide synchronized alternatives for multimedia

1.2.5 Sign language interpretation is provided for multimedia.

Not available

1.2.6 Extended audio descriptions of video are provided for prerecorded multimedia.

Not available

1.2.7 For prerecorded multimedia, a full multimedia text alternative including any interaction is provided.

Not available

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

Not available

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

Our audio recordings are done in an isolated environment. No background sound is recorder.

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

Not all areas are reachable using the keyboard

Guideline 2.2 : Allow users to control time limits on their reading or interaction

2.2.4 Except for real-time events, timing is not an essential part of the event or activity presented by the content

Correct, timing is not necessary to perform an action

2.2.5 Interruptions, such as updated content, can be postponed or suppressed by the user, except interruptions involving an emergency

No, the user can not postpone an update coming from an event

2.2.6 When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating

No, the data will be lost but the timeout is very long, so there is a very small chance for data lost.

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

We do not provide any flashing components

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.

Our titles, headings and labels are descriptive and in relation to the context

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.

In most cases accessing a web units triggers a focus in an element. The element is also visually detectable.

2.4.7 Information about the user's location within a set of Web units is available.

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.

2.4.8 The purpose of each link can be programmatically determined from the link.

We sometimes have non-specific links saying “click here” or “more”.

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.

We usually display expected data format and description for the expected input.

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.

We do not provide alternative list of definitions for words or phrases

3.1.4 A mechanism for finding the expanded form of abbreviations is available.

Usually if there is an abbreviation we provide titles in case the user is not familiar with it.

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

We do not provide illustrations or supplementary content to the provided one

3.1.6 A mechanism is available for identifying specific pronunciation of words where meaning cannot be determined without pronunciation.

We do not provide any type of glossary or voice recordings for pronunciation for words

Guideline 3.2 : Make the placement and functionality of content predictable.

3.2.5 Changes of context are initiated only by user request

We do not change context without the user requesting. Context is opened in the same window unless the user requests.

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.

We use standard libraries, however, in some cases we do create our own controls and not all satisfies Level 2 requirements.

 

8. References

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