WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Markup for question and answer scenario

for

From: Sean Keegan
Date: Jun 23, 2015 2:22AM

Yes - which is the short answer to the question all of you articulated far
better than I. Consistency and logical navigation is a major aspect I am
working to implement and, as Greg K. pointed out, there can be a trade-off
with the various types of questions that may be created.

@Jim - you answered an unasked question I had considered about providing
additional instructions. To go that route, I believe it would be best to
keep such instructions generic enough so as not to focus on one specific
screen-reader/AT application and describing how content is organized should
provide that starting point.

Appreciate the ideas,
Sean


From: Jim Allan < <EMAIL REMOVED> >
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Cc:
> Date: Mon, 22 Jun 2015 12:38:55 -0500
> Subject: Re: [WebAIM] Markup for question and answer scenario
> It would be prudent whatever structure is used, that instructions to the
> user about the structure and navigation is provided.
> Using Greg's scenario - informing users of the structure (headings,
> paragraphs, and form controls) lets them know that they will be using
> heading navigation, arrow navigation, and perhaps form navigation. All must
> be used or the user will miss information/instructions. Unless, you make a
> design choice and put tabindex=0 on everything. So, if the user only uses
> the tab key to navigate a test (generally large forms), they won't miss
> anything.
> Jim
>
> On Mon, Jun 22, 2015 at 10:55 AM, Greg Kraus < <EMAIL REMOVED> > wrote:
>
> > Hi Sean,
> >
> > I've worked with Moodle on the semantics of their quiz to make them
> > accessible. With complex and varied formats for quiz questions, in the
> > end you come down to a trade off - do you make each question within a
> > quiz as technically accessible as possible, or do you go for
> > consistency of semantics between all quiz questions.
> >
> > In the case of Moodle, we never knew exactly what was going to appear
> > in each question because of the flexibility the author has in creating
> > the questions. We went with ensuring consistent structure between all
> > question types. This is the basic format.
> >
> > <h2>Question number 1</h2>
> > <h3>Question status</h3>
> > <p>question status information goes here, like if it has been
> > answered, or flagged by the user so they can come back to it, or how
> > many points it is worth</p>
> > <h3>Question text</h3>
> > <p>question text goes here</p>
> > <h3>Answer</h3>
> > <p>answer inputs go here</p>
> >
> > This format gave users a consistent experience between all question
> > types to help them navigate, understand, and answer the question.
> >
> > I hope this helps.
> >
> > Greg
> > --
> > Greg Kraus
> > University IT Accessibility Coordinator
> > NC State University
> > 919.513.4087
> > <EMAIL REMOVED>
> > http://go.ncsu.edu/itaccess
> >
> >
> > On Mon, Jun 22, 2015 at 11:38 AM, Moore,Michael (HHSC)
> > < <EMAIL REMOVED> > wrote:
> > > Sean,
> > >
> > > If you are going to use aria-labelledby to add the question to the
> input
> > for the answer selection you will need to also point to the id for the
> > answer selection. When I have tested aria-labelled by overrides any
> > existing bound labels. So it would look like this <input ...
> > aria-labelledby="idOfQuestionHeading idOfAnswerText" ... /> This way a
> > screen reader would read both.
> > >
> > > Mike Moore
> > > Accessibility Coordinator
> > > Texas Health and Human Services Commission
> > > Civil Rights Office
> > > (512) 438-3431 (Office)
> > > (512) 574-0091 (Cell)
> > >
> > >