Date   

Re: Clockin on an On Mouse Over Link

Brian's Mail list account <bglists@...>
 

Yes but its all to easy to move the mouse pointer and the bit of the screen which changed changes back. This idea on pages has always been an issue as has the various direction sweeps with mice like onmouse up etc. In my view page authors should always provide an alternative to these controls as most of us want to be able to use pages without having to read manuals on screenreaders or try to work around purely visual systems like this. I seem to recall one page which wehen used with a screenreader said that the hover controls were being replaced by a set of links that opened the various items in a new window or tab. This seems sensible. I have no idea how one detetects in a page if a screenreader is being used though.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Gene" <gsasner@ripco.com>
To: <nvda@nvda.groups.io>
Sent: Tuesday, January 03, 2017 6:00 PM
Subject: Re: [nvda] Clockin on an On Mouse Over Link


You don't click an item if it has a mouse over feature if you want to use that feature. Clicking a mouse over link follows the link as in any other link. Mouse over is a function where you hover a mouse over a link and the page changes in some way. The change may not benefit blind users, such as the color might change in some way. But at times, something occurs that is of use, such as a menu opening somewhere on the page or something else occurring.

It's possible that moving to the link in the usual way in browse mode, then moving the mouse to the browse cursor, then looking around the page with the browse cursor would show something new.
But this is hardly a good or reasonable way to proceed because you don't know if something has changed nor where on the page it is. JAWS announces the line on which a change occurred if it did and if it can be localized in that way. You can then use the jump to line feature in JAWS to jump to that line, such as line 10.

Gene
----- Original Message -----

From: Andre Fisher
Sent: Tuesday, January 03, 2017 11:36 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Clockin on an On Mouse Over Link


Have you tried routing the mouse to the item? NVDA should certainly
announce this item as clickable, so you should be able to move the
mouse to it and click it, then review the page to see what has
changed.

On 1/3/17, Brian's Mail list account <bglists@blueyonder.co.uk> wrote:
ah and it only used to work on some pages with this silly function as well
unless they fixed it. Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Andre Fisher" <andrefisher729@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Tuesday, January 03, 2017 4:06 PM
Subject: Re: [nvda] Clockin on an On Mouse Over Link


That is a JAWS specific feature I'm afraid.

On 1/3/17, kelby carlson <kelbycarlson@gmail.com> wrote:
With JAWS, if there was a link you needed to hover the mouse over to
open up a submenu you'd use insert+ctrl+enter. I've tried that with
NVDA though and that doesn't seem to work. Am I doing something wrong?








Re: sapi 4 voices and windows 10

Brian's Mail list account <bglists@...>
 

I've certainly had them working vey well on 10. One of the bigger issues is that a 16bitt sappi 5 voice from scansoft called Emily seems not to work wheras the 32 bit ones danial and Serena do. Might just be badly installed. I'm not sure.
The voice installer came from an old copy of Dolphin software so may well have been updated by now.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "nasrin khaksar" <nasrinkhaksar3@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Wednesday, January 04, 2017 8:02 AM
Subject: Re: [nvda] sapi 4 voices and windows 10


yes.
there is no different between windows ten and previous versions in
this regard as i read in the previous posts in this list.

On 1/4/17, Rosemarie Chavarria <knitqueen2007@gmail.com> wrote:
Hi, everyone,

Does sapi 4 work with windows 10 or not now? Just wondering.

Rosemarie

--
we have not sent you but as a mercy to the creation.
holy quran, chapter 21, verse 107.
in the very authentic narration is:
imam hosein is the beacon of light and the ark of salvation.
best website for studying islamic book in different languages
al-islam.org


Re: sapi 4 voices and windows 10

 

yes.
there is no different between windows ten and previous versions in
this regard as i read in the previous posts in this list.

On 1/4/17, Rosemarie Chavarria <knitqueen2007@gmail.com> wrote:
Hi, everyone,

Does sapi 4 work with windows 10 or not now? Just wondering.

Rosemarie
--
we have not sent you but as a mercy to the creation.
holy quran, chapter 21, verse 107.
in the very authentic narration is:
imam hosein is the beacon of light and the ark of salvation.
best website for studying islamic book in different languages
al-islam.org


Re: LibreOffice Writer Annoyances - The beginning

 

i only want free and specially opensource program.
if i can open my word documents and convert them in to html or txt, is
enough for me.
i dont wordpad, because i have some problem using with nvda and i cant
use ancy because my language is persian and i need unicode!

On 1/4/17, Shaun Everiss <sm.everiss@gmail.com> wrote:
Well you could always save in ansi.
Unicode is only a major issue if you want or are needing to be writing a
multilanguage thing or be working with people with different language oses.
Short description though old the old ansi system can probably still work
if you don't need extra stuff.
I am not sure where this stuff is but back at uni I had to work with
unix code and files as well as standard text files, I used 2 command
line programs, unix to dos and dos to unix it allowed me to convert
standard text files to unix files and back again.
It may not help you in this case but still.
La tx is the industry standard but I have never tried it at all.



On 4/01/2017 12:03 p.m., Gene wrote:
I did a Google search and I found one or two free programs that do and I
found at least one shareware and one or more programs for purchase. I
have no idea if any are accessible.

You may have to use more than one program, for example, one program for
reading documents with read to end and another such as what you are using
now for editing.
The site is:
http://www.alanwood.net/unicode/utilities_editors.html

Gene
----- Original Message -----

