An add-on package for R primarily aimed at improving access to R for blind users. The package contains tools and functions that will help get a student through their first year statistics course, and probably well beyond it.
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
R
inst
man
po
tests
vignettes
.Rbuildignore
.gitignore
.travis.yml
CONDUCT.md
DESCRIPTION
NAMESPACE
NEWS.md
README.md
cran-comments.md

README.md

The BrailleR package is a collection of tools to make use of R a happier experience for blind people.

CRAN_Status_Badge CII Best Practices Travis-CI Build Status

Blind people's use of R

Blind people cannot use RStudio and depending on the combination of operating system and screen reading software we choose to use, we might have differing levels of success with the standard R GUI.

R is perhaps the most blind-friendly statistical software option because all scripts are written in plain text, using the text editor a user prefers, and all output can be saved in a wide range of file formats. The advent of R markdown and other reproducible research techniques can offer the blind user a degree of efficiency that is not offered in many other statistical software options.

Specific objectives of BrailleR

  1. Make accessing output simpler.
  2. Gain access to the content depicted in a graph.
  3. Help get into R markdown easier.
  4. Replace the tasks other users can do quickly using the RStudio IDE.

You can help

Any assistance to fill in the numerous gaps in what BrailleR delivers will be most gratefully received. As the primary developer of this package is himself blind, attempts to find out if the tools being created actually do replace visual elements or tasks requires a sighted person to sit alongside to offer commentary.

Code of Conduct

Please note that this project is released with a Contributor Code of Conduct. By participating in the BrailleR Project, you are agreeing to this code of conduct. Please check you agree with its terms before participating.

Wish list

Some issues to resolve:

  1. storing the graphical parameters in ScatterPlot() etc. does not necessarily get the right ones slected. Need to replace this by somehow keeping the ... arguments supplied by the user. Tested using col and pch in FittedLinePlot()
  2. Get extra bits of information for WTF() coming through, such as other shapes, lines etc.
  3. Add to the work done by Debra Warren and Paul Murrell on VI.ggplot() and related functions.
  4. ascertain which shiny app widgets are useful for blind users' screen reading software.
  5. link various plot objects to sonify package.
  6. get more graphics ready for making into SVG for use on Tiger products; mostly in SVGThis() method
  7. Get more Graph types working with the additional XML to make them interactive.
  8. fix background of all code chunks in slides being made. This is probably an issue in the css file.
  9. get graph files named properly by TwoFactors(); including boxplots etc vs each factor not both.
  10. In OneFactor() and TwoFactors(): ensure that boxplots are created for each factor unless a level is short of reps.
  11. WTF() doesn't pick up multiple outliers in boxplot() as more than one point
  12. fix VI.lm to cater for the weighted lm case.
  13. check the css is working for VI.lm()
  14. work out how to change colours in R console for low vision users as commands and/or settings
  15. create function to re-create vignettes from Rnw source into HTML
  16. Multiple language support was started but is in serious need of some love.
  17. Functions for the VI method to be completed include: VI.prcomp(), VI.factanal(), VI.glm(), VI.htest()?
  18. added functionality to compile all Rmd files in the current directory. Request from JYS; initial implementation done in June 2017. Includes batch file for use in Windows explorer and DOS prompt. Needs testing.
  19. VI.scatterplot() needs creating