Thread Subject: Re: Cognitive - compatibility
This archival content is maintained by WebAIM and NCDAE on behalf of TEITAC and the U.S. Access Board . Additional details on the updates to section 508 and section 255 can be found at the Access Board web site.
From: Slatin, John M
Date: Mon, Mar 05 2007 3:45 PM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Andi Snow-Weaver: "Re: Cognitive - compatibility"
- Previous message in thread: Andi Snow-Weaver: "Re: Cognitive - compatibility"
- Messages sorted by: Author | Thread | Date
<q>* Software for rendering or authoring text shall provide the
following features or support for ...</q>
Is there software for authoring text that doesn't also render text?
Is there some way we want to constrain what "render" means here?
"Good design is accessible design."
Dr. John M. Slatin, Director
University of Texas at Austin
1 University Station G9600
Austin, TX 78712
ph 512-495-4288, fax 512-495-4524
email = EMAIL ADDRESS REMOVED =
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Andi
Sent: Monday, March 05, 2007 3:09 PM
To: = EMAIL ADDRESS REMOVED =
Subject: Re: [teitac-websoftware] Cognitive - compatibility
My action item from last week's meeting was to update the cognitive
proposal dealing with word lookup, spelling correction, and text to
address concerns raised on the mailing list and in the meeting.
* Software for rendering or authoring text shall provide the following
features or support for assistive technology that implements the
** the ability to determine the definition of a word in the rendered
** the ability to read the rendered text outloud
* Software for authoring text shall provide the ability to check for
spelling errors and correct them or support for assistive technology
that implements the feature.