[NFBCS] Managing Pull Requests on Github with Screenreader

[Ida B]

Hi,

I have wanted to know the answer to this as well. My company uses
bitbucket, but it is similar enough to github that I am sure the same rules
would apply.

I am also wondering how one would manage seeing the “diff” between the PR
and the source branch? Easily viewing which files have been changed, and
then which lines in those files.

When I make my own PR, and others on my team comment, I have managed to
figure out how best to respond. In bitbucket, the comments are in nested
lists, and I can use the JAWS list navigation commands to navigate through
and reply/view comments along with what files they are referring to.

Looking forward to hearing from what others have done.


Thank you,
Ida

On Wed, Apr 1, 2020 at 2:46 PM Timothy Breitenfeldt via NFBCS <
nfbcs at nfbnet.org> wrote:

> Hi, I have been meaning to ask this for a while now. I was wondering
> how other screenreader users have been handling Github pull requests
> using JAWS or NVDA. I can open and close the pull requests in the web
> interface, but it is just not very easy because there are not really
> any landmarks to jump to everything that I need to, at least that I
> have figured out.
>
> Any suggestions for moving through the Github interface faster, or
> perhaps an alternative approach to using the web site?
>
> Thanks,
>
> Timothy Breitenfeldt
>
> --
>
> Timothy Breitenfeldt
>
> Phone: 509-388-7262
>
> Skype: timothyjb310 at outlook.com
>
> https://www.linkedin.com/in/timothybreitenfeldt/
>
> _______________________________________________
> NFBCS mailing list
> NFBCS at nfbnet.org
> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
> To unsubscribe, change your list options or get your account info for
> NFBCS:
> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/behreini.ida%40gmail.com
>