Thread Subject: Re: Merging Web and Software and what is Webcontent?

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: Andi Snow-Weaver
Date: Wed, Jul 11 2007 10:40 AM

Gregg,

You must have missed the introductory text to the software provisions that
said software must also consider both the General and the Content
provisions.

Andi




Gregg
Vanderheiden
< = EMAIL ADDRESS REMOVED = To
u> "'TEITAC Web/Software
Sent by: Subcommittee'"
teitac-websoftwar < = EMAIL ADDRESS REMOVED =
= EMAIL ADDRESS REMOVED = >
itac.org cc

Subject
07/11/2007 11:01 Re: [teitac-websoftware] Merging
AM Web and Software and what is
Webcontent?

Please respond to
TEITAC
Web/Software
Subcommittee
<teitac-websoftwa
= EMAIL ADDRESS REMOVED =
g>






Some quick thoughts to toss on the list for others to consider when reading
it

- wouldn't some of the things in content have to also apply to software?

1) Contrast for example. In software there is something about "if color
settings" but what if there aren't color settings? Then no contrast?

2) Color is another


Perhaps we end up with

Content and Software guidelnes
Additional Software guidelines

Maybe we also have
(Additional content guidelines?)

Don't know. Just took a quick look. Can't join you today unfortunately.
Funding agency deadline.



Gregg
-- ------------------------------
Gregg C Vanderheiden Ph.D.



> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf
> Of Andi Snow-Weaver
> Sent: Wednesday, July 11, 2007 8:12 AM
> To: = EMAIL ADDRESS REMOVED =
> Subject: [teitac-websoftware] Merging Web and Software and
> what is Webcontent?
>
>
> There has been a lot of discussion on the mailing list
> recently about whether or not we should merge Web and
> Software because the line distinguishing the two is blurring.
> Indeed, this issue came up early in the Web and Software
> subcommittee but we delayed any decision until we had done
> the bottoms up analysis of the issues with the existing 508
> provisions.
>
> I think it is hard to put this issue to rest, one way or the
> other, until we have looked at a proposal for merging the
> two. Otherwise, we are just talking theory and we really
> don't know which is the better approach.
>
> We have also been wrestling with the issue of applicability
> of the standard based on how the content is accessed; that
> is, some interpret the current
> 508 standard to apply to HTML content only if it is accessed
> via the Web but not if it is included as an attachment in an
> e-mail or stored on a CD.
>
> As I looked at it this morning, I came to believe that we
> can't just merge Web and software altogether but we might
> need to separate out the provisions for simple content for
> "authors" who are not "programmers".
>
> So I took a stab at it and then looked at how this would
> affect harmonization with international standards, another of
> our goals.
> Regardless of whether or not we choose to reorganize the
> provisions, we have ended up with some country-unique
> requirements. If we don't re-organize, we are fairly well
> harmonized with WCAG 2.0 but have some issues with ISO. If we
> reorganize, we will have the same issues with ISO
> harmonzation and more with WCAG 2.0.
>
> Please take a look at the analysis prior to today's meeting.
> I apologize for sending this out so late because it is rather
> a lot to get through.
>
> http://teitac.org/wiki/Web_and_Software:_Merging_Analysis
>
> Andi
>
>

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