Factors influencing what the flat review perceive

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

Factors influencing what the flat review perceive

vincent-lg
Hi everyone,


I'm working on a GUI application built with wxPython, and trying to
determine how accessible it is with NVDA.  Most of the window is taken
by a TextCtrl (a text field, for me, multiline and read-only).  This
text field contains a kind of log that is updated pretty quickly.


Since it's a read-only text field, it can be accessed in browse mode
without problems.  It's actually the best way to do it, I think, since
one can browse the entire content, go back at the beginning, use the
ReadAll functions, select and copy easily, and so on.  But I would also
like for this text field to be accessed through the flat review mode.  
In theory, no problem at all:  it's shorter, of course, because it
doesn't show more than what is displayed on the screen, but at least it
shows the end of the text field.  However, after some content has been
added, it doesn't show more than the 7 or 8 ending lines of the
content.  I'm not sure to know why, exactly, but then, I can't see the
screen.


Can anyone tell me what would influence the flat review perception in
this case?  Should I decrease font PointSize for instance, to allow more
text to be displayed?  Is there a way to prevent the flat review from
reading a few lines from other windows (it seems to often happen in my
case, the 3 or 4 lines at the bottom come from either another
application, or a patch of text that is now scrolled upward)?


Thanks for your reply,


Vincent


------------------------------------------------------------------------------
_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel
Reply | Threaded
Open this post in threaded view
|

Re: Factors influencing what the flat review perceive

derek riemer

Hi:

The primary use of flat reviiew (Screen review I assume)? is for inaccessible apps. Your wx read only edit field is not using browse mode, but rather lets the user

move with the arrow keys. If you set NVDA to object review while focused on this,, you'll see only the text in that box.

HTH,

Derek


On 9/20/2016 2:48 PM, Vincent LE GOFF wrote:
Hi everyone,


I'm working on a GUI application built with wxPython, and trying to 
determine how accessible it is with NVDA.  Most of the window is taken 
by a TextCtrl (a text field, for me, multiline and read-only).  This 
text field contains a kind of log that is updated pretty quickly.


Since it's a read-only text field, it can be accessed in browse mode 
without problems.  It's actually the best way to do it, I think, since 
one can browse the entire content, go back at the beginning, use the 
ReadAll functions, select and copy easily, and so on.  But I would also 
like for this text field to be accessed through the flat review mode.  
In theory, no problem at all:  it's shorter, of course, because it 
doesn't show more than what is displayed on the screen, but at least it 
shows the end of the text field.  However, after some content has been 
added, it doesn't show more than the 7 or 8 ending lines of the 
content.  I'm not sure to know why, exactly, but then, I can't see the 
screen.


Can anyone tell me what would influence the flat review perception in 
this case?  Should I decrease font PointSize for instance, to allow more 
text to be displayed?  Is there a way to prevent the flat review from 
reading a few lines from other windows (it seems to often happen in my 
case, the 3 or 4 lines at the bottom come from either another 
application, or a patch of text that is now scrolled upward)?


Thanks for your reply,


Vincent


------------------------------------------------------------------------------
_______________________________________________
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


------------------------------------------------------------------------------

_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel
Reply | Threaded
Open this post in threaded view
|

Re: Factors influencing what the flat review perceive

vincent-lg

Thank you for these clarifications, Derek.  The more I'm using this app, the less I believe the flat (or object) review should be used in that case.  It's so much easier to use the standard cursor to read the text, although the flat review mode can still be useful to peek at the end of the log.


Thanks again for your answer,


Vincent


On 9/21/2016 5:16 PM, derek riemer wrote:

Hi:

The primary use of flat reviiew (Screen review I assume)? is for inaccessible apps. Your wx read only edit field is not using browse mode, but rather lets the user

move with the arrow keys. If you set NVDA to object review while focused on this,, you'll see only the text in that box.

HTH,

Derek


On 9/20/2016 2:48 PM, Vincent LE GOFF wrote:
Hi everyone,


I'm working on a GUI application built with wxPython, and trying to 
determine how accessible it is with NVDA.  Most of the window is taken 
by a TextCtrl (a text field, for me, multiline and read-only).  This 
text field contains a kind of log that is updated pretty quickly.


Since it's a read-only text field, it can be accessed in browse mode 
without problems.  It's actually the best way to do it, I think, since 
one can browse the entire content, go back at the beginning, use the 
ReadAll functions, select and copy easily, and so on.  But I would also 
like for this text field to be accessed through the flat review mode.  
In theory, no problem at all:  it's shorter, of course, because it 
doesn't show more than what is displayed on the screen, but at least it 
shows the end of the text field.  However, after some content has been 
added, it doesn't show more than the 7 or 8 ending lines of the 
content.  I'm not sure to know why, exactly, but then, I can't see the 
screen.


Can anyone tell me what would influence the flat review perception in 
this case?  Should I decrease font PointSize for instance, to allow more 
text to be displayed?  Is there a way to prevent the flat review from 
reading a few lines from other windows (it seems to often happen in my 
case, the 3 or 4 lines at the bottom come from either another 
application, or a patch of text that is now scrolled upward)?


Thanks for your reply,


Vincent


------------------------------------------------------------------------------
_______________________________________________
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



------------------------------------------------------------------------------


_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel


------------------------------------------------------------------------------

_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel
Reply | Threaded
Open this post in threaded view
|

Re: Factors influencing what the flat review perceive

derek riemer

Hi:

I think there may be some confusion with Orca here, because What is Flat review in orca, is actually two or sometimes 3 modes in NVDA. There's Object review, where where the review cursor is restricted to the current navigator object (I.E. if the navigator object is set to the edit field, you can only read text in the edit field. If you are in "screen review", you can read all the text NVDA can scrape from the screen. This mode may or may not show anything in your app. There's also "document review" on the web, where it shows everything for a entire web page (document).


On 9/22/2016 3:11 PM, Vincent LE GOFF wrote:

Thank you for these clarifications, Derek.  The more I'm using this app, the less I believe the flat (or object) review should be used in that case.  It's so much easier to use the standard cursor to read the text, although the flat review mode can still be useful to peek at the end of the log.


Thanks again for your answer,


Vincent


On 9/21/2016 5:16 PM, derek riemer wrote:

Hi:

The primary use of flat reviiew (Screen review I assume)? is for inaccessible apps. Your wx read only edit field is not using browse mode, but rather lets the user

move with the arrow keys. If you set NVDA to object review while focused on this,, you'll see only the text in that box.

HTH,

Derek


On 9/20/2016 2:48 PM, Vincent LE GOFF wrote:
Hi everyone,


I'm working on a GUI application built with wxPython, and trying to 
determine how accessible it is with NVDA.  Most of the window is taken 
by a TextCtrl (a text field, for me, multiline and read-only).  This 
text field contains a kind of log that is updated pretty quickly.


Since it's a read-only text field, it can be accessed in browse mode 
without problems.  It's actually the best way to do it, I think, since 
one can browse the entire content, go back at the beginning, use the 
ReadAll functions, select and copy easily, and so on.  But I would also 
like for this text field to be accessed through the flat review mode.  
In theory, no problem at all:  it's shorter, of course, because it 
doesn't show more than what is displayed on the screen, but at least it 
shows the end of the text field.  However, after some content has been 
added, it doesn't show more than the 7 or 8 ending lines of the 
content.  I'm not sure to know why, exactly, but then, I can't see the 
screen.


Can anyone tell me what would influence the flat review perception in 
this case?  Should I decrease font PointSize for instance, to allow more 
text to be displayed?  Is there a way to prevent the flat review from 
reading a few lines from other windows (it seems to often happen in my 
case, the 3 or 4 lines at the bottom come from either another 
application, or a patch of text that is now scrolled upward)?


Thanks for your reply,


Vincent


------------------------------------------------------------------------------
_______________________________________________
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



------------------------------------------------------------------------------


_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel



------------------------------------------------------------------------------


_______________________________________________
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


------------------------------------------------------------------------------

_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel
Reply | Threaded
Open this post in threaded view
|

Re: Factors influencing what the screen review perceive (was: Factors influencing what the flat review perceive)

vincent-lg
Yes, sorry, I was talking about screen review, a confusion on my part.

Vincent
On 9/22/2016 3:43 PM, derek riemer wrote:

Hi:

I think there may be some confusion with Orca here, because What is Flat review in orca, is actually two or sometimes 3 modes in NVDA. There's Object review, where where the review cursor is restricted to the current navigator object (I.E. if the navigator object is set to the edit field, you can only read text in the edit field. If you are in "screen review", you can read all the text NVDA can scrape from the screen. This mode may or may not show anything in your app. There's also "document review" on the web, where it shows everything for a entire web page (document).


On 9/22/2016 3:11 PM, Vincent LE GOFF wrote:

Thank you for these clarifications, Derek.  The more I'm using this app, the less I believe the flat (or object) review should be used in that case.  It's so much easier to use the standard cursor to read the text, although the flat review mode can still be useful to peek at the end of the log.


Thanks again for your answer,


Vincent


On 9/21/2016 5:16 PM, derek riemer wrote:

Hi:

The primary use of flat reviiew (Screen review I assume)? is for inaccessible apps. Your wx read only edit field is not using browse mode, but rather lets the user

move with the arrow keys. If you set NVDA to object review while focused on this,, you'll see only the text in that box.

HTH,

Derek


On 9/20/2016 2:48 PM, Vincent LE GOFF wrote:
Hi everyone,


I'm working on a GUI application built with wxPython, and trying to 
determine how accessible it is with NVDA.  Most of the window is taken 
by a TextCtrl (a text field, for me, multiline and read-only).  This 
text field contains a kind of log that is updated pretty quickly.


Since it's a read-only text field, it can be accessed in browse mode 
without problems.  It's actually the best way to do it, I think, since 
one can browse the entire content, go back at the beginning, use the 
ReadAll functions, select and copy easily, and so on.  But I would also 
like for this text field to be accessed through the flat review mode.  
In theory, no problem at all:  it's shorter, of course, because it 
doesn't show more than what is displayed on the screen, but at least it 
shows the end of the text field.  However, after some content has been 
added, it doesn't show more than the 7 or 8 ending lines of the 
content.  I'm not sure to know why, exactly, but then, I can't see the 
screen.


Can anyone tell me what would influence the flat review perception in 
this case?  Should I decrease font PointSize for instance, to allow more 
text to be displayed?  Is there a way to prevent the flat review from 
reading a few lines from other windows (it seems to often happen in my 
case, the 3 or 4 lines at the bottom come from either another 
application, or a patch of text that is now scrolled upward)?


Thanks for your reply,


Vincent


------------------------------------------------------------------------------
_______________________________________________
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



------------------------------------------------------------------------------


_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel



------------------------------------------------------------------------------


_______________________________________________
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



------------------------------------------------------------------------------


_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel


------------------------------------------------------------------------------

_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel