Support for enhanced accessibility in Kindle 1.19

classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|

Support for enhanced accessibility in Kindle 1.19

James Teh
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

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel
Reply | Threaded
Open this post in threaded view
|

Re: Support for enhanced accessibility in Kindle 1.19

James Scholes
Hi Jamie,

I can't seem to get the reading of book content to work at all.  When I
open a book without Enhanced Typesetting, I do hear a message letting me
know that the content won't be accessible through my screen reader.
Additionally, the interface is generally more usable and responsive
across the board.  But unfortunately, when opening a supported book, I
only hear the word "border" in the content area.

Developer info for navigator object:
name: None
role: ROLE_BORDER
states: STATE_FOCUSABLE, STATE_FOCUSED
isFocusable: True
hasFocus: True
Python object: <appModules.kindle.PageTurnFocusIgnorer object at 0x0624DF50>
Python class mro: (<class 'appModules.kindle.PageTurnFocusIgnorer'>,
<class 'NVDAObjects.IAccessible.IAccessible'>, <class
'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class
'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>,
<type 'object'>)
description: None
location: (52, 93, 1392, 791)
value: None
appModule: <'kindle' (appName u'kindle', process ID 4448) at address
624dcf0>
appModule.productName: u'Kindle'
appModule.productVersion: u'1.19.0.46067'
TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'>
windowHandle: 9899114L
windowClassName: u'Qt5QWindowIcon'
windowControlID: 0
windowStyle: -1764818944
windowThreadID: 2640
windowText: u"James's Kindle for PC - The Elements of Eloquence: How to
Turn the Perfect English Phrase"
displayText: u''
IAccessibleObject: <POINTER(IAccessible2) ptr=0x8789dfc at 60ff800>
IAccessibleChildID: 0
IAccessible event parameters: windowHandle=9899114, objectID=-4,
childID=-2147483337
IAccessible accName: None
IAccessible accRole: ROLE_SYSTEM_BORDER
IAccessible accState: STATE_SYSTEM_FOCUSED, STATE_SYSTEM_FOCUSABLE,
STATE_SYSTEM_VALID (1048580)
IAccessible accDescription: None
IAccessible accValue: None
IAccessible2 windowHandle: 9899114
IAccessible2 uniqueID: -2147483337
IAccessible2 role: ROLE_SYSTEM_BORDER
IAccessible2 states:  (0)
IAccessible2 attributes: None

Let me know if there's anything else you need.
--
James Scholes
http://twitter.com/JamesScholes

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel
Reply | Threaded
Open this post in threaded view
|

Re: Support for enhanced accessibility in Kindle 1.19

James Teh
Hi James,

From your log, it looks to me like this book isn't accessible, even though it supports enhanced typesetting. Another user reported a similar problem with another book, though they also had one book that did work. I've reported these two books to Amazon and have requested clarification as to what's going on here. I've also asked about any free books that can be used for public testing. I'll post back here with any further info.

Thanks!

Jamie

On Wed, Jan 4, 2017 at 11:44 AM, James Scholes <[hidden email]> wrote:
Hi Jamie,

I can't seem to get the reading of book content to work at all.  When I
open a book without Enhanced Typesetting, I do hear a message letting me
know that the content won't be accessible through my screen reader.
Additionally, the interface is generally more usable and responsive
across the board.  But unfortunately, when opening a supported book, I
only hear the word "border" in the content area.

Developer info for navigator object:
name: None
role: ROLE_BORDER
states: STATE_FOCUSABLE, STATE_FOCUSED
isFocusable: True
hasFocus: True
Python object: <appModules.kindle.PageTurnFocusIgnorer object at 0x0624DF50>
Python class mro: (<class 'appModules.kindle.PageTurnFocusIgnorer'>,
<class 'NVDAObjects.IAccessible.IAccessible'>, <class
'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class
'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>,
<type 'object'>)
description: None
location: (52, 93, 1392, 791)
value: None
appModule: <'kindle' (appName u'kindle', process ID 4448) at address
624dcf0>
appModule.productName: u'Kindle'
appModule.productVersion: u'1.19.0.46067'
TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'>
windowHandle: 9899114L
windowClassName: u'Qt5QWindowIcon'
windowControlID: 0
windowStyle: -1764818944
windowThreadID: 2640
windowText: u"James's Kindle for PC - The Elements of Eloquence: How to
Turn the Perfect English Phrase"
displayText: u''
IAccessibleObject: <POINTER(IAccessible2) ptr=0x8789dfc at 60ff800>
IAccessibleChildID: 0
IAccessible event parameters: windowHandle=9899114, objectID=-4,
childID=-2147483337
IAccessible accName: None
IAccessible accRole: ROLE_SYSTEM_BORDER
IAccessible accState: STATE_SYSTEM_FOCUSED, STATE_SYSTEM_FOCUSABLE,
STATE_SYSTEM_VALID (1048580)
IAccessible accDescription: None
IAccessible accValue: None
IAccessible2 windowHandle: 9899114
IAccessible2 uniqueID: -2147483337
IAccessible2 role: ROLE_SYSTEM_BORDER
IAccessible2 states:  (0)
IAccessible2 attributes: None