From: Rosemarie Chavarria
Sent: Tuesday, January 03, 2017 4:28 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] LibreOffice Writer Annoyances - The beginning


I don't know of any word processing programs that support unicode.



-----Original Message-----
From: nasrin khaksar
Sent: Tuesday, January 3, 2017 1:16 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] LibreOffice Writer Annoyances - The beginning

i only need word processor which is accessible, opensource and
supports unicode UTF8.
could you please help me in this regard?
jarte does not support unicode unfortunately.

On 1/3/17, Shaun Everiss <sm.everiss@gmail.com> wrote:
I agree, my dad has the home use program for office which is why we have
it.
But now he is retired so we technically don't.
office pro is 600 bucks, home business is 300 and home users for the
basics is still 150 dollars or so.
You could take a 360 subscription.
But to be honest, my jarte for 35 bucks handles word documents for the
most part.
I don't need excell I have thunderbird in almost default mode.
I still have to handle with all the issues office has, and to be honest
I am itching to just clear office from the systems, reformat so all the
ms office junk is removed for ever and install something opensource.
I don't need office apps in my line of work which is web and email, I
can't remember when I processed a document.



On 3/01/2017 4:35 p.m., nasrin khaksar wrote:
hello walmir.
i completely agree with you.
when someone selects his her screen reader opensource, for sure should
select the office program opensource too!
and for me for example: wish that have all my programs opensource!
i believe the idea of opensource, have faith itn it and completely
admire
it.

On 1/3/17, nasrin khaksar <nasrinkhaksar3@gmail.com> wrote:
hello evry one.
carlos is it possible to microsoft gives there code to nvda developers
to make it better accessible with nvda?
i did not know this.
if its so, how it is possible because microsoft office is a commercial
product not opensource!

On 1/3/17, Quentin Christensen <quentin@nvaccess.org> wrote:
Ideally, we would love to be able to support every piece of software
possible. Indeed, as noted, there is a strong argument for
supporting
accessibility in other open source projects. The main issue from NV
Access' point of view really is our own limited resources.
Therefore,
we
need to prioritise the work we can do to try and have the most
positive
effect on the largest number of users. We are certainly not unaware
that
NVDA's capabilities in Libre Office and Open Office are not where
anyone
would like them to be at.

What I would say in order to facilitate work on Libre or Open Office,
would
be to file issues on GitHub https://github.com/nvaccess/nvda/issues
and
include as much useful detail as possible. If anyone has any
contacts
within the Libre or Open Office developers who would be interested in
starting a dialogue on improving accessibility (there are, of course,
things that can be done from both sides to provide a more accessible
experience for users), do feel free to get them in touch with us as
well.

Kind regards

Quentin.

On Tue, Jan 3, 2017 at 7:03 AM, Travis Siegel <tsiegel@softcon.com>
wrote:

The below statement makes no sense. Librioffice code is already
available
for anyone to inspect, NVDA developers included. Saying that
librioffice
needs to give their code to NVDA developers if they want it to be
more
compatible is a spurious argument. It's opensource, that means
anybody
can
inspect the code at any time, it has nothing to do with giving
anybody
anything. I have no idea if ms actually gave code to office to nvda
developers, but I'd tend to doubt it. It seems to me, that you have
things
backwards in this scenario.


I'm not addressing the business/home usage case, only the source
code
availability argument.



On 1/2/2017 2:04 PM, Carlos wrote:

If Libre Office wants to be compatible with NVDA they should give
NVDA
developers their code to inspect and study. MS Office has done so
for
NVDA
developers and it has made it possible for NVDA to work very well
with
MS
Office!





--
Quentin Christensen
Training Material Developer
Basic Training for NVDA & Microsoft Word with NVDA E-Books now
available:
http://www.nvaccess.org/shop/

Ph +61 7 3149 3306
www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess

--
we have not sent you but as a mercy to the creation.
holy quran, chapter 21, verse 107.
in the very authentic narration is:
imam hosein is the beacon of light and the ark of salvation.
best website for studying islamic book in different languages
al-islam.org




--
we have not sent you but as a mercy to the creation.
holy quran, chapter 21, verse 107.
in the very authentic narration is:
imam hosein is the beacon of light and the ark of salvation.
best website for studying islamic book in different languages
al-islam.org


Re: LibreOffice Writer Annoyances - The beginning

 

Well you could always save in ansi.
Unicode is only a major issue if you want or are needing to be writing a multilanguage thing or be working with people with different language oses.
Short description though old the old ansi system can probably still work if you don't need extra stuff.
I am not sure where this stuff is but back at uni I had to work with unix code and files as well as standard text files, I used 2 command line programs, unix to dos and dos to unix it allowed me to convert standard text files to unix files and back again.
It may not help you in this case but still.
La tx is the industry standard but I have never tried it at all.

On 4/01/2017 12:03 p.m., Gene wrote:
I did a Google search and I found one or two free programs that do and I found at least one shareware and one or more programs for purchase. I have no idea if any are accessible.

You may have to use more than one program, for example, one program for reading documents with read to end and another such as what you are using now for editing.
The site is:
http://www.alanwood.net/unicode/utilities_editors.html

Gene
----- Original Message -----

From: Rosemarie Chavarria
Sent: Tuesday, January 03, 2017 4:28 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] LibreOffice Writer Annoyances - The beginning


I don't know of any word processing programs that support unicode.



