舊文件

此處文件僅供參考,請自行考量時效性與適用程度,其他庫藏文件請參考文件頁面
我們亟需您的協助,進行共筆系統搬移、及文件整理工作,詳情請查閱參與我們

「資訊網內容親和力準則 2.0」修訂間的差異

出自 MozTW Wiki

(草草了事...)
行 1: 行 1:
 
__NOTOC__
 
__NOTOC__
<h1>Web Content Accessibility Guidelines 2.0</h1>
 
<h1>資訊網內容親合力準則 2.0</h1>
 
  
 
<h2>W3C 2004 年十一月 19 號工作草稿</h2>
 
<h2>W3C 2004 年十一月 19 號工作草稿</h2>
行 45: 行 43:
 
=== 目地 ===
 
=== 目地 ===
  
This document outlines design principles for creating cessible 資訊網內容 (Web content). When these principles are ignored, individuals with disabilities may not be able to access the content at all, or they may be able to do so only with great difficulty. When these principles are employed, they also make 資訊網內容 (Web content) accessible to a variety of Web-enabled devices, such as phones, handheld devices, kiosks, network appliances. By making content accessible to a variety of devices, that content will also be accessible to people in a variety of situations.
+
This document outlines 設計原則 for creating cessible 資訊網內容 (Web content). When these 原則 are ignored, individuals with disabilities may not be able to access the content at all, or they may be able to do so only with great difficulty. When these 原則 are employed, they also make 資訊網內容 (Web content) accessible to a variety of Web-enabled devices, such as phones, handheld devices, kiosks, network appliances. By making content accessible to a variety of devices, that content will also be accessible to people in a variety of situations.
  
 
本文件概述製作有親和力資訊網內容 (Web content) 的設計原則。若是這些原則被忽略,有障礙人士可能會完全無法使用這些內容,或者在使用上有很大的困難。這些原則被應用時,資訊網內容可以被用在各類的資訊網設備,如電話、掌上裝置、kiosk、網路 appliance 等。另外,讓內容可在不同裝置上用可以允許人們在不同情況下取得這些內容。
 
本文件概述製作有親和力資訊網內容 (Web content) 的設計原則。若是這些原則被忽略,有障礙人士可能會完全無法使用這些內容,或者在使用上有很大的困難。這些原則被應用時,資訊網內容可以被用在各類的資訊網設備,如電話、掌上裝置、kiosk、網路 appliance 等。另外,讓內容可在不同裝置上用可以允許人們在不同情況下取得這些內容。
  
The design principles in this document represent broad concepts that apply to all Web-based content. They are not specific to HTML, XML, or any other technology. This approach was taken so that the design principles could be applied to a variety of situations and technologies, including those that do not yet exist.
+
The 設計原則 in this document represent broad concepts that apply to all Web-based content. They are not specific to HTML, XML, or any other technology. This approach was taken so that the 設計原則 could be applied to a variety of situations and technologies, including those that do not yet exist.
  
 
本文件的設計原則代表了可用在所有基於資訊網內容的廣泛概念。它們並不特定針對 HTML、XML、或任何其它科技。採取這樣的方針是為了讓這些設計原則能應用在各種,包括目前不存在的情況與科技。
 
本文件的設計原則代表了可用在所有基於資訊網內容的廣泛概念。它們並不特定針對 HTML、XML、或任何其它科技。採取這樣的方針是為了讓這些設計原則能應用在各種,包括目前不存在的情況與科技。
行 55: 行 53:
 
=== 如何閱讀本文件 ===
 
=== 如何閱讀本文件 ===
  
In order to facilitate understanding of the guidelines and to help people focus in on just the parts they need, the guidelines are presented as a set of interrelated documents. There are 3 layers to the guidelines information.
+
為了要讓準則更容易懂,還有協助讀者集中在他們所需要的地方上,這些準則以一組相關文件方式呈現。準則資訊分三個層次。
  
 
==== 1 - Top layer - Overview of Design Principles, Guidelines, Success Criteria ====
 
==== 1 - Top layer - Overview of Design Principles, Guidelines, Success Criteria ====
 
==== 1 - 頂層 - 設計原則、準則、成功要件的概略====
 
==== 1 - 頂層 - 設計原則、準則、成功要件的概略====
  
The top layer is titled "Web Content Accessibility Guidelines 2.0". It is the document you are currently reading. This document provides:
+
頂層名為「資訊網內容親和力準則 2.0」(你現在在讀的文件)。這文件提供了:
  
 
# An introduction
 
# An introduction
# The 4 major principles for accessibility (Perceivable, Operable, Understandable and Robust).
+
# 四個主要的親和力原則(可察覺(perceivable)、可操作(operable)、可理解(understandable)與耐用(robust))
 
