The Voluntary Product Accessibility Template (VPAT) is a self-disclosing document that explains how accessible a particular product is according to the Revised 508 Standards and WCAG 2.0.

Sakai Accessibility Conformance Report

VPAT Version 2.3 - December 2018

Name of Product/Version: Sakai 12.5

Product Description: Collaboration and Learning Environment (CLE) software

Date: January 10, 2019

Tools Tested

Sakai is composed of an extensive set of tools and core functionality. The following specific tools were tested for this report. Note that untested tools may also have unidentified accessibility issues.

This product contains the “External Tool (LTI)” which allows an institution to integrate certain outside tools into the technology. This evaluation does not cover any outside tools that may be added by institutions or end users.

Additionally, content can be generated and uploaded by users. It is the responsibility of the user to ensure any content they generate or upload is accessible. Accessible content creation is encouraged through the inclusion of alt text fields, heading options and other tools. Some best practices for creating accessible content are also provided in support documentation.

Evaluation Methods Used

Testing with assistive technologies

The information contained within this Voluntary Product Accessibility Template (VPAT) is a result of an audit performed by Level Access in February 2018. This assessment fully tested the compliance of the web-based CLE software. This testing included, but was not limited to: automated testing, extensive manual testing, and testing by users who are blind and low-vision with leading assistive technologies such as the JAWS screen reader, the ZoomText screen magnification software, and Dragon NaturallySpeaking for compliance with the WCAG 2.0 A and AA and Section 508 standards. Additional automated and manual testing with accessibility inspection tools, as well as usability testing with assistive technologies was performed in December 2018 to verify remediation of several compliance violations found in the March 2018 audit.

Applicable Standards/Guidelines

This report covers the degree of conformance for the following accessibility standard/guidelines:

Note: When reporting on conformance with the WCAG 2.0 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.0 Conformance Requirements.

For each guideline in the WCAG 2.0 standard, there are testable success criteria, which are at three levels: A, AA, and AAA.

Terms

The terms used in the Conformance Level information are defined as follows:

Legal Disclaimer (Sakai)

Compliance to Section 508 (and the stated goal of meeting WCAG 2.0 A & AA Success Criteria) varies from tool to tool, and to a certain extent depends on how tools are configured.

Much of a user's experience - and how accessible Sakai feels to that user - will be determined by the content added to it, so a site with good accessibility will also require some forethought on the part of an instructor or designer.

WCAG 2.0 Report

Table 1: Success Criteria, Level A

CriteriaConformance
Level
Remarks and Explanations
1.1.1 Non-text Content

Partially

Supports
There are very few instances of non-compliance. Some known exceptions: A legend is provided in the "Notes" section of the meeting details page including images that do not include <alt> attributes.

The rich text editor tool used throughout the product is neither keyboard nor screen reader friendly, therefore any alternative attributes by screen readers and other cannot be accessed assistive technology.

1.2.1 Audio-only and Video-only (Prerecorded)Not Applicable

Neither audio nor video are included in the product.

1.2.2 Captions (Prerecorded)

Not Applicable

Neither audio nor video are included in the product.

1.2.3 Audio Description or Media Alternative (Prerecorded)Not Applicable

Neither audio nor video are included in the product.

1.3.1 Info and Relationships

Partially

Supports

Although in many respects the product presents info and relationships well, several instances are not properly implemented. Known exceptions include heading markup does not reflect page structure, HTML list elements are used for formatting in chat feature, sites feature does not alert user that it will open in dialogue, some expandable elements are not presented in a way to suggest they are expandable, some tables are not correctly marked for row header or scope.

The rich text editor tool used throughout the product is not keyboard friendly, which hinders understanding Info and Relationships for users of assistive technology.

1.3.2 Meaningful Sequence

Partially

Supports

Throughout the website, there are different layout tables that are not hidden from assistive technology.

The rich text editor tool used throughout the product is not keyboard friendly, which hinders understanding of a meaningful sequence for users of assistive technology.

1.3.3 Sensory Characteristics

Supports

Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound.

1.4.1 Use of Color

Partially

Supports

Supports with one known exception - the calendar picker indicates today's date with color only.

1.4.2 Audio ControlSupports

