RE: [WSG] RE: Tools or analytics to detect assistive devices
You may want to check out JAWS - it's one of the most popular screen readers and there is a free version you use to see how it works on a site. http://www.freedomscientific.com/fs_products/software_jaws.asp Here's a tip that may help, but isn't tested, screen readers act like link text browsers, so you may be able to use that to your advantage and also check the site using a text browser such as Lynx to determine a user-string that may work. Cortney *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
RE: [WSG] RE: Tools or analytics to detect assistive devices
> http://www.accessifyforum.com/viewtopic.php?t=3775 The flash method (detect presence of software that hooks into MSAA) may be of some help if you write a small swf that then pings Google Analytics or similar. But worth noting this recent article http://www.paciellogroup.com/blog/?p=61 More fundamentally though, the stats - if you manage to collect them - could be interpreted either way: - we are getting an insignificant number of screenreader users, so it's not worth bothering with accessibility (which also holds the additional misconception that accessibility is just about the extreme case of blind users with screenreaders, rather than the whole spectrum of different users, needs, assistive technologies, etc) or - we are getting such an insignificant number of screenreader users BECAUSE our site is so awful in terms of accessibility, so we really need to improve it. As for checking which users have trouble with certain pages, no stats package will help I think. Best you can do is make a very prominent help/contact link on all your pages and allow for users to send feedback directly. P *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
[WSG] RE: Tools or analytics to detect assistive devices
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of McLaughlin, Gail Sent: 19 November 2008 16:50 > I'm wondering if anybody here knows of a way to use analytics data > to help determine a good guess or idea of which users are using > screen readers to access data, or having trouble with certain > pages (thus making the case for doing usability and accessibility > exercises)? As screenreaders work within existing browsers (normally IE) it's very hard to detect them. To detect different browsers you'd use the user agent string, but screenreaders don't have user agent strings of their own. At least that's as far as I (and a few other people [1]) am aware. Maybe one of the accessibility gurus on the list has a magic method to detect of a visitor is using a screenreader? Chris [1] http://www.accessifyforum.com/viewtopic.php?t=3775 This message has been scanned for malware by SurfControl plc. www.surfcontrol.com *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***