...

1. System enables storing “Digital content accessibility guidelines” at system level in pdf format, in multiple languages. This is done through backend.

2. Contribution and Sourcing portals have a link to “Digital Content accessibility” page.

3. This is a static page that contains a brief description of content accessibility and overview of the guidelines.

4. It also has a list of languages in which content accessibility guidelines document is available.

5. User can select accessibility guidelines document in the language of his/her choice and download it.

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.

...

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

1. If accessibility is enabled for the tenant, the asset edit screen will show a button labeled “Accessibility Details”.

2. When the creator/contributor submits any asset for reviewclicks the button, a popup related to accessibility information of the asset pops up.

3. The popup will have a reference to the digital content accessibility page.

4. 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.

5. 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 needs.

6. The user can then proceed with submitting asset for review.

7. The submitted asset will have the information stored accessibility features and save.

8. Note: As of now all the accessibility information is optional

9. The accessibility information is stored in the asset and can be obtained by reading the asset.

10. The information is stored in such a way that

    1. it is easy to search content accessible for a one or more given special needs and features.

    2. it is easy to create report of % of accessible content for each special need and feature.

Configurability:

The following can be configured at system and tenant level:

1. Capture accessibility information - Yes or No. In case of yes, the popup button to show accessibility details is shown. If no, popup the button 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

2. List of accessibility features, grouped by accessibility needs - 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 accessibility information popup shows a message “Could not find any accessibility details”.

Accessibility feature is Mandatory or Non-mandatory - The list of

...

accessibility features that are mandatory. If this list is configured, user will not be allowed to submit asset for review unless the corresponding

...

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

...

syst.0em 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.

...

(This is not planned to be implemented for now. All accessibility information is optional).

Asset reviewer viewing/updating the accessibility information

1. 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.

2. Reviewer can optionally modify the information.

3. When a reviewer approves/publishes a content, the accessibility information popup is shown if configured.

4. Based on the configuration, reviewer can view or update the information and publish the assetthe asset review screen will show a button labeled “Accessibility Details”.

5. When Reviewer clicks on the button, it shows the same popup as shown to the creator. The information populated by the creator is shown by default. It can be updated by the reviewer based on the configuration.

6. The published asset will have the final information stored and can be obtained by reading the asset.

...

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 : In Case of PDF, Any Resources generated by converting image to PDF has to get highlighted with error.

QuML : In Case of QuML, All the QuML responses 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.

Video : Video transcripts need to be available for users to make sense of the content.

Enable assets have auto-readability for image etc.

As per WCAG guidelines, The Readability of the images is of prime importance as any included images in the context should be readable by screeb readers.

Enable creators choose proper color, fonts

Contrast Ratio and font size validation has to be done while creation of assets and mark the content as explicitly “Non Accessible“ Content in case of creator intends to bypass these validation errors.

Should have steps for the creator of asset to self certify the content whether it is accessible compliant or not.

As a Platform, we might have to explicitly tag the content as Accessible Friendly Or not against each asset created on the platform.

Enable uploading transcript to videos

The objective of this capability is to enable accessibility of the videos to the users with hearing challenges. The video transcript will be used to show subtitles/captions when the video is played.

This is to enable providing transcripts to a video content that is created.

Note: Videos can also be uploaded as part of a solution to a Question or as part of an interactive content (created through content editor). But the scope of the current story is only to upload transcripts when an individual video content that is created through uploading a video. This can be further enhanced in future to take care of other workflows.

The following sections detail the flows for the current scope:

Create video content

1. The user with contributor/creator role starts creating a content that has video (mp4 or web) as one of the supported formats.

2. User uploads the video from local machine.

3. User has an option to upload transcript

   1. User can choose a language and upload the transcript

   2. User can upload transcripts for multiple languages

   3. User can only upload one transcript for one language

   4. The list of languages come from a preconfigured list of languages supported in the system

   5. The transcript file extension can only be one of the allowed types, that are configured. Example .srt

   6. There can be a configuration at system/tenant level if transcript file is mandatory or optional. It is optional by default (if there is no configuration).

4. User uploads one or more transcript files (one for each language).

5. User saves the content.

6. User has the following options in the editor, to manage transcript files:

   1. Download a transcript file

   2. Replace a transcript file uploaded earlier

   3. Remove a transcript file

   4. Add one ore more transcript files

7. User finally submits content for review

Review video content

1. The user with reviewer role opens a video content for review.

2. The review page provides an option to see the list of transcript files uploaded for each language (if any).

3. If there are no transcript file uploaded, no option to download the transcript files is shown.

4. If there are one or more transcript files uploaded, there is an option for the reviewer to download the transcript files.

5. The reviewer can download the transcript file and review it offline as required.

6. Rest of the review flow is as is.

Modify published video content

As part of modification flow of a video content, the creator will be able to download/delete/replace/add one or more transcript files as in the creation flow. The modifications are saved.