This page captures the capabilities required in sourcing solution to support creation of assets that have accessibility.
Overview
Making assets accessible to persons with special needs is important to ensure systems developed using Sunbird become inclusive. Towards this, this page details the capabilities of the sourcing infrastructure of Sunbird to enable creation of assets that are accessible to various special needs.
Following are the high level capabilities envisaged based on the current understanding of the needs:
Enable easy access to the content accessibility guidelines
Enable storing of accessibility information of an asset
Enable assets created using Sunbird editors support accessibility features
Enable uploading transcript to videos
Note:
All the capabilities will be developed as configurable features (at system and tenant level). The implementation can choose the set of features to be
turned on or off
made mandatory or optional if turned on
Enable easy access to the digital content accessibility guidelines
The objective of this is to enable all the users such as administrators, reviewers, creators, contributors using sourcing solution to have easy access to the “Digital accessibility guidelines”.
Following is the capability to enable this:
System enables storing “Digital content accessibility guidelines” at system level, in multiple languages.
Contribution and Sourcing portals have a link to “Digital Content accessibility” page.
This is a static page that contains a brief description of content accessibility and overview of the guidelines.
It also has a list of languages in which content accessibility guidelines document is available.
User can select accessibility guidelines document in the language of his/her choice.
Configurability;
This page is optional and can be configured at a system level by a specific Sunbird implementation. In case this is configured, the contribution and sourcing portals will have the link shown. Else there will be no link shown.
Enable storing of accessibility information of an asset
The objective of this to store the accessibility information of an asset so that it can be used for both discovery and tracking purpose. As of now, the envisaged approach is to get this populate this information populated manually, by creator or publisher of an asset.
The information is whether the given asset supports accessibility features required for one or more special needs/
Asset creator providing the accessibility information
When the creator/contributor submits any asset for review, a popup related to accessibility information of the asset pops up.
The popup will have a reference to the digital content accessibility page.
The popup will have list of special needs supported to which the asset needs to be accessible.
User can select one or more needs to which the asset has accessibility features and declare that the asset is accessible to the selected needs.
The user can then proceed with submitting asset for review.
The submitted asset will have the information stored and can be obtained by reading the asset.
The information is stored in such a way that
it is easy to search content accessible for a one or more given special needs.
it is easy to create report of % of accessible content for each special need.
Configurability:
The following can be configured at system and tenant level:
Capture accessibility information - Yes or No. In case of yes, the popup is shown. If no, popup is not shown. If this is not configured at tenant level, system level configuration is taken. If there is no system config, the default value is No. Note: If this value is “Yes”, then content accessibility page is mandatory.
Mandatory accessibility needs - The list of special needs for which accessibility is mandatory. If this list is configured, user will not be allowed to submit asset for review unless the corresponding special needs option is selected. If the list is empty, the user will be allowed to submit even if no option is selected. If this is not configured at tenant level, system level configuration is taken. If there is no system config, the default is empty list. Note, a tenant can make the mandatory list empty and override even if system level has a non-empty list.
List of special needs to be shown in the popup - This can be configured at tenant level. If a tenant doesn’t have the list, it is taken from system level config. If there is no list even at system level, the popup is not shown.
Asset reviewer viewing/updating the accessibility information
When a reviewer opens an asset for review, in case accessibility information capture is enabled, there is an option to view the accessibility information provided by creator.
Reviewer can optionally modify the information.
When a reviewer approves/publishes a content, the accessibility information popup is shown if configured.
Based on the configuration, reviewer can view or update the information and publish the asset.
The published asset will have the information stored and can be obtained by reading the asset.
Configurability:
The configurability is same as that for creation. In addition following can be configured at system and tenant level:
Enable modification of accessibility information by reviewer - Yes/No. If this is Yes, reviewer will be able to modify the accessible information (using same popup). Else the popup will be in read only mode. If there is no config at tenant level, system level config is used. In case system level config is not present, the default value is No.
Enable assets created using Sunbird editors support accessibility features
Enable navigation through keyboard short-cuts
All the content types with html as base like ECML,QuML, PDF contents need to be accessible compliant.
Ex:
ECML : In Case of ECML, All the HTML tags generated should be accessible compliant. Questions,Answers should be added with ARIA labels, roles. Images has to be considered for alt text content embedded onto the image attribute.
PDF :
0 Comments