Skip to end of metadata
Go to start of metadata

RA11y Plan (Review Accessibility Plan)

MS Word alternative version - rA11yPlan.docx 

The RA11Y Plan (Review Accessibility Plan) is an initiative by the Sakai Accessibility Working Group to commission a substantive review of Sakai’s accessibility by an NFB-like group with a goal of obtaining a certification, including a VPAT and WCAG2-based review, that would assure potential adopters and current users alike.  Sakai has a good history of accessibility but resources are limited and new developments in Sakai need to be reviewed and brought up to standard.

 

Some institutions have already contributed funds.  More is needed and community input about priorities is welcome. 
Our goal is US$61,000 as this matches some of the quotes we’ve received for the review and some assumptions made about the work that needs to be done in response to the review.

Phased Plan

Timeline described in table below

  1. Review and Identify

2. Fix and Enhance

3. Comprehensive Review for VPAT & WCAG2

  • Generate prioritized and comprehensive review of remaining unaudited areas of Sakai
  • Identify potential contributors
  • Create/adapt test scenarios for reviewers

    Existing Resources:
  • Use 2013 Brock University partial audit
  • Use 2013 Longsight partial audit
  • Ongoing community reports
  • Identify work and other requirements associated with reported JIRAs
  • Make enhancements in response to itemized reports (JIRAs). Requires contributions from community at large & tool leads
  • Incorporate replacement components in assessments (ie. Syllabus enhancements, Morpheus project)
  • Verify the likelihood of a successful review (this could result in a VPAT1)
  • Select a reviewer to provide an audit and a statement of success, like the NFB
  • Commission a review


As items are identified and resolved issues and tools will move through parts one and two. All parts will need resources. Areas of Sakai might move through phases one and two at different paces, but they should culminate in phase three together.
As the Longsight partial audit is incorporated, a revised list of unreviewed areas of Sakai can be generated, prioritized based on the 2014 tool use survey and the scope of a complementary partial review can be identified. Based on the prioritized list, the new partial review project cost can estimated and the estimate used to seek contributions.
The partial review will no doubt identify issues that need resolution before a full review and accessibility statement can be sought. Additional contributions responding to these issues will be needed. Contributions would include modifying components directly or contributing funds to support work by commercial partners.

A recording of the update webinar can be found on YouTube.

 

Timeline

  • Short term, Winter 2015
  • Medium term, Winter 2015 ~ Summer 2015
    • Encourage work on identified issues from the short term.
    • Fundraise for partial accessibility audit and remaining issues in Sakai.
    • Commission partial audit of Sakai.
    • Identify the scope and resources required for identified work.
    • Encourage work on newly identified issues.
  • Long term, After Completion of Phases 1 and 2.
    • Phases 1 - Fall and Winter of 2015
      • Verify that Sakai is ready to be reviewed and seek an accessibility statement
        • Create a Voluntary Product Accessibility Template (VPAT) as a self study before submission for a full review and interim certification.
      • Agree on a reviewer like the National Federation of the Blind (NFB) or a similar established commercial reviewer.
      • Fundraise for full review
    • Phase 2 - Summer and Winter 2016
      • Commission full review
      • Work to address idenfited issues
  • Outcome
    • Verification or conditional statement of accessibility from a reviewer like NFB and confirmed or conditional WCAG 2 Level AA status for Sakai.



1 VPAT - Voluntary Product Accessibility Template - {+}http://www.state.gov/m/irm/impact/126343.htm+
2 Sakai Jira - {+}https://jira.sakaiproject.org/browse+


Issues Identified

453 instances have been consolidated to 51 JIRA-issues, listed below or searchable in Sakai's JIRA

Some trends of key issues have been identified:

 

Total: 60 . Chart by: Assignee
Total: 60 . Chart by: Resolution

Full List