-----Original Message-----
From: nasrin khaksar
Sent: Tuesday, January 3, 2017 1:16 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] LibreOffice Writer Annoyances - The beginning

i only need word processor which is accessible, opensource and
supports unicode UTF8.
could you please help me in this regard?
jarte does not support unicode unfortunately.

On 1/3/17, Shaun Everiss <sm.everiss@gmail.com> wrote:
I agree, my dad has the home use program for office which is why we have
it.
But now he is retired so we technically don't.
office pro is 600 bucks, home business is 300 and home users for the
basics is still 150 dollars or so.
You could take a 360 subscription.
But to be honest, my jarte for 35 bucks handles word documents for the
most part.
I don't need excell I have thunderbird in almost default mode.
I still have to handle with all the issues office has, and to be honest
I am itching to just clear office from the systems, reformat so all the
ms office junk is removed for ever and install something opensource.
I don't need office apps in my line of work which is web and email, I
can't remember when I processed a document.



On 3/01/2017 4:35 p.m., nasrin khaksar wrote:
hello walmir.
i completely agree with you.
when someone selects his her screen reader opensource, for sure should
select the office program opensource too!
and for me for example: wish that have all my programs opensource!
i believe the idea of opensource, have faith itn it and completely admire
it.

On 1/3/17, nasrin khaksar <nasrinkhaksar3@gmail.com> wrote:
hello evry one.
carlos is it possible to microsoft gives there code to nvda developers
to make it better accessible with nvda?
i did not know this.
if its so, how it is possible because microsoft office is a commercial
product not opensource!

On 1/3/17, Quentin Christensen <quentin@nvaccess.org> wrote:
Ideally, we would love to be able to support every piece of software
possible. Indeed, as noted, there is a strong argument for supporting
accessibility in other open source projects. The main issue from NV
Access' point of view really is our own limited resources. Therefore,
we
need to prioritise the work we can do to try and have the most positive
effect on the largest number of users. We are certainly not unaware
that
NVDA's capabilities in Libre Office and Open Office are not where
anyone
would like them to be at.

What I would say in order to facilitate work on Libre or Open Office,
would
be to file issues on GitHub https://github.com/nvaccess/nvda/issues and
include as much useful detail as possible. If anyone has any contacts
within the Libre or Open Office developers who would be interested in
starting a dialogue on improving accessibility (there are, of course,
things that can be done from both sides to provide a more accessible
experience for users), do feel free to get them in touch with us as
well.

Kind regards

Quentin.

On Tue, Jan 3, 2017 at 7:03 AM, Travis Siegel <tsiegel@softcon.com>
wrote:

The below statement makes no sense. Librioffice code is already
available
for anyone to inspect, NVDA developers included. Saying that
librioffice
needs to give their code to NVDA developers if they want it to be more
compatible is a spurious argument. It's opensource, that means
anybody
can
inspect the code at any time, it has nothing to do with giving anybody
anything. I have no idea if ms actually gave code to office to nvda
developers, but I'd tend to doubt it. It seems to me, that you have
things
backwards in this scenario.


I'm not addressing the business/home usage case, only the source code
availability argument.



On 1/2/2017 2:04 PM, Carlos wrote:

If Libre Office wants to be compatible with NVDA they should give
NVDA
developers their code to inspect and study. MS Office has done so
for
NVDA
developers and it has made it possible for NVDA to work very well
with
MS
Office!





--
Quentin Christensen
Training Material Developer
Basic Training for NVDA & Microsoft Word with NVDA E-Books now
available:
http://www.nvaccess.org/shop/

Ph +61 7 3149 3306
www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess

--
we have not sent you but as a mercy to the creation.
holy quran, chapter 21, verse 107.
in the very authentic narration is:
imam hosein is the beacon of light and the ark of salvation.
best website for studying islamic book in different languages
al-islam.org



Re: LibreOffice Writer Annoyances - The beginning

 

Well wordpad itself can handle unicode.
Other things you can try are edsharp but I forget where that is at right now.
There is also balabolka which is free and does work to an extent.
Depending on the windows version you may still be able to get an old version of office and it will work.
I know for example that while office 2016 and 2013 are pricy 2010 is not to bad, and 2007 which is still being maintained is still being updated security wise but can be quite cheap.
I havn't tried this but assume 2003 may still work but not lower.

On 4/01/2017 1:06 p.m., Jason White via Groups.Io wrote:
Rosemarie Chavarria <knitqueen2007@gmail.com> wrote:
I don't know of any word processing programs that support unicode.

Most do - LibreOffice, Microsoft Word, etc.

If instead what is needed is a text editor rather than a word processor, there
should be suitable options available, too.

I'm an Emacs and Vi kind of person, definitely not a word processor
enthusiast, and absolutely supportive of LaTeX, Pandoc Markdown, etc., with a
good Git repository to take care of document revisions.




Support for enhanced accessibility in Kindle 1.19

 

Hi all,

We're excited to announce that NVDA 2017.1 will support the enhanced accessibility functionality available in Amazon Kindle for PC version 1.19. This enables users to read books in browse mode, work with notes and highlighted text and much more. NVDA 2017.1 is expected to be available in late February 2017, but a beta version of NVDA with Kindle support is available for testing today. See this page for details:
http://www.nvaccess.org/kindle/
Try it out and tell us what you think!

Thanks!

Jamie


Re: LibreOffice Writer Annoyances - The beginning

Jason White
 

