[XDA Developer TV] meltwater:
I totally agree with both of you, technology should be a enabler of content to those with sight and/or hearing difficulties, not a barrier. The hardware is more than capable, it is down to people designing it in.

To go slightly off-topic, I recently saw a Braille keyboard implementation for tablets, something which had not occurred to me, but highly useful for those who would otherwise need to pay a lot of money for one. I started looking at Braille displays and it is serious money (even a single line display) for something which would make a huge difference to someone, technology should be able to provide solutions at better prices (i.e. Kindle for the blind).

I hope that Google gets the Android Open Accessory function they've been talking about since this could potentially allow for low cost custom devices for a range of needs.

I think quite often this is not considered enough when things are being designed, such as the freeview standards, it wouldn't have taken much to adapt the red button service to also include a "signing overlay" like they have for late night repeats, so they could be available all the time (and taken off if not required). While they are at it they could have also included censor codes in the sound-track so bad language etc can be filtered if required.

Anyway, back to topic. I don't view youtube directly (due to access issues of when I am able to view content) but I'm working on automated extracting of content (able to grab the videos and create the podcast). My initial look at the CC stuff on youtube suggested the data is accessible, so potentially it could be used if it was there.

I guess the view should be that anything is better than nothing, so even if the transcript isn't redone after recording/editing it will still provide a means to test with and hopefully some assistance for some. A perfect transcript and CC would probably be time consuming, but even if a quick dump of the prompter file would be enough for testing with.

So..what do we need?

1. Support of people who want this (an idea of users who would want this would help drive it's development - this would probably include non-native english persons - that includes american's who can't understand Queens/Brummy Engish and vice-a-versa)

2. Test video(s) with CC (ideally an Xda one) - don't have to be fully done, but something would be useful (also would help the authors get into the habit of including them hopefully).

3. Information about current methods other broadcasters, podcasts etc implement CC delivery (in-particular I'm interested if there is a standard way to include CC files as additional enclosures on RSS feeds).

4. Application support:

a) NathanPC's XdaTv apps would be an ideal place for support.

b) I am hopeful that the excellent Android podcast/RSS reader application BeyondPod could include such support if a standard way of delivering caption content is determined, as the developer there is very proactive with meeting the needs of users.

On Item 3: So far not found many examples of it being done.

My current thinking on RSS is that it doesn't officially (although heard some feeds do this) support multiple enclosures, so for best support it may need to be created as a secondary feed (not all readers will allow download of more than one enclosure per an item). This would then create the issue of putting the videos back with the subtitles, this would be harder to support automatically unless all media is put in the same directory (I don't think this is common).

So far the options as I see it are:

a) One feed for videos and a separate one for subtitle files, would probably require the user to copy the files into the same directory afterwards (video & subtitle file should would as long as the reader uses the name from the feed when downloaded).

b) Single feed with multiple enclosures, breaks the standard, and not many readers will download more than one file per an item.

c) Single feed with duplicated items (one for video and one for subtitle), makes handling items a pain as additional items are added in the feed.

Here's an interesting service, which perhaps could be put into use:

http://dotsub.com/tutorials