Computing at UW-MadisonDivision of Information Technology
Students Faculty/Staff Services Services A through D Services E through L Services M through R Services S through Z Help Desk Tech Store About DoIT   

Accessibility

Transcribing Podcasts

The following are the transcripts as they were received:

"Is Your Document Accessible"

  1. Premium Business Serrvice Transcript:

    Is Your Document Accessible?
    (2 minutes, 57 seconds, 2.1 MB)

    Author: Neal Ewers, Ravenswood Productions
    Local phone: 608-277-1995, Toll Free: 888-544-8332
    Email: neal.ewers@ravenswood.org, http://www.ravenswood.org

    I think there are two things that make a document accessible. First of all the information has to be present. That seems kind of obvious, actually, but it really doesn’t always happen. If for example you have a printer that is almost out of ink, and you print something, and the text is almost illegible, then that information isn’t really there. If the color contrast between the paper and the ink is such that the document can’t be read easily, then again, that information isn’t really there.

    If you’ve created a document, by making an image of a page, and that image is not really clear, then the document can be very fuzzy and some people won’t be able to read it. And if you try to enlarge that image with magnification software, the text is going to be so grainy that it is not going to be able to be read either. In addition, if you try to read that text with any kind of speech software, which you might be using to supplement what you are seeing, the information won’t be read because screen reading software only reads information that is text oriented, not graphical.

    So there are any number of reasons why the information just may not be there in the first place.

    Secondly, the information that is there has to be able to be navigated in such a way that the user can understand the document based on how it is laid out. In the early days when people were using ASCII text files, you could get a document with line after line after line of unbroken text. How is one supposed to know where the paragraph boundaries were, where the headers were, where the list items were, etcetera? So the information was there, but you weren’t able to navigate to the parts of the document you needed. If I’m writing a document and I want certain points to be obvious, I’m going either leave white space around them so that they stand out, I’m going to make them a different color, I’m going to make them a different size, I’m going to make them bold print, or italic, or whatever. I’m going to do something to help people get to the points of the document that I think are relevant as quickly as they can. So a document has to be navigable. People are likely going to be reading your document using different forms of reading devices. Some people might look at it visually, and that is enough for them. Some people might use voice or screen reading technology to listen to the document at the same time they are reading it in print. Some people may use it on a computer. Some people may look at it on paper. In whatever way the document is used, it has to be able to be navigated in a way that people can get to the points they want to get to. That means you have to give some thought to the layout of the document just as you do to the content. So if the information is there and readable, and if it is able to be navigable, that goes a long way towards making it accessible.

  2. CastingWords

    -------- Original Message --------
    Subject: Your Transcript is Ready
    Date: Thu, 21 Sep 2006 23:28:18 -0700
    From: support@castingwords.com
    To: eacurran@doit.wisc.edu

    Hi Elizabeth,
    We've just finished transcribing a podcast for you, "doc accessible". The text is below and you can download the results in these formats as well:
    RTF: http://castingwords.com/transcripts/zv6/14825.rtf
    html: http://castingwords.com/transcripts/zv6/14825.html
    text: http://castingwords.com/transcripts/zv6/14825.txt

    Please write if you have any questions or comments. We look forward to transcribing more audio for you in the future!

    The castingWords team,
    support@castingwords.com
    http://castingwords.com

    more formats:
    alternate html: http://castingwords.com/transcripts/zv6/14825-a.html
    formated text: http://castingwords.com/transcripts/zv6/14825.text

    --------------

    Man: I think there are two things that make a document accessible. First of all, the information has to be present; that seems kind of obvious, actually, but it really doesn't always happen.

    If, for example, you have a printer that's almost out of ink, and you print something and the text is almost illegible, then that information isn't really there. If the color contrast between the paper and the ink is such that the document can't be read easily, then again, that information isn't really there. If you've created a document by making an image of a page, and that image is not really clear, then the document can be very fuzzy and some people won't be able to read it. And if you try to enlarge that image with magnification software the text is going to be so grainy that it's not going to be able to be read either. In addition, if you try to read that text with any kind of speech software which you might be using to supplement what you're seeing, the information won't be read, because screen reading software only reads information that is text oriented, not graphical. So there are any number of reasons why the information just may not be there in the first place.

    Secondly, the information that is there has to be able to be navigated in such a way that the user can understand the document based on how it's laid out. In the early days when people were using ASCII test files you could get a document with line after line after line of unbroken text. How was one supposed to know where the paragraph boundaries were, where the headers were, where the list items were, et cetera? So the information was there, but you weren't able to navigate to the parts of the document you needed.

    If I'm writing a document and I want certain points to be obvious I'm going to either leave white space around them so that they stand out, I'm going to make them a different color, I'm going to make them a different size, I'm going to make them bold print, or italic, or whatever. I'm going to do something to help people get to the points of the document that I think are relevant as quickly as they can.

    So a document has to be navigable. People are likely going to be reading your document using different forms of reading devices. Some people might look at it visually, and that is enough for them. Some people might use voice or screen reading technology to listen to the document at the same time they're reading it in print. Some people may use it on a computer, some people may look at it on paper. In whatever way the document's used, it has to be able to be navigated in a way that people can get to the points they want to get to. That means you have to give some thought to the layout of the document, just as you do to the content. So if the information is there, and readable, and if it's able to be navigated, that goes a long way to making a document accessible.

  3. Enablr

    From: clement.lo@kingmarketing.ca
    Subject: Transcript
    Date: September 18, 2006 2:26:40 PM CDT
    To: alice.anderson@doit.wisc.edu

    Hi Alice,

    Thank you very much for your business. Please find your transcript attached to this e-mail.

    Sincerely,
    Clement Lo

    --
    Enablr.com

    Alice Anderson Sample
    The audio for this podcast can be downloaded at

    I think there are two things that make a document accessible. First of all, the information has to be present. That seems kind of obvious, actually, but it really doesn't always happen. If, for example, you have a printer that is almost out of ink, and you print something and the text is almost illegible then that information isn't really there. If the color contrast between the paper and the ink is such that the document can't be read easily, then again, that information isn't really there. If you've created a document by making an image of a page and that image is not really clear then the document can be very fuzzy and some people won't be able to read it. If you try to enlarge that image with magnification software, the text is going to be so grainy that it is not going to be able to be read either.
    0:48

    In addition, if you try to read that text with any kind of speech software, which you might be using to supplement what you’re seeing, the information won't be read. Because screen reading software only reads information that is text oriented, not graphical. So there is any number of reasons why the information just may not be there in the first place.

    1:11
    Secondly, the information that is there has to be able to be navigated in such a way that the user can understand the document based on how it's laid out.

    1:21
    In the early days, when people were using ASCII text files, you can get a document with line after line after line of unbroken text. How was one supposed to know where the paragraph boundaries were? Where the headers were? Where the list items were? Etc. So the information was there but you weren't able to navigate to the part of the document you needed.

    1:42
    If I'm writing a document and I want certain points to be obvious, I'm going to either leave white space around them so that they stand out. I'm going to make them a different color. I'm going to make them a different size. I'm going to make them bold print or italic or whatever. I'm going to do something to help people get to the point of the document that I think are relevant as quickly as they can. So a document has to be navigable.

    2:09
    People are likely going to be reading your document using different forms of reading devices. Some people might look at it visually and that is enough for them. Some people might use voice or screen reading technology to listen to the document at the same time they're reading it in print. Some people may use it on a computer. Some people may look at it on paper.

    2:35
    In whatever way the document is used, it has to be able to be navigated in a way that people can get to the point they want to get to. That means you have to give some thought to the layout of the document just as you do to the content. So if the information is there and readable, and if it's able to be navigated, that goes a long way to making a document accessible.

  4. Podclerk

    -------- Original Message --------
    Subject: Order Number 2571716876
    Date: Sat, 16 Sep 2006 10:00:04 -0400
    From: postmaster@podclerk.com
    Reply-To: postmaster@podclerk.com
    To:

    Dear XXX,

    Attached please find the transcription file for the above order. It is renamed to ".tx_" but notepad can open it.

    Should you need further assistance about this order, please let us know.

    Thank you for using PodClerk service.

    Regards,

    Sherwin delos Santos

    Tx file received – converted:

    I think there are two things that make a document accessible. First of all, the information h as to be present. That seems kind of obvious, actually, but it really doesn't always happen. If, for example, you have a printer that's almost out of ink and you print something and the ink is almost legilbe, then that information isn't really there. If the color contrast between the paper and the ink is such that the document can't be read easily, then again, that information isn't really there. If you've created a document by making an image of a page and that image is not really clear, then the document can be very fuzzy, and some people won't be able to read it. And if you try to enlarge that image with magnification software, the text is gonna be so grainy that it's not gonna be able to be read, either. In addition, if you try to read that text with any kind of speech software which you might be using to supplement what you're seeing, the information won't be read because screen reading software only reads information that is text-oriented, not graphical. So there are any number of reasons why the information just may not be there in the first place. Secondly, the information that is there has to be able to be navigated in such a way that the user can understand the document based on how it's laid out. In the early days when people were using ASCII text files, you can cut a document with line after line after line of unbroken text. How was one supposed to know where the paragraph boundaries were? Where the headers were? Where the list items were, etc.? So, the information was there but you weren't able to navigate to the part of the document you needed. If I'm writing a document and I want certain points to be obvious, I'm gonna either leave white space around them so that they stand out, I'm gonna make them a different color, I'm gonna make them a different size, I'm gonna make them bold, print, or italic or whatever. I'm gonna do something to help people get to the point of the document where I think are relevant as quickly as they can. So, a document has to be navigable. People are likely gonna be reading your document using different forms of reading devices. Some people might look at it visually and that is enough for them. Some people might use voice or screen reading technology to listen to the document at the same time they're reading it in print. Some people may use it in a computer; some people may look at it on paper. In whatever the document is used, it has to be able to be navigated in a way that people can get to the point they wanna get to. That means, you have to give some thought to the layout of the document just as you do to the content. So, if the information is there and readable, and if it's able to be navigated, that goes a long way to making a document accessible.