Loading
Key Summary T Created Updated Due Assignee Reporter P Status Resolution
SAM-3131 Add hidden text meaning for blank and numeric questions Sub-task Feb 01, 2017 May 19, 2017 Sam Ottenhoff Matt Clare Blocker Open Unresolved
SAM-2995 Provide a valid label for form fields Sub-task Aug 02, 2016 Feb 13, 2017 Sam Ottenhoff Matt Clare Blocker Closed Fixed
SAM-2994 Ensure screen reader specific content is rendered off-screen rather than hidden or not displayed: Samigo use of skip class Bug Aug 02, 2016 Feb 13, 2017 Unassigned Matt Clare Blocker Closed Fixed
SAM-2217 Form field labeling is missing in many areas Bug Oct 02, 2013 Oct 12, 2016 SAMIGO TEAM Matt Clare Critical Open Unresolved
SAK-32352 Text in the .skip class are not fully hidden Bug Mar 20, 2017 Apr 03, 2017 Matt Clare Ramon Sanchez Minor Resolved Fixed
SAK-31904 Accessibility block for visually impaired users - Syllabus Tool Bug Oct 28, 2016 Dec 07, 2016 Core Team Benjamin Rappleyea Minor Resolved Won't Fix
SAK-31886 Sites Nav misplaced (Mrphs-sitesNav__menuitem) Bug Oct 25, 2016 Feb 15, 2017 Eduardo Rey Jara Alejandro González Jiménez Blocker Closed Fixed
SAK-31864 Visual indication of focus needed Bug Oct 13, 2016 Oct 13, 2016 Matt Clare Matt Clare Major Resolved Duplicate
SAK-31822 Screen jumps on some items in preferences page clicking title Bug Sep 30, 2016 Apr 04, 2017 Matthew Jones Matthew Jones Minor Closed Fixed
SAK-31818 Ensure ARIA roles, states, and properties are valid on Mrphs-sitesNav__menuitem Bug Sep 29, 2016 Feb 13, 2017 Hunter Sonn Matt Clare Major Closed Fixed
SAK-31811 Ensure link text provides sufficient contrast - Tool Title Nav Links Sub-task Sep 28, 2016 Feb 13, 2017 Shawn Foster Shawn Foster Minor Verified Fixed
SAK-31635 Provide alternative text for images - Syllabus actions Bug Aug 02, 2016 Feb 13, 2017 Yuanhua Qu Matt Clare Blocker Closed Fixed
SAK-31634 Ensure screen reader specific content is rendered off-screen rather than hidden or not displayed Sub-task Aug 02, 2016 Feb 01, 2017 Unassigned Matt Clare Major Verified Fixed
SAK-31633 Provide alternative text for images - Sign-up Bug Aug 02, 2016 Feb 22, 2017 Yuanhua Qu Matt Clare Blocker Closed Fixed
SAK-31632 Provide alternative text for images - Sign-up Bug Aug 02, 2016 Feb 22, 2017 Yuanhua Qu Matt Clare Blocker Closed Fixed
SAK-31631 Provide a valid label for form fields - signup Bug Aug 02, 2016 Feb 22, 2017 Sam Ottenhoff Matt Clare Blocker Resolved Incorporated
SAK-31630 Provide a valid label for form fields - signup meeting details Bug Aug 02, 2016 May 12, 2017 Sam Ottenhoff Matt Clare Blocker Closed Fixed
SAK-31629 Ensure simulated controls are keyboard accessible - Signup Bug Aug 02, 2016 Apr 25, 2017 Sam Ottenhoff Matt Clare Major Resolved Fixed
SAK-31628 Ensure simulated controls are keyboard accessible - Signup Bug Aug 02, 2016 May 16, 2017 Matthew Jones Matt Clare Critical Verified Fixed
SAK-31627 Ensure screen reader specific content is rendered off-screen rather than hidden or not displayed Sub-task Aug 02, 2016 Feb 22, 2017 Unassigned Matt Clare Major Resolved Fixed
SAK-31626 Provide a valid label for form fields - permission widget Bug Aug 02, 2016 May 15, 2017 Sam Ottenhoff Matt Clare Blocker Closed Fixed
SAK-31625 Ensure screen reader specific content is rendered off-screen rather than hidden or not displayed Sub-task Aug 02, 2016 Jan 24, 2017 Unassigned Matt Clare Major Resolved Fixed
SAK-31624 Ensure ARIA roles, states, and properties are valid Bug Aug 02, 2016 Oct 13, 2016 Matt Clare Matt Clare Minor Resolved Cannot Reproduce
SAK-31623 Provide alternative text for images - Profile picture Bug Aug 02, 2016 Oct 18, 2016 Yuanhua Qu Matt Clare Blocker Resolved Fixed
SAK-31622 Ensure screen reader specific content is rendered off-screen rather than hidden or not displayed Sub-task Aug 02, 2016 Jan 24, 2017 Unassigned Matt Clare Major Resolved Fixed
SAK-31621 Ensure keyboard focus is not provided to inactive elements Bug Aug 02, 2016 Apr 27, 2017 Sam Ottenhoff Matt Clare Critical Resolved Fixed
SAK-31620 Ensure ARIA roles, states, and properties are valid - Morpheus, sites list Bug Aug 02, 2016 Oct 04, 2016 Matt Clare Matt Clare Major Closed Fixed
SAK-31619 Ensure all active elements receive keyboard focus Bug Aug 02, 2016 Apr 04, 2017 Unassigned Matt Clare Critical Verified Fixed
SAK-31618 Avoid the sole use of device-dependent event handlers - Home, Preferences Bug Aug 02, 2016 Oct 04, 2016 Matthew Jones Matt Clare Critical Closed Fixed
SAK-31617 Ensure sufficient colour contrast: WCAG2 AA Bug Aug 02, 2016 Jan 28, 2017 Shawn Foster Matt Clare Minor Resolved Incorporated
SAK-31616 Ensure that keyboard focus remains within modal simulated dialogs Bug Aug 02, 2016 Jan 31, 2017 Matthew Jones Matt Clare Critical Open Unresolved
SAK-31615 Ensure simulated controls are keyboard accessible - Morpheus Bug Aug 02, 2016 Apr 05, 2017 Unassigned Matt Clare Major Awaiting Review Unresolved
SAK-31614 Ensure screen reader specific content is rendered off-screen rather than hidden or not displayed Sub-task Aug 02, 2016 Jan 24, 2017 Unassigned Matt Clare Major Resolved Fixed
SAK-31613 Ensure link text provides sufficient contrast - throughout Sakai/Morpheus Sub-task Aug 02, 2016 Oct 04, 2016 Shawn Foster Matt Clare Minor Verified Fixed
SAK-31612 Ensure link text provides sufficient contrast - Current User Menu Sub-task Aug 02, 2016 Oct 04, 2016 Shawn Foster Matt Clare Minor Verified Fixed
SAK-31611 Ensure link text provides sufficient contrast - Left Tool Menu - Current Tool Sub-task Aug 02, 2016 Oct 04, 2016 Shawn Foster Matt Clare Minor Verified Fixed
SAK-31610 Ensure keyboard focus is indicated visually Bug Aug 02, 2016 May 16, 2017 Neal Caidin Matt Clare Critical Closed Fixed
SAK-31609 Provide a valid label for form fields - Membership tool Bug Aug 02, 2016 May 18, 2017 Sam Ottenhoff Matt Clare Major Closed Fixed
SAK-31597 Ensure screen reader specific content is rendered off-screen rather than hidden or not displayed - Forms Sub-task Jul 29, 2016 Jan 24, 2017 Sam Ottenhoff Matt Clare Major Resolved Fixed
SAK-31594 Provide a valid label for form fields - Resources/Content Bug Jul 29, 2016 May 12, 2017 Sam Ottenhoff Matt Clare Blocker Closed Fixed
SAK-31593 Ensure screen reader specific content is rendered off-screen rather than hidden or not displayed Sub-task Jul 29, 2016 Jan 24, 2017 Unassigned Matt Clare Major Resolved Fixed
SAK-31592 Ensure elements with multiple labels are rendered appropriately Bug Jul 29, 2016 Feb 13, 2017 Sam Ottenhoff Matt Clare Critical Verified Fixed
SAK-31591 Ensure custom controls provide proper textual roles and descriptions Bug Jul 29, 2016 Jan 18, 2017 Unassigned Matt Clare Major Resolved Duplicate
SAK-31590 Ensure custom controls provide proper textual roles and descriptions - Details expansion - Resources/Content Bug Jul 29, 2016 Apr 24, 2017 Matt Clare Matt Clare Major Resolved Duplicate
SAK-31589 Ensure custom controls provide proper textual roles and descriptions - Create Folder Details - Resources/Content Bug Jul 29, 2016 May 16, 2017 Sam Ottenhoff Matt Clare Major Verified Fixed
SAK-31588 Ensure ARIA roles, states, and properties are valid Bug Jul 29, 2016 Oct 13, 2016 Unassigned Matt Clare Minor Resolved Cannot Reproduce
SAK-31587 Ensure that simulated dialogs can be closed via the keyboard - Chat (portal chat?) Bug Jul 29, 2016 Feb 13, 2017 Sristi Shrestha Matt Clare Critical Closed Fixed
SAK-31586 Ensure screen reader specific content is rendered off-screen rather than hidden or not displayed - Chat Sub-task Jul 29, 2016 Jan 24, 2017 Unassigned Matt Clare Major Resolved Fixed
SAK-31585 Ensure ARIA roles, states, and properties are valid - Chat Bug Jul 29, 2016 Oct 03, 2016 Unassigned Matt Clare Minor Resolved Cannot Reproduce
SAK-31575 Ensure screen reader specific content is rendered off-screen rather than hidden or not displayed Sub-task Jul 27, 2016 Jan 24, 2017 Unassigned Matt Clare Major Resolved Fixed
SAK-31573 Ensure ARIA roles, states, and properties are valid - Assignments Bug Jul 27, 2016 Apr 24, 2017 Unassigned Matt Clare Minor Resolved Cannot Reproduce
SAK-31549 Ensure screen reader specific content is rendered off-screen rather than hidden or not displayed Bug Jul 22, 2016 Mar 27, 2017 Matthew Jones Matt Clare Major Verified Fixed
SAK-31548 Avoid inappropriate use of ARIA roles, states, and properties - Resources Bug Jul 22, 2016 Apr 24, 2017 Sam Ottenhoff Matt Clare Major Resolved Incorporated
SAK-31547 Ensure screen reader specific content is rendered off-screen rather than hidden or not displayed Bug Jul 22, 2016 Feb 14, 2017 Unassigned Matt Clare Major Verified Fixed
SAK-31546 Avoid inappropriate use of ARIA roles, states, and properties - Announcements Bug Jul 22, 2016 Feb 01, 2017 Matt Clare Matt Clare Minor Resolved Incorporated
Showing 55 out of 60 issues Refresh

 


