Thread Subject: Re: more "content"

Note

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: Tom Brett
Date: Thu, May 10 2007 1:50 PM


One of the themes that we are trying to incorporate into the standards is
Usability. If standards are written in a complex manner they will not be
used.



Tom Brett


-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Andrew
Kirkpatrick
Sent: Thursday, May 10, 2007 3:33 PM
To: TEITAC Web/Software Subcommittee
Subject: Re: [teitac-websoftware] more "content"

> > "Any sequence of bytes with associated metadata that causes
> it to be
> > interpreted, by specification, as being fit to render for
> the purpose
> > of conveying information."

My problem with this language is that it may not be easy for humanoid
life forms to understand it and that it doesn't help clarify where a
developer or content provider might need to look to content standards vs
web or software standards.

AWK


WebAIM is an initiative of:
Center for Persons with Disabilities (CPD) Utah State University