E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 5 (In chronological order)

From: E.J. Zufelt
Date: Tue, Oct 26 2010 1:00PM
Subject: Re: Accessible Authoring Tool
No previous message | Next message →

Good afternoon Michael,

The functionality that you are talking about sounds a lot like what is provided by the Drupal accessible content module - http://drupal.org/project/accessible_content

I haven't used the module myself, but I do know the developer. I believe that there * may * be a Wordpress plugin for this functionality as well. The functionality comes from a php project, so it may be able to be used with other CMSs as well.

HTH,

Everett Zufelt
http://zufelt.ca

Follow me on Twitter
http://twitter.com/ezufelt

View my LinkedIn Profile
http://www.linkedin.com/in/ezufelt



On 2010-10-26, at 2:52 PM, Langum, Michael J wrote:

> The Draft for the New Section 508 standards includes:
> 413.2 Authoring Tools. For all formats supported by the authoring tool, authoring tools shall provide a mode of operation to create or modify content that conforms to Chapter 5 (Electronic Documents). [emphasis added]
> I'm wondering what this implies for web 2.0 apps where content will be created by folks who do not know accessibility requirements.
>
> Can we (those ruled by sect. 508) accept end-user generated content that is not "accessible?"
>
> If not, will we need to ensure a "508 clearance" process, before publication?
>
> Assuming that we must ensure that user-generated content is accessible, Is anyone aware of browser text input control, that supports or ensures accessibility standards. That is, on submit, does a quick check of the input, and prompts the user for corrections or needed additional information.. E.g.
>
> * if I create a table, the control will catch this, and make sure that I have row and column heads identified,
> * if I add an image, the control will catch this and prompt me for an alternative text?
>
>
> -- Mike
>
>

From: Langum, Michael J
Date: Tue, Oct 26 2010 1:06PM
Subject: Accessible Authoring Tool
← Previous message | Next message →

The Draft for the New Section 508 standards includes:
413.2 Authoring Tools. For all formats supported by the authoring tool, authoring tools shall provide a mode of operation to create or modify content that conforms to Chapter 5 (Electronic Documents). [emphasis added]
I'm wondering what this implies for web 2.0 apps where content will be created by folks who do not know accessibility requirements.

Can we (those ruled by sect. 508) accept end-user generated content that is not "accessible?"

If not, will we need to ensure a "508 clearance" process, before publication?

Assuming that we must ensure that user-generated content is accessible, Is anyone aware of browser text input control, that supports or ensures accessibility standards. That is, on submit, does a quick check of the input, and prompts the user for corrections or needed additional information.. E.g.

* if I create a table, the control will catch this, and make sure that I have row and column heads identified,
* if I add an image, the control will catch this and prompt me for an alternative text?


-- Mike

From: Langum, Michael J
Date: Tue, Oct 26 2010 1:30PM
Subject: Re: Accessible Authoring Tool
← Previous message | Next message →

Everett (or others) ,

Is there a .Net control?
-- Mike

From: E.J. Zufelt
Date: Tue, Oct 26 2010 1:42PM
Subject: Re: Accessible Authoring Tool
← Previous message | Next message →

Good afternoon Michael,

I am not aware of a .Net control.

You might try contacting the Drupal module author to see if he has heard of a .Net solution. http://drupal.org/user/125882/contact

Thanks,
Everett Zufelt
http://zufelt.ca

Follow me on Twitter
http://twitter.com/ezufelt

View my LinkedIn Profile
http://www.linkedin.com/in/ezufelt



On 2010-10-26, at 3:26 PM, Langum, Michael J wrote:

> Everett (or others) ,
>
> Is there a .Net control?
> -- Mike
>
>
>

From: Vlad Alexander (XStandard)
Date: Tue, Oct 26 2010 1:48PM
Subject: Re: Accessible Authoring Tool
← Previous message | No next message

Hi Mike,

>Is anyone aware of browser text input control, that supports
>or ensures accessibility standards.
We produce an editor, which is a browser plug-in, that generates accessible markup. Please see:
http://xstandard.com/en/documentation/xstandard-dev-guide/accessibility/

>That is, on submit, does a quick check of the input, and prompts
>the user for corrections or needed additional information.
You will get significantly better results if the editor enforces accessibility requirements at the point of authoring content, rather than on submit.

>if I create a table, the control will catch this, and make
>sure that I have row and column heads identified
That's not enough. The content author needs to check if the association is correct. Our Screen Reader Preview feature will display tables in linear form so that the content author can see if the association is correctly done.

>if I add an image, the control will catch this and prompt me
>for an alternative text?
That's not enough. Not all images should have alternate text. XStandard prompts the user to identify if the images is used for decoration or not.

Regards,
Vlad Alexander
http://xstandard.com


-------- Original Message --------
From: Langum, Michael J
Date: 10/26/2010 11:52 AM
> The Draft for the New Section 508 standards includes:
> 413.2 Authoring Tools. For all formats supported by the authoring tool, authoring tools shall provide a mode of operation to create or modify content that conforms to Chapter 5 (Electronic Documents). [emphasis added]
> I'm wondering what this implies for web 2.0 apps where content will be created by folks who do not know accessibility requirements.
>
> Can we (those ruled by sect. 508) accept end-user generated content that is not "accessible?"
>
> If not, will we need to ensure a "508 clearance" process, before publication?
>
> Assuming that we must ensure that user-generated content is accessible, Is anyone aware of browser text input control, that supports or ensures accessibility standards. That is, on submit, does a quick check of the input, and prompts the user for corrections or needed additional information.. E.g.
>
> * if I create a table, the control will catch this, and make sure that I have row and column heads identified,
> * if I add an image, the control will catch this and prompt me for an alternative text?
>
>
> -- Mike
>
>