Updates

Early Fall 2015 Update

Fully funded!

The $61,000 and 60 hours of in-kind development time have been pledged.

Thanks to: Apereo, Durham Tech, Tufts University, Oxford, Pepperdine, Longsight and I should probably thank Brock University.

Next is for members of the accessibility working group to have serious talks with accessibility reviewers.

There are still many ways to contribute: There's participating in decision making process around selecting an accessibility reviewer selection and the opportunity to fund or directly provide development time to respond to the audit results.

A big thanks to those individuals and institutions that have pledged and everyone who has participated in the process.

Summer 2015 Update 2

As of Thursday September 3, 2015 $54,500 and 60 hours of in-kind development time have been pledged!

Matt Clare (Matt.Clare@Brocku.ca) would love to hear from the people or places that can help get us to our goal!

Summer 2015 Update

We are under way and hoping to raise US$61,000.

If support in the form of financial contributions to these costs is possible, please contact Matt Clare (Matt.Clare@Brocku.ca) to let Matt know the amount and so that the Apereo Foundation can prepare an invoice and set up electronic transfers.

March 2015 Update

Progress on this project continues.  The  accessibility reviews of previous versions of Sakai that have been made public, notably Brock University’s and Longsight’s, have been incorporated into https://jira.sakaiproject.org.  Most issues have been reviewed and some have already had work completed on them for Sakai 11, and potentially coming updates to Sakai 10.