# The (non-technology-specific) guidelines (13 in total).
 
# The (non-technology-specific) guidelines (13 in total).
 
# Success criteria (normative), and definitions, benefits and examples (all non-normative) for each guideline
 
# Success criteria (normative), and definitions, benefits and examples (all non-normative) for each guideline
行 69: 行 67:
  
 
==== 2 - Technology-specific Checklists ====
 
==== 2 - Technology-specific Checklists ====
 +
==== 2 - 特定技術檢核表 ====
  
 
In addition to the general guidelines, there will be a series of technology-specific checklist documents. These documents will provide information on what is required when using different technologies in order to meet the WCAG 2.0 Working Draft.
 
In addition to the general guidelines, there will be a series of technology-specific checklist documents. These documents will provide information on what is required when using different technologies in order to meet the WCAG 2.0 Working Draft.
行 75: 行 74:
  
 
==== 3 - Bottom layer - Technology-specific application information ====
 
==== 3 - Bottom layer - Technology-specific application information ====
 +
==== 3 - 頂層 - 特定技術的應用資訊 ====
  
 
The Techniques Documents (技巧文件) will include code examples, screen shots, and other information specific to a technology. These documents will be non-normative. They will contain different strategies for meeting the requirements as well as the current preferred approaches, where they exist. Examples include:
 
The Techniques Documents (技巧文件) will include code examples, screen shots, and other information specific to a technology. These documents will be non-normative. They will contain different strategies for meeting the requirements as well as the current preferred approaches, where they exist. Examples include:
  
 
* 一般技巧
 
* 一般技巧
* Hypertext Markup Language (HTML) and Extensible Hypertext Markup Language (XHTML) 技巧
+
* 超文字標示語言(HTML)與可延伸超文字標示語言(XHTML)技巧
 
* Cascading Style Sheets (CSS) 技巧
 
* Cascading Style Sheets (CSS) 技巧
* Server-side 腳本(撰寫)技巧
+
* 伺服機端(Server-side)腳本(撰寫)技巧
 
* 客戶端腳本(撰寫)技巧
 
* 客戶端腳本(撰寫)技巧
 
* Scalable Vector Graphics (SVG) 技巧
 
* Scalable Vector Graphics (SVG) 技巧
行 89: 行 89:
 
<em>(Items above will become active links as the corresponding Working Drafts are published)</em>
 
<em>(Items above will become active links as the corresponding Working Drafts are published)</em>
  
=== Audience ===
+
=== 文章對象 ===
  
 
These guidelines have been written to meet the needs of many different audiences, from policy makers, to managers, to those who create 資訊網內容 (Web content), to those who write the code. Every attempt has been made to make the document as readable and usable as possible while still retaining the accuracy and clarity needed in a technical specification. For first time users, the work of the Education and Outreach Working Group of the Web Accessibility Initiative is highly recommended. In particular, Getting Started: Making a Web Site Accessible.
 
These guidelines have been written to meet the needs of many different audiences, from policy makers, to managers, to those who create 資訊網內容 (Web content), to those who write the code. Every attempt has been made to make the document as readable and usable as possible while still retaining the accuracy and clarity needed in a technical specification. For first time users, the work of the Education and Outreach Working Group of the Web Accessibility Initiative is highly recommended. In particular, Getting Started: Making a Web Site Accessible.
行 95: 行 95:
 
=== 編製 (Authoring) 工具 ===
 
=== 編製 (Authoring) 工具 ===
  
A large part of 資訊網內容 (Web content) is created using 編製 (authoring) tools. These tools often determine how 資訊網內容 (Web content) is implemented, either by making 編製 (authoring) decisions directly or by limiting the choices available to the author. As a result, 編製 (authoring) tools will play an important role in creating 資訊網內容 (Web content) that conforms to the Web Content Accessibility Guidelines. At the same time, we recommend that all authors become familiar with the Guidelines because this will help in creating accessible content and coverage of the Guidelines may vary between tools.
+
有很多的資訊網內容(Web content)是由編製(authoring)工具所創造。不論是藉由直接做編製決定或是限制作者(author)的選擇,這些工具常常決定了資訊網內容(Web content)是如何地實做。因此,在創造符合本「資訊網內容親和力準則」的資訊網內容(Web content)上編製工具扮演著很大的角色。同時,我們建議所有的作者熟悉本「準則」,因為這可協助有親和力的內容的創造,也因為各工具對本「準則」的支援範圍可能有所不同。
  
