E-mail List Archives
Re: comprehensive list of keyboard accessible software?
From: Jonathan Metz
Date: Jul 30, 2013 3:30PM
- Next message: Steve Green: "Language declaration when using XHTML+RDFa 1.0"
- Previous message: Bourne, Sarah (ITD): "Re: comprehensive list of keyboard accessible software?"
- Next message in Thread: Jonathan Metz: "Re: comprehensive list of keyboard accessible software?"
- Previous message in Thread: Bourne, Sarah (ITD): "Re: comprehensive list of keyboard accessible software?"
- View all messages in this Thread
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 Articulate’s Storyline eLearning software
(http://www.articulate.com/products/storyline-section-508-vpat.php). I
think it’s important to highlight where accessibility exceeds (for
example, if something hits WCAG AAA level, it should be mentioned), and if
it doesn’t 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 doesn’t inform me of what the thing does or doesn’t do,
it’s not a good VPAT.
Jon
- Next message: Steve Green: "Language declaration when using XHTML+RDFa 1.0"
- Previous message: Bourne, Sarah (ITD): "Re: comprehensive list of keyboard accessible software?"
- Next message in Thread: Jonathan Metz: "Re: comprehensive list of keyboard accessible software?"
- Previous message in Thread: Bourne, Sarah (ITD): "Re: comprehensive list of keyboard accessible software?"
- View all messages in this Thread