The product does not contain audio set to autoplay. Users who add audio content can set the audio to “don’t autoplay.”

2.1.1 Keyboard

Partially

Supports

Supports with a handful of exceptions. Known exceptions include some elements in sign-up advanced settings that lack keyboard focus. Calendar picker can be opened by keyboard, but the buttons cannot be used by keyboard. However, there is an alternate date and time input that is keyboard accessible.

Other known exceptions include rich text editor options are not keyboard accessible, and "Add item" and "Expand All" links in syllabus tool are not keyboard accessible.

2.1.2 No Keyboard Trap

Supports

If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away.

2.2.1 Timing Adjustable

Supports

Tool allows author to adjust timing of content. Timed elements are only in use if an instructor has designed their content to be timed. Instructors can opt to avoid including timed elements.

Features of the authoring tool are not timed.

2.2.2 Pause, Stop, HideSupports

Product does not contain moving, blinking, scrolling, or auto-updating information unless added by a user.

2.3.1 Three Flashes or Below ThresholdSupports

Web pages do not contain anything that flashes more than three times in any one second period unless added by a user.

2.4.1 Bypass BlocksSupports

Product contains multiple mechanisms for bypassing blocks of content that are repeated on multiple Web pages.

2.4.2 Page Titled

Partially

Supports

Supports with the exception of a few pages that could have more distinct, informative titles.

2.4.3 Focus Order

Partially

Supports

Supports with a few known exceptions including focus moving to the top of the page when modal windows are closed.

2.4.4 Link Purpose (In Context)

Partially Supports

Supports with a few exceptions in the Authoring Tool including links "More," "Delete," and "Remove Tool" which are not unique or descriptive enough.
3.1.1 Language of PageSupports

Human language of pages can be programmatically determined.

3.2.1 On FocusSupports

When any component receives focus, it does not initiate a change of context.

3.2.2 On Input

Partially

Supports

Supports with the known exception: upon selection of an input value from a combo-box, it refreshes the page without informing users.

3.3.1 Error IdentificationSupports

If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text.

3.3.2 Labels or Instructions

Partially

Supports

Labels and instructions are provided, however they could be more informative in some instances. Not all form control groups are contained within fieldsets, some form controls have visual labels, but lack for and id attributes.

4.1.1 ParsingSupports

In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features. No known exceptions.

4.1.2 Name, Role, Value

Partially

Supports

Some interface components lack proper name, role, or value.

Table 2: Success Criteria, Level AA

Note: Neither audio nor video are included in the product.

CriteriaConformance
Level
Remarks and Explanations
1.2.4 Captions (Live)Not ApplicableNeither audio nor video are included in the product.
1.2.5 Audio Description (Prerecorded)Not ApplicableNeither audio nor video are included in the product.

1.4.3 Contrast (Minimum)

Partially

Supports

There are very few known exceptions: calendar picker, required *, checkbox check, radio button select do not pass contrast minimum. Visual focus is not high enough contrast in some instances.

1.4.4 Resize textSupports

Text can be resized without assistive technology up to 200 percent without loss of content or functionality.

1.4.5 Images of TextSupports

Text is used to convey information rather than images of text except for essential elements (logos).

2.4.5 Multiple Ways

Partially

Supports

Product contains a limited search feature. Known elements that cannot be reached in multiple ways include the sites dialogue and the login dialogue.

2.4.6 Headings and LabelsSupports

Headings and labels describe topic or purpose.

2.4.7 Focus Visible

Partially Supports

Keyboard operable user interfaces have visual keyboard focus with the exception of the tools within the rich text editor.

3.1.2 Language of PartsSupports

Human language of passages or phrases can be programmatically determined.

3.2.3 Consistent NavigationSupports

Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user.

3.2.4 Consistent IdentificationSupports

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

3.3.3 Error SuggestionSupports

If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content.

3.3.4 Error Prevention (Legal, Financial, Data)

Partially

Supports

Regarding Tests and Quizzes: Submissions are not reversible. Once a quiz has been submitted, only the instructor can delete the original submission and/or allow a retake. Data entered by the user is not checked for input errors. A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission. Students are prompted to confirm that they are ready to submit the assessment for grading prior to submission.

