OK, I got it figured out. My problem wasn't
navigating. It was that I didn't realize that the text field on the sign in
screen is *not!* for your user name as I thought it was. It's for the pin. You
don't put your user name into the app itself. That's handled through the OAuth
token you get through Firefox. That text field in the app is for the 7 digit
numerical pin. Once I typed the pin in that box instead of my user name, the
continue button finally appeared, and when I hit it, I was connected. So, sorry
about that.
--- Christopher Gilland Co-founder of Genuine Safe Haven
Ministries
----- Original Message -----
Sent: Thursday, October 19, 2017 1:59
PM
Subject: Re: [orca-list] Authorizing my
account in Corebird
Hello,
If you are adding new twitter account in Corebird,
follow these steps. If this is the first time you are adding Corebird there
is no account configured. In this case new account screen pops up
automagically on the app startup. If you already have some accounts and you
wish to add some more focus the Corebird main window, keep pressing ctrl+tab
until you land on the toggle button saying toggle button not pressed Show
configured accounts. I know you might be wondering why most buttons are
reported name followed by its role and state and this one works the other way
round. It's because this button has no name only an icon and a tooltip
describing the icon. So press the space bar on this button. The list of
menu items corresponding with your existing accounts will pop up. At the end
there is one more item saying Add new account. So navigate by pressing up and
down arrow keys and activate once you hear orca reporting Add new
account. A new dialog will show up. You can navigate by pressing tab or
shift+tab in this dialog. It has the following focusable controls: Request
pin button - with the initial focus Don't have a Twitter account yet,
create one label with a link inside. Pressing enter key here opens your
default browser of choice where you can register a new twitter account if you
don't yet have one. An empty label I don't know what it does. Perhaps it's
used for displaying error messages. Something that's silent when focused.
Perhaps that's some sizer or other grouping like control that should not be
focusable at all. We are definatelly not interested in this one. So we will
tab several times until we'll land on the request pin button and activate it
with the enter key. Twitter website should open in the default web browser
(Firefox is recommended here unless you know what you are doing while using
other browsers) where you can login and authorize corebird to access twitter
on your's behalf. Once it's authorized just select the resulting pin code
you've got on the Twitter web site displayed in your browser by using
shift+left or shift+right arrow keys and copy that into your clipboard by
pressing ctrl+c. Once you have your code in your clipboard go back to the
corebird window either by pressing alt+tab or by using windows pane in the
Activities overview on your Gnome desktop. When you land on the Corebird
window you can see a few differences as compared with the moment when you
leaved that window before activating Get pin button. Get pin button is now
replaced with Retry button. The empty label is still there so you just have
to skip over it by pressing the tab key again. The empty grouping control
is still there so you have to ignore it the same way we have done
before. And finally there is an entirely new control it's a text entry
labelled Pin. It should be empty unless you have accidentally typed something
into it. Pressing left or right arrow key should produce beeping bell because
there is nothing to read. You can paste your text from the clipboard into
this pin text entry. Once the pin is entered correctly you can press the
tab key several times in order to find a Confirm button which you can also
activate with the enter or space bar key.
Can you please try this out
and compare it with the results you were getting before? Can you please
describe the differences in similar details like I'm describing these
steps? I find this pretty straightforward eventhough there are some ugly
things here and there, however I can't see no major accessibility barriers
here. I am really curious what might be different on your system or where I
might be thinking differently.
Thanks for your
interest.
Greetings
Peter
|