Rosemarie Chavarria <knitqueen2007@gmail.com> wrote:
I don't know of any word processing programs that support unicode.

Most do - LibreOffice, Microsoft Word, etc.

If instead what is needed is a text editor rather than a word processor, there
should be suitable options available, too.

I'm an Emacs and Vi kind of person, definitely not a word processor
enthusiast, and absolutely supportive of LaTeX, Pandoc Markdown, etc., with a
good Git repository to take care of document revisions.


Re: LibreOffice Writer Annoyances - The beginning

Gene
 

I did a Google search and I found one or two free programs that do and I found at least one shareware and one or more programs for purchase.  I have no idea if any are accessible. 
 
You may have to use more than one program, for example, one program for reading documents with read to end and another such as what you are using now for editing. 
The site is:
 
Gene

----- Original Message -----
Sent: Tuesday, January 03, 2017 4:28 PM
Subject: Re: [nvda] LibreOffice Writer Annoyances - The beginning

I don't know of any word processing programs that support unicode.



-----Original Message-----
From: nasrin khaksar
Sent: Tuesday, January 3, 2017 1:16 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] LibreOffice Writer Annoyances - The beginning

i only need word processor which is accessible, opensource and
supports unicode UTF8.
could you please help me in this regard?
jarte does not support unicode unfortunately.

On 1/3/17, Shaun Everiss <sm.everiss@...> wrote:
> I agree, my dad has the home use program for office which is why we have
> it.
> But now he is retired so we technically don't.
> office pro is 600 bucks, home business is 300 and home users for the
> basics is still 150 dollars or so.
> You could take a 360 subscription.
> But to be honest, my jarte for 35 bucks handles word documents for the
> most part.
> I don't need excell I have thunderbird in almost default mode.
> I still have to handle with all the issues office has, and to be honest
> I am itching to just clear office from the systems, reformat so all the
> ms office junk is removed for ever and install something opensource.
> I don't need office apps in my line of work which is web and email, I
> can't remember when I processed a document.
>
>
>
> On 3/01/2017 4:35 p.m., nasrin khaksar wrote:
>> hello walmir.
>> i completely agree with you.
>> when someone selects his her screen reader opensource, for sure should
>> select the office program opensource too!
>> and for me for example: wish that have all my programs opensource!
>> i believe the idea of opensource, have faith itn it and completely admire
>> it.
>>
>> On 1/3/17, nasrin khaksar <nasrinkhaksar3@...> wrote:
>>> hello evry one.
>>> carlos is it possible to microsoft gives there code to nvda developers
>>> to make it better accessible with nvda?
>>> i did not know this.
>>> if its so, how it is possible because microsoft office is a commercial
>>> product not opensource!
>>>
>>> On 1/3/17, Quentin Christensen <quentin@...> wrote:
>>>> Ideally, we would love to be able to support every piece of software
>>>> possible.  Indeed, as noted, there is a strong argument for supporting
>>>> accessibility in other open source projects.  The main issue from NV
>>>> Access' point of view really is our own limited resources.  Therefore,
>>>> we
>>>> need to prioritise the work we can do to try and have the most positive
>>>> effect on the largest number of users.  We are certainly not unaware
>>>> that
>>>> NVDA's capabilities in Libre Office and Open Office are not where
>>>> anyone
>>>> would like them to be at.
>>>>
>>>> What I would say in order to facilitate work on Libre or Open Office,
>>>> would
>>>> be to file issues on GitHub https://github.com/nvaccess/nvda/issues and
>>>> include as much useful detail as possible.  If anyone has any contacts
>>>> within the Libre or Open Office developers who would be interested in
>>>> starting a dialogue on improving accessibility (there are, of course,
>>>> things that can be done from both sides to provide a more accessible
>>>> experience for users), do feel free to get them in touch with us as
>>>> well.
>>>>
>>>> Kind regards
>>>>
>>>> Quentin.
>>>>
>>>> On Tue, Jan 3, 2017 at 7:03 AM, Travis Siegel <tsiegel@...>
>>>> wrote:
>>>>
>>>>> The below statement makes no sense.  Librioffice code is already
>>>>> available
>>>>> for anyone to inspect, NVDA developers included.  Saying that
>>>>> librioffice
>>>>> needs to give their code to NVDA developers if they want it to be more
>>>>> compatible is a spurious argument.  It's opensource, that means
>>>>> anybody
>>>>> can
>>>>> inspect the code at any time, it has nothing to do with giving anybody
>>>>> anything.  I have no idea if ms actually gave code to office to nvda
>>>>> developers, but I'd tend to doubt it.  It seems to me, that you have
>>>>> things
>>>>> backwards in this scenario.
>>>>>
>>>>>
>>>>> I'm not addressing the business/home usage case, only the source code
>>>>> availability argument.
>>>>>
>>>>>
>>>>>
>>>>> On 1/2/2017 2:04 PM, Carlos wrote:
>>>>>
>>>>>> If Libre Office wants to be compatible with NVDA they should give
>>>>>> NVDA
>>>>>> developers their code to inspect and study.  MS Office has done so
>>>>>> for
>>>>>> NVDA
>>>>>> developers and it has made it possible for NVDA to work very well
>>>>>> with
>>>>>> MS
>>>>>> Office!
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Quentin Christensen
>>>> Training Material Developer
>>>> Basic Training for NVDA & Microsoft Word with NVDA E-Books now
>>>> available:
>>>> http://www.nvaccess.org/shop/
>>>>
>>>> Ph +61 7 3149 3306
>>>> www.nvaccess.org
>>>> Facebook: http://www.facebook.com/NVAccess
>>>> Twitter: @NVAccess
>>>>
>>>
>>>
>>> --
>>> we have not sent you but as a mercy to the creation.
>>> holy quran, chapter 21, verse 107.
>>> in the very authentic narration is:
>>> imam hosein is the beacon of light and the ark of salvation.
>>> best website for studying islamic book in different languages
>>> al-islam.org
>>>
>>
>>
>
>
>
>


