From 6c7783cd6f9a5c64368fbcc61b0d1f9930e6d55c Mon Sep 17 00:00:00 2001 From: Mike Gower Date: Mon, 7 Apr 2025 16:07:00 -0700 Subject: [PATCH 1/5] Meeting audio description through existing narration - Added the word "additional" to note 1 - Added a new technique "Providing audio descriptions by incorporating narration into the existing soundtrack" --- techniques/general/G226.html | 51 +++++++++++++++++++ ...tion-or-media-alternative-prerecorded.html | 5 +- .../20/audio-description-prerecorded.html | 8 ++- 3 files changed, 61 insertions(+), 3 deletions(-) create mode 100644 techniques/general/G226.html diff --git a/techniques/general/G226.html b/techniques/general/G226.html new file mode 100644 index 0000000000..60a396b2d6 --- /dev/null +++ b/techniques/general/G226.html @@ -0,0 +1,51 @@ +Providing audio descriptions by incorporating narration into the existing soundtrack

Providing audio descriptions by incorporating narration into the existing soundtrack

ID: G173

Technology: general

Type: Technique

When to Use

+

Any technology that supports audio and video.

+

Description

+

The objective of this technique is to provide audio descriptions through narrative incorporated into the soundtrack of the synchronized video, so that it is possible for people who cannot see to be able to understand important visual material.

+

Since most user agents today cannot merge multiple sound tracks, this technique adds additional context by revising the draft or pre-existing soundtrack so that the narrative includes audio description via a single audio track. This additional information may address actions, characters, scene changes, and on-screen text (not captions) that are important to understanding the content.

+

The existing narrative is either revised or new narrative is added during pauses in existing dialogue. This limits the amount of supplementary information that can be added to program.

+

This technique is most appropriate in instructional, marketing, and other videos where the narrative is intended to be informational. In such cases, a soundtrack which reinforces the visual "takeaways" in the video will be vital to blind people and people with low vision, and may be of use to many users, including some users with cognitive disabilities.

+

Examples

+

An instructional video is scripted with narration that describes important visual content

+

Someone creating a instructional video demonstrating the features of an application, or recording a slide presentation, prepares a script where what is being shown visually is reinforced through the narration, to arrive at an efficient and cost-effective means of making accessible videos and presentations.

+

Here are some key points to make the narration and presentation delivery accessible. Each is elaborated on in the following sections:

+
    +
  1. Describe any pertinent and meaningful text on the screen or slide
    2. +
  2. Avoid saying only “this” or “here” to describe UI components
    3. +
  3. For better context, describe elements by sensory perceptions as well as by label
    4. +
  4. Fully describe sequences of action, including any dynamic content that appears
    5. +
  5. When a main page or dialog appears, say its title and describe its features
    6. +
  6. When using a mouse to show something (such as to hover, select, scroll, and open), say what you are doing
    7. +
+

Describe any pertinent and meaningful text on the screen or slide

+

When referring to URLs, dialogs, labels, and headings, read out the text. Sometimes presenters (narrators) just highlight or point to text; speaking the visible text ensures this meaningful text is made accessible to everyone including blind users or those with low vision. When describing actions a user can do, be sure to specifically state the button names to improve the context (e.g., "choose the green 'Go' button").

+

Avoid saying only “this” or “here” to describe UI components

+

This goes hand in hand with the first rule to announce text on the screen. When presenters (narrators) point out “this button” or say “you'll see this”, they are typically referring to a visual cue they are providing on the screen or slide. Someone who can't see the screen or slide lacks the context to understand what is being referenced. Replace or augment “this” and “here” with the labels/titles to provide context: “Choose the blue Save button”, “The Profile Settings dialog appears with several options”.

+

For better context, describe elements by sensory perceptions as well as by label

+

Including position and other sensory qualities like color can really help some low vision users and users with cognitive disabilities. However, you will want to include other context, such as structural headings, in addition to position, which may not be very helpful to some blind users. For components with visible labels, always read out the label when referring to the component. Where a visible label is absent, but you are aware of other programmatic labeling that will be read by the screen reader (e.g., the aria-label property; page regions), use that text. Also include placement and structure (headings) on the page or slide (e.g., “the red “Cancel” button at the bottom right of the dialog”, “Select the “online only” radio button in the Settings options”).

