Check out the LimeSurvey source code on GitHub!
Welcome, Guest
Username: Password:

TOPIC: Accessibility With Screen Readers

Accessibility With Screen Readers 5 years 5 months ago #60175

  • lhughes30
  • lhughes30's Avatar
  • Offline
  • Junior Lime
  • Posts: 20
  • Thank you received: 1
  • Karma: 1
I have a user with the following concerns about accessibility for people using screen readers. These comments are related to the Demo survey at I'd greatly appreciate any help or ideas with meeting these requirements:

1. Radio buttons/checkboxes:
The radio buttons are labeled with the <label> element but are not
explicitly associated with any actual questions. One way to solve this
problem is to use <fieldset> to group the answers with each question;
otherwise the screen reader reads only the answers (the checkboxes/buttons)
but the user must search around for each question. Also, they should add
headings (h1, h2, h3, etc.) to each question to make it easy for
screen-reader users to jump from one question to the next by pressing the
heading shortcut key (this is important).

2. The data table on page 2 poses some interesting problems. To fully
understand this question, users must approach the grid as a data table, not
as a sequence of form fields. This is a straightforward procedure when
users navigate using a screen reader's table-reading commands: scan to the
correct row, then move the focus over to the correct button/table cell to
answer the question for that row. Conventional form markup (i.e., the
<label> element) may not work here because of the tablular construction.
One alternate approach may be to use aria-labelledby but we'd need to test

Another approach would be to implement this table simply as a series of data
cells, each of which contains a dropdown list that poses the question AND
holds the answers. That is, the initial value (that is, the visible text)
of each dropdown list is the actual *question* which needs to be answered.
For instance, the initial value of the first dropdown list could be
"Database, such as MySQL"; when the dropdown list is opened the user would
see the answers and simply choose the appropriate one: "I don't know what
this is," "I've heard of it," "No answer," etc.

3. The form elements at the top of page 5, where users must click an item
in a list box on the left side and then that item automatically moves to a
list on the right side, are not keyboard accessible or screen-reader
accessible. This approach will be tricky to make accessible.
The administrator has disabled public write access.
Time to create page: 3.842 seconds
Imprint                   Privacy policy         General Terms & Conditions         Revocation information and revocation form