--
we have not sent you but as a mercy to the creation.
holy quran, chapter 21, verse 107.
in the very authentic narration is:
imam hosein is the beacon of light and the ark of salvation.
best website for studying islamic book in different languages
al-islam.org






Re: LibreOffice Writer Annoyances - The beginning

Rosemarie Chavarria
 

I don't know of any word processing programs that support unicode.

-----Original Message-----
From: nasrin khaksar
Sent: Tuesday, January 3, 2017 1:16 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] LibreOffice Writer Annoyances - The beginning

i only need word processor which is accessible, opensource and
supports unicode UTF8.
could you please help me in this regard?
jarte does not support unicode unfortunately.

On 1/3/17, Shaun Everiss <sm.everiss@gmail.com> wrote:
I agree, my dad has the home use program for office which is why we have
it.
But now he is retired so we technically don't.
office pro is 600 bucks, home business is 300 and home users for the
basics is still 150 dollars or so.
You could take a 360 subscription.
But to be honest, my jarte for 35 bucks handles word documents for the
most part.
I don't need excell I have thunderbird in almost default mode.
I still have to handle with all the issues office has, and to be honest
I am itching to just clear office from the systems, reformat so all the
ms office junk is removed for ever and install something opensource.
I don't need office apps in my line of work which is web and email, I
can't remember when I processed a document.



On 3/01/2017 4:35 p.m., nasrin khaksar wrote:
hello walmir.
i completely agree with you.
when someone selects his her screen reader opensource, for sure should
select the office program opensource too!
and for me for example: wish that have all my programs opensource!
i believe the idea of opensource, have faith itn it and completely admire
it.

On 1/3/17, nasrin khaksar <nasrinkhaksar3@gmail.com> wrote:
hello evry one.
carlos is it possible to microsoft gives there code to nvda developers
to make it better accessible with nvda?
i did not know this.
if its so, how it is possible because microsoft office is a commercial
product not opensource!

On 1/3/17, Quentin Christensen <quentin@nvaccess.org> wrote:
Ideally, we would love to be able to support every piece of software
possible. Indeed, as noted, there is a strong argument for supporting
accessibility in other open source projects. The main issue from NV
Access' point of view really is our own limited resources. Therefore,
we
need to prioritise the work we can do to try and have the most positive
effect on the largest number of users. We are certainly not unaware
that
NVDA's capabilities in Libre Office and Open Office are not where
anyone
would like them to be at.

What I would say in order to facilitate work on Libre or Open Office,
would
be to file issues on GitHub https://github.com/nvaccess/nvda/issues and
include as much useful detail as possible. If anyone has any contacts
within the Libre or Open Office developers who would be interested in
starting a dialogue on improving accessibility (there are, of course,
things that can be done from both sides to provide a more accessible
experience for users), do feel free to get them in touch with us as
well.

Kind regards

Quentin.

On Tue, Jan 3, 2017 at 7:03 AM, Travis Siegel <tsiegel@softcon.com>
wrote:

The below statement makes no sense. Librioffice code is already
available
for anyone to inspect, NVDA developers included. Saying that
librioffice
needs to give their code to NVDA developers if they want it to be more
compatible is a spurious argument. It's opensource, that means
anybody
can
inspect the code at any time, it has nothing to do with giving anybody
anything. I have no idea if ms actually gave code to office to nvda
developers, but I'd tend to doubt it. It seems to me, that you have
things
backwards in this scenario.


I'm not addressing the business/home usage case, only the source code
availability argument.



On 1/2/2017 2:04 PM, Carlos wrote:

If Libre Office wants to be compatible with NVDA they should give
NVDA
developers their code to inspect and study. MS Office has done so
for
NVDA
developers and it has made it possible for NVDA to work very well
with
MS
Office!





--
Quentin Christensen
Training Material Developer
Basic Training for NVDA & Microsoft Word with NVDA E-Books now
available:
http://www.nvaccess.org/shop/

Ph +61 7 3149 3306
www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess

--
we have not sent you but as a mercy to the creation.
holy quran, chapter 21, verse 107.
in the very authentic narration is:
imam hosein is the beacon of light and the ark of salvation.
best website for studying islamic book in different languages
al-islam.org



--
we have not sent you but as a mercy to the creation.
holy quran, chapter 21, verse 107.
in the very authentic narration is:
imam hosein is the beacon of light and the ark of salvation.
best website for studying islamic book in different languages
al-islam.org


sapi 4 voices and windows 10

Rosemarie Chavarria
 

Hi, everyone,
 
Does sapi 4 work with windows 10 or not now? Just wondering.
 
Rosemarie


Re: NVDA remote git hub

 

Hi,
I have zero information on that, sorry.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Paulius
Sent: Tuesday, January 3, 2017 10:29 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA remote git hub

Hello.
Do you know when it'll be ready to come in the next release?
Thanks.

