The release notes provide information on the features and improvements in the specified version. The release dates that are related to the version of the release are published in the Study guide release schedule.
Improvements
The issues in release mentioned under the section improvements are considered as new functionality, user experience improvements or bug fixes. Issues marked as hotfix are developed in this sprint but applied to the previous release or directly to production, depending on impact.
Assessment fields should return the value instead of N/A - SG-499
WCAG 2.2 compliancy improvements - SG-497
Based on feedback and regular planned validation on WCAG compliancy a number of changes have been applied to Study guide to meet the WCAG 2.2 compliancy definitions.
The following changes are applied:
Run through all pages to validate and if necessary adjust that all tabs, buttons, and links are keyboard-accessible with proper ARIA labels. The sub-tabs are extended with icon and transition support.
Streamlined / simplified the user interface by limiting the number of buttons that were offered multiple times on the same page. Also change the breadcrumb on detail pages with a back button.
Reduced the visual noise by removing lines in the quick-view (search result detail) and changing several box shadows with subtle borders.
Usage of so called semantic elements for titles, e.g. h1, h2. This allows for a clearer visual hierarchy and improves understanding by reading tools.
Used semantic elements for other elements too, like summary, details, main, footer, etc.
Relaxed some spacing, and overall styling for a cleaner look and feel
Improved navigation speed.
As a bonus from adjusting to WCAG compliancy, the complexity and maintainability is improved by consolidating overlapping business logic, in overview and detail components, into generic stuff.
The screenshot below shows the implementation of 'Tab' and 'Tab order' support from a usability perspective.
The list overview is cleaned and next to the tab-order support the used buttons are more clear and no longer duplicated.
Even though we perform a regular check on compliancy, we are always open for things we missed. In case in Study guide a non-matching WCAG 2.2 compliancy is identified, please sent a ticket to support, so we can pick it up.
Security
An integral part of our development and build process is automatic scanning for known security vulnerabilities. The vulnerabilities will be fixed based on their impact, which means that in some cases an immediate hot-fix will be applied, and in other cases the vulnerability will be fixed in the current or next Sprint (release). The security section provides an overview of the vulnerabilities mitigated. For more information on reported vulnerabilities, see the central database of vulnerabilities.
During this release no vulnerabilities were reported that require mitigation.
For more guidance on configuration and setup of Study Guide, use the relevant Study Guide manual.