GNOME.org
 

Re: [orca-list] Orca not indicating that a Firefox text entry is writable

Aha. This should now be fixed in master, along with some other issues I
found along the way. One known-issue which I still have to look into is
that when you backspace in that entry, Orca is getting a text
notification that text which was not removed was actually removed. It
may be a case of the widget nuking everything there and replacing it.

So.... With the above caveat in mind: How is are these entries working
for you now?

Thanks again!
--joanie

On 02/07/2018 01:17 PM, Nolan Darilek wrote:

When you actually create a username, then enter the chatroom. The only
area that doesn't indicate editable state is the message entry area. And
that indication is inconsistent. Tabbing to it speaks correctly.
Navigating by e/E doesn't.


Thanks a bunch!



On 02/07/2018 12:15 PM, Joanmarie Diggs wrote:

When I follow those steps I get a "To get started, pick a username!"
entry. Because Orca calls it an entry and not editable content, I'm
guessing that's not the entry you're talking about. Which one is?

On 02/07/2018 11:45 AM, Nolan Darilek wrote:

This change still speaks the specific area as just "blank," but it does
indicate that the Thunderbird message area is editable now, so I think
it should stay.


If you don't mind creating an account, you can access
https://riot.im/app, click one of the rooms (Matrix HQ), click the
button to join the discussion, then create a username. Sorry, I wish
there was some way of snapshotting a running web app so I could capture
state at the time of the bug.




On 02/07/2018 10:39 AM, Joanmarie Diggs wrote:

Hi again.

For my test case, Orca was not finding all editable content items with
quick nav key "e". So I just committed a change to master to address
that too. Please test and let me know.

Thanks!
--joanie

On 02/07/2018 05:20 AM, Peter Vágner wrote:

Hello,

Sorry for the double posting. I have looked into this one more time.
I have found out, orca can find this element when pressing the edit
field quick nav key however it is only presenting its content.
I think this is tricky as this is kind of an editor where you can
compose rich formatted message. We need to compare how e.g. gmail,
etherpad and other similar apps are doing it. Still I believe this
might
be more a web authoring issue than an orca issue. And other screen
readers may opt to workaround it because it's quite frequent on the
web.


Greetings

Peter


2018-02-06 20:53 GMT+01:00 Peter Vágner <pvdeejay gmail com
<mailto:pvdeejay gmail com>>:

      Hey Nolan,

      The issue where orca is unable to identify Riot.im input area as
      editable text navigable to via quick nav key in browse mode is
      partially an orca issue and partially matrix-react-sdk issue I
guess.

      The riot.im <http://riot.im> issue is that this is simply a html
div
      with a lot of javascript functionality and the role is set via
aria.

      Orca is skipping over it, however NVDA can navigate to it via
quick nav.

      There is a WIP PR which might address this at the riot.im
      <http://riot.im> side of things:
      https://github.com/matrix-org/matrix-react-sdk/pull/1561
      <https://github.com/matrix-org/matrix-react-sdk/pull/1561>

      Also there is an #a11y:matrix.org <http://matrix.org> room for
      discussing Riot accessibility. There is not much activity
currently
      however it would be nice to talk more about over verbosity of
      messages time line view, fixing corresponding live region not
to be
      active wich each text change in that part including scrolling
and
      similar.
      I am not currently working on it however I am looking for a
way on
      how to make it work. I was thinking about using aria-hidden
on the
      icons entangled within the text and flip the aria-hidden on
these
      when focussing on them via tab / shift + tab. In such a case we
      would get nice brief experience when reading with browse mode
and we
      might still be able to activate controls not presented to screen
      reader users by default. However this is clear abuse of ARIA, I
      think it's against aria best practices and very likelly to be
hated
      by accessibility evangelists. So I would be happy to talk
about it
      to someone who might potentially like to help me to clear up my
mind.

      I apologize for an off-topic.

      Greetings

      Peter



      2018-02-06 19:55 GMT+01:00 Joanmarie Diggs <jdiggs igalia com
      <mailto:jdiggs igalia com>>:

          Thanks for the report Nolan. I'll add this to my list.
          --joanie

          On 02/06/2018 11:41 AM, Nolan Darilek wrote:
          > Hey, as usual, not sure whether this is an Orca or Firefox
          issue. I'm
          > making accessibility tweaks in the Riot Matrix web client,
and
          notice
          > that when I use e/E to navigate between text entry fields
with
          Orca
          > master, the message entry field just speaks "blank" rather
          than "entry".
          > Is this something wrong with the web markup? If so, then I
can
          fix that.
          >
          >
          > Here's a debug log of me flipping through text entries
in the
          app. There
          > are 3:
          >
          >
          > https://www.dropbox.com/s/jkjdw0txnftvbhr/debug.out?dl=0
          <https://www.dropbox.com/s/jkjdw0txnftvbhr/debug.out?dl=0>
          >
          >
          > As an aside, this field has a placeholder, not a label.
Not
          sure if that
          > has anything to do with why it isn't presented
correctly, but
          I hope the
          > placeholder is read when using e/E to navigate.
          >
          >
          > Thanks!
          >
          > _______________________________________________
          > orca-list mailing list
          > orca-list gnome org <mailto:orca-list gnome org>
          > https://mail.gnome.org/mailman/listinfo/orca-list
          <https://mail.gnome.org/mailman/listinfo/orca-list>
          > Orca wiki: https://wiki.gnome.org/Projects/Orca
          <https://wiki.gnome.org/Projects/Orca>
          > Orca documentation:
https://help.gnome.org/users/orca/stable/
          <https://help.gnome.org/users/orca/stable/>
          > GNOME Universal Access guide:
          > https://help.gnome.org/users/gnome-help/stable/a11y.html
          <https://help.gnome.org/users/gnome-help/stable/a11y.html>
          > Log bugs and feature requests at http://bugzilla.gnome.org
          >

          _______________________________________________
          orca-list mailing list
          orca-list gnome org <mailto:orca-list gnome org>
          https://mail.gnome.org/mailman/listinfo/orca-list
          <https://mail.gnome.org/mailman/listinfo/orca-list>
          Orca wiki: https://wiki.gnome.org/Projects/Orca
          <https://wiki.gnome.org/Projects/Orca>
          Orca documentation:
https://help.gnome.org/users/orca/stable/
          <https://help.gnome.org/users/orca/stable/>
          GNOME Universal Access guide:
          https://help.gnome.org/users/gnome-help/stable/a11y.html
          <https://help.gnome.org/users/gnome-help/stable/a11y.html>
          Log bugs and feature requests at http://bugzilla.gnome.org




_______________________________________________
orca-list mailing list
orca-list gnome org
https://mail.gnome.org/mailman/listinfo/orca-list
Orca wiki: https://wiki.gnome.org/Projects/Orca
Orca documentation: https://help.gnome.org/users/orca/stable/
GNOME Universal Access guide:
https://help.gnome.org/users/gnome-help/stable/a11y.html
Log bugs and feature requests at http://bugzilla.gnome.org
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]