英文翻译毕业设计.rar
英文翻译毕业设计,【注意】一共包含5篇中英翻译第一篇（1－3页）简易工具的介绍authorware6.5是由macromedia公司为了所有的课件开发者（包括残疾人）更简易的制作课件而发行的一款软件。这个软件现以升级至authorware7.0比如自我演示╠╠authorware的分布，这个教程采用了所功能的演示。它说明...
该文档为压缩文件,包含的文件列表如下:
内容介绍
原文档由会员 云贝贝 发布
英文翻译毕业设计
【注意】一共包含5篇中英翻译
第一篇（1－3页）
简易工具的介绍
Authorware6.5是由macromedia公司为了所有的课件开发者（包括残疾人）更简易的制作课件而发行的一款软件。这个软件现以升级至Authorware7.0
比如自我演示――Authorware的分布，这个教程采用了所功能的演示。它说明了Macromedia公司用简化的术语设计的最优化方法。
Macromedia公司推荐你可以使用这个自我演示做为一个原始模型来开发你自已的课件，来以使它满足你的要求。例如：你可以设计你自已的用户界面和图表在保留这个自我演示所表达的逻辑和图标流程。
这个工具仅仅是为开发者提供设计流程和适当的软件特征而设计的。它不能够保证它本身和任何一个开发的产品都有相同的流程。例如，对第508段而言。确保你的产品被广大人们所接受的唯一途径是深思熟虑的开发、测试和评估。
Authorware7.0有哪些新的特性？
● 新的交互平台“语音函数”
● 简化的“字符→语音”逻辑转化
● 语音选择对话框
● 改良的“简易窗口控制”模式
● 文本滚屏的替代技术
如果你的计算机上已经安装了“文本→语音”软件，它包括像JAWS的屏幕阅读器或窗口监视器等，如果它已经运行，那么人你现在可以听到读出屏幕上文本的声音了。
如果你的机器上没有安装这个软件，你可以在这个教程的下一章得到这个软件。（如果你想立即使“文本→声音”可以使用，那么你可以点击“这里”或输入“1”以直接跳转到那儿。）
这个教程中的大多数屏幕使用了“文本→声音”有一些没有使用，留给大家做练习用。
下面几个重要的键你要了解一下
●选择下面的“pac-man”图标可以打开或关闭声音
● 按“插入”键来中断声音（JAWS用户可以用按按扭来实现）
● 想得到更多的关于语音键的帮助，你可以按”Shift+F1”
● 想得到更多的关于导航图标键的帮助，你可以按”Control+F1”
如果你的读屏发出第几幅图的声音，比如：“Graphic1234”，你应该关闭这种错误并且无效的状况。
使用这个教程的最好方法就是继续接着往下读，把它当作未打包的Authorware部分来运行它。
它将指导你在不同的位置按“Control-B”把你带回流程的当前位置。注意：在暂停之后，要按“Ctrl-p”或控制面板来重新显示。
为了记住你所想看的位置，利用上面“书签”菜单的功能选择。（前进，立即使用）
为了使你的Authorware产品易于理解而不是难理解的、琐碎的程序。我们希望你使用这个使程序得意并且更易于理解的工具包
然而，假设你已经至少亲自开发过一个较大的开发项目，你应该熟悉了先进的Authorware概念,尤其是脚本语言和工作表。如果你没有这样的经历，你可以考虑：
● 同其它人一起作为一个团队来攻克
● 订阅简单程序的资料并注意易理解的程序的发行
● 请一个顾问来完成产品的开发，这样你可以集中在内容方面
这个工具箱是为了使创作的内容直接转化成图标而设计的Authorware应用程序。这个工具箱能够找出在它的模框架上面的每一屏的页码并且能够读出上面的文字，例如的显示图标的简单制作
这个工具箱不是为下面几项设计的：
● 被应用程序所控制的内容，测验或评估问题知识对象。
● 被数据库或别的外部文件所控制的内容。
对于这些“黑箱”或模板近似，许多易于接近的特性将是常规程序。
你应该做什么来适合残疾人？总的来说，你应该考虑他们的弱点：
● 视力
● 听力
● 惯用右手的
到目前为止，视觉损害者在大多数的易接近特征已达到目标
Authorware开始用于开发教学课件和介绍产品信息，如果完成一个课件是人们完成一个工作的唯一标志，即使是残疾人，那么使得课件易于理解是我们开发者所负有的责任。
仅仅有一小部分残疾的观众是完全看不见或听不见的，大多数可以借助辅助工具能够听或看到（在下一个话题来介绍）
使得你的课件易于理解也将帮助处在办公室噪音干扰的环境的身体健全的使用者。
W3C 标准主体关于在线内容的易接近建立指导方针 。很多企业政府机关在建立他们的在线易于理解的政策时主要引用这些方针。如果你的Authorware作品发布在网上，你需要特别请注意W3C。
不幸的是，在写这个工具包的时候，没有任何一个指导方针充分的向一个Authorware申请应该如何做才能更接近演说。指导方针易于以技术规定解决以使用W3C标准而且解散商业的产品涨价语言，例如Authorware。
我们真心期待网络内容易接近指导方针的 2.0 版的批准 , 说明从实际的和有效的操作远景易接近应该如何被实现。只有这个指导方针能直接应用到Authorware应用程序中。
在美国，复原行为的第 508 节在2001年六月内被修正而且带了效果 。
l它制定法律那个信息科技，而且它的易于接近的产品被联邦代理提供给所有相对于常人无能力的人们。
不适当的负担被解除 哪里或产品的基本效力会被妥协处理
易于理解的要求通过董事会解决了（建筑和运输障碍并且服从董事会，）。这些要求已列入联邦政府购货过程的故障分析报告中了。
这就意味着如果你要为联邦代销处开发一个Authorware应用程序，或者作为政府或者承包者的一个雇员，那么你会遇到易理解性的要求。
.
藉由跟随推荐而且实现在个别指导中被示范的技术，你将会是在一个位置中宣称服从第 508 节
Authorware应用程序只能在Windows下制作，但是也可以在苹果机上发布。这个演示只能在编辑模式下运行，它需要在Windows下传递、编辑。
下面的这些特性不能在苹果机上运行：
● 读屏演示和其支持文件
● Authorware窗口控制按扭、菜单
● 由U32和动态链接衍生出的功能
● 微软的快捷特性（如放大镜）
屏幕和反馈学科对象的整个导航方案和运行目录在苹果机上经过设计已经能使用。适合苹果机语音导入函数的版本已经上设市并能运用到你的应用程序中。
注意：
方便使用不是关于满足政治方面的正确习惯。而是关使你的Authorware内容在实际改造时可以被所有的人使用，包括残疾人。
这是这个这个话题的最后一页，选择“向上的箭头”来返回主菜单。
第一篇
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.
【注意】一共包含5篇中英翻译
第一篇（1－3页）
简易工具的介绍
Authorware6.5是由macromedia公司为了所有的课件开发者（包括残疾人）更简易的制作课件而发行的一款软件。这个软件现以升级至Authorware7.0
比如自我演示――Authorware的分布，这个教程采用了所功能的演示。它说明了Macromedia公司用简化的术语设计的最优化方法。
Macromedia公司推荐你可以使用这个自我演示做为一个原始模型来开发你自已的课件，来以使它满足你的要求。例如：你可以设计你自已的用户界面和图表在保留这个自我演示所表达的逻辑和图标流程。
这个工具仅仅是为开发者提供设计流程和适当的软件特征而设计的。它不能够保证它本身和任何一个开发的产品都有相同的流程。例如，对第508段而言。确保你的产品被广大人们所接受的唯一途径是深思熟虑的开发、测试和评估。
Authorware7.0有哪些新的特性？
● 新的交互平台“语音函数”
● 简化的“字符→语音”逻辑转化
● 语音选择对话框
● 改良的“简易窗口控制”模式
● 文本滚屏的替代技术
如果你的计算机上已经安装了“文本→语音”软件，它包括像JAWS的屏幕阅读器或窗口监视器等，如果它已经运行，那么人你现在可以听到读出屏幕上文本的声音了。
如果你的机器上没有安装这个软件，你可以在这个教程的下一章得到这个软件。（如果你想立即使“文本→声音”可以使用，那么你可以点击“这里”或输入“1”以直接跳转到那儿。）
这个教程中的大多数屏幕使用了“文本→声音”有一些没有使用，留给大家做练习用。
下面几个重要的键你要了解一下
●选择下面的“pac-man”图标可以打开或关闭声音
● 按“插入”键来中断声音（JAWS用户可以用按按扭来实现）
● 想得到更多的关于语音键的帮助，你可以按”Shift+F1”
● 想得到更多的关于导航图标键的帮助，你可以按”Control+F1”
如果你的读屏发出第几幅图的声音，比如：“Graphic1234”，你应该关闭这种错误并且无效的状况。
使用这个教程的最好方法就是继续接着往下读，把它当作未打包的Authorware部分来运行它。
它将指导你在不同的位置按“Control-B”把你带回流程的当前位置。注意：在暂停之后，要按“Ctrl-p”或控制面板来重新显示。
为了记住你所想看的位置，利用上面“书签”菜单的功能选择。（前进，立即使用）
为了使你的Authorware产品易于理解而不是难理解的、琐碎的程序。我们希望你使用这个使程序得意并且更易于理解的工具包
然而，假设你已经至少亲自开发过一个较大的开发项目，你应该熟悉了先进的Authorware概念,尤其是脚本语言和工作表。如果你没有这样的经历，你可以考虑：
● 同其它人一起作为一个团队来攻克
● 订阅简单程序的资料并注意易理解的程序的发行
● 请一个顾问来完成产品的开发，这样你可以集中在内容方面
这个工具箱是为了使创作的内容直接转化成图标而设计的Authorware应用程序。这个工具箱能够找出在它的模框架上面的每一屏的页码并且能够读出上面的文字，例如的显示图标的简单制作
这个工具箱不是为下面几项设计的：
● 被应用程序所控制的内容，测验或评估问题知识对象。
● 被数据库或别的外部文件所控制的内容。
对于这些“黑箱”或模板近似，许多易于接近的特性将是常规程序。
你应该做什么来适合残疾人？总的来说，你应该考虑他们的弱点：
● 视力
● 听力
● 惯用右手的
到目前为止，视觉损害者在大多数的易接近特征已达到目标
Authorware开始用于开发教学课件和介绍产品信息，如果完成一个课件是人们完成一个工作的唯一标志，即使是残疾人，那么使得课件易于理解是我们开发者所负有的责任。
仅仅有一小部分残疾的观众是完全看不见或听不见的，大多数可以借助辅助工具能够听或看到（在下一个话题来介绍）
使得你的课件易于理解也将帮助处在办公室噪音干扰的环境的身体健全的使用者。
W3C 标准主体关于在线内容的易接近建立指导方针 。很多企业政府机关在建立他们的在线易于理解的政策时主要引用这些方针。如果你的Authorware作品发布在网上，你需要特别请注意W3C。
不幸的是，在写这个工具包的时候，没有任何一个指导方针充分的向一个Authorware申请应该如何做才能更接近演说。指导方针易于以技术规定解决以使用W3C标准而且解散商业的产品涨价语言，例如Authorware。
我们真心期待网络内容易接近指导方针的 2.0 版的批准 , 说明从实际的和有效的操作远景易接近应该如何被实现。只有这个指导方针能直接应用到Authorware应用程序中。
在美国，复原行为的第 508 节在2001年六月内被修正而且带了效果 。
l它制定法律那个信息科技，而且它的易于接近的产品被联邦代理提供给所有相对于常人无能力的人们。
不适当的负担被解除 哪里或产品的基本效力会被妥协处理
易于理解的要求通过董事会解决了（建筑和运输障碍并且服从董事会，）。这些要求已列入联邦政府购货过程的故障分析报告中了。
这就意味着如果你要为联邦代销处开发一个Authorware应用程序，或者作为政府或者承包者的一个雇员，那么你会遇到易理解性的要求。
.
藉由跟随推荐而且实现在个别指导中被示范的技术，你将会是在一个位置中宣称服从第 508 节
Authorware应用程序只能在Windows下制作，但是也可以在苹果机上发布。这个演示只能在编辑模式下运行，它需要在Windows下传递、编辑。
下面的这些特性不能在苹果机上运行：
● 读屏演示和其支持文件
● Authorware窗口控制按扭、菜单
● 由U32和动态链接衍生出的功能
● 微软的快捷特性（如放大镜）
屏幕和反馈学科对象的整个导航方案和运行目录在苹果机上经过设计已经能使用。适合苹果机语音导入函数的版本已经上设市并能运用到你的应用程序中。
注意：
方便使用不是关于满足政治方面的正确习惯。而是关使你的Authorware内容在实际改造时可以被所有的人使用，包括残疾人。
这是这个这个话题的最后一页，选择“向上的箭头”来返回主菜单。
第一篇
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.
