Accessible alternatives for radioButtons, checkboxGroupInput and fileInput added
This commit is contained in:
52
man/a11yRadioButtons.Rd
Normal file
52
man/a11yRadioButtons.Rd
Normal file
@@ -0,0 +1,52 @@
|
||||
% Generated by roxygen2: do not edit by hand
|
||||
% Please edit documentation in R/a11yRadioButtons.R
|
||||
\name{a11yRadioButtons}
|
||||
\alias{a11yRadioButtons}
|
||||
\title{Create radio buttons}
|
||||
\usage{
|
||||
a11yRadioButtons(
|
||||
inputId,
|
||||
label,
|
||||
choices = NULL,
|
||||
selected = NULL,
|
||||
inline = FALSE,
|
||||
width = NULL,
|
||||
choiceNames = NULL,
|
||||
choiceValues = NULL
|
||||
)
|
||||
}
|
||||
\arguments{
|
||||
\item{inputId}{The \code{input} slot that will be used to access the value.}
|
||||
|
||||
\item{label}{Display label for the control, or \code{NULL} for no label.}
|
||||
|
||||
\item{choices}{List of values to select from (if elements of the list are
|
||||
named then that name rather than the value is displayed to the user). If
|
||||
this argument is provided, then \code{choiceNames} and \code{choiceValues} must not
|
||||
be provided, and vice-versa. The values should be strings; other types
|
||||
(such as logicals and numbers) will be coerced to strings.}
|
||||
|
||||
\item{selected}{The initially selected value. If not specified, then it
|
||||
defaults to the first item in \code{choices}. To start with no items selected,
|
||||
use \code{character(0)}.}
|
||||
|
||||
\item{inline}{If \code{TRUE}, render the choices inline (i.e. horizontally)}
|
||||
|
||||
\item{width}{The width of the input, e.g. \code{'400px'}, or \code{'100\%'};
|
||||
see \code{\link[shiny:validateCssUnit]{validateCssUnit()}}.}
|
||||
|
||||
\item{choiceNames, choiceValues}{List of names and values, respectively, that
|
||||
are displayed to the user in the app and correspond to the each choice (for
|
||||
this reason, \code{choiceNames} and \code{choiceValues} must have the same length).
|
||||
If either of these arguments is provided, then the other \emph{must} be provided
|
||||
and \code{choices} \emph{must not} be provided. The advantage of using both of these
|
||||
over a named list for \code{choices} is that \code{choiceNames} allows any type of UI
|
||||
object to be passed through (tag objects, icons, HTML code, ...), instead
|
||||
of just simple text. See Examples.}
|
||||
}
|
||||
\description{
|
||||
Creates more accessible shiny radio buttons
|
||||
}
|
||||
\seealso{
|
||||
\code{\link[shiny:radioButtons]{shiny::radioButtons()}}
|
||||
}
|
||||
Reference in New Issue
Block a user