英文翻譯畢業(yè)設(shè)計
【注意】一共包含5篇中英翻譯

第一篇（1－3頁）
簡易工具的介紹
Authorware6.5是由macromedia公司為了所有的課件開發(fā)者（包括殘疾人）更簡易的制作課件而發(fā)行的一款軟件。這個軟件現(xiàn)以升級至Authorware7.0
比如自我演示――Authorware的分布，這個教程采用了所功能的演示。它說明了Macromedia公司用簡化的術(shù)語設(shè)計的最優(yōu)化方法。
Macromedia公司推薦你可以使用這個自我演示做為一個原始模型來開發(fā)你自已的課件，來以使它滿足你的要求。例如：你可以設(shè)計你自已的用戶界面和圖表在保留這個自我演示所表達(dá)的邏輯和圖標(biāo)流程。
這個工具僅僅是為開發(fā)者提供設(shè)計流程和適當(dāng)?shù)能浖卣鞫O(shè)計的。它不能夠保證它本身和任何一個開發(fā)的產(chǎn)品都有相同的流程。例如，對第508段而言。確保你的產(chǎn)品被廣大人們所接受的唯一途徑是深思熟慮的開發(fā)、測試和評估。
Authorware7.0有哪些新的特性？
● 新的交互平臺“語音函數(shù)”
● 簡化的“字符→語音”邏輯轉(zhuǎn)化
● 語音選擇對話框
● 改良的“簡易窗口控制”模式
● 文本滾屏的替代技術(shù)
如果你的計算機(jī)上已經(jīng)安裝了“文本→語音”軟件，它包括像JAWS的屏幕閱讀器或窗口監(jiān)視器等，如果它已經(jīng)運行，那么人你現(xiàn)在可以聽到讀出屏幕上文本的聲音了。

如果你的機(jī)器上沒有安裝這個軟件，你可以在這個教程的下一章得到這個軟件。（如果你想立即使“文本→聲音”可以使用，那么你可以點擊“這里”或輸入“1”以直接跳轉(zhuǎn)到那兒。）

這個教程中的大多數(shù)屏幕使用了“文本→聲音”有一些沒有使用，留給大家做練習(xí)用。


下面幾個重要的鍵你要了解一下
●選擇下面的“pac-man”圖標(biāo)可以打開或關(guān)閉聲音
● 按“插入”鍵來中斷聲音（JAWS用戶可以用按按扭來實現(xiàn)）
● 想得到更多的關(guān)于語音鍵的幫助，你可以按”Shift+F1”
● 想得到更多的關(guān)于導(dǎo)航圖標(biāo)鍵的幫助，你可以按”Control+F1”

如果你的讀屏發(fā)出第幾幅圖的聲音，比如：“Graphic1234”，你應(yīng)該關(guān)閉這種錯誤并且無效的狀況。

使用這個教程的最好方法就是繼續(xù)接著往下讀，把它當(dāng)作未打包的Authorware部分來運行它。

它將指導(dǎo)你在不同的位置按“Control-B”把你帶回流程的當(dāng)前位置。注意：在暫停之后，要按“Ctrl-p”或控制面板來重新顯示。
為了記住你所想看的位置，利用上面“書簽”菜單的功能選擇。（前進(jìn)，立即使用）

為了使你的Authorware產(chǎn)品易于理解而不是難理解的、瑣碎的程序。我們希望你使用這個使程序得意并且更易于理解的工具包
然而，假設(shè)你已經(jīng)至少親自開發(fā)過一個較大的開發(fā)項目，你應(yīng)該熟悉了先進(jìn)的Authorware概念,尤其是腳本語言和工作表。如果你沒有這樣的經(jīng)歷，你可以考慮：
● 同其它人一起作為一個團(tuán)隊來攻克
● 訂閱簡單程序的資料并注意易理解的程序的發(fā)行
● 請一個顧問來完成產(chǎn)品的開發(fā)，這樣你可以集中在內(nèi)容方面
這個工具箱是為了使創(chuàng)作的內(nèi)容直接轉(zhuǎn)化成圖標(biāo)而設(shè)計的Authorware應(yīng)用程序。這個工具箱能夠找出在它的模框架上面的每一屏的頁碼并且能夠讀出上面的文字，例如的顯示圖標(biāo)的簡單制作

這個工具箱不是為下面幾項設(shè)計的：
● 被應(yīng)用程序所控制的內(nèi)容，測驗或評估問題知識對象。
● 被數(shù)據(jù)庫或別的外部文件所控制的內(nèi)容。
對于這些“黑箱”或模板近似，許多易于接近的特性將是常規(guī)程序。

你應(yīng)該做什么來適合殘疾人？總的來說，你應(yīng)該考慮他們的弱點：
● 視力
● 聽力
● 慣用右手的

