E-mail List Archives
Re: comprehensive list of keyboard accessible software?
From: Ryan E. Benson
Date: Jul 31, 2013 5:04PM
- Next message: Alastair Campbell: "building accessible javascript accordions?"
- Previous message: Louis Li: "Web Accessibility Study (second iteration, can be done remotely)"
- Next message in Thread: Jonathan Metz: "Re: comprehensive list of keyboard accessible software?"
- Previous message in Thread: Jonathan Metz: "Re: comprehensive list of keyboard accessible software?"
- View all messages in this Thread
> I recently found a relatively decent
example from Articulates Storyline eLearning software
(http://www.articulate.com/products/storyline-section-508-vpat.php).
Personally I no longer trust Articulate. TL;DR: A year ago I checked them
out, they claimed full compliance then. No demos were compliant. I had one
team of experienced people in both e-learning and 508 put something
together via StoryLine, following all directions. Upon testing, the output
was kind of compliant, but had a slew of issues, nothing I'd "green light."
While working with our team, I was talking to one of their VPs, who said
the team was doing it incorrectly. I requested that they provide me a fully
compliant demo, they were not able to.
--
Ryan E. Benson
On Tue, Jul 30, 2013 at 5:30 PM, Jonathan Metz
< <EMAIL REMOVED> >wrote:
> Debra makes some good points about what to look out for. A lot of VPATs
> seem to be marketing propaganda too, but they should read like a technical
> spec sheet.
>
> The purpose of VPATs should be to highlight what makes one product or
> service more accessible than another. I recently found a relatively decent
> example from Articulates Storyline eLearning software
> (http://www.articulate.com/products/storyline-section-508-vpat.php). I
> think its important to highlight where accessibility exceeds (for
> example, if something hits WCAG AAA level, it should be mentioned), and if
> it doesnt meet a provision, then it should be mentioned or a workaround
> suggested (i.e. Final delivered PDFs will not include comments).
>
> My rule is, if it doesnt inform me of what the thing does or doesnt do,
> its not a good VPAT.
>
> Jon
>
>
>
> On 7/30/13 5:02 PM, "McMorland, Gabriel" < <EMAIL REMOVED> > wrote:
>
> >My question is really, Is some other institution already doing a great
> >job at vetting commercial software accessibility? I hope so, because it
> >looks time consuming and a lot of the programs our students would use are
> >widely used by lots of people.
> >
> >I do take the point about the complexity of this issue, though. Debra has
> >a good insight on reading VPATs.
- Next message: Alastair Campbell: "building accessible javascript accordions?"
- Previous message: Louis Li: "Web Accessibility Study (second iteration, can be done remotely)"
- Next message in Thread: Jonathan Metz: "Re: comprehensive list of keyboard accessible software?"
- Previous message in Thread: Jonathan Metz: "Re: comprehensive list of keyboard accessible software?"
- View all messages in this Thread