1. I'm totally blind (I've been that way since birth). 2. I've been working with Music Software accessible to blind students since I started college back in 2003. 3. I'm presently a college student. -----Original Message----- From: jawsscripts-bounce@xxxxxxxxxxxxx [mailto:jawsscripts-bounce@xxxxxxxxxxxxx] On Behalf Of Geoff Chapman Sent: Tuesday, April 10, 2012 4:40 PM To: jawsscripts@xxxxxxxxxxxxx Subject: [jawsscripts] Re: Urgent! Accessibility For Sibelius Sound Set Editor? Fair enough Annabell. Sound set edotir, not sound skulpting editor tool per Se. Ok I got that. So do you have any further comments re the rest of my response? Thanks much. G. ----- Original Message ----- From: "Geoff Chapman" <gch@xxxxxxxxxxxxxxxx> To: <jawsscripts@xxxxxxxxxxxxx> Sent: Tuesday, April 10, 2012 10:59 PM Subject: [jawsscripts] Re: Urgent! Accessibility For Sibelius Sound Set Editor? > HI Annabelle. > > Since as you've no doubt observed, noone has as yet responded to your > queeries for assistance/information re your sibelius sound editor > accessibility issues, > Although i have no personal knowledge at all of the particular > software/sound editor component in question, I did used to mess with > music > editing Software myself, and can only tell you that you may be up for a > potentially disappointing time, re your understandable desire for complete > blind-friendly access to this type of software. > > May I ask you first, how Long you've been working with Jaws/music creation > software yourself? And what education level student are you at present? > Also, Are you yourself blind/vision impaired? > > Firstly I'll warn up front, that the below may not at all be something > you'll be ready/wanting to hear. and I am sorry about this, and wish to > prepare you before I convey. > > but, As you may know, Many appplications these days, are simply not > developed with the blind/screen-reader access user in mind at all. And > hense utilization of standard keyboard accessible/opperable controls, as > you list below, is commonly not taken into consideration during > development > of many applications, most particularly in this kind of sound-editing > environment.. > Would that be a fair call to say You think Jackie? > > I well remember when I was really into this kind of thing myself, how > really > emotionally irritating, and difficult, this was to hear. > > I felt blocked off from being able to fully express my stuff with what I > wanted to do with music software, and many of us have felt this pain too. > Not that this makes it any easier for you I know. > Particularly If this is the first time you've struck these types of > accessibility barriers . > > To make a non-standardized application,fully keyboard navigable, and > editable, is thus notin any way, a simple process, even if it be a dooable > one at all! And even this is not certain. a Great deal depends on simply > a > verritable host of factors, particularly related to > how the developer has implemented/utilized her/his development > environment, > and the subsequent user-interface, (UI,) control of the application. > > I.e. much of it can often be very graphical/object oriented in nature, > designed to be operated/nomipulated with the mouse only. > > This is not to say necessarily exclusively, but very often primarily. > > Have you been in touch with the Sibelius developers at all? > There was a company called Dancing Dots, who used to produce JAWS scripts > for sibelius access, but I've no idea whether they're still involved in > doing that now, or what version jaws support has kept pace with. > > But, they're probably your best bet to be contacting first, regarding your > issues, and to what level of developer contact they either have or may've > had, to begin working on just how far you might expect to be able to go > with > this. > > their website HOmepage Address is: > http://www.dancingdots.com > > And the part which I've just discovered talks about discontinuation of > sibelius support, is: > http://www.dancingdots.com/prodesc/SibSpeaking.htm > > They do talk about another product line though on that site which you may > wish to check out. > > David Pinto who used to be the mainstream developer of that product, is a > member of this list though, and perhaps he could tell you a little more > about why that product needed to be discontinued, and/or what direction > the > app might've taken since then? > > I hope this helps a little annabell. > > Geoff c. > > > > ----- Original Message ----- > From: "Annabelle Susan Morison" <foristnights@xxxxxxxxxxx> > To: <jawsscripts@xxxxxxxxxxxxx> > Sent: Thursday, April 05, 2012 3:30 PM > Subject: [jawsscripts] Urgent! Accessibility For Sibelius Sound Set > Editor? > > >> Content-Type: text/plain; >> charset="us-ascii" >> Content-Transfer-Encoding: 7bit >> Hi, it's Annabelle. >> I use JAWS 10.0 with a bunch of applications, and I have run into a >> serious >> situation. I am having a lot of trouble accessing the Sibelius Sound Set >> Editor with Adobe Air. Is there a way to make the Sound Set Editor >> accessible to blind customers like me? In other words, make it accessible >> with a menu bar, text-based buttons and controls, and >> screenreader-friendly >> options? Here is a list of controls that I've heard are recognized by >> JAWS. >> Note that these controls have to have text-based icons that go with them, >> since JAWS does not read and recognize icons with bitmap images. >> 1. 3-State Button >> 2. Button >> 3. Button Menu >> 4. Checkbox >> 5. Combo Box >> 6. Dialogue >> 7. Edit >> 8. Edit Combo >> 9. Extended Select List Box >> 10. Graphic >> 11. Group Box >> 12. Header Bar >> 13. Hot Key >> 14. Left-Right Slider >> 15. List Box >> 16. List View >> 17. MS Active Accessibility >> 18. Multiline Edit >> 19. Multi Select List Box >> 20. Password Edit >> 21. Radio Button >> 22. Read Only Edit >> 23. SpinBox >> 24. Static >> 25. Status Bar >> 26. Tab Control >> 27. Toolbar >> 28. Tool Tip >> 29. Tree View >> 30. Up-Down Slider >> If any of you fellow JAWS scripting members have any further information, >> questions, or suggestions for me, please feel free to Email me at any >> time, >> as I check my Emails several times each day. >> Kind Regards, >> Annabelle >> foristnights@xxxxxxxxxxx >> _____ >> >> No virus found in this message. >> Checked by AVG - www.avg.com >> Version: 2012.0.1873 / Virus Database: 2102/4649 - Release Date: 11/30/11 >> >> _____ >> >> No virus found in this message. >> Checked by AVG - www.avg.com >> Version: 2012.0.1913 / Virus Database: 2114/4909 - Release Date: 04/01/12 >> >> _____ >> >> No virus found in this message. >> Checked by AVG - www.avg.com >> Version: 2012.0.1913 / Virus Database: 2114/4910 - Release Date: 04/02/12 >> >> _____ >> >> No virus found in this message. >> Checked by AVG - www.avg.com >> Version: 2012.0.1913 / Virus Database: 2114/4910 - Release Date: 04/02/12 >> >> _____ >> >> No virus found in this message. >> Checked by AVG - www.avg.com >> Version: 2012.0.1913 / Virus Database: 2114/4910 - Release Date: 04/02/12 >> >> _____ >> >> No virus found in this message. >> Checked by AVG - www.avg.com >> Version: 2012.0.1913 / Virus Database: 2114/4912 - Release Date: 04/03/12 >> >> _____ >> >> No virus found in this message. >> Checked by AVG - www.avg.com >> Version: 2012.0.1913 / Virus Database: 2409/4915 - Release Date: 04/04/12 >> >> >> >> >> __________� >> >> View the list's information and change your settings at >> //www.freelists.org/list/jawsscripts >> >> > > __________� > > View the list's information and change your settings at > //www.freelists.org/list/jawsscripts > __________� View the list's information and change your settings at //www.freelists.org/list/jawsscripts ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.1913 / Virus Database: 2411/4926 - Release Date: 04/10/12 ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.1913 / Virus Database: 2411/4927 - Release Date: 04/10/12 __________� View the list's information and change your settings at //www.freelists.org/list/jawsscripts