<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: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=iso-8859-9">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-ligatures:standardcontextual;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@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="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Hello,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">There isn’t a list I am aware of, but that doesn’t mean it doesn’t exist. I’ve seen some blog posts from the Jumping Rivers people which mention accessibility.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">I’ve tried to get accessibility built into the mainstream packages wherever possible, rather than having access built on as some sort of after-thought. For example, some standard HTML accessibility
features are included in the rmarkdown and knitr packages’ processing of Rmd files.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">A package that uses ggplot2 to create graphics may or may not work with BrailleR’s automatic description of graphs features. I’ve seen some examples that do play nicely and some that do not at all<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">You might look out for packages that create pdf files, whether for the graphics they create or in their vignettes. It seems quite a few people know my contempt for the pdf as a document format.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Package vignettes and package down web pages may have some access issues, so documentation is one area I’d look at. The help pages should be accessible out of the box, but that doesn’t mean the examples
are, or that the help pages are actually helpful to the target end users.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">HTH,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Jonathan<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="mso-ligatures:none">From:</span></b><span lang="EN-US" style="mso-ligatures:none"> BlindRUG <blindrug-bounces@nfbnet.org>
<b>On Behalf Of </b>çagri gökçek via BlindRUG<br>
<b>Sent:</b> Sunday, October 1, 2023 4:29 PM<br>
<b>To:</b> çağrı gökçek via BlindRUG <blindrug@nfbnet.org><br>
<b>Cc:</b> çağrı gökçek <cagri_gokcek@hotmail.com><br>
<b>Subject:</b> [BlindRUG] A list of R packages providing accessibility features for the blind<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US">Hi all,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">I am a blind R learner. I have recently been involved in an R training. In this training, I am supposed to give a feedback to one of my cohort members. He has a package in which there are mapping functions. My main goal
is checking his packages’ the level of integration with the existing accessibility packages such as BrailleR. Since I am very new in package review processes and my knowledge in R is not very broad. I am happy to get any kind of suggestion. Is there any list
of packages that I can use in this review process to test their accessibility functions in line with my friend’s mapping and other visualization features?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Thanks in advance for all replies.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Best.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Cagri<o:p></o:p></span></p>
</div>
</body>
</html>