Indeed, all of the following are true:

1. You will not find the buttons for audio control on the https://golubovsky.bandcamp.com/album/unhuman-voices page except by using the B quick navigation shortcut
2. Hitting spacebar or enter when you have gained focus on those buttons does nothing.
3. Using NVDA+/ to route the PC mouse pointer to the NVDA navigator object, then using NumPad slash to activate it will make it play (or, if you're on the jump to next track or other audio control button do what that button does).

-- 

Brian - Windows 10 Home, 64-Bit, Version 1809, Build 17763  

A great deal of intelligence can be invested in ignorance when the need for illusion is deep.

          ~ Saul Bellow, To Jerusalem and Back

 

 

Hi,
That's subjective. I find the compact versions don't mangle some
pronunciations.
All the best
Steve
-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of luke scholey
Sent: 22 February 2019 12:12
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA CodeFactory imbedded pro voices
Higher is better quality.
Luke

On 22 Feb 2019, at 02:53, Chris Shook <chris0309@sero.email> wrote:

Hi,
WHen using Eloquence and Vocalizer expressive for NVDA, what is the

difference in the imbedded pro and the imbedded high?

I know the imbedded pro is more precise in it's pronunciation and takes up

less space, but is there an official difference?

Thanks
Chris

On 24 Feb 2019, at 17:52, Steve Nutt <steve@comproom.co.uk> wrote:

Hi,

That's subjective. I find the compact versions don't mangle some
pronunciations.

All the best

Steve

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of luke scholey
Sent: 22 February 2019 12:12
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA CodeFactory imbedded pro voices

Higher is better quality.
Luke

On 22 Feb 2019, at 02:53, Chris Shook <chris0309@sero.email> wrote:

Hi,
WHen using Eloquence and Vocalizer expressive for NVDA, what is the

difference in the imbedded pro and the imbedded high?

I know the imbedded pro is more precise in it's pronunciation and takes up

less space, but is there an official difference?

Thanks
Chris

Seriously, it seems more work than I feel like doing, but I'll do just because I really want to hear how that project would sound after all.
The idea of robotic music be it whatever it could be fascinates me. Smiles.

Marcio,

           What's really peculiar to me is that the quick navigation shortcuts will gain you focus on the various buttons, which I had not tried before because this is the first time I have ever encountered a page where brute force tab traversal doesn't encounter controls in roughly the same order as they're seen on the screen.  At some point I'm going to have to keep tabbing and tabbing and tabbing to see if, eventually, those buttons are traversed.

            Using the B quick navigation shortcut will get you focus on the button, but when I have focus on the button with NVDA using NumPad Slash to left click still does nothing at all.  Neither does spacebar or enter.   However, once I have focus on the button via the B command, if I use NVDA+Num Pad Slash to route the mouse to the NVDA item with focus, then hit NumPad Slash (or left click if you have a prepared mouse or have left your mousepad hard buttons active while covering the tracking area), it works.

             You have to go around Jake's barn, as they say in the region I live in to get it to work, but you eventually can.  But in order to even get to that stage relatively quickly you have to know there are buttons on the page, use the B quick navigation command to get to one, find that spacebar or enter won't activate it, then play the route PC to screen reader focus and emulate left click game to activate it.

              That's more than I'd expect anyone unfamiliar with a page's contents from the outset to ever be able to do quickly and "instinctively."

--

Brian - Windows 10 Home, 64-Bit, Version 1809, Build 17763  

A great deal of intelligence can be invested in ignorance when the need for illusion is deep.

          ~ Saul Bellow, To Jerusalem and Back

 

 

But nothing happens when you press space bar on the button.

 

Sent from Mail for Windows 10

 

From: Gene
Sent: 24 February 2019 17:26
To: nvda@nvda.groups.io
Subject: Re: [nvda] Having troubles to play with a website

 

Using Chrome and the play button, I can move to the button and to other buttons on the page.  Perhaps with Firefox, that can't be done.

 

Gene

----- Original Message -----

From: Brian Vogel

Sent: Sunday, February 24, 2019 10:56 AM

To: nvda@nvda.groups.io

Subject: Re: [nvda] Having troubles to play with a website

 

Marcio,

          This is a very strange site indeed in that the play buttons do not even get visited when brute force tabbing through the page.   When I looked at the page source, it turns out that they have used ARIA labels for each and every play button for the tracks listed.  For example, the track called Desensitized has an ARIA label on its play button, "Play Desensitized".

          I don't know whether that will help in any way, but it's the best I can do.  I have not previously encountered a music player page where the actual buttons that control play are not visited.

--

Brian - Windows 10 Home, 64-Bit, Version 1809, Build 17763  

A great deal of intelligence can be invested in ignorance when the need for illusion is deep.

          ~ Saul Bellow, To Jerusalem and Back

 

 

 

Using Chrome and the play button, I can move to the button and to other buttons on the page.  Perhaps with Firefox, that can't be done.

Marcio,

          This is a very strange site indeed in that the play buttons do not even get visited when brute force tabbing through the page.   When I looked at the page source, it turns out that they have used ARIA labels for each and every play button for the tracks listed.  For example, the track called Desensitized has an ARIA label on its play button, "Play Desensitized".

          I don't know whether that will help in any way, but it's the best I can do.  I have not previously encountered a music player page where the actual buttons that control play are not visited.

--

Brian - Windows 10 Home, 64-Bit, Version 1809, Build 17763  

A great deal of intelligence can be invested in ignorance when the need for illusion is deep.

          ~ Saul Bellow, To Jerusalem and Back

Marcio,

           What's really peculiar to me is that the quick navigation shortcuts will gain you focus on the various buttons, which I had not tried before because this is the first time I have ever encountered a page where brute force tab traversal doesn't encounter controls in roughly the same order as they're seen on the screen.  At some point I'm going to have to keep tabbing and tabbing and tabbing to see if, eventually, those buttons are traversed.

            Using the B quick navigation shortcut will get you focus on the button, but when I have focus on the button with NVDA using NumPad Slash to left click still does nothing at all.  Neither does spacebar or enter.   However, once I have focus on the button via the B command, if I use NVDA+Num Pad Slash to route the mouse to the NVDA item with focus, then hit NumPad Slash (or left click if you have a prepared mouse or have left your mousepad hard buttons active while covering the tracking area), it works.

             You have to go around Jake's barn, as they say in the region I live in to get it to work, but you eventually can.  But in order to even get to that stage relatively quickly you have to know there are buttons on the page, use the B quick navigation command to get to one, find that spacebar or enter won't activate it, then play the route PC to screen reader focus and emulate left click game to activate it.

              That's more than I'd expect anyone unfamiliar with a page's contents from the outset to ever be able to do quickly and "instinctively."

--

Brian - Windows 10 Home, 64-Bit, Version 1809, Build 17763  

A great deal of intelligence can be invested in ignorance when the need for illusion is deep.

          ~ Saul Bellow, To Jerusalem and Back

 

 

Marcio,

            No, I can click it and it works fine.  I just do not land on any of the Play buttons when using NVDA, and Chrome.
--

Brian - Windows 10 Home, 64-Bit, Version 1809, Build 17763  

A great deal of intelligence can be invested in ignorance when the need for illusion is deep.

          ~ Saul Bellow, To Jerusalem and Back

 

 

The screen-reader can't work with the search built into the browser.  The page that you are reading is in a buffer where the screen-reader reformats it.

 

Gene

----- Original Message -----

From: marcio via Groups.Io

Sent: Sunday, February 24, 2019 11:30 AM

To: nvda@nvda.groups.io

Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

So it's an option that the screen reader isn't able to deal with, is it right?
Sorry for asking too much as I am but it really got me curious.

Cheers,
Marcio
Follow or add me on Facebook

Em 24/02/2019 14:30, Gene escreveu:

If you aren't using a screen-reader you use the actual search built into the browser itself. 

 

Gene

----- Original Message -----

From: marcio via Groups.Io

Sent: Sunday, February 24, 2019 11:13 AM

To: nvda@nvda.groups.io

Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

But, what's the point of the "search for" option built-in on the browser? How one would deal with this option not using a screen reader?

Cheers,
Marcio
Follow or add me on Facebook

Em 24/02/2019 14:11, Gene escreveu:

You are searching using the buffer which screen-readers that use browse mode or the Virtual PC cursor use.  You aren't working directly with the page in browse mode or equivalent mode in a different screen-reader.  You must use the search command the screen-reader designates.

 

Gene

From: marcio via Groups.Io

Sent: Sunday, February 24, 2019 10:09 AM

To: nvda@nvda.groups.io

Subject: [nvda] Differences between using the NVDA and the browser commands search on a webpage

Hi guys,
Anyone could tell me what's the difference between these two commands?
I'm asking because using the browser command to search, nothing happens after I hit enter. On the other hand if I use the NVDA command I'll able to search for what I'm wanting to.
P.S.: Using Firefox.

--

Cheers,
Marcio
Follow or add me on Facebook

If you aren't using a screen-reader you use the actual search built into the browser itself. 

 

Gene

----- Original Message -----

From: marcio via Groups.Io

Sent: Sunday, February 24, 2019 11:13 AM

To: nvda@nvda.groups.io

Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

But, what's the point of the "search for" option built-in on the browser? How one would deal with this option not using a screen reader?

Cheers,
Marcio
Follow or add me on Facebook

Em 24/02/2019 14:11, Gene escreveu:

You are searching using the buffer which screen-readers that use browse mode or the Virtual PC cursor use.  You aren't working directly with the page in browse mode or equivalent mode in a different screen-reader.  You must use the search command the screen-reader designates.

 

Gene

From: marcio via Groups.Io

Sent: Sunday, February 24, 2019 10:09 AM

To: nvda@nvda.groups.io

Subject: [nvda] Differences between using the NVDA and the browser commands search on a webpage

Hi guys,
Anyone could tell me what's the difference between these two commands?
I'm asking because using the browser command to search, nothing happens after I hit enter. On the other hand if I use the NVDA command I'll able to search for what I'm wanting to.
P.S.: Using Firefox.

--

Cheers,
Marcio
Follow or add me on Facebook

Marcio,

            No, I can click it and it works fine.  I just do not land on any of the Play buttons when using NVDA, and Chrome.
--

Brian - Windows 10 Home, 64-Bit, Version 1809, Build 17763  

A great deal of intelligence can be invested in ignorance when the need for illusion is deep.

          ~ Saul Bellow, To Jerusalem and Back

 

 

On 22 Feb 2019, at 02:53, Chris Shook <chris0309@sero.email> wrote:

Hi,
WHen using Eloquence and Vocalizer expressive for NVDA, what is the

I know the imbedded pro is more precise in it's pronunciation and takes up

Thanks
Chris

If you aren't using a screen-reader you use the actual search built into the browser itself. 

 

Gene

----- Original Message -----

From: marcio via Groups.Io

Sent: Sunday, February 24, 2019 11:13 AM

To: nvda@nvda.groups.io

Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

But, what's the point of the "search for" option built-in on the browser? How one would deal with this option not using a screen reader?

Cheers,
Marcio
Follow or add me on Facebook

Em 24/02/2019 14:11, Gene escreveu:

You are searching using the buffer which screen-readers that use browse mode or the Virtual PC cursor use.  You aren't working directly with the page in browse mode or equivalent mode in a different screen-reader.  You must use the search command the screen-reader designates.

 

Gene

From: marcio via Groups.Io

Sent: Sunday, February 24, 2019 10:09 AM

To: nvda@nvda.groups.io

Subject: [nvda] Differences between using the NVDA and the browser commands search on a webpage

Hi guys,
Anyone could tell me what's the difference between these two commands?
I'm asking because using the browser command to search, nothing happens after I hit enter. On the other hand if I use the NVDA command I'll able to search for what I'm wanting to.
P.S.: Using Firefox.

--

Cheers,
Marcio
Follow or add me on Facebook