到目前為止，視覺損害者在大多數(shù)的易接近特征已達(dá)到目標(biāo)
Authorware開始用于開發(fā)教學(xué)課件和介紹產(chǎn)品信息，如果完成一個課件是人們完成一個工作的唯一標(biāo)志，即使是殘疾人，那么使得課件易于理解是我們開發(fā)者所負(fù)有的責(zé)任。

僅僅有一小部分殘疾的觀眾是完全看不見或聽不見的，大多數(shù)可以借助輔助工具能夠聽或看到（在下一個話題來介紹）

使得你的課件易于理解也將幫助處在辦公室噪音干擾的環(huán)境的身體健全的使用者。

W3C 標(biāo)準(zhǔn)主體關(guān)于在線內(nèi)容的易接近建立指導(dǎo)方針 。很多企業(yè)政府機(jī)關(guān)在建立他們的在線易于理解的政策時主要引用這些方針。如果你的Authorware作品發(fā)布在網(wǎng)上，你需要特別請注意W3C。

不幸的是，在寫這個工具包的時候，沒有任何一個指導(dǎo)方針充分的向一個Authorware申請應(yīng)該如何做才能更接近演說。指導(dǎo)方針易于以技術(shù)規(guī)定解決以使用W3C標(biāo)準(zhǔn)而且解散商業(yè)的產(chǎn)品漲價語言，例如Authorware。

我們真心期待網(wǎng)絡(luò)內(nèi)容易接近指導(dǎo)方針的 2.0 版的批準(zhǔn) , 說明從實際的和有效的操作遠(yuǎn)景易接近應(yīng)該如何被實現(xiàn)。只有這個指導(dǎo)方針能直接應(yīng)用到Authorware應(yīng)用程序中。

在美國，復(fù)原行為的第 508 節(jié)在2001年六月內(nèi)被修正而且?guī)Я诵Ч?。

l它制定法律那個信息科技，而且它的易于接近的產(chǎn)品被聯(lián)邦代理提供給所有相對于常人無能力的人們。
不適當(dāng)?shù)呢?fù)擔(dān)被解除 哪里或產(chǎn)品的基本效力會被妥協(xié)處理

易于理解的要求通過董事會解決了（建筑和運輸障礙并且服從董事會，）。這些要求已列入聯(lián)邦政府購貨過程的故障分析報告中了。

這就意味著如果你要為聯(lián)邦代銷處開發(fā)一個Authorware應(yīng)用程序，或者作為政府或者承包者的一個雇員，那么你會遇到易理解性的要求。
.
藉由跟隨推薦而且實現(xiàn)在個別指導(dǎo)中被示范的技術(shù)，你將會是在一個位置中宣稱服從第 508 節(jié)

Authorware應(yīng)用程序只能在Windows下制作，但是也可以在蘋果機(jī)上發(fā)布。這個演示只能在編輯模式下運行，它需要在Windows下傳遞、編輯。

下面的這些特性不能在蘋果機(jī)上運行：
● 讀屏演示和其支持文件
● Authorware窗口控制按扭、菜單
● 由U32和動態(tài)鏈接衍生出的功能
● 微軟的快捷特性（如放大鏡）

屏幕和反饋學(xué)科對象的整個導(dǎo)航方案和運行目錄在蘋果機(jī)上經(jīng)過設(shè)計已經(jīng)能使用。適合蘋果機(jī)語音導(dǎo)入函數(shù)的版本已經(jīng)上設(shè)市并能運用到你的應(yīng)用程序中。

注意：
　　方便使用不是關(guān)于滿足政治方面的正確習(xí)慣。而是關(guān)使你的Authorware內(nèi)容在實際改造時可以被所有的人使用，包括殘疾人。

這是這個這個話題的最后一頁，選擇“向上的箭頭”來返回主菜單。
第一篇

Introduction to the Accessibility Kit
With Authorware 6.5, Macromedia released the Authorware Application Accessibility Kit to help developers make their products accessible to all users, including people with disabilities. This Kit has been updated and improved for Authorware 7.0.

Like the Show Me examples distributed with Authorware, this tutorial takes the form of a full working demonstration. It represents what Macromedia considers to be best practice in terms of authoring for accessibility.

Macromedia recommends that you use it as a template for your own work, then adapt it to suit your needs. For example, you should design your own user interface of buttons and graphics whilst retaining the logic and icon flow structures demonstrated with this tutorial


Disclaimer: This Kit is designed solely to assist developers by providing guidelines and appropriate software features. It can not in itself guarantee that a product created with it conforms, for example, to Section 508 requirements. The only way to ensure that your product is accessible is through deliberate development, testing and evaluation, informed by human judgment


What accessibility features are new for Authorware 7.0?

? new cross-platform Speech Xtra

? Simplified text-to-speech detection logic

? Speech options dialog

