[Xerte] Re: Xerte online toolkits and Jaws

Ron Mitchell ronm at mitchellmedia.co.uk
Wed May 30 16:14:18 BST 2012


Alistair will be best placed to answer but I think he's busy at a conference
today and tomorrow. I'd have thought this would have cropped up previously
especially during the accessibility review during those two developer days.
Wasn't there a version problem recently where the top buttons were being
skipped and could it be that?

 

From: xerte-bounces at lists.nottingham.ac.uk
[mailto:xerte-bounces at lists.nottingham.ac.uk] On Behalf Of Julian Tenney
Sent: 30 May 2012 12:05
To: Xerte discussion list
Subject: [Xerte] Re: Xerte online toolkits and Jaws

 

Interesting: we do this in Flash to set up the screen reader stuff:

 

     this.backBtn._accProps = new Object();

     this.backBtn._accProps.name =
engine.languageData.backButton[0].description;

     Accessibility.updateProperties();

 

As far as I know JAWS should read the _accProps.name property. I'm trying to
find out if we should also set _accProps.description, but am a bit unsure
why JAWS is failing to do what a screen reader should do. If I know what to
change to make this work, it's trivial and I'll happily do the changes, just
not sure why this hasn't been flagged up before if there has always been a
problem. AFAIK, the accessibility stuff works well in screen readers?

 

Anyone from techDis able to chip in with any insight? Does this fail in all
versions of JAWS?

 

From: xerte-bounces at lists.nottingham.ac.uk
[mailto:xerte-bounces at lists.nottingham.ac.uk] On Behalf Of K.L.Baker
Sent: 30 May 2012 10:41
To: 'xerte at lists.nottingham.ac.uk'
Subject: [Xerte] Xerte online toolkits and Jaws

 

Hello

 

A colleague has been testing some learning objects that we've developed
using Xerte online toolkits with Jaws screen reading software. The results
have not been that good so far and I would like to try to improve this. A
significant issue has been that the Xerte navigation buttons at the top and
bottom (e.g. next page, previous page) don't seem to be labelled helpfully -
(e.g. Unlabeled 14 Button; 1 Button; Unlabeled 16 Button etc). Is there a
way that we can edit the source code somehow to provide accurate labels for
the buttons? I think this would improve the situation a great deal. I am not
a technical person but we do have a developer who could do this for us if
it's possible.

 

Many thanks for your advice

 

Kirsty Baker

Information Literacy Specialist

Open University Library

01908 (8) 58478

 

 

 


-- 
The Open University is incorporated by Royal Charter (RC 000391), an exempt
charity in England & Wales and a charity registered in Scotland (SC 038302).

 

This message and any attachment are intended solely for the addressee and
may contain confidential information. If you have received this message in
error, please send it back to me, and immediately delete it. Please do not
use, copy or disclose the information contained in this message or in any
attachment. Any views or opinions expressed by the author of this email do
not necessarily reflect the views of the University of Nottingham. 

This message has been checked for viruses but the contents of an attachment
may still contain software viruses which could damage your computer system:
you are advised to perform your own checks. Email communications with the
University of Nottingham may be monitored as permitted by UK legislation. 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nottingham.ac.uk/pipermail/xerte/attachments/20120530/4bc32992/attachment-0001.html>


More information about the Xerte mailing list