[Athen] QTI 2.2 specification, MathML, and drop down interactions

Sean Keegan skeegan at ccctechcenter.org
Tue Dec 1 14:49:51 PST 2015

Thanks for the contact, Steve.

In part, I am trying to understand if it is I who is misreading the spec or
if the developers are trying something that is technically conforming but
functionally not usable. We are also using MathJax, although it is being
used in its default implementation. We did try a number of alternative
solutions (aria labels, off-screen text, etc.) as well as modifying the
Angular-Bootstrap component, but nothing seemed to work.

I do need to have an immediate solution, but I would like to address the
root issue. The developers keep insisting they are following the
specification and because this is considered valid, the issue is believed
to be with the assistive technology, not with the implementation.
Unfortunately, there is little guidance as to how one should implement this
specific interaction type so that it also supports accessibility.

Is there going to be an update to the APIP documentation or is it
considered current for the QTI 2.2 specification?

Thanks again,

On Tue, Dec 1, 2015 at 6:50 AM, <steve.noble at louisville.edu> wrote:

> Actually, this issue has surfaced in some of our APIP accessibility task

> force meetings. You may want to reach out to Paul Grudnitski from

> Pearson ‎[paul.grudnitski at gmail.com], as he has developed some sample

> content where he used MathJax in a special configuration to get past this

> issue. This assumes that your interest is in getting something that works

> now in your specific implementation, as opposed to fixing the root problem

> for all mankind.



> --Steve Noble

> steve.noble at louisville.edu

> 502-969-3088

> http://louisville.academia.edu/SteveNoble

> <https://exchange.louisville.edu/owa/redir.aspx?C=CdhMttRtdkSZAY1GqZCRu5k28cp7bNAIPUU6wKc1De8y-_GlninyxASwkrwRp4PfcJ9J6C2iqrk.&URL=http%3a%2f%2flouisville.academia.edu%2fSteveNoble>



> ------------------------------

> *From:* athen-list [athen-list-bounces at mailman13.u.washington.edu] on

> behalf of Madeleine Rothberg [madeleine_rothberg at wgbh.org]

> *Sent:* Tuesday, December 01, 2015 9:31 AM

> *To:* Access Technology Higher Education Network

> *Subject:* Re: [Athen] QTI 2.2 specification, MathML, and drop down

> interactions


> Sean,


> It sounds like you found an interesting bug — maybe in QTI or maybe in the

> component coding or the browser you are using. You may find people who can

> help answer your question in the IMS forum for QTI:



> http://www.imsglobal.org/forums/ims-glc-public-forums-and-resources/question-test-interoperability-public-forum

> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.imsglobal.org_forums_ims-2Dglc-2Dpublic-2Dforums-2Dand-2Dresources_question-2Dtest-2Dinteroperability-2Dpublic-2Dforum&d=AwMFAw&c=SgMrq23dbjbGX6e0ZsSHgEZX6A4IAf1SO3AJ2bNrHlk&r=4WMck1ZVLo4tV0IVllcBNKXCSGU6lUERtx_4HD4DqmE&m=lZpgVCI4j4dV7RAbyJgsPr6gvi2ev39UulE4tTAhJ2g&s=RQ03YDhlQSsaxrlublVMcAR_sOkU7c_2VehQ0NE6-co&e=>


> -Madeleine


> -----

> Madeleine Rothberg

> Senior Subject Matter Expert

> National Center for Accessible Media at WGBH

> 617-300-2492 (voicemail)

> http://ncam.wgbh.org

> <https://urldefense.proofpoint.com/v2/url?u=http-3A__ncam.wgbh.org&d=AwMFAw&c=SgMrq23dbjbGX6e0ZsSHgEZX6A4IAf1SO3AJ2bNrHlk&r=4WMck1ZVLo4tV0IVllcBNKXCSGU6lUERtx_4HD4DqmE&m=lZpgVCI4j4dV7RAbyJgsPr6gvi2ev39UulE4tTAhJ2g&s=d3FLRWRh6r3Ia-S2ROIIZw5cpu2F_q6lMXVABAK0kFo&e=>

> madeleine_rothberg at wgbh.org


> From: Sean Keegan <skeegan at ccctechcenter.org>

> Reply-To: Access Technology Higher Education Network <

> athen-list at u.washington.edu>

> Date: Tuesday, November 24, 2015 8:12 PM

> To: Access Technology Higher Education Network <

> athen-list at u.washington.edu>

> Subject: [Athen] QTI 2.2 specification, MathML, and drop down interactions


> Hello,


> 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:

> https://angular-ui.github.io/bootstrap/#/dropdown

> <https://urldefense.proofpoint.com/v2/url?u=https-3A__angular-2Dui.github.io_bootstrap_-23_dropdown&d=AwMFAw&c=SgMrq23dbjbGX6e0ZsSHgEZX6A4IAf1SO3AJ2bNrHlk&r=4WMck1ZVLo4tV0IVllcBNKXCSGU6lUERtx_4HD4DqmE&m=lZpgVCI4j4dV7RAbyJgsPr6gvi2ev39UulE4tTAhJ2g&s=VHmk1_qhD-6DkFzTrCamkasNg6U7ZqLemEE9i9z0rD0&e=>


> 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

> specifications.


> Take care,

> Sean



> _______________________________________________

> athen-list mailing list

> athen-list at mailman13.u.washington.edu

> http://mailman13.u.washington.edu/mailman/listinfo/athen-list



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman12.u.washington.edu/pipermail/athen-list/attachments/20151201/2482db11/attachment.html>

More information about the athen-list mailing list