Let me know if there's anything else you need.
--
James Scholes
http://twitter.com/JamesScholes

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel
Reply | Threaded
Open this post in threaded view
|

Re: Support for enhanced accessibility in Kindle 1.19

John Isige
In reply to this post by James Teh
Moby Dick, which is free, seems to be working fine for me. I also picked
a sample of "The Weird" and that worked too. Awesome stuff! Is there a
way to go to the top of a book? Ctrl-home didn't seem to do it. But page
up and page down, the arrows, and NVDA-down arrow all work fine. I
haven't messed with notes and such yet, nor have I looked into browsing
books in the Kindle app and all, which I assume you can do, and get the
book details page to find out if they have enhanced type. I just had
these loaded in because I grabbed them with the Kindle app on my phone
and I guess it keeps track of that, so I tried them.


On 1/3/2017 6:08 PM, James The wrote:

> 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
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>
>
> _______________________________________________
> Nvda-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/nvda-devel


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel
Reply | Threaded
Open this post in threaded view
|

NVDA announce empty word when moving cursor inside Google docs

Mgr. Janusz Chmiel-3
Do you think, that NVDA would stop to say empty word while moving cursor
inside Google docs document? No matter, which cursor key have been
pressed. NVDA announces empty word before any other output.
It is not pleasant.
I Am using
NVDA next-13761,fc9ed0a7
And latest stable Google chrome.
Any bud correction is very welcomed.
Thank You for yours understanding.


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel
Reply | Threaded
Open this post in threaded view
|

Re: NVDA announce empty word when moving cursor inside Google docs

Kevin Chao
Fixed+Verified in Chrome Canary 57.0.2953.0.
Does this issue match the following? 
"issue that takes place when I use Chrome and
NVDA with Google Docs when Braille Mode is disabled.

1. Open Chrome and load any document in Google Docs.

2. Ensure that Braille Mode is not checked from the Accessibility >
Settings menu.

3. Try to type something and try to move around the document.

4. Notice that "blank" is announced before everything."

On Tue, Jan 3, 2017 at 11:22 PM Mgr. Janusz Chmiel <[hidden email]> wrote:
Do you think, that NVDA would stop to say empty word while moving cursor
inside Google docs document? No matter, which cursor key have been
pressed. NVDA announces empty word before any other output.
It is not pleasant.
I Am using
NVDA next-13761,fc9ed0a7
And latest stable Google chrome.
Any bud correction is very welcomed.
Thank You for yours understanding.


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel
Reply | Threaded
Open this post in threaded view
|

Re: NVDA announce empty word when moving cursor inside Google docs

derek riemer
In reply to this post by Mgr. Janusz Chmiel-3

Please create a new thread for this.


On 1/4/2017 12:18 AM, Mgr. Janusz Chmiel wrote:
Do you think, that NVDA would stop to say empty word while moving cursor 
inside Google docs document? No matter, which cursor key have been 
pressed. NVDA announces empty word before any other output.
It is not pleasant.
I Am using
NVDA next-13761,fc9ed0a7
And latest stable Google chrome.
Any bud correction is very welcomed.
Thank You for yours understanding.


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel

--

Derek Riemer

  • Department of computer science, third year undergraduate student.
  • Proud user of the NVDA screen reader.
  • Open source enthusiast.
  • Member of Bridge Cu
  • Avid skiier.

Websites:
Honors portfolio
Awesome little hand built weather app!

[hidden email]
Phone: (303) 906-2194


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel
Reply | Threaded
Open this post in threaded view
|

Re: Support for enhanced accessibility in Kindle 1.19

