Thread Subject: Re: Allen's proposal for a new section oncontent

From: Gregg Vanderheiden
Date: Sun, Apr 01 2007 1:10 PM

• Return to this mailing list's archives
• View all messages in this thread
• Next message in thread: Hoffman, Allen: "Re: Allen's proposal for a new sectiononcontent"
• Previous message in thread: Andi Snow-Weaver: "Allen's proposal for a new section on content"
• Messages sorted by: Author | Thread | Date

Overall I think this is a good direction and in keeping with what the
General Group discovered (the need to qualify the application of the
various guidelines)



Couple of comments here and three below marked GV:

Some others look like they need some tuning.



GV: maybe delete 'encoding' to make them more technology neutral

GV: 'verbal' means 'words' not 'speech' (vocal). Braille is verbal.
Maybe use "Auditory"





Add a new section to 508 (1194.27?)



1. When a content format supports non-text objects, an encoding mechanism
shall be provided to associate non-text objects with textual descriptions
displayable by a user-agent.

2. When a content format supports multimedia, an encoding mechanism shall
be provided to include synchronized text of verbal content, and audio
descriptions of critical nonverbal activity displayable by a user-agent.

GV: 'verbal means words not speech (vocal). Braille is verbal. Maybe
use "Auditory" would work better here than 'verbal'.

3. When a content format supports color, an encoding mechanism shall be
provided to identify all colors selected for text, both foreground and
background displayable by a user-agent.

GV: Not clear the benefit of this. Since there are millions of colors and
there are not names for them and few people could identify a color by its
codes. Suggest two other guidelines

a) information is not presented only using color.

b) that foreground text and its background have a contrast of at least
relative luminance contrast of X:1 (5?). (which makes the contrast color
insensitive)



4. When a content format supports 2 dimensional display of information,
an encoding mechanism shall be provided to identify the logical linear
reading order of the content displayable by a user-agent.

5. When a content format supports data tables, an encoding mechanism
shall be provided to identify row and column headers for tabular information
displayable by a user-agent.

6. When a content format supports data tables, an encoding mechanism
shall be provided to associate row and column headers with other table
cells, displayable by a user-agent.

7. When a content format supports interactive elements, an encoding
mechanism shall be provided to identify identity, operation, and state, of
any interactive elements displayable by a user-agent.

GV: Should add "name" to the lists. Identity is often a unique number or
code.



8. When a content format supports links, an encoding mechanism shall be
provided to identify link text or graphics displayable by a user-agent.

9. When a content format supports embedded comments, an encoding
mechanism shall be provided to identify embedded comments and associate
those comment locations within the document.

10. Encoding mechanism which allow programmatic input and execution of
end-user scripting, shall provide access to the embedded scripts.

11. When a content format supports scanned images of text, an encoding
mechanism shall be provided to identify text of scanned images of text,
displayable by a user-agent. Note, this means allowing for inclusion of the
text of a scanned image of text.

12. When a content format supports dynamic presentations, graphs, or other
extracted information, an encoding mechanism shall be provided to include
data used for any dynamic presentations, graphs, or other extracted
information displayable by a user-agent.





Gregg

-- ------------------------------

Gregg C Vanderheiden Ph.D.







> -----Original Message-----

> From: = EMAIL ADDRESS REMOVED =

> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf

> Of Andi Snow-Weaver

> Sent: Friday, March 30, 2007 3:12 PM

> To: = EMAIL ADDRESS REMOVED =

> Subject: [teitac-websoftware] Allen's proposal for a new

> section on content

>

>

> Please carefully review Allen's proposal on content before

> next week. [1] As I said yesterday in the meeting, I added a

> phrase to the beginning of each one to cover a concern that

> was raised about applicability; that is, you only have to

> provide an encoding mechanism for table headers if the

> content format supports data tables.

>

> I provided some comments and questions on the wiki "discuss"

> page. [2] Feel free to add your comments to the wiki or to

> post them here on the mailing list and we will summarize

> before next week's call.

>

> [1]

> http://teitac.org/wiki/Web_and_Software:content#Add_a_new_sect

> ion_to_508_.281194.27.3F.29

> [2] http://teitac.org/wiki/Talk:Web_and_Software:content

>

> Andi

>

>

• Next message in Thread: Hoffman, Allen: "Re: Allen's proposal for a new sectiononcontent"
• Previous message in Thread: Andi Snow-Weaver: "Allen's proposal for a new section on content"