+

Fully describe sequences of action, including any dynamic content that appears

+

When you are demonstrating a process, be sure to describe all steps you are carrying out. As well, announce when status messages appear, such as “loading”, and when other content appears or disappears on the screen or next slide.

+

When a main page, new slide, or dialog appears, say its title and describe its features

+

When a dialog, slide, or page appears, read out its title. For a new page, also describe its purpose or any distinguishing characteristics. Practice a natural storytelling style that does not simply read the text on the slide or screen.

+

When using a mouse to show something (such as to hover, select, scroll, or open), say what you are doing

+

When operating the content, especially by mouse, announce what you plan to do before doing it, then describe while you are interacting with it, and finally summarize what you just did.

+

Additional narration is added to gaps in the existing soundtrack

+

A marketing video does not contain any important visuals which cannot be inferred from the audio soundtrack. However, it uses on-screen text to identify new speakers, as well as to provide a url at the end of the video where people can go for more information. In post-production a new narrator announces the onscreen text in gaps in the dialog.

+

Tests

+

Procedure

+
    +
  1. Open the synchronized media that includes audio description.
    2. +
  2. Listen to the movie.
    3. +
  3. Check to see if the main narration is used to convey important information in the visual content, such as new speakers and on-screen text.
    4. +
  4. Where important visual information is not conveyed through the soundtrack or addressed in the original narration, check to see if additional narration has been added in available gaps in the dialog.
    5. +
+
+

Expected Results

+
    +
  • #3 and #4 are true.
    • +
+
+
\ No newline at end of file diff --git a/understanding/20/audio-description-or-media-alternative-prerecorded.html b/understanding/20/audio-description-or-media-alternative-prerecorded.html index 38cbc11fd0..423e733b25 100644 --- a/understanding/20/audio-description-or-media-alternative-prerecorded.html +++ b/understanding/20/audio-description-or-media-alternative-prerecorded.html @@ -58,7 +58,7 @@

Intent of Audio Description or Media Alternative (Prerecorded)

For 1.2.3 and 1.2.5, if all of the important information in the video track is already - conveyed in the audio track, no audio description is necessary. + conveyed in the audio track, no additional audio description is necessary.

@@ -255,6 +255,9 @@

