|
|
| Line 86: |
Line 86: |
| * haptic representation: braille text | | * haptic representation: braille text |
| * aural representation: auditive descriptions, text-to-speech (TTS) screen-reader | | * aural representation: auditive descriptions, text-to-speech (TTS) screen-reader |
| * mouse replacement: tabbing through content
| |
|
| |
|
| The following are actual technologies that can provide such channels for audio & video files: | | The following are actual technologies that can provide such channels for audio & video files: |
| Line 113: |
Line 112: |
|
| |
|
| MULTIPLEX INTO OGG: as extra timed text track | | MULTIPLEX INTO OGG: as extra timed text track |
|
| |
| ==== Tabbing through video ====
| |
| * as a video plays back, people have the opportunity to click on the timeline and randomly access offset points in video
| |
| * blind people don't have the opportunity to use a mouse to access content
| |
| * the general means of navigation for blind people is tabbing through content structure
| |
| * video (in particular video that has audio descriptions) needs to have a structure that can be accessed via tabbing through it, to allow (blind) people to directly jump to areas of interest
| |
| Discussion:
| |
| * (+) providing video with a structure for direct access to fragments is useful not just to blind people
| |
| * (+) audio should also be able to be structured in this way
| |
|
| |
| POSSIBLE SOLUTION: the structure of the file created through timed text tracks should be accessible from the Web page and access be controlled through a javascript API
| |
|
| |
|
| |
|
| === Requirements for internationalisation === | | === Requirements for internationalisation === |