Donations of funds to support commissioning Phase 1 and Phase 3 reviews are being sought.  Resources in any form are appreciated for the fix and enhance portion of Phase 2.

The Sakai Accessibility Working Group is maintaining a list of the review status of unique pages and trying to assign a priority to unreviewed areas.  Crudely, there are 341 unreviewed pages in Sakai 10.  Industry scans have suggested that a worst-case budgetary figure for having each unique web pages professionally reviewed is $100/page.

Inquiries has been made with the following organizations about complitary Phase 1 partial reports and the possibility of a Phase 3 certification statements, starting with a VPAT and then a WCAG 2 Level AA certifications.  Discussions are ongoing, but early positive developments include suggestions that a representative selection of Sakai’s total unique elements maybe be sufficient for certification by some groups.

Status of current vendor inquiries:
  • Deque Systems, Inc.- web contact
  • National Foundation of the Blind - Emailed
  • SSB bart Group - Emailed, phone conversation
  • WebAIM - Emailed, ongoing dialogue 
  • jimthatcher.com - Web contact
  • Paciello Group - Respectfully declined the opportunity

If you are interested in participating please contact Matt Clare through details outlined on the main page of the Accessibility Working Group.

Matt Clare

Spring 2016 / Open Apereo Con 2016

If you are interested in reviewing the results please contact Matt Clare through details outlined on the main page of the Accessibility Working Group.