Sufficient Techniques for Audio Description or Media Alternative (Prerecorde Providing audio description in SMIL 2.0 +
  • + Providing audio descriptions by incorporating narration into the existing soundtrack +
  • Using any player that supports audio and video
    • diff --git a/understanding/20/audio-description-prerecorded.html b/understanding/20/audio-description-prerecorded.html index 1f971d0ce7..b3b737582e 100644 --- a/understanding/20/audio-description-prerecorded.html +++ b/understanding/20/audio-description-prerecorded.html @@ -35,7 +35,7 @@

    Intent of Audio Description (Prerecorded)

    For 1.2.3 and 1.2.5, if all of the important information in the video track is already - conveyed in the audio track, no audio description is necessary. + conveyed in the audio track, no additional audio description is necessary.

    @@ -186,7 +186,11 @@

    Sufficient Techniques for Audio Description (Prerecorded)

    Providing audio description in SMIL 2.0 - + +
  • + Providing audio descriptions by incorporating narration into the existing soundtrack +
    • +
  • Using any player that supports audio and video
    • From 1e2a155e4016a61ab9ba08f10c83f33545048914 Mon Sep 17 00:00:00 2001 From: Mike Gower Date: Mon, 7 Apr 2025 16:16:39 -0700 Subject: [PATCH 2/5] Changed technique title Changed the preposition from "into" to "to" --- techniques/general/G226.html | 2 +- .../audio-description-or-media-alternative-prerecorded.html | 3 ++- understanding/20/audio-description-prerecorded.html | 4 ++-- 3 files changed, 5 insertions(+), 4 deletions(-) diff --git a/techniques/general/G226.html b/techniques/general/G226.html index 60a396b2d6..5d0807f10f 100644 --- a/techniques/general/G226.html +++ b/techniques/general/G226.html @@ -1,4 +1,4 @@ -Providing audio descriptions by incorporating narration into the existing soundtrack

    Providing audio descriptions by incorporating narration into the existing soundtrack

    ID: G173

    Technology: general

    Type: Technique

    When to Use

    +Providing audio descriptions by incorporating narration in the existing soundtrack

    Providing audio descriptions by incorporating narration in the existing soundtrack

    ID: G173

    Technology: general

    Type: Technique

    When to Use

    Any technology that supports audio and video.

    Description

    The objective of this technique is to provide audio descriptions through narrative incorporated into the soundtrack of the synchronized video, so that it is possible for people who cannot see to be able to understand important visual material.

    diff --git a/understanding/20/audio-description-or-media-alternative-prerecorded.html b/understanding/20/audio-description-or-media-alternative-prerecorded.html index 423e733b25..404f2d784d 100644 --- a/understanding/20/audio-description-or-media-alternative-prerecorded.html +++ b/understanding/20/audio-description-or-media-alternative-prerecorded.html @@ -255,8 +255,9 @@

    Sufficient Techniques for Audio Description or Media Alternative (Prerecorde Providing audio description in SMIL 2.0 +
  • - Providing audio descriptions by incorporating narration into the existing soundtrack + Providing audio descriptions by incorporating narration in the existing soundtrack
  • Using any player that supports audio and video
    • diff --git a/understanding/20/audio-description-prerecorded.html b/understanding/20/audio-description-prerecorded.html index b3b737582e..48a99d3834 100644 --- a/understanding/20/audio-description-prerecorded.html +++ b/understanding/20/audio-description-prerecorded.html @@ -188,9 +188,9 @@

    Sufficient Techniques for Audio Description (Prerecorded)

  • - Providing audio descriptions by incorporating narration into the existing soundtrack + Providing audio descriptions by incorporating narration in the existing soundtrack
    • - +
  • Using any player that supports audio and video
    • From 2fb837996b45a9e15818cfbc3801e1e22d189823 Mon Sep 17 00:00:00 2001 From: Mike Gower Date: Mon, 7 Apr 2025 16:35:10 -0700 Subject: [PATCH 3/5] Update G226.html Updated the ID, and made editorial changes to improve the new technique --- techniques/general/G226.html | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/techniques/general/G226.html b/techniques/general/G226.html index 5d0807f10f..2231ef3863 100644 --- a/techniques/general/G226.html +++ b/techniques/general/G226.html @@ -1,14 +1,14 @@ -Providing audio descriptions by incorporating narration in the existing soundtrack

    Providing audio descriptions by incorporating narration in the existing soundtrack

    ID: G173

    Technology: general

    Type: Technique

    When to Use

    +Providing audio descriptions by incorporating narration in the existing soundtrack

    Providing audio descriptions by incorporating narration in the existing soundtrack

    ID: G226

    Technology: general

    Type: Technique

    When to Use

    Any technology that supports audio and video.

    Description

    -

    The objective of this technique is to provide audio descriptions through narrative incorporated into the soundtrack of the synchronized video, so that it is possible for people who cannot see to be able to understand important visual material.

    +

    The objective of this technique is to provide audio descriptions through narrative incorporated into the soundtrack of the synchronized video, so that people who cannot see are able to understand important visual material.

    Since most user agents today cannot merge multiple sound tracks, this technique adds additional context by revising the draft or pre-existing soundtrack so that the narrative includes audio description via a single audio track. This additional information may address actions, characters, scene changes, and on-screen text (not captions) that are important to understanding the content.

    -

    The existing narrative is either revised or new narrative is added during pauses in existing dialogue. This limits the amount of supplementary information that can be added to program.

    +

    The existing narrative is either revised or new narrative is added during pauses in existing dialogue (which potentially limits the amount of supplementary narration that can be added).

    This technique is most appropriate in instructional, marketing, and other videos where the narrative is intended to be informational. In such cases, a soundtrack which reinforces the visual "takeaways" in the video will be vital to blind people and people with low vision, and may be of use to many users, including some users with cognitive disabilities.

    Examples

    An instructional video is scripted with narration that describes important visual content

    Someone creating a instructional video demonstrating the features of an application, or recording a slide presentation, prepares a script where what is being shown visually is reinforced through the narration, to arrive at an efficient and cost-effective means of making accessible videos and presentations.

    -

    Here are some key points to make the narration and presentation delivery accessible. Each is elaborated on in the following sections:

    +

    Several key strategies help the narration improve a video's accessibility. Each is described more fully in the following subsections:

    1. Describe any pertinent and meaningful text on the screen or slide
    2. Avoid saying only “this” or “here” to describe UI components
      3. @@ -18,19 +18,19 @@

      An instructional video is scripted with narration that describes important v
    3. When using a mouse to show something (such as to hover, select, scroll, and open), say what you are doing

    Describe any pertinent and meaningful text on the screen or slide

    -

    When referring to URLs, dialogs, labels, and headings, read out the text. Sometimes presenters (narrators) just highlight or point to text; speaking the visible text ensures this meaningful text is made accessible to everyone including blind users or those with low vision. When describing actions a user can do, be sure to specifically state the button names to improve the context (e.g., "choose the green 'Go' button").

    +

    When referring to URLs, dialogs, labels, and headings, read out the text. Sometimes presenters (narrators) just highlight or point to text; speaking the visible text ensures this meaningful text is made accessible to everyone including blind users or those with low vision. When describing actions a user can do, be sure to specifically state the button names to improve the context (for example, "choose the green 'Go' button").

    Avoid saying only “this” or “here” to describe UI components

    -

    This goes hand in hand with the first rule to announce text on the screen. When presenters (narrators) point out “this button” or say “you'll see this”, they are typically referring to a visual cue they are providing on the screen or slide. Someone who can't see the screen or slide lacks the context to understand what is being referenced. Replace or augment “this” and “here” with the labels/titles to provide context: “Choose the blue Save button”, “The Profile Settings dialog appears with several options”.

    +

    This goes hand in hand with the first rule to announce text on the screen. When presenters (narrators) point out “this button” or say “you'll see this”, they are typically referring to a visual cue they are providing on the screen or slide. Someone who can't see the screen or slide lacks the context to understand what is being referenced. Replace or augment “this” and “here” with the labels/titles to provide context: “Choose the blue Save button”, “The Profile Settings dialog appears, with several options.”

    For better context, describe elements by sensory perceptions as well as by label

    -

    Including position and other sensory qualities like color can really help some low vision users and users with cognitive disabilities. However, you will want to include other context, such as structural headings, in addition to position, which may not be very helpful to some blind users. For components with visible labels, always read out the label when referring to the component. Where a visible label is absent, but you are aware of other programmatic labeling that will be read by the screen reader (e.g., the aria-label property; page regions), use that text. Also include placement and structure (headings) on the page or slide (e.g., “the red “Cancel” button at the bottom right of the dialog”, “Select the “online only” radio button in the Settings options”).

    +

    Including position and other sensory qualities like color can really help some low vision users and users with cognitive disabilities. However, you will want to include other context, such as structural headings, in addition to position (which is usually not very helpful to blind user). For components with visible labels, always read out the label when referring to the component. Where a visible label is absent, but you are aware of other programmatic labeling that will be read by the screen reader (for example, the aria-label property or page regions), use that text. Also include placement and structure (headings) on the page or slide (for example, “the red “Cancel” button at the bottom right of the dialog”, “Select the “online only” radio button in the Settings options”).

    Fully describe sequences of action, including any dynamic content that appears

    -

    When you are demonstrating a process, be sure to describe all steps you are carrying out. As well, announce when status messages appear, such as “loading”, and when other content appears or disappears on the screen or next slide.

    +

    When you are demonstrating a process, be sure to describe all steps you are carrying out. As well, announce when status messages appear, such as “loading”, and when other content appears or disappears on the screen or slide.

    When a main page, new slide, or dialog appears, say its title and describe its features

    When a dialog, slide, or page appears, read out its title. For a new page, also describe its purpose or any distinguishing characteristics. Practice a natural storytelling style that does not simply read the text on the slide or screen.

    When using a mouse to show something (such as to hover, select, scroll, or open), say what you are doing

    -

    When operating the content, especially by mouse, announce what you plan to do before doing it, then describe while you are interacting with it, and finally summarize what you just did.

    +

    When performing complex interactions, especially by mouse, it is sometimes helpful to announce what you plan to do before doing it, then narrate while you are interacting with it, and finally summarize what you just did.

    Additional narration is added to gaps in the existing soundtrack

    -

    A marketing video does not contain any important visuals which cannot be inferred from the audio soundtrack. However, it uses on-screen text to identify new speakers, as well as to provide a url at the end of the video where people can go for more information. In post-production a new narrator announces the onscreen text in gaps in the dialog.

    +

    A marketing video's important visuals can be mainly inferred from the audio soundtrack. However, it only uses on-screen text to identify new speakers, as well as to provide a url at the end of the video where people can go for more information. In post-production a new narrator announces the onscreen text in gaps in the dialog.

    Tests

    Procedure

      From 68a772f855f3b8bc9147adb197202053550790e5 Mon Sep 17 00:00:00 2001 From: Mike Gower Date: Mon, 7 Apr 2025 21:25:43 -0700 Subject: [PATCH 4/5] Update G226.html Removed the references to a slide presentation --- techniques/general/G226.html | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/techniques/general/G226.html b/techniques/general/G226.html index 2231ef3863..a65c3f0f44 100644 --- a/techniques/general/G226.html +++ b/techniques/general/G226.html @@ -7,26 +7,26 @@

      This technique is most appropriate in instructional, marketing, and other videos where the narrative is intended to be informational. In such cases, a soundtrack which reinforces the visual "takeaways" in the video will be vital to blind people and people with low vision, and may be of use to many users, including some users with cognitive disabilities.

    Examples

    An instructional video is scripted with narration that describes important visual content

    -

    Someone creating a instructional video demonstrating the features of an application, or recording a slide presentation, prepares a script where what is being shown visually is reinforced through the narration, to arrive at an efficient and cost-effective means of making accessible videos and presentations.

    -

    Several key strategies help the narration improve a video's accessibility. Each is described more fully in the following subsections:

    +

    Someone creating an instructional video demonstrating the features of an application prepares a script where what is being shown visually is reinforced through the narration, to arrive at an efficient and cost-effective means of making a more accessible video.

    +

    Several key strategies are followed to improve the video's narration. Each is described more fully in the following subsections:

      -
    1. Describe any pertinent and meaningful text on the screen or slide
      2. +
    2. Describe any pertinent and meaningful text on the screen
    3. Avoid saying only “this” or “here” to describe UI components
    4. For better context, describe elements by sensory perceptions as well as by label
    5. Fully describe sequences of action, including any dynamic content that appears
    6. When a main page or dialog appears, say its title and describe its features
    7. When using a mouse to show something (such as to hover, select, scroll, and open), say what you are doing
    -

    Describe any pertinent and meaningful text on the screen or slide

    +

    Describe any pertinent and meaningful text on the screen

    When referring to URLs, dialogs, labels, and headings, read out the text. Sometimes presenters (narrators) just highlight or point to text; speaking the visible text ensures this meaningful text is made accessible to everyone including blind users or those with low vision. When describing actions a user can do, be sure to specifically state the button names to improve the context (for example, "choose the green 'Go' button").

    Avoid saying only “this” or “here” to describe UI components

    -

    This goes hand in hand with the first rule to announce text on the screen. When presenters (narrators) point out “this button” or say “you'll see this”, they are typically referring to a visual cue they are providing on the screen or slide. Someone who can't see the screen or slide lacks the context to understand what is being referenced. Replace or augment “this” and “here” with the labels/titles to provide context: “Choose the blue Save button”, “The Profile Settings dialog appears, with several options.”

    +

    This goes hand in hand with the first rule to announce text on the screen. When presenters (narrators) point out “this button” or say “you'll see this”, they are typically referring to a visual cue they are providing on the screen. Someone who can't see the screen lacks the context to understand what is being referenced. Replace or augment “this” and “here” with the labels/titles to provide context: “Choose the blue Save button”, “The Profile Settings dialog appears, with several options.”

    For better context, describe elements by sensory perceptions as well as by label

    -

    Including position and other sensory qualities like color can really help some low vision users and users with cognitive disabilities. However, you will want to include other context, such as structural headings, in addition to position (which is usually not very helpful to blind user). For components with visible labels, always read out the label when referring to the component. Where a visible label is absent, but you are aware of other programmatic labeling that will be read by the screen reader (for example, the aria-label property or page regions), use that text. Also include placement and structure (headings) on the page or slide (for example, “the red “Cancel” button at the bottom right of the dialog”, “Select the “online only” radio button in the Settings options”).

    +

    Including position and other sensory qualities like color can really help some low vision users and users with cognitive disabilities. However, you will want to include other context, such as structural headings, in addition to position (which is usually not very helpful to blind user). For components with visible labels, always read out the label when referring to the component. Where a visible label is absent, but you are aware of other programmatic labeling that will be read by the screen reader (for example, the aria-label property or page regions), use that text. Also include placement and structure (headings) on the page (for example, “the red “Cancel” button at the bottom right of the dialog”, “Select the “online only” radio button in the Settings options”).

    Fully describe sequences of action, including any dynamic content that appears

    -

    When you are demonstrating a process, be sure to describe all steps you are carrying out. As well, announce when status messages appear, such as “loading”, and when other content appears or disappears on the screen or slide.

    -

    When a main page, new slide, or dialog appears, say its title and describe its features

    -

    When a dialog, slide, or page appears, read out its title. For a new page, also describe its purpose or any distinguishing characteristics. Practice a natural storytelling style that does not simply read the text on the slide or screen.

    +

    When you are demonstrating a process, be sure to describe all steps you are carrying out. As well, announce when status messages appear, such as “loading”, and when other content appears or disappears on the screen.

    +

    When a main page or dialog appears, say its title and describe its features

    +

    When a dialog or page appears, read out its title. For a new page, also describe its purpose or any distinguishing characteristics. Practice a natural storytelling style that does not simply read the text on the screen.

    When using a mouse to show something (such as to hover, select, scroll, or open), say what you are doing

    When performing complex interactions, especially by mouse, it is sometimes helpful to announce what you plan to do before doing it, then narrate while you are interacting with it, and finally summarize what you just did.

    Additional narration is added to gaps in the existing soundtrack

    From 898215d80bf09a16d60fa0cd50530bc6d25c5e08 Mon Sep 17 00:00:00 2001 From: Mike Gower Date: Tue, 15 Apr 2025 16:01:00 -0700 Subject: [PATCH 5/5] Remove "existing" from title Based on comments stripped out the adjective so it just covers narration added to the soundtrack --- techniques/general/G226.html | 2 +- .../20/audio-description-or-media-alternative-prerecorded.html | 2 +- understanding/20/audio-description-prerecorded.html | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/techniques/general/G226.html b/techniques/general/G226.html index a65c3f0f44..5f20d6273f 100644 --- a/techniques/general/G226.html +++ b/techniques/general/G226.html @@ -1,4 +1,4 @@ -Providing audio descriptions by incorporating narration in the existing soundtrack

    Providing audio descriptions by incorporating narration in the existing soundtrack

    ID: G226

    Technology: general

    Type: Technique

    When to Use

    +Providing audio descriptions by incorporating narration in the soundtrack

    Providing audio descriptions by incorporating narration in the soundtrack

    ID: G226

    Technology: general

    Type: Technique

    When to Use

    Any technology that supports audio and video.

    Description

    The objective of this technique is to provide audio descriptions through narrative incorporated into the soundtrack of the synchronized video, so that people who cannot see are able to understand important visual material.

    diff --git a/understanding/20/audio-description-or-media-alternative-prerecorded.html b/understanding/20/audio-description-or-media-alternative-prerecorded.html index 404f2d784d..5ae68ca320 100644 --- a/understanding/20/audio-description-or-media-alternative-prerecorded.html +++ b/understanding/20/audio-description-or-media-alternative-prerecorded.html @@ -257,7 +257,7 @@

    Sufficient Techniques for Audio Description or Media Alternative (Prerecorde
  • - Providing audio descriptions by incorporating narration in the existing soundtrack + Providing audio descriptions by incorporating narration in the soundtrack
  • Using any player that supports audio and video
    • diff --git a/understanding/20/audio-description-prerecorded.html b/understanding/20/audio-description-prerecorded.html index 48a99d3834..a17946d442 100644 --- a/understanding/20/audio-description-prerecorded.html +++ b/understanding/20/audio-description-prerecorded.html @@ -188,7 +188,7 @@

    Sufficient Techniques for Audio Description (Prerecorded)

  • - Providing audio descriptions by incorporating narration in the existing soundtrack + Providing audio descriptions by incorporating narration in the soundtrack
  • Using any player that supports audio and video