Sincerely,
Paulius Leveris

2017-01-03 20:12 GMT+02:00, Joseph Lee <joseph.lee22590@gmail.com>:
Hi,

I suggest asking Chris Toth and Tyler Spivey for official quotes, as
they are the chief maintainers.

Cheers,

Joseph



From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of
Robert Kingett
Sent: Tuesday, January 3, 2017 10:13 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA remote git hub



Can I quote you?



On 1/3/2017 11:59 AM, Joseph Lee wrote:

Hi all,
I can tell you that, soon, you'll be hearing reasons why NVDA Remote
opens up possibilities (or will open up possibilities). One hint I can
give you
now: one particular feature will benefit those using braille. Stay
tuned for news on the next generation NVDA Remote version.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
[mailto:nvda@nvda.groups.io] On Behalf Of Robert Kingett
Sent: Tuesday, January 3, 2017 9:50 AM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: [nvda] NVDA remote git hub

I am not sure if anyone knew but below is the NVDA remote page on git hub.
It is open source.

https://github.com/nvdaremote/nvdaremote












Re: LibreOffice Writer Annoyances - The beginning

Walmir Schultz <wsautodidata@...>
 

I agree. This point is by far the most important: the dialog between both dev teams.


Em 03/01/2017 15:21, Brian's Mail list account escreveu:

I think a lot of the issues with Libra are due to lack of events to allow screenreaders to easily do some common things, the read to end being one of the most annoying of course.
If the dev teams of the two products could get some dialogue going with screenreader folk things might improve.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Walmir Schultz via Groups.Io" <wsautodidata=yahoo.com.br@groups.io>
To: <nvda@nvda.groups.io>
Sent: Tuesday, January 03, 2017 10:15 AM
Subject: Re: [nvda] LibreOffice Writer Annoyances - The beginning


But I am using LibreOffice in my work...

After all, the question is more about the open source "spirit" than of business needs or wich office suite is more popular.



Em 02/01/2017 17:04, Carlos escreveu:
Hello:

The main purpose of NVDA is not only for personal use. It is also for use in office/work environments.

Most office/work environments use MS Office as their office software of choice. Libre Office is more popular for business use in the European union.

MS Office will always come first when it comes to the workplace! And, work/jobs will always come first when it comes to screen reader usage!

If Libre Office wants to be compatible with NVDA they should give NVDA developers their code to inspect and study. MS Office has done so for NVDA developers and it has made it possible for NVDA to work very well with MS Office!

Just because software is open source it does not mean that NVDA developers can work with the code without the blessing/permission of the software developers!

So, if you want Libre Office to work better with NVDA direct your efforts to letting Libre Office know that your screen reader of choice is NVDA and that they need to include better support for NVDA in their software!!!



On 1/2/2017 10:32 AM, Walmir Schultz via Groups.Io wrote:
But this is exactly the point.

Why an open source screen reader is being constantly enhanced to work wit a paid office suite while an open source one is being "abandoned"?



Em 02/01/2017 15:26, Andre Fisher escreveu:
This is an NVDA enhancement. The developers have not looked into this
enhancement as yet.

On 1/2/17, Walmir Schultz via Groups.Io
<wsautodidata=yahoo.com.br@groups.io> wrote:
In a trial version of MS Office I saw the the toggling between browse
and edit mode using the INSERT+SPACE works like in web pages.

In a Writer document this is not possible, even if you are using all
header styles, lists etc.

This make the navigation in large documents very difficult.











Re: LibreOffice Writer Annoyances - The beginning

Walmir Schultz <wsautodidata@...>
 

I completely agree.


Em 03/01/2017 13:08, Mallard escreveu:

When NVDA started giving priority to Firefox, IE was the "market saturating" browser.

Of course, if nobody starts taking into account alternatives, nothing will ever happen in terms of "market saturation".

If NVDA were to work a little more on alternative office suites like Open Office and/or LibreOffice, probably many more blind users would move on to those for more than one reason - last but not least the fact that they're free.


Utopia? Maybe, but I still wish this would come true one of these days.

Ciao,

Ollie





Il 03/01/2017 16:16, Brian Vogel ha scritto:

I really don't get how so many participating on this thread do not understand that on any software project there are limited human resources that can be deployed and priorities must be set.

There is absolutely no doubt that, given the choice between focusing on Microsoft Office, which has far and away the greatest market saturation worldwide, and either Libre Office (or Open Office, which is in more than a bit of trouble) or other office suite, the choice is obvious: You work where the most good for the most people will result first.

It would be ridiculous to prioritize any office suite above Microsoft Office. That doesn't mean that no attention should be paid, either, but "first things first" puts MS-Office first, period. The same applies to web browsers. No one is continuing to focus intensively on Internet Explorer but priorities have shifted to Firefox and Chrome because of market saturation, with Edge coming in third, but being in the mix, because it's to be Microsoft's eventual replacement for IE. Whether the market accepts Edge or not remains a very open question and IE is now stable and will get only security updates, and for how long that will continue no one really knows.
--
*/Brian/*

*/Life is the art of drawing sufficient conclusions from /**/insufficient premises./*

*/~ Samuel Butler, /1835-1902*




Re: LibreOffice Writer Annoyances - The beginning

Walmir Schultz <wsautodidata@...>
 

I also agree with the list and will not post more "annoyances", since NVDA developers now have plenty of information.

I only feel sad some people came here and said they had no issues using LibreOffice and NVDA. I cannot understand that.