There are 452 Issues Detected with guidance on how to address them.

Matt Clare

July 2016

453 instances have been consolidated to 140 JIRA-issues
The export from SSB Bart has been reviewed for:

  • Correct component
  • additional brief community summary
  • additional notes
  • Add {code} {code} and {noformat} as needed

Matt (and any others are welcome) to review with SSB Bart on Delivery Call, Matt’s concern is some of the ARIA/Tabpanel feedback is very vague.

SSB Bart currently asses Sakai 11 (from April 15 2016) as 75% WCAG2 A compliant and 76% WCAG2 AA compliant.

Next steps:
Matt Clare slices the Google Sheet by Sakai Project/Component and imports into JIRA based on this mapping (Screenshot of mapping) http://www.screencast.com/t/Tf2qHSY3UpH
Example of what they look imported to JIRA in a "fake" project https://jira.sakaiproject.org/projects/ACCTEST

Once import is deemed ready, will import issues per project/component to their areas of JIRA
Will create public searches to reveal rA11y Project across JIRA

Once in JIRA:
Sakai development community alerted to new rA11y related JIRAs. Focus on the quick wins.
Informing others Core team meetings: Every Tuesdays 10AM EST
Alert Sak-dev and Slack
Will host Q&As on issues (ideally common ones)

Matt Clare

August  2016

453 instances have been consolidated to 51 JIRA-issues 
The export from SSB Bart has been reviewed for:
  • Correct component
  • additional brief community summary
  • additional note
  • Add {code} {code} and {noformat} as needed
The complete list of 51 rA11y related JIRAs can be found by searching for the label rA11y (case counts)

Some issues are large in scope, many are seemingly small, such as colour changes ( SAK-31617 - Ensure sufficient colour contrast: WCAG2 AA Resolved ) and CSS class use ( SAK-31549 - Ensure screen reader specific content is rendered off-screen rather than hidden or not displayed Verified ) and ideally can represent some swift and significant progress.

A few trends have been identified  "Ensure screen reader specific content is rendered off-screen rather than hidden or not displayed"  has emerged as a wide-ranging issues that might be easy to solve, a
We're hoping that work can begin on these issues within components and projects in the Sakai community.  There are also some funds and pledged time that can be used to address difficult issues, but ideally now that items are identified the resolution is forthcoming through regular means, but those funds and time could be used.

Before the end of 2016 Sakai needs to be ready to be ready to be reviewed and at that time SSB Bart can issues a WCAG 2 Level AA compliance statement, ideally without reservations.


 

 

  • No labels