Closed Bug 275878 Opened 20 years ago Closed 19 years ago

Jaws sofware from Freedom Scientific doesn't speaks menus and links

Categories

(Core :: Disability Access APIs, defect)

1.7 Branch
x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: dilsiam, Assigned: aaronlev)

Details

(Keywords: access)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041217
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041217




   When using Jaws from Freedom Scientific, Jaws doesn't speaks the links, menus
and buttons in browser and other components of Mozilla

Reproducible: Always

Steps to Reproduce:
1.Open the browser Mozilla

2.Jaws tell me its open

3.Jaws speaks almost everything 

Actual Results:  


Jaws did not speak menus and links

Expected Results:  



Jaws should speak the links, menus and buttons
Assignee: jag → aaronleventhal
Component: XP Apps → Disability Access APIs
Product: Mozilla Application Suite → Core
QA Contact: pawyskoczka → core.accessibility-apis
Version: unspecified → 1.7 Branch
What version of JAWS?

By the way, please contact Freedom Scientific and ask them to support the
Mozilla products you're interested. They keep track of how many users ask for
support of a given product, and work is required on their end for Mozilla support.
Keywords: access
Also, do you mind trying with a more recent version, like Mozilla 1.8a5?
  Thank you guys, I'll do that what you say I'll contact Freedom. I recently
went to the Official downloads page and  didn't find the version 1.8a5, the
version featured is 1.7.5. Where do I find 1.8a5?.

Thanks
Dilsia
    One additional suggestion, it would help if you put the newest build first
on the downloads page; build 1.7 is first in the long row of downloads. I've
installed build 1.8a5

Thanks
Dilsia
We don't put that on the downloads page because it's an alpha, testing version.
We don't want the general public to be downloading it unless the'yre interested
in helping us fix problems. Since you reported a bug in Bugzilla, I assumed you
fall into that category of helpers.

Here's the latest alpha release, 1.8a5:
http://ftp.mozilla.org/pub/mozilla.org/mozilla/releases/mozilla1.8a5/

By the way, we are working much better right now with the Window-Eyes 5 beta.
They've put a little work into it. You could try that for now, until we have
JAWS support.
  Hi guys:


     I'm a newbie helper, please forgive me if I make a blooper, the comment I
did about the downloads page came because I was told : Do you care to download
1.8a5? 

      Now I understand I was in the right path downloading 1.7.5 since that was
the Official release of Mozilla suite.Now a question if I download an Official
release and find a bug the correct step is to report it isn't it? 

  Thank you for your thorough work with Windows Eyes beta and the Windows Eyes
staff.

Happy Holidays

Dilsia
If you find a bug in Mozilla 1.7.5 or even Firefox 1.0 it might no longer be
relevant. The bug may have already been fixed by now, because the current alpha
builds have evolved beyond those 'stable' versions that are made available for
mass-consumption. Therefore, to be really helpful you need to also install a
recent alpha build, also known as the trunk build or developer's build. It is
safe to install these bleeding edge builds in a separate directory from your
stable 1.7.5. The testing and bug fixing we do occur on the most recent builds,
which are what most future products will be made from. It is your choice if you
wish to go that far to help.
Ahhhhh I see, I see yes I would like to go that far. I'm in; now I have 1.8a5 to
test. I'll use it regularly to see how it behaves. Thanks a lot guys.

    Let's see what the Freedom guys say to my request.

Best wishes
Dilsia
newbie in Mozilla
Thanks Dilsia, and welcome to the project. It's a lot of work, but it's fun.
- Aaron
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
JAWS 7 speaks menus in Firefox 1.5.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
If a new version of "Jaws" fixed this, then no code was actually checked into
Mozilla, so it can't, itself, have been broken or fixed.  (And this should
actually have been a Tech Evangelism bug.  However.)

-> WORKSFORME
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago19 years ago
Resolution: --- → WORKSFORME
(In reply to comment #12)
> If a new version of "Jaws" fixed this, then no code was actually checked into
> Mozilla, so it can't, itself, have been broken or fixed.  (And this should
> actually have been a Tech Evangelism bug.  However.)
> 
> -> WORKSFORME

I just spent since late 2004 putting the MSAA support into Mozilla so JAWS could
work in it. So, this should be marked FIXED. Whatever, doesn't really matter.
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago19 years ago
Resolution: --- → FIXED
> I just spent since late 2004 putting the MSAA support into Mozilla

Fair enough, my mistake.  (Although no mention of that was made in the comments
of this bug or its resolution. :)

If you could reference the bug responsible for checking in that code that would
be great.
You need to log in before you can comment on or make changes to this bug.