[nfbcs] Fwd: Target looking for contractors to assist with accessibility testing

Steve Jacobson steve.jacobson at visi.com
Fri Jul 13 16:13:57 UTC 2012


Aaron,

I think you raise a very interesting point, and it is hard to know the answer.  If a web site that has 
important information for a blind person and they have followed the latest accessibility 
recommendations, one would think they shouldn't be held accountable.  Yet, if no screen reader reads 
their pages well or easily, that would seem to have to count for something as well.  There is a 
tendency, in my opinion, for screen reader developers to occasionally blame web sites for the lack of 
support that the screen reader has for a new technology that should be accessible.  One can find cases 
where NVDA works better than Window-Eyes or JFW, but of course there are still areas where Window-Eyes 
and JFW work but NVDA does not work, especially with older software.  I was surprised to find that NVDA 
seems to handle the FLASH updater better than either JFW or Window-Eyes and one has to wonder why and 
whether it is fair for us to be criticizing Adobe.  Yet, how hard should it be for Adobe to write 
something as simple as an updater with three or four buttons that would work with everything.  Is it 
really necessary for them to use a new technology that is associated with a process that is required to 
run on our computers?  I think this is a question that is worth some discussion.

Best regards,

Steve Jacobson

On Fri, 13 Jul 2012 07:46:45 -0500, Aaron Cannon wrote:

>Speaking about Window Eyes in particular, based on what I have seen
>from some testing of ARIA attributes and the like, Window Eyes doesn't
>always seem to support the new accessibility information exposed by
>modern browsers.  To be fair, Jaws doesn't support everything either,
>but Jaws and NVDA seem to do a much better job than Window Eyes at
>keeping up.

>I guess the real question in all this is at what point does the burden
>of accessibility shift from the web developers to the screen reader
>manufacturers?

>That being said, this may not apply to Target, as they may not be
>doing anything so advanced as to run into any of Window Eyes' rough
>edges.

>Just my $0.02.

>Aaron

>On 7/12/12, Mike Freeman <k7uij at panix.com> wrote:
>> (1) "Suboptimal" is in the eye of the beholder.
>>
>> (2) While I agree with you in theory, in practice, I doubt that any
>> mainstream company is going to cater to the whims of any moniority as small
>> as we to the extent of testing with multiple screen-readers.
>>
>> Mike
>>
>>
>> -----Original Message-----
>> From: nfbcs-bounces at nfbnet.org [mailto:nfbcs-bounces at nfbnet.org] On Behalf
>> Of Bill
>> Sent: Tuesday, July 03, 2012 12:29 PM
>> To: NFB in Computer Science Mailing List
>> Subject: Re: [nfbcs] Fwd: Target looking for contractors to assist with
>> accessibility testing
>>
>> I appreciate the thought of making the web accessible, but it is
>> ridiculous that companies still insist on supporting one screen reader
>> and just hope the rest of us are going to follow like little lost
>> duckies.  Policies like this that do not support other common screen
>> readers like window-eyes and system access should not be allowed to
>> consider or promote their product or site accessible.  Should these
>> companies be required to support at least the top 3-5 screen readers
>> to comply with any applicable law, or to be able to claim their
>> product to be accessible?  I would be interested in the thoughts of
>> others.  This seems like the internet explorer all over again.
>> Companies insisting on supporting only one suboptimal non-standard
>> compliant, product simply because it is the most used.  It has started
>> to become less of a problem with the browsers, lets hope we can avoid
>> it here.
>> Bill
>> On Mon, Jul 2, 2012 at 5:57 PM, David Andrews <dandrews at visi.com> wrote:
>>>
>>>>
>>>> Target is currently looking to contract with a number of individuals to
>>>> perform accessibility testing on its web site.  Candidates nationwide
>>>> are
>>>> urged to apply.
>>>>
>>>> Position title:  Accessibility Specialist
>>>>
>>>>
>>>> Position type:  Contract
>>>>
>>>>
>>>> Reports to:  Operations Analyst, Accessibility
>>>>
>>>>
>>>> RESPONSIBILITIES
>>>>    * Performs testing to ensure that web sites are free from
>>>> accessibility-related defects and are functioning as planned; confirming
>>>> that user requirements, design specifications, development and
>> accessibility
>>>> meet or exceed expectations.
>>>>    * Develops, follows, and maintains documentation including User
>>>> Requirements, Test plans, and User Scenarios.
>>>>    * Reports all bugs, enhancements, or tasks in JIRA (bug tracking
>>>> software).
>>>>    * Assigns all accessibility issues to appropriate team members and
>>>> works directly with Project Manager or development staff to identify
>>>> solutions and next steps.
>>>>    * Tracks progress regarding issue resolution and confirms that issues
>>>> are retested and closed.
>>>>    * Supports Accessibility and Technical leads regarding all issue
>>>> tracking & reporting needs.
>>>>    * Manages priorities and risks as defined by the site deployment time
>>>> line.
>>>>
>>>>
>>>> KNOWLEDGE AND SKILLS
>>>> §  Screen-reader proficiency, particularly JAWS an absolute must.
>>>> §  Expert-level knowledge of W3C accessibility standards (WCAG 1.0/2.0).
>>>> §  Strong analytical skills and problem solving skills necessary to
>>>> identify programming errors or inconsistencies, and the ability to
>> recommend
>>>> solutions.
>>>> §  Highly organized with great attention to detail.
>>>> §  Excellent verbal and written communication skills.
>>>> §  Ability to collaborate with developers as needed to isolate root
>>>> cause
>>>> of defects.
>>>> §  Familiarity with common web site applications, web browsers, and user
>>>> experience best practices.
>>>>
>>>>
>>>> How to apply:  Please direct any inquiries/resumes via Email to:  Steve
>>>> Sawczyn <mailto:Steve.Sawczyn at target.com>Steve.Sawczyn at target.com .
>>>>
>>>>
>>>>
>>> _______________________________________________
>>> nfbcs mailing list
>>> nfbcs at nfbnet.org
>>> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
>>> To unsubscribe, change your list options or get your account info for
>> nfbcs:
>>> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/cassonw%40gmail.com
>>
>>
>>
>> --
>> Bill Casson
>> University of New Mexico
>> M.S. Computer Science
>> Lewis & Clark Alumnus '11
>> B.A. Physics and Math/Comp Sci.
>> (505) 695-1374
>> cassonw at gmail.com
>>
>> _______________________________________________
>> nfbcs mailing list
>> nfbcs at nfbnet.org
>> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
>> To unsubscribe, change your list options or get your account info for
>> nfbcs:
>> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/k7uij%40panix.com
>>
>>
>> _______________________________________________
>> nfbcs mailing list
>> nfbcs at nfbnet.org
>> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
>> To unsubscribe, change your list options or get your account info for
>> nfbcs:
>> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/cannona%40fireantproductions.com
>>

>_______________________________________________
>nfbcs mailing list
>nfbcs at nfbnet.org
>http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
>To unsubscribe, change your list options or get your account info for nfbcs:
>http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/steve.jacobson%40visi.com








More information about the NFBCS mailing list