Em 03/01/2017 12:10, nasrin khaksar escreveu:

hi.
thanks so much for your list.
i completely agree with them.
and i should add two issues to your list.
7- nvda does not support tables.
and 8- the persian and arabic diacritics is not supported using nvda
with left and right arrow keys.

On 1/3/17, Jorge Gonçalves <joport3@gmail.com> wrote:
Hi everyone,


Just to be clear I decided to list my problems using Nvda and
Librioffice. They forced me to use MS Office because I am writing my
master thesis this year.

But I like Librioffice and I think it's a software with a great
potencial, if issues will be solved with Nvda. Please note that I only
tried Writer because it's the one I need.

So there we go:


1. Nvda doesn't read the whole document with the say All Command
Nvda+Down Arrow;


2. Nvda most of the time doesn't detect the spelling errors;


3. Nvda doesn't read the foot notes;


4. It is impossible to use browse mode with Nvda so it's very hard to
navigate in long documents.


5. Very often, the program freezes and the only solution is to restart
Nvda.

6. Very often the program answers extremely slow. Unnormally slow. Most
of the programs work fine but here Librioffice, I don't know sometimes
gets tired and it's a pain to work with it.

Those are the ones I can remember for the moment.
Cheers,
Jorge


Às 12:46 de 03/01/2017,5. Very often it freezes and the only solution is
to restart Nvda.

nasrin khaksar escreveu:
walmir,
i agree with you.
please tell the developers to solve these issues and change there
priorities.

On 1/3/17, Walmir Schultz via Groups.Io
<wsautodidata=yahoo.com.br@groups.io> wrote:
To ask the users of two open source software to contact both developer
teans in order to get better compatibility between both applications is
weird.

I think the direct contact of the two programs developers is more
productive and logic.



Em 02/01/2017 22:22, Quentin Christensen escreveu:
Ideally, we would love to be able to support every piece of software
possible. Indeed, as noted, there is a strong argument for supporting
accessibility in other open source projects. The main issue from NV
Access' point of view really is our own limited resources. Therefore,
we need to prioritise the work we can do to try and have the most
positive effect on the largest number of users. We are certainly not
unaware that NVDA's capabilities in Libre Office and Open Office are
not where anyone would like them to be at.

What I would say in order to facilitate work on Libre or Open Office,
would be to file issues on GitHub
https://github.com/nvaccess/nvda/issues and include as much useful
detail as possible. If anyone has any contacts within the Libre or
Open Office developers who would be interested in starting a dialogue
on improving accessibility (there are, of course, things that can be
done from both sides to provide a more accessible experience for
users), do feel free to get them in touch with us as well.

Kind regards

Quentin.

On Tue, Jan 3, 2017 at 7:03 AM, Travis Siegel <tsiegel@softcon.com
<mailto:tsiegel@softcon.com>> wrote:

The below statement makes no sense. Librioffice code is already
available for anyone to inspect, NVDA developers included. Saying
that librioffice needs to give their code to NVDA developers if
they want it to be more compatible is a spurious argument. It's
opensource, that means anybody can inspect the code at any time,
it has nothing to do with giving anybody anything. I have no idea
if ms actually gave code to office to nvda developers, but I'd
tend to doubt it. It seems to me, that you have things backwards
in this scenario.


I'm not addressing the business/home usage case, only the source
code availability argument.



On 1/2/2017 2:04 PM, Carlos wrote:

If Libre Office wants to be compatible with NVDA they should
give NVDA developers their code to inspect and study. MS
Office has done so for NVDA developers and it has made it
possible for NVDA to work very well with MS Office!









--
Quentin Christensen
Training Material Developer
Basic Training for NVDA & Microsoft Word with NVDA E-Books now
available: http://www.nvaccess.org/shop/

Ph +61 7 3149 3306 <tel:%2B61%207%203149%203306>
www.nvaccess.org <http://www.nvaccess.org/>;
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess



Re: NVDA remote git hub

 

Hello.
Do you know when it'll be ready to come in the next release?
Thanks.

Sincerely,
Paulius Leveris

2017-01-03 20:12 GMT+02:00, Joseph Lee <joseph.lee22590@gmail.com>:

Hi,

I suggest asking Chris Toth and Tyler Spivey for official quotes, as they
are the chief maintainers.

Cheers,

Joseph



From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Robert
Kingett
Sent: Tuesday, January 3, 2017 10:13 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA remote git hub



Can I quote you?



On 1/3/2017 11:59 AM, Joseph Lee wrote:

Hi all,
I can tell you that, soon, you'll be hearing reasons why NVDA Remote opens
up possibilities (or will open up possibilities). One hint I can give you
now: one particular feature will benefit those using braille. Stay tuned
for
news on the next generation NVDA Remote version.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
[mailto:nvda@nvda.groups.io] On Behalf Of Robert
Kingett
Sent: Tuesday, January 3, 2017 9:50 AM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: [nvda] NVDA remote git hub

I am not sure if anyone knew but below is the NVDA remote page on git hub.
It is open source.

https://github.com/nvdaremote/nvdaremote












Re: NVDA remote git hub

 

Hi,

I suggest asking Chris Toth and Tyler Spivey for official quotes, as they are the chief maintainers.

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Robert Kingett
Sent: Tuesday, January 3, 2017 10:13 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA remote git hub

 

Can I quote you?

 

On 1/3/2017 11:59 AM, Joseph Lee wrote:

