E-mail List Archives

Re: Front End Developers and ATs


From: David Ashleydale
Date: Aug 29, 2013 10:20AM

Wow, lot's of great feedback! I should have also said, though, that I
didn't mean to just give JAWS to a developer with no accessibility
training. The developers will already know how to code with accessibility
in mind. I was just wondering if I should insist that they also use ATs in
their work for when they are coding new things. Giving them ATs would also
be accompanied by training in how to use the ATs, from the point of view of
regular users of those ATs.

But lots of great points above. I'm going to go write some of them down and
let you know what we have so far as a recommendation.


On Thu, Aug 29, 2013 at 3:55 AM, Alastair Campbell < <EMAIL REMOVED> > wrote:

> Steve Green wrote:
> > I agree that you need to be careful, so it is important to work with a
> > variety of people [snip] However, even working with one person is better
> > than not working with any, which is where almost every FED is right now.
> >
> I guess this comes down to what we think a useful minimum is? I think we
> agree that exposure is useful, but you need the macro view as well.
> Given little resource, what would we recommend for a front-end developer? I
> would suggest:
> - A training day on web accessibility, something fairly practical that
> covers the different interaction styles. This should help with the big
> picture view, and provide some basis for interpreting results.
> - Whenever the organisation conducts usability / accessibility testing,
> observing all the sessions (assuming it's done by other people).
> - Adding things to their personal development plan (I guess most places
> have those back-burner internal projects that people do for their own
> development?), like assessing their own work against the guidelines, and
> testing it with various AT.
> Any other useful, not too expensive things FEDs can do?
> -Alastair
> > > >