[Athen] QTI 2.2 specification, MathML, and drop down interactions
skeegan at ccctechcenter.org
Tue Nov 24 17:12:49 PST 2015
I have an assessment application that developers are building according to
the QTI 2.2 specification. One of the interaction types is that of a
dropdown choice (like a <select> menu) but implemented using
Angular-Bootstrap. It is based off the following:
As an example - there could be a sentence with a word missing and the
dropdown menu would offer several choices so as to complete the sentence.
While this interaction type can be made accessible and works fine for text
content, it fails when MathML is used to present any math content. Visually
the math is presented, but the MathML content cannot be read by any
assistive technologies. In fact, interacting with this component from the
keyboard becomes problematic if any AT is running at the time.
As part of the IMS QTI 2.2 specification, MathML is "approved" for use in
certain interaction types, one being InlineChoiceGroup in which the
dropdown interaction is used. We have AT that supports MathML and yet by
following the IMS QTI 2.2 specification, that content is no longer
communicated to the user.
I have been reviewing the Accessible Portable Item Protocol and best
practices, but this points to the QTI 2.1 specification and does not appear
to provide any direction as to how to resolve such an issue.
Looking for suggestions from anyone who has any experience with these
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the athen-list