<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-NZ" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hello Nicholas,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I’ve seen your posts on another list about the transition from low to no vision and the challenges that will bring.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">You and I had already communicated off-list so I was sort of hoping others on this list would share their experiences. I realise that the main question you
have needs to be visible in the list archive just in case someone else comes along in your situation.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Practically everything you do in RStudio that is plain R stuff can be done in either the terminal or GUI versions of R. We have found some exceptions where
package authors have created tools that create an additional GUI and don’t work on the command line whether that be in the terminal or R GUI. In those circumstances the inaccessibility of RStudio is not the culprit.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">You will be able to write R markdown documents and develop shiny apps outside RStudio. R markdown files are just plain text and are easily rendered into HTML
using rmarkdown::render() at the command prompt in R. I do this more often than any other way of working now. It is just too easy to have the markdown file open in an editor (screen reader friendly of course), the successful HTML file open in a browser, and
the R terminal sitting waiting for me to re-issue the render() command. Yes, I have to hit f5 a lot, and the documents that are full of math content take a long time to load <sigh> because they’re using MathJax, but at least the HTML is totally readable.
I do have some hints at <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><a href="https://r-resources.massey.ac.nz/rmarkdown/">https://r-resources.massey.ac.nz/rmarkdown/</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">The key development of shiny apps is done in plain text files as well. The problem is that the widgets used to build shiny apps are not all accessible with
a screen reader. Most work very well, but a couple lead to some very strange behaviour for the screen reader. Unfortunately, I have not yet found anyone willing to help me discover which ones are in the problem set.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Jonathan<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> BlindRUG [mailto:blindrug-bounces@nfbnet.org]
<b>On Behalf Of </b>Nicholas J via BlindRUG<br>
<b>Sent:</b> Wednesday, 15 March 2017 2:59 p.m.<br>
<b>To:</b> blindrug@nfbnet.org<br>
<b>Cc:</b> Nicholas J<br>
<b>Subject:</b> [BlindRUG] Switching from Doing with Eyesight to Doing Without<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Hello,<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I am legally blind, with enough vision to do things on the computer using Zoomtext and using a portable cctv to view things from a distance. I have been relying on this technology to do everything from programming, to statistical work,
to reading, to viewing boards, and surfing the web. I can still see the same amount, but the inefficiencies in all these techniques has become apparent. I have been switching over to technologies like Jaws, Kurzweil, and braille. For r programming, I'm thinking
Jaws is the best to use, but I am not sure how. I've read about the terminal and used it before. I mainly use Rstudio visually now and saw that many of the features in it like creating rmarkdown files and such would have to be done differently in places like
the terminal. I've learned that Rstudio is not very Jaws friendly, but am not at all sure how to use Jaws and r together. How can you view a whole script of r code at once? In a terminal, doesn't one run code line by line? How can all line be corrected and
run at once like in Rstudio? How do I code in r just using my hearing and not eyesight? How do I create such things as an rmarkdown file or a shiny app without Rstudio? I looked through the threads in this list and found things that are very helpful, but am
not sure how to use them without using my vision. Any help would very much be appreciated.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thank you,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Nicholas<o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>