Developers of 編製 (Authoring)  tools can help to make their tools more aware of the Web Content Accessibility Guidelines by following the 編製工具 (Authoring Tool) Accessibility Guidelines.
+
編製工具的開發者可遵守[http://www.w3.org/TR/ATAG10/ 編製工具親和力準則],讓他們的工具更有本「資訊網內容親和力準則」的意識。
  
 
We encourage users and purchasers of 編製 (authoring) tools to consider conformance to the Authoring Tool Accessibility Guidelines as a criterion when selecting tools.
 
We encourage users and purchasers of 編製 (authoring) tools to consider conformance to the Authoring Tool Accessibility Guidelines as a criterion when selecting tools.
  
 
<div style="background-color:#99ff66;">編按:The Authoring Tool Accessibility Guidelines Working Group has published Working Drafts of ATAG 2.0. The above references will need to be updated as ATAG 2.0 moves through recommendation track.</div>
 
<div style="background-color:#99ff66;">編按:The Authoring Tool Accessibility Guidelines Working Group has published Working Drafts of ATAG 2.0. The above references will need to be updated as ATAG 2.0 moves through recommendation track.</div>
 +
 +
 +
 +
 +
 +
<h2 style="border:1px solid;">原則一: 內容必須是可察覺(perceivable)</h2>
 +
<h2 style="border:1px solid;">原則二: 介面元素必須是可操作(operable)</h2>
 +
<h2 style="border:1px solid;">原則三: 內容與控制件必須是可理解(understandable)</h2>
 +
<h2 style="border:1px solid;">原則四: 對目前與未來技術,內容必須足夠耐用(robust)</h2>
 +
 
{{link|技術傳教專案|技術傳教專案主頁}}
 
{{link|技術傳教專案|技術傳教專案主頁}}

於 2005年5月20日 (五) 15:12 的修訂


W3C 2004 年十一月 19 號工作草稿

這版本: 
http://www.w3.org/TR/2004/WD-WCAG20-20041119/
最新版: 
http://www.w3.org/TR/WCAG20/
前一版: 
http://www.w3.org/TR/2004/WD-WCAG20-20040730/
編輯: 
Ben Caldwell, Trace R&D Center
Wendy Chisholm, W3C
Gregg Vanderheiden, Trace R&D Center
Jason White, University of Melbourne

Copyright © 2004 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark, document use rules apply.

版權所有。受 W3C 責任商標文件使用規則規範。

摘要

The World Wide Web Consortium (W3C) published the 資訊網內容 Accessibility Guidelines 1.0 (WCAG 1.0) as a Recommendation in May 1999. This Working Draft for version 2.0 builds on WCAG 1.0. It has the same aim: to explain how to make 資訊網內容 (Web content) accessible to people with disabilities and to define target levels of accessibility. Incorporating feedback on WCAG 1.0, this Working Draft of version 2.0 focuses on guidelines. It attempts to apply guidelines to a wider range of technologies and to use wording that may be understood by a more varied audience.

本文件的制定始末與狀態

This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.

This document is prepared by the Web Content Accessibility Guidelines Working Group (WCAG WG) to show how more generalized (less HTML-specific) WCAG guidelines might read. This draft is not yet based on consensus of the WCAG Working Group nor has it gone through W3C process. This Working Draft in no way supersedes WCAG 1.0.

Please refer to "Issue Tracking for WCAG 2.0 Working Draft" for a list of open issues related to this Working Draft. The "History of Changes to WCAG 2.0 Working Drafts" is also available.

Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress. A list of current W3C Recommendations and other technical documents is available.

The Working Group welcomes comments on this document at public-comments-wcag20@w3.org. The archives for this list are publicly available. Archives of the WCAG WG mailing list discussions are also publicly available.

This document was produced under the 24 January 2002 CPP as amended by the W3C Patent Policy Transition Procedure. The Working Group maintains a public list of patent disclosures relevant to this document; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) with respect to this specification should disclose the information in accordance with section 6 of the W3C Patent Policy.

This document has been produced as part of the W3C Web Accessibility Initiative (WAI). The goals of the WCAG WG are discussed in the Working Group charter. The WCAG WG is part of the WAI Technical Activity.

Introduction

目地

This document outlines 設計原則 for creating cessible 資訊網內容 (Web content). When these 原則 are ignored, individuals with disabilities may not be able to access the content at all, or they may be able to do so only with great difficulty. When these 原則 are employed, they also make 資訊網內容 (Web content) accessible to a variety of Web-enabled devices, such as phones, handheld devices, kiosks, network appliances. By making content accessible to a variety of devices, that content will also be accessible to people in a variety of situations.

