FCKeditor 3.x/Design and Architecture/Accessibility - Revision history

Martinkou: Updated the VPAT link.

2009-05-20T07:46:17Z

Updated the VPAT link.

Fredck at 09:24, 6 February 2008

2008-02-06T09:24:03Z

Fredck at 23:04, 4 February 2008

2008-02-04T23:04:34Z

Fredck: New page: NOTOCThere are two levels of accessibility features we aim to provide with V3: * Making the editor usable by people with disabilities. * Ensuring that accessibility features can be i...

2008-02-02T00:26:15Z

New page: __NOTOC__There are two levels of accessibility features we aim to provide with V3: * Making the editor usable by people with disabilities. * Ensuring that accessibility features can be i...

New page

__NOTOC__There are two levels of accessibility features we aim to provide with V3:

* Making the editor usable by people with disabilities.

* Ensuring that accessibility features can be introduced in the contents produced with the editor, guaranteeing and enforcing the minimum accessibility level in the contents.

== Standards ==

The first and most practical way to ensure accessibility in both the above aspects is by following the rules and requirements defined by the common standard available for web applications.

We have chosen two of the most notable standards as those we'll be working to be compliant to:

* The [http://www.w3.org/WAI/ WAI], published by the W3C, which actually comprehends a number of standards and guidelines that interest our project: [http://www.w3.org/WAI/intro/wcag.php Web Content Accessibility Guidelines (WCAG)], [http://www.w3.org/WAI/intro/atag.php Authoring Tool Accessibility Guidelines (ATAG)] and [http://www.w3.org/WAI/intro/aria.php Accessible Rich Internet Applications (WAI-ARIA)];

* The US [http://www.section508.gov/ Section 508] of the Rehabilitation Act.

Apart from the real accessibility needs present in the world, compliance to these two standards is a requirement for many companies and public agencies.

== Certification ==

Resources permitting, we'll be working to certify our accessibility compliance, making the results of our efforts tangible and trustable.

== The Real World ==

Standards are good, at the bureaucratic point of view. But our main purpose is really making our editor effectively usable by people with disabilities. The most important thing is giving our end users a wonderful editing experience, not only satisfying the checklists defined by the standards.

We invite accessibility experts and end users to participate, helping us providing the dreamed accessibility solution for browser based editing.

== Features ==

[TODO: List the features we need to provide for accessibility and standards compliance]

← Older revision		Revision as of 09:24, 6 February 2008
Line 22:		Line 22:

	Resources permitting, we'll be working to certify our accessibility compliance, making the results of our efforts tangible and trustable.		Resources permitting, we'll be working to certify our accessibility compliance, making the results of our efforts tangible and trustable.
		+
		+	Not a certification tool, but for Section 508, a common communication approach for compliance is the [http://www.itic.org/archives/articles/20040506/voluntary_product_accessibility_template_vpat.php Voluntary Product Accessibility Template (VPAT)].<br>

	== The Real World ==		== The Real World ==

← Older revision		Revision as of 23:04, 4 February 2008
Line 1:		Line 1:
		+	(Draft)
		+
	__NOTOC__There are two levels of accessibility features we aim to provide with V3:		__NOTOC__There are two levels of accessibility features we aim to provide with V3:

@@ Line 1: / Line 1: @@
 (Draft)
 __NOTOC__There are two levels of accessibility features we aim to provide with V3:
-* Making the editor usable by people with disabilities.
+*Making the editor usable by people with disabilities.
-* Ensuring that accessibility features can be introduced in the contents produced with the editor, guaranteeing and enforcing the minimum accessibility level in the contents.
+*Ensuring that accessibility features can be introduced in the contents produced with the editor, guaranteeing and enforcing the minimum accessibility level in the contents.
-== Standards ==
+== Standards  ==
 The first and most practical way to ensure accessibility in both the above aspects is by following the rules and requirements defined by the common standard available for web applications.
 We have chosen two of the most notable standards as those we'll be working to be compliant to:
-* The [http://www.w3.org/WAI/ WAI], published by the W3C, which actually comprehends a number of standards and guidelines that interest our project: [http://www.w3.org/WAI/intro/wcag.php Web Content Accessibility Guidelines (WCAG)], [http://www.w3.org/WAI/intro/atag.php Authoring Tool Accessibility Guidelines (ATAG)] and [http://www.w3.org/WAI/intro/aria.php Accessible Rich Internet Applications (WAI-ARIA)];
+*The [http://www.w3.org/WAI/ WAI], published by the W3C, which actually comprehends a number of standards and guidelines that interest our project: [http://www.w3.org/WAI/intro/wcag.php Web Content Accessibility Guidelines (WCAG)], [http://www.w3.org/WAI/intro/atag.php Authoring Tool Accessibility Guidelines (ATAG)] and [http://www.w3.org/WAI/intro/aria.php Accessible Rich Internet Applications (WAI-ARIA)];
-* The US [http://www.section508.gov/ Section 508] of the Rehabilitation Act.
+*The US [http://www.section508.gov/ Section 508] of the Rehabilitation Act.
 Apart from the real accessibility needs present in the world, compliance to these two standards is a requirement for many companies and public agencies.
-== Certification ==
+== Certification  ==
 Resources permitting, we'll be working to certify our accessibility compliance, making the results of our efforts tangible and trustable.
-Not a certification tool, but for Section 508, a common communication approach for compliance is the [http://www.itic.org/archives/articles/20040506/voluntary_product_accessibility_template_vpat.php Voluntary Product Accessibility Template (VPAT)].<br>
+Not a certification tool, but for Section 508, a common communication approach for compliance is the [http://www.access-star.org/ITI-VPAT-v1.3.html Voluntary Product Accessibility Template (VPAT)].<br>
-== The Real World ==
+== The Real World  ==
 Standards are good, at the bureaucratic point of view. But our main purpose is really making our editor effectively usable by people with disabilities. The most important thing is giving our end users a wonderful editing experience, not only satisfying the checklists defined by the standards.
 We invite accessibility experts and end users to participate, helping us providing the dreamed accessibility solution for browser based editing.
-== Features ==
+== Features  ==
 [TODO: List the features we need to provide for accessibility and standards compliance]

FCKeditor 3.x/Design and Architecture/Accessibility - Revision history

Martinkou: Updated the VPAT link.

Fredck at 09:24, 6 February 2008

Fredck at 23:04, 4 February 2008

Fredck: New page: __NOTOC__There are two levels of accessibility features we aim to provide with V3: * Making the editor usable by people with disabilities. * Ensuring that accessibility features can be i...

Fredck: New page: NOTOCThere are two levels of accessibility features we aim to provide with V3: * Making the editor usable by people with disabilities. * Ensuring that accessibility features can be i...