Noelia
In reply to this post by John Isige
Hi, here is my opinion and results of test.
First of all, I confess that I don't like Amazon to buy books. I prefer
for instance Google Play, with ePUB format, readable with different
systems from Windows, also in browse mode with Firefox add-ons as
ePUBReader, or with Adobe Digital Editions in case of ePUB 3 files.
General impression: The Kindle support is much better than nothing or
the old plugin provided by Amazon. Anyway, I don't like that we can just
select or explore a page. I prefer to see full chapters, where headings
or landmarks are placet in a natural way; pages are not natural
divisions for me.
I bought a book with enhanced typesettings in Amazon, and I didn't like
this. I didn't see headings or links in pages of the book, perhaps due
to page division, which can be small respect the whole book. The
advantage was that when searching test I could know the highligting
text, and also was possible to add notes. NVDA announced that the text
had comments, but I couldn't move to them with a, the list elements
didn't work properly (below is the log when trying to change the element
type), and NVDA+alt+c didn't read them. I know that it's just initial
support, of course.
Anyway, as aside, I have tested an ePUB 3 sample of IDPF with Adobe
Digital Editions. This program sometimes get crashed on my system, I
don't know why. But I can add bookmarks, search and use browse mode
moving with tab, and, the most important thing, select and review a
whole chapter.
Adding notes seems not to be supported on Windows by ADE.
I think it would be good to provide accurate information on ePUB test
accessibility page with NVDA. Now this info seems not to be updated to
NVDA 2016.4:
http://epubtest.org/testsuite/accessibility/
Thanks.
***

ERROR - queueHandler.flushQueue (06:30:37):
Error in func initElementType from eventQueue
Traceback (most recent call last):
   File "queueHandler.pyc", line 50, in flushQueue
   File "browseMode.pyc", line 758, in initElementType
   File "appModules\kindle.pyc", line 150, in _iterNodesByType
NotImplementedError
ERROR - queueHandler.flushQueue (06:30:38):
Error in func initElementType from eventQueue
Traceback (most recent call last):
   File "queueHandler.pyc", line 50, in flushQueue
   File "browseMode.pyc", line 758, in initElementType
   File "appModules\kindle.pyc", line 150, in _iterNodesByType
NotImplementedError
ERROR - queueHandler.flushQueue (06:30:40):
Error in func initElementType from eventQueue
Traceback (most recent call last):
   File "queueHandler.pyc", line 50, in flushQueue
   File "browseMode.pyc", line 758, in initElementType
   File "appModules\kindle.pyc", line 150, in _iterNodesByType
NotImplementedError
ERROR - queueHandler.flushQueue (06:30:40):
Error in func initElementType from eventQueue
Traceback (most recent call last):
   File "queueHandler.pyc", line 50, in flushQueue
   File "browseMode.pyc", line 758, in initElementType
   File "appModules\kindle.pyc", line 150, in _iterNodesByType
NotImplementedError

El 04/01/2017 a las 4:59, John Isige escribió:

> Moby Dick, which is free, seems to be working fine for me. I also picked
> a sample of "The Weird" and that worked too. Awesome stuff! Is there a
> way to go to the top of a book? Ctrl-home didn't seem to do it. But page
> up and page down, the arrows, and NVDA-down arrow all work fine. I
> haven't messed with notes and such yet, nor have I looked into browsing
> books in the Kindle app and all, which I assume you can do, and get the
> book details page to find out if they have enhanced type. I just had
> these loaded in because I grabbed them with the Kindle app on my phone
> and I guess it keeps track of that, so I tried them.
>
>
> On 1/3/2017 6:08 PM, James The wrote:
>> 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
>>
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>>
>>
>> _______________________________________________
>> Nvda-devel mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/nvda-devel
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Nvda-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/nvda-devel
>

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel
Reply | Threaded
Open this post in threaded view
|

Re: Support for enhanced accessibility in Kindle 1.19

Brian's Mail list account BY
No I've no time to listen to books myself, and find Amazon a bit daunting in
this respect, though of course now they are supporting so many devices it
should make things easier for many people.
 Brian

[hidden email]
Sent via blueyonder.
Please address personal email to:-
[hidden email], putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Noelia" <[hidden email]>
To: "NVDA screen reader development" <[hidden email]>
Sent: Saturday, January 07, 2017 5:38 AM
Subject: Re: [Nvda-devel] Support for enhanced accessibility in Kindle 1.19