Revised Section 508 Report

Functional Performance Criteria (FPC)

CriteriaConformance
Level
Remarks and Explanations

302.1 Without Vision

Supports

Where a visual mode of operation is provided, product provides at least one mode of operation that does not require user vision. Product is screen reader friendly.

302.2 With Limited Vision

SupportsWhere a visual mode of operation is provided, product provides at least one mode of operation that magnifies, one mode that reduces the field of vision required, and one mode that allows user control of contrast. Product is web-based and is compatible with browser zoom up to 200%, MAGic, ZoomText, and browser plug-ins for altering contrast.

302.3 Without Perception of Color

Partially

Supports

Where a visual mode of operation is provided, product provides at least one mode of operation that does not require user perception of color.

Known exceptions: distinguishing dates in the calendar.

302.4 Without Hearing

Not Applicable

Product contains no built-in audio. Any audio components are uploaded by the user. It is up to the user to provide captions, transcripts, or audio descriptions.

302.5 With Limited Hearing

Not ApplicableProduct contains no built-in audio. Any audio components are uploaded by the user. It is up to the user to provide captions, transcripts, or audio descriptions.

302.6 Without Speech

Not Applicable

Product does not require speech input, control, or operation.

302.7 With Limited Manipulation

Partially

Supports

Product is keyboard and assistive technology friendly with very few exceptions, which are indicated in the above report.

302.8 With Limited Reach and Strength

Partially

Supports
Product is keyboard and assistive technology friendly with very few exceptions, which are indicated in the above report.

302.9 With Limited Language, Cognitive, and Learning Abilities

Partially

Supports

The pages of this product have a consistent navigation and presentation with clear labels, titles etc. However, some best practices are not followed including ability to reverse form submission for tests and quizzes, data being checked for input error prior to submission, and as described in 2.4.4, a few links have inadequate text.

Authoring Tools

CriteriaConformance
Level
Remarks and Explanations

504.2 Content Creation or Editing (if not authoring tool, enter “not applicable”)

See WCAG 2.0 section

See information in WCAG section.

504.2.1 Preservation of Information Provided for Accessibility in Format Conversion

Not Applicable

Product does not convert content/file formats.

504.2.2 PDF Export

Does Not Support

Several tools within the product give the option to generate a print PDF view for non-PDF content. The standard of the PDF is reliant on the user’s system. These generated PDFs are not accessible.

504.3 Prompts

Partially

Supports
Accessibility tools such as headings, ordered and unordered list builders, and high-contrast colors are readily available in the rich text authoring tool, however they are not required. There is a prompt for alt text when adding an image.

504.4 Templates

Not Applicable

Product does not provide content templates. Any templates used in the product would have been supplied by the institution.

Support Documentation

CriteriaConformance
Level
Remarks and Explanations

602.2 Accessibility and Compatibility Features

Supports

Product includes a help section devoted to accessibility and users of assistive technology. This section includes an overview of the product including organization, landmarks, a list of skip links, access keys and supportive information for accessible and efficient navigation and operation. Information on color/contrast modification and enlarging screen elements are also available. Detailed information is also provided on best practices for creating accessible content for the product.

602.3 Electronic Support Documentation

See WCAG 2.0 sectionSee information in WCAG section.

602.4 Alternate Formats for Non-Electronic Support Documentation

Not Applicable

Product is open source. Institutions may choose between self-hosting and vendor support (e.g., Longsight).

End users receive alternate support via offline and in-person methods as determined appropriate by their academic institution.

Support Services

CriteriaConformance
Level
Remarks and Explanations

603.2 Information on Accessibility and Compatibility Features

Supports

A basic overview of best practices for accessibility is provided as part of faculty/staff training, if it is requested by the client. Clients are reminded to keep accessibility in mind when creating content and given examples of best practices and common pitfalls. Clients are also referred to the section of the online support documentation devoted to accessibility and compatibility features mentioned above in 602.2.

603.3 Accommodation of Communication Needs

Not Applicable

Product is open source. Institutions may choose between self-hosting and vendor support (e.g., Longsight).

End users receive alternate support via offline and in-person methods as determined appropriate by their academic institution.