CKEditor 3.x/Accessibility Compliance/Web Content Accessibility Guidelines - Revision history

Fredck: /* Priority 3 Checkpoints */

2009-09-29T19:36:37Z

‎Priority 3 Checkpoints

Fredck: /* Priority 2 Checkpoints */

2009-09-29T19:36:05Z

‎Priority 2 Checkpoints

Fredck: /* Priority 1 Checkpoints */

2009-09-29T19:35:33Z

‎Priority 1 Checkpoints

Martinkou: /* Priority 1 Checkpoints */

2009-05-22T03:45:10Z

‎Priority 1 Checkpoints

Martinkou: /* Priority 3 Checkpoints */

2009-05-20T07:33:43Z

‎Priority 3 Checkpoints

Martinkou: /* Priority 3 Checkpoints */

2009-05-20T07:18:54Z

‎Priority 3 Checkpoints

Martinkou: /* Priority 3 Checkpoints */

2009-05-20T07:16:33Z

‎Priority 3 Checkpoints

Martinkou at 07:08, 20 May 2009

2009-05-20T07:08:44Z

Martinkou at 07:05, 20 May 2009

2009-05-20T07:05:18Z

Martinkou at 06:05, 20 May 2009

2009-05-20T06:05:19Z

@@ Line 227: / Line 227: @@
 == Priority 3 Checkpoints  ==
-{| width="100%" cellspacing="1" cellpadding="1" border="1"
+{| width="100%" class="datatable"
 |-
 ! colspan="3" | In General (Priority 3)

@@ Line 89: / Line 89: @@
 == Priority 2 Checkpoints  ==
-{| width="100%" cellspacing="1" cellpadding="1" border="1"
+{| width="100%" class="datatable"
 |-
 ! colspan="3" | In General (Priority 2)
@@ Line 224: / Line 224: @@
 | <br>
 |}
 == Priority 3 Checkpoints  ==

@@ Line 3: / Line 3: @@
 == Priority 1 Checkpoints<br>  ==
-{| width="100%" cellspacing="1" cellpadding="1" border="1"
+{| width="100%" class="datatable"
 |-
 ! colspan="3" | In General (Priority 1)<br>
@@ Line 86: / Line 86: @@
 | An equivalent text-only page with a &lt;textarea&gt; element can be created by not activating CKEditor's replace API, if JavaScript is not an option.<br>
 |}
 == Priority 2 Checkpoints  ==

@@ Line 16: / Line 16: @@
 |-
 | [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-identify-changes 4.1] Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions). <br>
-| No<br>
+| Yes<br>
-| <br>
+| The lang attribute is present in the editor's HTML container, dialogs and popup menus.<br>
 |-
 | [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-order-style-sheets 6.1] Organize documents so they may be read without style sheets. For example, when an HTML document is rendered without associated style sheets, it must still be possible to read the document.<br>
@@ Line 87: / Line 87: @@
 |}
 <br>
 == Priority 2 Checkpoints  ==

@@ Line 234: / Line 234: @@
 ! colspan="3" | In General (Priority 3)
 |-
 | [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-expand-abbr 4.2] Specify the expansion of each abbreviation or acronym in a document where it first occurs. <br>
 | No<br>
 | <br>
 |-
 | [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-identify-lang 4.3] Identify the primary natural language of a document. <br>
 | No<br>
 | <br>
 |-
 | [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-tab-order 9.4] Create a logical tab order through links, form controls, and objects. <br>
 | Yes<br>
 | All user interactive controls in the editor UI have JavaScript-based tab order.<br>
 |-
 | [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-keyboard-shortcuts 9.5] Provide keyboard shortcuts to important links (including those in client-side image maps), form controls, and groups of form controls.<br>
 | Yes<br>
 | Frequently used toolbar buttons, such as Bold and Undo, have keyboard shortcuts.<br>
 |-
 | [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-divide-links 10.5] Until user agents (including assistive technologies) render adjacent links distinctly, include non-link, printable characters (surrounded by spaces) between adjacent links.<br>
-| <br>
+| No<br>
 | <br>
 |-
 | [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-content-preferences 11.3] Provide information so that users may receive documents according to their preferences (e.g., language, content type, etc.) <br>
-| <br>
+| Yes<br>
-| <br>
+| The editor is able to detect the preferred language settings in the browser and display with the appropriate translation.<br>
 |-
 | [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-nav-bar 13.5] Provide navigation bars to highlight and give access to the navigation mechanism. <br>
-| <br>
+| Yes<br>
 | <br>
 |-
 | [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-group-links 13.6] Group related links, identify the group (for user agents), and, until user agents do so, provide a way to bypass the group. <br>
-| <br>
+| No<br>
 | <br>
 |-
 | [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-searches 13.7] If search functions are provided, enable different types of searches for different skill levels and preferences. <br>
-| <br>
+| No<br>
 | <br>
 |-
 | [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-front-loading 13.8] Place distinguishing information at the beginning of headings, paragraphs, lists, etc. <br>
-| <br>
+| NA<br>
 | <br>
 |-
 | [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-bundled-version 13.9] Provide information about document collections (i.e., documents comprising multiple pages.). <br>
-| <br>
+| NA<br>
 | <br>
 |-
 | [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-skip-over-ascii 13.10] Provide a means to skip over multi-line ASCII art. <br>
 | NA<br>
 | There is no ASCII art in the editor UI.<br>
 |-
 | [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-icons 14.2] Supplement text with graphic or auditory presentations where they will facilitate comprehension of the page. <br>
-| <br>
+| No<br>
 | <br>
 |-
 | [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-consistent-style 14.3] Create a style of presentation that is consistent across pages. <br>
-| <br>
+| Yes<br>
-| <br>
+| The theme and skin systems in the editor ensures that different UI elements will have consistent styles.<br>
 |-
 ! colspan="3" | And if you use images and image maps (Priority 3)<br>
 |-
 | [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-redundant-client-links 1.5] Until user agents render text equivalents for client-side image map links, provide redundant text links for each active region of a client-side image map.<br>
-| <br>
+| NA<br>
-| <br>
+| There are no image maps in the editor.<br>
 |-
 ! colspan="3" | And if you use tables (Priority 3)
 |-
 | [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-table-summaries 5.5] Provide summaries for tables. <br>
-| <br>
+| NA<br>
-| <br>
+| Tables in the editor UI are only used for layout purposes.<br>
 |-
 | [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-abbreviate-labels 5.6] Provide abbreviations for header labels. <br>
-| <br>
+| NA<br>
-| <br>
+| Tables in the editor UI are only used for layout purposes.<br>
 |-
 | [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-linear-tables 10.3] Until user agents (including assistive technologies) render side-by-side text correctly, provide a linear text alternative (on the current page or some other) for all tables that lay out text in parallel, word-wrapped columns. <br>
-| <br>
+| No<br>
 | <br>
 |-
 ! colspan="3" | And if you use forms (Priority 3)
 |-
 | [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-place-holders 10.4] Until user agents handle empty controls correctly, include default, place-holding characters in edit boxes and text areas. <br>
-| <br>
+| No<br>
 | <br>
 |}

@@ Line 302: / Line 302: @@
 | <br>
 |-
-| 5.6 Provide abbreviations for header labels. <br>
+| [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-abbreviate-labels 5.6] Provide abbreviations for header labels. <br>
 | <br>
 | <br>
 |-
-| 10.3 Until user agents (including assistive technologies) render side-by-side text correctly, provide a linear text alternative (on the current page or some other) for all tables that lay out text in parallel, word-wrapped columns. <br>
+| [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-linear-tables 10.3] Until user agents (including assistive technologies) render side-by-side text correctly, provide a linear text alternative (on the current page or some other) for all tables that lay out text in parallel, word-wrapped columns. <br>
 | <br>
 | <br>
@@ Line 312: / Line 312: @@
 ! colspan="3" | And if you use forms (Priority 3)
 |-
-| 10.4 Until user agents handle empty controls correctly, include default, place-holding characters in edit boxes and text areas. <br>
+| [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-place-holders 10.4] Until user agents handle empty controls correctly, include default, place-holding characters in edit boxes and text areas. <br>
 | <br>
 | <br>
 |}