Hi, here is my opinion and results of test.
First of all, I confess that I don't like Amazon to buy books. I prefer
for instance Google Play, with ePUB format, readable with different
systems from Windows, also in browse mode with Firefox add-ons as
ePUBReader, or with Adobe Digital Editions in case of ePUB 3 files.
General impression: The Kindle support is much better than nothing or
the old plugin provided by Amazon. Anyway, I don't like that we can just
select or explore a page. I prefer to see full chapters, where headings
or landmarks are placet in a natural way; pages are not natural
divisions for me.
I bought a book with enhanced typesettings in Amazon, and I didn't like
this. I didn't see headings or links in pages of the book, perhaps due
to page division, which can be small respect the whole book. The
advantage was that when searching test I could know the highligting
text, and also was possible to add notes. NVDA announced that the text
had comments, but I couldn't move to them with a, the list elements
didn't work properly (below is the log when trying to change the element
type), and NVDA+alt+c didn't read them. I know that it's just initial
support, of course.
Anyway, as aside, I have tested an ePUB 3 sample of IDPF with Adobe
Digital Editions. This program sometimes get crashed on my system, I
don't know why. But I can add bookmarks, search and use browse mode
moving with tab, and, the most important thing, select and review a
whole chapter.
Adding notes seems not to be supported on Windows by ADE.
I think it would be good to provide accurate information on ePUB test
accessibility page with NVDA. Now this info seems not to be updated to
NVDA 2016.4:
http://epubtest.org/testsuite/accessibility/
Thanks.
***

ERROR - queueHandler.flushQueue (06:30:37):
Error in func initElementType from eventQueue
Traceback (most recent call last):
   File "queueHandler.pyc", line 50, in flushQueue
   File "browseMode.pyc", line 758, in initElementType
   File "appModules\kindle.pyc", line 150, in _iterNodesByType
NotImplementedError
ERROR - queueHandler.flushQueue (06:30:38):
Error in func initElementType from eventQueue
Traceback (most recent call last):
   File "queueHandler.pyc", line 50, in flushQueue
   File "browseMode.pyc", line 758, in initElementType
   File "appModules\kindle.pyc", line 150, in _iterNodesByType
NotImplementedError
ERROR - queueHandler.flushQueue (06:30:40):
Error in func initElementType from eventQueue
Traceback (most recent call last):
   File "queueHandler.pyc", line 50, in flushQueue
   File "browseMode.pyc", line 758, in initElementType
   File "appModules\kindle.pyc", line 150, in _iterNodesByType
NotImplementedError
ERROR - queueHandler.flushQueue (06:30:40):
Error in func initElementType from eventQueue
Traceback (most recent call last):
   File "queueHandler.pyc", line 50, in flushQueue
   File "browseMode.pyc", line 758, in initElementType
   File "appModules\kindle.pyc", line 150, in _iterNodesByType
NotImplementedError

El 04/01/2017 a las 4:59, John Isige escribió:

> Moby Dick, which is free, seems to be working fine for me. I also picked
> a sample of "The Weird" and that worked too. Awesome stuff! Is there a
> way to go to the top of a book? Ctrl-home didn't seem to do it. But page
> up and page down, the arrows, and NVDA-down arrow all work fine. I
> haven't messed with notes and such yet, nor have I looked into browsing
> books in the Kindle app and all, which I assume you can do, and get the
> book details page to find out if they have enhanced type. I just had
> these loaded in because I grabbed them with the Kindle app on my phone
> and I guess it keeps track of that, so I tried them.
>
>
> On 1/3/2017 6:08 PM, James The wrote:
>> 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
>>
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>>
>>
>> _______________________________________________
>> Nvda-devel mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/nvda-devel
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Nvda-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/nvda-devel
>

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel 


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel
Reply | Threaded
Open this post in threaded view
|

Re: Support for enhanced accessibility in Kindle 1.19

Noelia
I prefer ePUB format, and Google Play seems more comfortable, since
several books are ofered also in PDF.
I have searched selected words in the dictionary with this feature of
NVDA for testing. But I think that the most important thing is to read
whole documents in browse mode, as ebooks, at least in ePUB and PDF,
have capabilities based or similar to HTML. But pages are not documents
and this is the main issue for me.
Thanks.

El 07/01/2017 a las 11:46, Brian's Mail list account BY escribió:

> No I've no time to listen to books myself, and find Amazon a bit daunting in
> this respect, though of course now they are supporting so many devices it
> should make things easier for many people.
>  Brian
>
> [hidden email]
> Sent via blueyonder.
> Please address personal email to:-
> [hidden email], putting 'Brian Gaff'
> in the display name field.
> ----- Original Message -----
> From: "Noelia" <[hidden email]>
> To: "NVDA screen reader development" <[hidden email]>
> Sent: Saturday, January 07, 2017 5:38 AM
> Subject: Re: [Nvda-devel] Support for enhanced accessibility in Kindle 1.19
>
>
> Hi, here is my opinion and results of test.
> First of all, I confess that I don't like Amazon to buy books. I prefer
> for instance Google Play, with ePUB format, readable with different
> systems from Windows, also in browse mode with Firefox add-ons as
> ePUBReader, or with Adobe Digital Editions in case of ePUB 3 files.
> General impression: The Kindle support is much better than nothing or
> the old plugin provided by Amazon. Anyway, I don't like that we can just
> select or explore a page. I prefer to see full chapters, where headings
> or landmarks are placet in a natural way; pages are not natural
> divisions for me.
> I bought a book with enhanced typesettings in Amazon, and I didn't like
> this. I didn't see headings or links in pages of the book, perhaps due
> to page division, which can be small respect the whole book. The
> advantage was that when searching test I could know the highligting
> text, and also was possible to add notes. NVDA announced that the text
> had comments, but I couldn't move to them with a, the list elements
> didn't work properly (below is the log when trying to change the element
> type), and NVDA+alt+c didn't read them. I know that it's just initial
> support, of course.
> Anyway, as aside, I have tested an ePUB 3 sample of IDPF with Adobe
> Digital Editions. This program sometimes get crashed on my system, I
> don't know why. But I can add bookmarks, search and use browse mode
> moving with tab, and, the most important thing, select and review a
> whole chapter.
> Adding notes seems not to be supported on Windows by ADE.
> I think it would be good to provide accurate information on ePUB test
> accessibility page with NVDA. Now this info seems not to be updated to
> NVDA 2016.4:
> http://epubtest.org/testsuite/accessibility/
> Thanks.
> ***
>
> ERROR - queueHandler.flushQueue (06:30:37):
> Error in func initElementType from eventQueue
> Traceback (most recent call last):
>    File "queueHandler.pyc", line 50, in flushQueue
>    File "browseMode.pyc", line 758, in initElementType
>    File "appModules\kindle.pyc", line 150, in _iterNodesByType
> NotImplementedError
> ERROR - queueHandler.flushQueue (06:30:38):
> Error in func initElementType from eventQueue
> Traceback (most recent call last):
>    File "queueHandler.pyc", line 50, in flushQueue
>    File "browseMode.pyc", line 758, in initElementType
>    File "appModules\kindle.pyc", line 150, in _iterNodesByType
> NotImplementedError
> ERROR - queueHandler.flushQueue (06:30:40):
> Error in func initElementType from eventQueue
> Traceback (most recent call last):
>    File "queueHandler.pyc", line 50, in flushQueue
>    File "browseMode.pyc", line 758, in initElementType
>    File "appModules\kindle.pyc", line 150, in _iterNodesByType
> NotImplementedError
> ERROR - queueHandler.flushQueue (06:30:40):
> Error in func initElementType from eventQueue
> Traceback (most recent call last):
>    File "queueHandler.pyc", line 50, in flushQueue
>    File "browseMode.pyc", line 758, in initElementType
>    File "appModules\kindle.pyc", line 150, in _iterNodesByType
> NotImplementedError
>
> El 04/01/2017 a las 4:59, John Isige escribió:
>> Moby Dick, which is free, seems to be working fine for me. I also picked
>> a sample of "The Weird" and that worked too. Awesome stuff! Is there a
>> way to go to the top of a book? Ctrl-home didn't seem to do it. But page
>> up and page down, the arrows, and NVDA-down arrow all work fine. I
>> haven't messed with notes and such yet, nor have I looked into browsing
>> books in the Kindle app and all, which I assume you can do, and get the
>> book details page to find out if they have enhanced type. I just had
>> these loaded in because I grabbed them with the Kindle app on my phone
>> and I guess it keeps track of that, so I tried them.
>>
>>
>> On 1/3/2017 6:08 PM, James The wrote:
>>> 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
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>>>
>>>
>>> _______________________________________________
>>> Nvda-devel mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/nvda-devel
>>
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Nvda-devel mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/nvda-devel
>>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Nvda-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/nvda-devel
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Nvda-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/nvda-devel
>

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel
Reply | Threaded
Open this post in threaded view
|

Re: Support for enhanced accessibility in Kindle 1.19

James Teh
In reply to this post by Noelia
Hey Noelia,
Thanks for your feedback. Replies inline:

On Sat, Jan 7, 2017 at 3:38 PM, Noelia <[hidden email]> wrote:
Anyway, I don't like that we can just
select or explore a page. I prefer to see full chapters, where headings
or landmarks are placet in a natural way; pages are not natural
divisions for me.
It's true that  we render only one page at a time in browse mode. However, in most respects, this shouldn't be relevant to the user, since NVDA should turn pages automatically when you try to move beyond the start or end of a page. In what cases did you notice this (apart from first letter navigation)?

I bought a book with enhanced typesettings in Amazon, and I didn't like
this. I didn't see headings or links in pages of the book, perhaps due
to page division, which can be small respect the whole book.
Reporting of headings is not yet supported, though it's definitely something I'm pushing for.
 
The
advantage was that when searching test I could know the highligting
text, and also was possible to add notes. NVDA announced that the text
had comments, but I couldn't move to them with a,
This is also a known issue which I hope to fix soon.
 
the list elements
didn't work properly (below is the log when trying to change the element
type)
Oops. That's my bad; I'll fix this. Note that the only supported type in Elements List should be links, so we shouldn't list headings or landmarks.
 
and NVDA+alt+c didn't read them.
This one too is known and I'm pushing for a fix. It requires a change in Kindle.

Anyway, as aside, I have tested an ePUB 3 sample of IDPF with Adobe
Digital Editions. This program sometimes get crashed on my system, I
don't know why. But I can add bookmarks, search and use browse mode
moving with tab, and, the most important thing, select and review a
whole chapter.
I don't quite follow what you mean by "select and review a whole chapter". Digital Editions also renders page by page, but it too turns pages automatically when you reach the end.
 
Thanks!

Jamie


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel
Reply | Threaded
Open this post in threaded view
|

Re: Support for enhanced accessibility in Kindle 1.19

Noelia

Hi, I am learning SoftBraille Keyboard on Android, hope I can explain things fine.
For me is important view pages in these cases:
1. As you say, in quick navigation using characters.
2. For list of elements. 3 To use search in browse mode, apart of searching with programs features.
4. When using add-ons designed for browse mode (I use placeMarkers).
Pages seems to small and not logical when reading, and I viewed that certain sentence was divided in a bad way, and page change is perceptible. I am used to read whole chapters in epubs and comparing this, I prefer, when possible, to read them.
About Adobe Digital Edition, when epub are version 3, they are show as you say, in a window by pages, but it is also possible to view another window with NVDA, where the whole chapter containing the current page is displayed in browse mode
Thanks

Enviado con AquaMail para Android http://www.aqua-mail.com

En 8 de enero de 2017 23:09:35 James Teh <[hidden email]> escribió:

Hey Noelia,
Thanks for your feedback. Replies inline:

On Sat, Jan 7, 2017 at 3:38 PM, Noelia <[hidden email]> wrote:
Anyway, I don't like that we can just
select or explore a page. I prefer to see full chapters, where headings
or landmarks are placet in a natural way; pages are not natural
divisions for me.
It's true that  we render only one page at a time in browse mode. However, in most respects, this shouldn't be relevant to the user, since NVDA should turn pages automatically when you try to move beyond the start or end of a page. In what cases did you notice this (apart from first letter navigation)?

I bought a book with enhanced typesettings in Amazon, and I didn't like
this. I didn't see headings or links in pages of the book, perhaps due
to page division, which can be small respect the whole book.
Reporting of headings is not yet supported, though it's definitely something I'm pushing for.
 
The
advantage was that when searching test I could know the highligting
text, and also was possible to add notes. NVDA announced that the text
had comments, but I couldn't move to them with a,
This is also a known issue which I hope to fix soon.
 
the list elements
didn't work properly (below is the log when trying to change the element
type)
Oops. That's my bad; I'll fix this. Note that the only supported type in Elements List should be links, so we shouldn't list headings or landmarks.
 
and NVDA+alt+c didn't read them.
This one too is known and I'm pushing for a fix. It requires a change in Kindle.

Anyway, as aside, I have tested an ePUB 3 sample of IDPF with Adobe
Digital Editions. This program sometimes get crashed on my system, I
don't know why. But I can add bookmarks, search and use browse mode
moving with tab, and, the most important thing, select and review a
whole chapter.
I don't quite follow what you mean by "select and review a whole chapter". Digital Editions also renders page by page, but it too turns pages automatically when you reach the end.
 
Thanks!

Jamie


Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel