<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1256">
<style id="owaParaStyle">P {
MARGIN-BOTTOM: 0px; MARGIN-TOP: 0px
}
</style>
</head>
<body style="WORD-WRAP: break-word; FONT-SIZE: 14px; FONT-FAMILY: Times,sans-serif; COLOR: rgb(0,0,0)" fPStyle="1" ocsi="0">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">
<p>Actually, this issue has surfaced in some of our APIP accessibility task force meetings. You may want to reach out to
<span onclick="_e(this,this.getAttribute("_e_onclick"), event)" ondblclick="_e(this,this.getAttribute("_e_ondblclick"), event)" id="spnR" title="paul.grudnitski@gmail.com" class="rwRRO" oncontextmenu="_e(this,this.getAttribute("_e_oncontextmenu"), event)" _ao="3" _em="paul.grudnitski@gmail.com" _rt="SMTP" _dn="Paul Grudnitski" _e_oncontextmenu="onRwCm(event);" _e_onclick="onClkRcp(event);" _e_ondblclick="onDblClkReadRcp(event);" _sa="paul.grudnitski@gmail.com" _rf="0">
Paul Grudnitski from Pearson ý[paul.grudnitski@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.</span></p>
<span onclick="_e(this,this.getAttribute("_e_onclick"), event)" ondblclick="_e(this,this.getAttribute("_e_ondblclick"), event)" title="paul.grudnitski@gmail.com" class="rwRRO" oncontextmenu="_e(this,this.getAttribute("_e_oncontextmenu"), event)" _ao="3" _em="paul.grudnitski@gmail.com" _rt="SMTP" _dn="Paul Grudnitski" _e_oncontextmenu="onRwCm(event);" _e_onclick="onClkRcp(event);" _e_ondblclick="onDblClkReadRcp(event);" _sa="paul.grudnitski@gmail.com" _rf="0">
<div>
<p> </p>
<div style="FONT-SIZE: 13px; FONT-FAMILY: Tahoma">--Steve Noble<br>
steve.noble@louisville.edu<br>
502-969-3088<br>
<a href="https://exchange.louisville.edu/owa/redir.aspx?C=CdhMttRtdkSZAY1GqZCRu5k28cp7bNAIPUU6wKc1De8y-_GlninyxASwkrwRp4PfcJ9J6C2iqrk.&URL=http%3a%2f%2flouisville.academia.edu%2fSteveNoble" target="_blank">http://louisville.academia.edu/SteveNoble</a></div>
</div>
<p> ý</span></p>
<div style="FONT-SIZE: 16px; FONT-FAMILY: Times New Roman; COLOR: #000000">
<hr tabindex="-1">
<div id="divRpF76513" style="DIRECTION: ltr"><font color="#000000" size="2" face="Tahoma"><b>From:</b> athen-list [athen-list-bounces@mailman13.u.washington.edu] on behalf of Madeleine Rothberg [madeleine_rothberg@wgbh.org]<br>
<b>Sent:</b> Tuesday, December 01, 2015 9:31 AM<br>
<b>To:</b> Access Technology Higher Education Network<br>
<b>Subject:</b> Re: [Athen] QTI 2.2 specification, MathML, and drop down interactions<br>
</font><br>
</div>
<div></div>
<div>
<div>Sean,</div>
<div><br>
</div>
<div>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:</div>
<div><br>
</div>
<div><a href="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=" target="_blank">http://www.imsglobal.org/forums/ims-glc-public-forums-and-resources/question-test-interoperability-public-forum</a></div>
<div><br>
</div>
<div>-Madeleine</div>
<div><br>
</div>
<div>
<div>-----</div>
<div>Madeleine Rothberg</div>
<div>Senior Subject Matter Expert</div>
<div>National Center for Accessible Media at WGBH</div>
<div>617-300-2492 (voicemail)</div>
<div><a href="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=" target="_blank">http://ncam.wgbh.org</a></div>
<div>madeleine_rothberg@wgbh.org</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="FONT-SIZE: 11pt; BORDER-TOP: #b5c4df 1pt solid; FONT-FAMILY: Calibri; BORDER-RIGHT: medium none; BORDER-BOTTOM: medium none; COLOR: black; PADDING-BOTTOM: 0in; TEXT-ALIGN: left; PADDING-TOP: 3pt; PADDING-LEFT: 0in; BORDER-LEFT: medium none; PADDING-RIGHT: 0in">
<span style="FONT-WEIGHT: bold">From: </span>Sean Keegan <<a href="mailto:skeegan@ccctechcenter.org" target="_blank">skeegan@ccctechcenter.org</a>><br>
<span style="FONT-WEIGHT: bold">Reply-To: </span>Access Technology Higher Education Network <<a href="mailto:athen-list@u.washington.edu" target="_blank">athen-list@u.washington.edu</a>><br>
<span style="FONT-WEIGHT: bold">Date: </span>Tuesday, November 24, 2015 8:12 PM<br>
<span style="FONT-WEIGHT: bold">To: </span>Access Technology Higher Education Network <<a href="mailto:athen-list@u.washington.edu" target="_blank">athen-list@u.washington.edu</a>><br>
<span style="FONT-WEIGHT: bold">Subject: </span>[Athen] QTI 2.2 specification, MathML, and drop down interactions<br>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="PADDING-BOTTOM: 0px; PADDING-TOP: 0px; PADDING-LEFT: 5px; MARGIN: 0px 0px 0px 5px; BORDER-LEFT: #b5c4df 5px solid; PADDING-RIGHT: 0px">
<div>
<div>
<div dir="ltr">Hello,
<div><br>
</div>
<div>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:</div>
<div><a style="FONT-SIZE: 12px" href="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=" rel="noreferrer" target="_blank">https://angular-ui.github.io/bootstrap/#/dropdown</a><br>
</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>Looking for suggestions from anyone who has any experience with these specifications.</div>
<div><br>
</div>
<div>Take care,<br>
Sean</div>
<div><br>
</div>
</div>
</div>
</div>
</blockquote>
</span></div>
</div>
</div>
</body>
</html>