...
The objective of this to store the accessibility information of an asset so that it can be used for both discovery and tracking reporting 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 accessibleconfigured accessible features that an asset can have. The features are grouped by different types of accessibility needs. Both the different types of accessibility needs and the features for each need are configured.
User can select one or more needs to which the asset has accessibility features and declare that the asset is accessible to supports the selected needsaccessible features.
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.
...
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 .
List of accessibility features 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.
List of mandatory accessibility features - The list of special needs for which accessibility is accessibility features that are mandatory. If this list is configured, user will not be allowed to submit asset for review unless the corresponding special needs option is features are 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 popup to view/update the information is same as that appears for creator. The information populated by the creator is shown by default. It can be updated by the reviewer based on the configuration.
The published asset will have the information stored and can be obtained by reading the asset.
...