EdReady release notes - 23 June 2018

The following bug fixes, new features, and improvements are now part of the EdReady platform, as of 23 June 2018:

• With this update, we are hoping that we have achieved WCAG 2.0 AA accessibility compliance for the EdReady platform. We are scheduled for a third-party audit in July, so stay tuned. This round of development included:
  • Full coverage of every learning objective with assessment items (i.e., test questions) with complete alt-text descriptions for every embedded image.
  • Similar alt-text treatment for all of the topic texts.
  • Activation of a student option to focus all of the testing and learning objects on items which are deemed fully accessible. Students can ‘Request accessibility support’ on the sign-up page and on their My Account page.
  • Administrators can also activate this option for students in the Students management tab.
• The accessibility work achieved to date is only the beginning. We will continue to drive toward documented compliance, but our ultimate goal is to go well beyond compliance standards where we can offer and support much more nuanced approaches to student’s exercising their right to learn using whatever formats are best suited to their needs.
• We upgraded the security basis for storing student passwords. Most students will be asked to re-type their EdReady passwords when they log in for the first time after the update. That extra step will update their information and only takes place that one time.
• We performed a lot of behind-the-scenes maintenance work to make sure that all of the various technologies in use by the EdReady application are up to date and optimized.
• It is now possible to delete goals. The actual process is a bit obscure because there are so many dependencies in the system on the goal structure. If you are interested in deleting goals, please get in touch with NROC support.
• There were a couple of bugs reported which had a common basis, where the data used for the student experience was not the same as the data used to report on student progress for teachers. We were able to diagnose and repair all of those problems, and the code has been updates so we should not see those issues again.
• We squashed a number of other bugs and made a number of minor improvements throughout, as usual.