← Older revision		Revision as of 07:05, 20 May 2009
Line 228:		Line 228:


−	== Priority 3 Checkpoints ==	+	== Priority 3 Checkpoints ==
		+
		+	{\| width="100%" cellspacing="1" cellpadding="1" border="1"
		+	\|-
		+	! colspan="3" \| In General (Priority 3)
		+	\|-
		+	\|
		+	\|
		+	\|
		+	\|-
		+	\|
		+	\|
		+	\|
		+	\|-
		+	\|
		+	\|
		+	\|
		+	\|-
		+	\|
		+	\|
		+	\|
		+	\|-
		+	\|
		+	\|
		+	\|
		+	\|-
		+	\|
		+	\|
		+	\|
		+	\|-
		+	\|
		+	\|
		+	\|
		+	\|-
		+	\|
		+	\|
		+	\|
		+	\|-
		+	\|
		+	\|
		+	\|
		+	\|-
		+	\|
		+	\|
		+	\|
		+	\|-
		+	\|
		+	\|
		+	\|
		+	\|-
		+	\|
		+	\|
		+	\|
		+	\|-
		+	\|
		+	\|
		+	\|
		+	\|-
		+	\|
		+	\|
		+	\|
		+	\|-
		+	! colspan="3" \| And if you use images and image maps (Priority 3)<br>
		+	\|-
		+	\|
		+	\|
		+	\|
		+	\|-
		+	! colspan="3" \| And if you use tables (Priority 3)
		+	\|-
		+	\|
		+	\|
		+	\|
		+	\|-
		+	\|
		+	\|
		+	\|
		+	\|-
		+	\|
		+	\|
		+	\|
		+	\|-
		+	! colspan="3" \| And if you use forms (Priority 3)
		+	\|-
		+	\|
		+	\|
		+	\|
		+	\|}