Thread Subject: Ball Grid Array/Surface Mounted Device Rework Systems
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.
Return to this mailing list's archives
From: Baquis David
Date: Mon, Jul 23 2007 11:15 AM
Subject: Ball Grid Array/Surface Mounted Device Rework Systems
See: http://www.air-vac-eng.com/drs25.htm
The Access Board gets a lot of questions like this - regarding products
I never heard of before. I don't know if 508 requirements are kicked in.
I would like the TEITAC to please discuss whether it can provide
guidance to agencies who are faced with many such decisions regarding
whether a product is covered by 508. It is a yes or no question.
My question is whether the software mentioned in the product description
performs an IT function within a product that is not IT because its
principle function is not that of IT. (Similar to the embedded IT in the
definition of E&IT.) I used to say that all software was covered by 508,
but now I am hesitant to continue saying that. I would like the
refreshed standards to clarify how to better determine if something is
covered by 508. Specifically, how does one determine what the principle
function is of something that is not ordinary (at least not to us), and
particularly whether that function is an IT function?
David Baquis
Accessibility Specialist
U.S. Access Board
1331 F Street, NW, #1000
Washington, DC 20004
800-USA-ABLE; (202) 272-0013 (desk tel); 240-855-1682 (cell)
www.access-board.gov <http://www.access-board.gov> ;
= EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = > "Leading
the way to excellence in accessibility"
From: Jim Tobias
Date: Mon, Jul 23 2007 12:20 PM
Subject: Re: Ball Grid Array/Surface Mounted Device ReworkSystems
i would say this is not e&it. it's a soldering workstation.
i think it'd be great to have a central federal resource that could provide
such guidance.
***
Jim Tobias
Inclusive Technologies
+1.732.441.0831 v/tty
+1.908.907.2387 mobile
skype jimtobias
_____
From: Baquis David [mailto: = EMAIL ADDRESS REMOVED = ]
Sent: Monday, July 23, 2007 1:09 PM
To: = EMAIL ADDRESS REMOVED =
Subject: [teitac-general] Ball Grid Array/Surface Mounted Device
ReworkSystems
See: http://www.air-vac-eng.com/drs25.htm
The Access Board gets a lot of questions like this - regarding products I
never heard of before. I don't know if 508 requirements are kicked in. I
would like the TEITAC to please discuss whether it can provide guidance to
agencies who are faced with many such decisions regarding whether a product
is covered by 508. It is a yes or no question.
My question is whether the software mentioned in the product description
performs an IT function within a product that is not IT because its
principle function is not that of IT. (Similar to the embedded IT in the
definition of E&IT.) I used to say that all software was covered by 508, but
now I am hesitant to continue saying that. I would like the refreshed
standards to clarify how to better determine if something is covered by 508.
Specifically, how does one determine what the principle function is of
something that is not ordinary (at least not to us), and particularly
whether that function is an IT function?
David Baquis
Accessibility Specialist
U.S. Access Board
1331 F Street, NW, #1000
Washington, DC 20004
800-USA-ABLE; (202) 272-0013 (desk tel); 240-855-1682 (cell)
<http://www.access-board.gov> www.access-board.gov;
<mailto: = EMAIL ADDRESS REMOVED = > = EMAIL ADDRESS REMOVED = "Leading the
way to excellence in accessibility"
From: Peter Korn
Date: Mon, Jul 23 2007 12:40 PM
Subject: Re: Ball Grid Array/Surface Mounted Device ReworkSystems
David, Jim,
We touched in this a bit last week, bandying about language about
"primary function". I think the conversation might have been more
focused on telecommunications products (e.g. primary functions vs.
incidental functions), but perhaps there is some applicability of those
concepts to this situation.
The primary function of this device is to assemble hardware components;
and it has embedded E&IT to support that function.
Regards,
Peter Korn
Accessibility Architect,
Sun Microsystems, Inc.
> i would say this is not e&it. it's a soldering workstation.
> i think it'd be great to have a central federal resource that could
> provide such guidance.
>
> ***
> Jim Tobias
> Inclusive Technologies
> +1.732.441.0831 v/tty
> +1.908.907.2387 mobile
> skype jimtobias
>
>
> ------------------------------------------------------------------------
> *From:* Baquis David [mailto: = EMAIL ADDRESS REMOVED = ]
> *Sent:* Monday, July 23, 2007 1:09 PM
> *To:* = EMAIL ADDRESS REMOVED =
> *Subject:* [teitac-general] Ball Grid Array/Surface Mounted Device
> ReworkSystems
>
> See: http://www.air-vac-eng.com/drs25.htm
>
> The Access Board gets a lot of questions like this – regarding
> products I never heard of before. I don’t know if 508 requirements
> are kicked in. I would like the TEITAC to please discuss whether
> it can provide guidance to agencies who are faced with many such
> decisions regarding whether a product is covered by 508. It is a
> yes or no question.
>
> My question is whether the software mentioned in the product
> description performs an IT function within a product that is not
> IT because its principle function is not that of IT. (Similar to
> the embedded IT in the definition of E&IT.) I used to say that all
> software was covered by 508, but now I am hesitant to continue
> saying that. I would like the refreshed standards to clarify how
> to better determine if something is covered by 508. Specifically,
> how does one determine what the principle function is of something
> that is not ordinary (at least not to us), and particularly
> whether that function is an IT function?
>
> David Baquis
>
> Accessibility Specialist
>
> U.S. Access Board
>
> 1331 F Street, NW, #1000
>
> Washington, DC 20004
>
> 800-USA-ABLE; (202) 272-0013 (desk tel); 240-855-1682 (cell)
>
> www.access-board.gov <http://www.access-board.gov>;
> = EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = > //
> ////“Leading the way to excellence in accessibility”//
>
> // //////
>
> ------------------------------------------------------------------------
>
>
From: Hoffman, Allen
Date: Tue, Jul 24 2007 7:05 AM
Subject: Re: Ball Grid Array/Surface Mounted Device ReworkSystems
I think from this thread we are on the right track to developing
guidance for just such items. I've assess items like mail-handling
equipment that sorts mail, has a software interface, but really is a
specialized mechanism to sort mail, not process electronic information.
Allen Hoffman -- = EMAIL ADDRESS REMOVED = ; v: 202-447-0303
From: Jim Tobias
Date: Tue, Jul 24 2007 8:50 AM
Subject: Re: Ball Grid Array/Surface Mounted DeviceReworkSystems
There is a complexity to products like this that may make software
accessibility useless in the final analysis. For those who can't see the
picture, this product looks like a stereo inspection microscope with other
attachments, for use in inspecting and perhaps repairing circuit boards.
LEt's say for argument's sake that the software drives the x-y coordinate
microscope stage in small steps. It's true that we could require that
software to be screen reader compatible, for example, but the visual nature
of the task would not be finessed. A blind person could use the software
but not the product.
If we are going to address products whose principal function is not E&IT,
but which use embedded E&IT to perform their non-E&IT function, we need to
write provisions in such a way that we are doing some good. Perhaps the
principal is that we want to require the embedded E&IT to meet the Standard
if that will allow the user to perform the non-E&IT function. Another way
of saying it is that the inaccessible E&IT was the principal barrier to use.
***
Jim Tobias
Inclusive Technologies
+1.732.441.0831 v/tty
+1.908.907.2387 mobile
skype jimtobias
_____
From: Hoffman, Allen [mailto: = EMAIL ADDRESS REMOVED = ]
Sent: Tuesday, July 24, 2007 8:59 AM
To: TEITAC General Interface Accessibility Subcommittee
Cc: Peterson, Bill
Subject: Re: [teitac-general] Ball Grid Array/Surface Mounted
DeviceReworkSystems
I think from this thread we are on the right track to developing guidance
for just such items. I've assess items like mail-handling equipment that
sorts mail, has a software interface, but really is a specialized mechanism
to sort mail, not process electronic information.
Allen Hoffman -- = EMAIL ADDRESS REMOVED = ; v: 202-447-0303
_____
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Baquis David
Sent: Monday, July 23, 2007 1:09 PM
To: = EMAIL ADDRESS REMOVED =
Subject: [teitac-general] Ball Grid Array/Surface Mounted Device
ReworkSystems
See: http://www.air-vac-eng.com/drs25.htm
The Access Board gets a lot of questions like this - regarding products I
never heard of before. I don't know if 508 requirements are kicked in. I
would like the TEITAC to please discuss whether it can provide guidance to
agencies who are faced with many such decisions regarding whether a product
is covered by 508. It is a yes or no question.
My question is whether the software mentioned in the product description
performs an IT function within a product that is not IT because its
principle function is not that of IT. (Similar to the embedded IT in the
definition of E&IT.) I used to say that all software was covered by 508, but
now I am hesitant to continue saying that. I would like the refreshed
standards to clarify how to better determine if something is covered by 508.
Specifically, how does one determine what the principle function is of
something that is not ordinary (at least not to us), and particularly
whether that function is an IT function?
David Baquis
Accessibility Specialist
U.S. Access Board
1331 F Street, NW, #1000
Washington, DC 20004
800-USA-ABLE; (202) 272-0013 (desk tel); 240-855-1682 (cell)
<http://www.access-board.gov> www.access-board.gov;
<mailto: = EMAIL ADDRESS REMOVED = > = EMAIL ADDRESS REMOVED = "Leading the
way to excellence in accessibility"
From: Rex Lint
Date: Tue, Jul 24 2007 4:10 PM
Subject: Re: Ball Grid Array/Surface MountedDeviceReworkSystems
Jim,
I don't agree that it's the complexity that makes it not solvable by
accessibility, it's the nature of the decisions that must be made in the
feedback loop. Here, one MUST see the target and provide inputs that guide
the tools to the target. If you can't see the target, then your use of the
tool would require fundamental alteration of the product to make it possible
for you to use it for the intended function.
Doug Wakefield used a similar argument to say that air traffic control
consoles didn't have to be accessible.
Rex
Rex Lint, Consultant
Chair, Section 508 Working Group
Information Technology Ass'n of America
PH: 603-860-7651
_____
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Jim Tobias
Sent: Tuesday, July 24, 2007 10:47 AM
To: 'TEITAC General Interface Accessibility Subcommittee'
Cc: 'Peterson, Bill'
Subject: Re: [teitac-general] Ball Grid Array/Surface
MountedDeviceReworkSystems
There is a complexity to products like this that may make software
accessibility useless in the final analysis. For those who can't see the
picture, this product looks like a stereo inspection microscope with other
attachments, for use in inspecting and perhaps repairing circuit boards.
LEt's say for argument's sake that the software drives the x-y coordinate
microscope stage in small steps. It's true that we could require that
software to be screen reader compatible, for example, but the visual nature
of the task would not be finessed. A blind person could use the software
but not the product.
If we are going to address products whose principal function is not E&IT,
but which use embedded E&IT to perform their non-E&IT function, we need to
write provisions in such a way that we are doing some good. Perhaps the
principal is that we want to require the embedded E&IT to meet the Standard
if that will allow the user to perform the non-E&IT function. Another way
of saying it is that the inaccessible E&IT was the principal barrier to use.
***
Jim Tobias
Inclusive Technologies
+1.732.441.0831 v/tty
+1.908.907.2387 mobile
skype jimtobias
_____
From: Hoffman, Allen [mailto: = EMAIL ADDRESS REMOVED = ]
Sent: Tuesday, July 24, 2007 8:59 AM
To: TEITAC General Interface Accessibility Subcommittee
Cc: Peterson, Bill
Subject: Re: [teitac-general] Ball Grid Array/Surface Mounted
DeviceReworkSystems
I think from this thread we are on the right track to developing guidance
for just such items. I've assess items like mail-handling equipment that
sorts mail, has a software interface, but really is a specialized mechanism
to sort mail, not process electronic information.
Allen Hoffman -- = EMAIL ADDRESS REMOVED = ; v: 202-447-0303
_____
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Baquis David
Sent: Monday, July 23, 2007 1:09 PM
To: = EMAIL ADDRESS REMOVED =
Subject: [teitac-general] Ball Grid Array/Surface Mounted Device
ReworkSystems
See: http://www.air-vac-eng.com/drs25.htm
The Access Board gets a lot of questions like this - regarding products I
never heard of before. I don't know if 508 requirements are kicked in. I
would like the TEITAC to please discuss whether it can provide guidance to
agencies who are faced with many such decisions regarding whether a product
is covered by 508. It is a yes or no question.
My question is whether the software mentioned in the product description
performs an IT function within a product that is not IT because its
principle function is not that of IT. (Similar to the embedded IT in the
definition of E&IT.) I used to say that all software was covered by 508, but
now I am hesitant to continue saying that. I would like the refreshed
standards to clarify how to better determine if something is covered by 508.
Specifically, how does one determine what the principle function is of
something that is not ordinary (at least not to us), and particularly
whether that function is an IT function?
David Baquis
Accessibility Specialist
U.S. Access Board
1331 F Street, NW, #1000
Washington, DC 20004
800-USA-ABLE; (202) 272-0013 (desk tel); 240-855-1682 (cell)
<http://www.access-board.gov> www.access-board.gov;
<mailto: = EMAIL ADDRESS REMOVED = > = EMAIL ADDRESS REMOVED = "Leading the
way to excellence in accessibility"
WebAIM is an initiative of:
