<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<font style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks, nicely done.
<br>
<br>
<br>
</font><br>
<br>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<font style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><b>From</b>: Ken Petri [mailto:petri.1@osu.edu]
<br>
<b>Sent</b>: Thursday, December 19, 2013 10:14 AM<br>
<b>To</b>: Access Technology Higher Education Network <athen-list@u.washington.edu>; CIC IT Accessibility Usability Group <cic-it-accessibility@cic.net>
<br>
<b>Subject</b>: [Athen] Login problems with Microsoft 365 login <br>
</font> <br>
</div>
<div dir="ltr">
<div>
<div>Ohio State students use Microsoft's hosted email system. (Faculty and staff use a local Exchange instance.) The service for students that we call Buckeyemail was upgraded by Microsoft earlier this week to keep it in line with the MS 365 product.
<br>
<br>
</div>
We found that, once you had logged in once and your browser recognized your organizational email address, subsequent logins with the same browser gave you a login interface that was not (easily) accessible to screen reader users. The organizational login button
is not clickable using a screen reader, unless you put the screen reader into pass-through mode -- something that we felt our students would be unlikely to discover on their own.<br>
<br>
</div>
We have put a notification up on our Buckeyemail/email selection page, here:<br>
<div>
<div>
<div>
<div>
<div>
<div>
<p dir="ltr"><a href="https://email.osu.edu/" target="_blank">https://email.osu.edu/</a></p>
<p>Right now users are directed to contact our help line, but in the next day or so we will be adding a link to a knowledge base article that explains how to work around the issue. We are also in contact with MS through our campus rep.</p>
<p>If your campus uses 365 for student or other email, your screen reader users may be affected.
<br>
</p>
<p>Note that keyboard only users are not affected. Note also that we could not get VoiceOver on Mac to work with the login interface at all.</p>
<p>The problem is only apparent after you have logged in once and your browser sets the cookie to remember your username for subsequent logins.
<br>
</p>
<p>Best,</p>
<p>ken<br>
</p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>