Hi all,
I can tell you that, soon, you'll be hearing reasons why NVDA Remote opens
up possibilities (or will open up possibilities). One hint I can give you
now: one particular feature will benefit those using braille. Stay tuned for
news on the next generation NVDA Remote version.
Cheers,
Joseph
 
-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Robert
Kingett
Sent: Tuesday, January 3, 2017 9:50 AM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA remote git hub
 
I am not sure if anyone knew but below is the NVDA remote page on git hub.
It is open source.
 
https://github.com/nvdaremote/nvdaremote
 
 
 
 
 
 

 


Re: LibreOffice Writer Annoyances - The beginning

 

could you please answer one of the biggest concern about my document
and book which i mentioned in my previous message?

On 1/3/17, Mallard <mallard@kimabe.eu> wrote:
No, no... You got me wrong.

NVDA started building compatibility with Firefox when Jaws was still
drinking milk from a biberon in that respect...





Il 03/01/2017 18:21, Brian Vogel ha scritto:
On Tue, Jan 3, 2017 at 08:08 am, Mallard wrote:

When NVDA started giving priority to Firefox, IE was the "market
saturating" browser.

It wasn't just NVDA. In the early days JAWS gave virtually exclusive
attention to Internet Explorer, too, as it was:

a) King of the Mountain at that time.

b) Included in Windows.

c) There was a need to focus on doing the most good for the most people.


Things shifted as the market landscape shifted and, as a general rule,
most screen readers will be slightly behind the market because it
makes very little sense to try to predict it and, in the grand scheme
of things, all screen reader development shops have very limited
resources compared to the wide world of software development around
them. What makes it even worse, in many cases, is that the other
software companies make absolutely no effort to put information out at
a technical level about their "upcoming latest and greatest" because
they might end up being beaten to the market by someone else.

This is not a simple issue, in any way, shape, or form. No matter
what decision a given screen reader development team makes there will
be a substantial number of users who don't think it's the right one.
I understand entirely why setting a direction, and sticking to it
(barring some really major indication it was a mistake or
circumstances have changed suddenly and substantially) is the way any
software development shop is going to handle things. In the immortal
lyrics of the Rolling Stones, "You can't always get what you want, but
if you try sometimes, you just might find, you get what you need."
--
*/Brian/*

*/Life is the art of drawing sufficient conclusions from
/**/insufficient premises./*

*/~ Samuel Butler, /1835-1902*





--
we have not sent you but as a mercy to the creation.
holy quran, chapter 21, verse 107.
in the very authentic narration is:
imam hosein is the beacon of light and the ark of salvation.
best website for studying islamic book in different languages
al-islam.org


Re: NVDA remote git hub

 

Can I quote you?


On 1/3/2017 11:59 AM, Joseph Lee wrote:
Hi all,
I can tell you that, soon, you'll be hearing reasons why NVDA Remote opens
up possibilities (or will open up possibilities). One hint I can give you
now: one particular feature will benefit those using braille. Stay tuned for
news on the next generation NVDA Remote version.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Robert
Kingett
Sent: Tuesday, January 3, 2017 9:50 AM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA remote git hub

I am not sure if anyone knew but below is the NVDA remote page on git hub.
It is open source.

https://github.com/nvdaremote/nvdaremote








Re: Clockin on an On Mouse Over Link

Gene
 

You don't click an item if it has a mouse over feature if you want to use that feature.  Clicking a mouse over link follows the link as in any other link.  Mouse over is a function where you hover a mouse over a link and the page changes in some way.  The change may not benefit blind users, such as the color might change in some way.  But at times, something occurs that is of use, such as a menu opening somewhere on the page or something else occurring.
 
It's possible that moving to the link in the usual way in browse mode, then moving the mouse to the browse cursor, then looking around the page with the browse cursor would show something new. 
But this is hardly a good or reasonable way to proceed because you don't know if something has changed nor where on the page it is.  JAWS announces the line on which a change occurred if it did and if it can be localized in that way.  You can then use the jump to line feature in JAWS to jump to that line, such as line 10. 
 
Gene

----- Original Message -----
Sent: Tuesday, January 03, 2017 11:36 AM
Subject: Re: [nvda] Clockin on an On Mouse Over Link

Have you tried routing the mouse to the item? NVDA should certainly
announce this item as clickable, so you should be able to move the
mouse to it and click it, then review the page to see what has
changed.

On 1/3/17, Brian's Mail list account <bglists@...> wrote:
> ah and it only used to work on some pages with this silly function as well
> unless they fixed it. Brian
>
> bglists@...
> Sent via blueyonder.
> Please address personal email to:-
> briang1@..., putting 'Brian Gaff'
> in the display name field.
> ----- Original Message -----
> From: "Andre Fisher" <andrefisher729@...>
> To: <nvda@nvda.groups.io>
> Sent: Tuesday, January 03, 2017 4:06 PM
> Subject: Re: [nvda] Clockin on an On Mouse Over Link
>
>
>> That is a JAWS specific feature I'm afraid.
>>
>> On 1/3/17, kelby carlson <kelbycarlson@...> wrote:
>>> With JAWS, if there was a link you needed to hover the mouse over to
>>> open up a submenu you'd use insert+ctrl+enter. I've tried that with
>>> NVDA though and that doesn't seem to work. Am I doing something wrong?
>>>
>>>
>>>
>>>
>>
>>
>>
>
>
>
>
>