E-mail List Archives
do you call a combo box a "combo box" in user documentation?
From: glen walker
Date: Mar 22, 2018 10:56AM
- Next message: JP Jamous: "Re: do you call a combo box a "combo box" in userdocumentation?"
- Previous message: Jared Smith: "New Web Accessibility Practitioners Survey"
- Next message in Thread: JP Jamous: "Re: do you call a combo box a "combo box" in userdocumentation?"
- Previous message in Thread: None
- View all messages in this Thread
We are writing user guides and describing what actions you have to take to
change settings or print a report, etc. My advice to the documentation
writers is to use the "accessible name" (normally the label for the object)
and to include the object's type. So, for example, we'd say "Select the
Settings link" or "select the Start Date button".
But I'm not sure what to do with combo boxes (<select>/<option>). We want
the guides written for everyone. Technically, JAWS and NVDA call the
objects a "combo box". Voiceover calls them a "pop up button". But a
sighted user doesn't care what a screen reader calls them. "Combo box" is
kind of a technical term.
The writer's a leaning towards "drop down menu". That sort of explains the
behavior of the object. It does drop down and usually gives you a menu or
list of choices. Perhaps "drop down list"? Would either of those terms
makes sense to all users? If you're used to hearing AT say "combo box",
and then you listen to the user documentation and it says "drop down list",
is that ok?
- Next message: JP Jamous: "Re: do you call a combo box a "combo box" in userdocumentation?"
- Previous message: Jared Smith: "New Web Accessibility Practitioners Survey"
- Next message in Thread: JP Jamous: "Re: do you call a combo box a "combo box" in userdocumentation?"
- Previous message in Thread: None
- View all messages in this Thread