本文件概述製作有親和力資訊網內容 (Web content) 的設計原則。若是這些原則被忽略,有障礙人士可能會完全無法使用這些內容,或者在使用上有很大的困難。這些原則被應用時,資訊網內容可以被用在各類的資訊網設備,如電話、掌上裝置、kiosk、網路 appliance 等。另外,讓內容可在不同裝置上用可以允許人們在不同情況下取得這些內容。

The 設計原則 in this document represent broad concepts that apply to all Web-based content. They are not specific to HTML, XML, or any other technology. This approach was taken so that the 設計原則 could be applied to a variety of situations and technologies, including those that do not yet exist.

本文件的設計原則代表了可用在所有基於資訊網內容的廣泛概念。它們並不特定針對 HTML、XML、或任何其它科技。採取這樣的方針是為了讓這些設計原則能應用在各種,包括目前不存在的情況與科技。

如何閱讀本文件

為了要讓準則更容易懂,還有協助讀者集中在他們所需要的地方上,這些準則以一組相關文件方式呈現。準則資訊分三個層次。

1 - Top layer - Overview of Design Principles, Guidelines, Success Criteria

1 - 頂層 - 設計原則、準則、成功要件的概略

頂層名為「資訊網內容親和力準則 2.0」(你現在在讀的文件)。這文件提供了:

  1. An introduction
  2. 四個主要的親和力原則(可察覺(perceivable)、可操作(operable)、可理解(understandable)與耐用(robust))
  3. The (non-technology-specific) guidelines (13 in total).
  4. Success criteria (normative), and definitions, benefits and examples (all non-normative) for each guideline
  5. An appendix containing definitions, references and other support information.

2 - Technology-specific Checklists

2 - 特定技術檢核表

In addition to the general guidelines, there will be a series of technology-specific checklist documents. These documents will provide information on what is required when using different technologies in order to meet the WCAG 2.0 Working Draft.

編按:These checklists do not yet exist. At the present time, it is not clear if the checklists will be normative or non-normative. If checklists are non-normative, it is easier to update them. If checklists are normative, changes made to them alter the definition of conformance. However, it may be necessary to make checklists normative in order for the guidelines to be testable

3 - Bottom layer - Technology-specific application information

3 - 頂層 - 特定技術的應用資訊

The Techniques Documents (技巧文件) will include code examples, screen shots, and other information specific to a technology. These documents will be non-normative. They will contain different strategies for meeting the requirements as well as the current preferred approaches, where they exist. Examples include:

  • 一般技巧
  • 超文字標示語言(HTML)與可延伸超文字標示語言(XHTML)技巧
  • Cascading Style Sheets (CSS) 技巧
  • 伺服機端(Server-side)腳本(撰寫)技巧
  • 客戶端腳本(撰寫)技巧
  • Scalable Vector Graphics (SVG) 技巧
  • Synchronized Multimedia Integration Language (SMIL) 技巧
  • Extensible Markup Language (XML) 技巧

(Items above will become active links as the corresponding Working Drafts are published)

文章對象

These guidelines have been written to meet the needs of many different audiences, from policy makers, to managers, to those who create 資訊網內容 (Web content), to those who write the code. Every attempt has been made to make the document as readable and usable as possible while still retaining the accuracy and clarity needed in a technical specification. For first time users, the work of the Education and Outreach Working Group of the Web Accessibility Initiative is highly recommended. In particular, Getting Started: Making a Web Site Accessible.

編製 (Authoring) 工具

有很多的資訊網內容(Web content)是由編製(authoring)工具所創造。不論是藉由直接做編製決定或是限制作者(author)的選擇,這些工具常常決定了資訊網內容(Web content)是如何地實做。因此,在創造符合本「資訊網內容親和力準則」的資訊網內容(Web content)上編製工具扮演著很大的角色。同時,我們建議所有的作者熟悉本「準則」,因為這可協助有親和力的內容的創造,也因為各工具對本「準則」的支援範圍可能有所不同。

編製工具的開發者可遵守編製工具親和力準則,讓他們的工具更有本「資訊網內容親和力準則」的意識。

We encourage users and purchasers of 編製 (authoring) tools to consider conformance to the Authoring Tool Accessibility Guidelines as a criterion when selecting tools.

編按:The Authoring Tool Accessibility Guidelines Working Group has published Working Drafts of ATAG 2.0. The above references will need to be updated as ATAG 2.0 moves through recommendation track.

原則一: 內容必須是可察覺(perceivable)

原則二: 介面元素必須是可操作(operable)

原則三: 內容與控制件必須是可理解(understandable)

原則四: 對目前與未來技術,內容必須足夠耐用(robust)

個人工具