Thread Subject: Re: General Issues: Browser Requirements

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: Gregg Vanderheiden
Date: Wed, Jan 10 2007 2:35 PM

Good point

Agree

In hfes 200 and iso 171 we talk about this class of products by description
- not by naming.

software that interacts with hardware or provides services for other
software
EXAMPLES: An operating system, device drivers, windowing systems, and
software toolkits, browsers


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



> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf
> Of Sean Hayes
> Sent: Wednesday, January 10, 2007 7:17 AM
> To: TEITAC Web/Software Subcommittee
> Subject: Re: [teitac-websoftware] General Issues: Browser Requirements
>
> Browsers, Players, and Virtual machines are all special cases
> of platform software like the OS and probably should be
> subject to similar rules. I'd be unhappy to single out just
> browsers (assuming we could even adequately define browser).
>
> Sean Hayes
> Standards and Policy Team
> Accessible Technology Group
> Microsoft
> Phone:
> mob +44 7977 455002
> office +44 117 9719730
>
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf
> Of Andi Snow-Weaver
> Sent: 09 January 2007 22:13
> To: = EMAIL ADDRESS REMOVED =
> Subject: [teitac-websoftware] General Issues: Browser Requirements
>
>
> Some have suggested that we might want to impose some
> requirements on browser. For example, if browsers provided
> more keyboard support, ATs wouldn't have to and users who
> don't use AT would benefit.
>
> Thoughts on this topic?
>
> Andi
>
>

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