Sakai 12 branch created!

We are finally here! A big milestone has been reached with the branching of Sakai 12.0. What is a "branch"? A branch means we've taken a snapshot in time of Sakai and put it to the side so we improve it, mostly QA (quality assurance testing) and bug fixing until we feel it is ready to release to the world and become a community supported release. We have a stretch goal from this point of releasing before the end of this year, 2017. 

Check out some of our new features.

The Sakai UI Inventory Project

(posted on behalf of Jolie Tingen, Learning Technology Analyst, Duke University)

 

In the last few years, Sakai’s user interface and user experience has improved significantly.  The community’s effort to make Sakai a responsive and easy-to-use application is evident in the latest release. Improved navigation, streamlined workflows, and a modern interface are all noticeable improvements in Sakai 11.  Yet, these improvements have not been documented in a style guide for Sakai.

 

To address this gap, Duke University is partnering with the Sakai Community to develop an updated style guide for Sakai.  

Global Accessibility Awareness Day

(posted on behalf of Matt Clare, Brock University, Chair of Sakai Accessibility Working Group)

 

Thursday, May 18 2017 is Global Accessibility Awareness Day.

 

Sakai should have a positive impact on all who encounter it, a key part of this goal is how accessible Sakai is.

 

Today is Global Accessibility Awareness Day (GAAD) and part of GAAD is building awareness of what we all can do to promote access for, and inclusion of, people with different abilities.

 

Sakai has a good history of accessibility but recent versions of Sakai have not been released with a thorough review of the accessibility and to what degree it meets recognized international standard like the WCAG 2.  I’m pleased to share that thanks to community efforts in fundraising over $61,000 and 60 hours of development work Sakai’s accessibility has been reviewed by a recognized accessibility reviewer, SSB Bart, and our plans are to deliver Sakai 12 with an accessibility compliance statement.

 

Sakai 11.2

Even though we have release notes [1], I was wondering if it would be helpful to make a blog post about our maintenance releases. Also motivated by the fact that in 11.2 we had to turn off one of the new features of Sakai 11 for the mobile view, and thought that would be important to communicate. This blog post is really about both Sakai 11.1 and Sakai 11.2 since combined there are 350 improvements since the 11.0 release on 23 July 2016. 

 

Celebrate Sakai 11 on Twitter #turnitupto11

Between the dates of September 12 - 21, tweet away on Twitter with the hashtags #sakaiproject and #turnitupto11 to enter a fun contest. 
 

Announcing the release of Sakai 11 !

Sakai 11 has had a facelift! The new version of Sakai supports a responsive design meaning that it can be used on any device with any screen size, any place, anytime, anywhere! The new release represents one of the biggest, if not the biggest, improvement in Sakai in years. Sakai 11 is, of course, still 100% open source and its redesign was informed by UX testing with real users and delivered by the worldwide Sakai community.  

 

Sakai Accessibility Ra11y Plan update

Phase 1 of the Ra11y plan [1] is complete!  We are one (big) step closer to WCAG2 Certification. 
 
What does this mean? It means that we completed a substantive review of the accessibility of the Sakai system by contracting out the assessment
to a reputable 3rd party, SSB Bart [2]. Improving Sakai's accessibility means making it easier for people of all abilities to use our system. Our aim, as it always has been, is to make the system genuinely as accessible as possible, which directly impacts students, instructors, and other users in a positive way with a better user experience. We also wish to achieve WCAG 2 certification, which validates the community's hard work in this area. A double win!
 
The good news is that Sakai, as it stands now, is assessed at 74% compliant, which is not a bad starting point. Also we have gone painstakingly through the 453 identified issues and consolidated them into 51 Jiras [3] .  We are off to a great start and we don't want to lose the momentum!
 
 
 
 
 
 

Sakai 11 timeline

The Sakai core team is planning a Beta release the week of May 9, 2016. A Beta release is feature complete and within striking distance of an RC01, our first release candidate. We are anticipating having an RC01 shortly after Open Apereo 2016 and an expected release date in late June.