? Improved Accessible Windows Controls model

? Techniques to replace scrolling text



If you have text-to-speech software installed in your computer, including a screen reader like JAWS or Window-Eyes which must be running, you should now be hearing this text being spoken.

If not, you will learn in the next topic of this tutorial how to obtain this software. (If you are keen to get text-to-speech working immediately, then click here or press the 1 key to jump directly there now.)

Most screens in this tutorial have been prepared for speech. Some screens have not been prepared so you can practice on them.

Here are a few important keys you should know about:
? Select the "pac-man" icon below to turn speech on and off.
? Press the Insert key to interrupt audio (JAWS users should press the Control key).
? For further speech key help, press Shift-F1.
? For navigation key help, press Control-F1.

If your screen reader is announcing numbered graphic items, like "Graphic 1234", you should turn off this default and meaningless behavior.



The best way to start using this tutorial is to continue reading as you are now doing. You should be running this as an unpackaged Authorware piece.

At various points you will be instructed to press Control-B to take you to the current position in the Authorware flowline. NOTE: After pausing the piece, you need to press Control-P or use the Control Panel to resume this presentation.

So as not to lose your place, take advantage of the Bookmark menu options above. Go ahead, try it now.

Making your Authorware product accessible is not a trivial process. We hope that using this Kit will make the process easier and more comprehensive.

However, it is assumed that you have at least one major Authorware development project under your belt already. You should be familiar with advanced Authorware concepts, especially the scripting language and working with lists. If you don't have this experience, then consider:
? working in a team, working it out together
? subscribing to the AWARE list and monitor accessibility issues
? bringing in a consultant just to set up your product, leaving you to concentrate on the content.

This Kit is designed for Authorware applications that have the content authored directly into the icons. The Kit expects to find each screen on its own framework page and find text to be spoken, for example, simply authored in display icons.

The Kit is not designed for:

? Content that is controlled by the Application, Quiz or Assessment Question Knowledge Objects.

? Content that is controlled by a database or other external file.

For these "black box" or templated approaches, many accessibility features will have to be custom-programmed.


What disabilities should you be catering for? Generally speaking, you need to consider people who have impaired:
? Vision
? Hearing
? Dexterity

By far, it is the vision-impaired at whom most accessibility features are aimed.

Authorware is used primarily to create learning courses and information products. If completing a course is the only thing that

stands in the way of people undertaking a job, even if they are disabled, then it is incumbent upon us as developers to make the course accessible.

Only a small proportion of your disabled audience is totally blind or deaf. Most will have some capability which can be augmented by assistive technology (covered in the next topic).

Making your product accessible will also help able-bodied users who encounter environmental distractions such as office noise, mice that don't work or missing sound cards or speakers!


The W3C standards body establishes guidelines regarding accessibility of online content Many enterprises and government bodies reference these guidelines in establishing their online accessibility policy. If you publish your Authorware product for the web, then you need to pay attention to W3C.

Unfortunately, at the time of writing this Kit, none of the guidelines adequately addresses how an Authorware application should be made accessible. The guidelines tend to prescribe solutions in terms of technologies that use markup languages which conform to W3C standards and dismiss commercial products such as Authorware.

We eagerly await the ratification of Version 2.0 of the Web Content Accessibility Guidelines which states from a practical and effective operational perspective how accessibility should be implemented. Only this guideline can be applied directly to Authorware applications.


In the United States, Section 508 of the Rehabilitation Act was amended and took effect in June 2001
It legislates that information technology and its products provided for and by all federal agencies must be accessible to staff or public users with disabilities in a manner comparable to people without disability.

An exemption is given where an undue burden is incurred (well defined in disability law) or where the effectiveness of the product would be fundamentally compromised.

The requirements for accessibility are laid down by the Access Board (Architectural & Transportation Barriers and Compliance Board, These requirements have been rolled into the Federal Acquisition Regulations (FAR) which govern the federal purchasing procedures.

This means that if you want to build an Authorware application for a federal agency, either as an employee of the government or as a contractor, then you must meet the accessibility requirements.

By following the recommendations and implementing the techniques demonstrated in this tutorial, you will be in a position to claim Section 508 compliance._


Authorware applications can only be authored under Windows but may also be published for playback on a Macintosh. As this tutorial is meant to be run in authoring mode, it is necessarily tailored for Windows delivery.

The following features can not be ported to the Macintosh runtime:
? the demonstrated screen readers and their support files
? Authorware Windows Controls
? functions from U32s and DLLs
? Microsoft accessibility features (e.g. Magnifier)

The entire navigation scheme and the runtime contents of the Screen and Feedback Knowledge Objects have been designed to play back on Macintosh. A version of the Speech Xtra for Macintosh has been provided and must be distributed with your application.

Remember this:

Accessibility is not about satisfying the mores of political correctness.