<div dir="ltr">It's a shared responsibility but unfortunately the weight of it is going to fall more on AT developers, as typical app developers cannot always be depended on to abide by accessibility standards. AT may have it handled but they will always have to play catch-up especially nowadays with how often things are changing. <div><br></div><div>I just told someone recently that it would be great if we could expect that all developers of apps would utilize the tools provided them to ensure that their apps are accessible. For instance, Google takes this approach - they provide the tools and APIs necessary for developers to make their apps accessible; however, many developers complain that they do not have the time or resources. Therefore, I would argue that it's the responsibility of the tech giants, such as Google, to recognize the importance of accessibility of their services and to become leaders in this endeavor. It is my opinion that Apple has done better at this, making a firm commitment company-wide to accessibility and not leaving it up to individual teams and units across the company to implement accessibility however they see fit.</div><div><br></div><div>Thanks,</div><div>Robert</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jul 24, 2018 at 1:52 AM, Dan Comden <span dir="ltr"><<a href="mailto:danc@uw.edu" target="_blank">danc@uw.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hi Deborah,</div><div>Thanks for linking the article. The following is not directed at you. And your article is not Off Topic at all.<br></div><div><br></div><div>How about a different position -- AT has things handled. For the most part, screenreaders, TTS, STS, magnifiers -- they all understand basic underlying html.</div><div><br></div><div>So who is getting it wrong? The companies putting out shoddy interfaces and non-standard apps? Or the browsers? Assistive tech for the most part has it handled.<br></div><div><br></div><div>Discuss.</div><div><br></div><div>-*- Dan<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jul 23, 2018 at 1:46 PM, Deborah Armstrong <span dir="ltr"><<a href="mailto:armstrongdeborah@fhda.edu" target="_blank">armstrongdeborah@fhda.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div link="#0563C1" vlink="#954F72" lang="EN-US">
<div class="m_-6786503250229018092m_-4451069183358148385WordSection1">
<p class="MsoNormal">Bloomberg has an interesting story about Amy Hood, Microsoft’s CFO.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">One business trend for this past decade is that a CFO is no longer a glorified accountant/budget analyst. They are now part of the senior management team – determiners of strategy rather than implementers. Microsoft’ Q4 earnings report
came out Thursday and according to Bloomberg, investors are saying Ms. Hood is the best CFO Microsoft has ever had.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">One thing she’s done is take money away from legacy divisions and put it in to the cloud. Since 2002 when she was hired her goal is to move Microsoft more towards cloud-based subscription models for their products – I’m paraphrasing Bloomberg
here—previously most divisions could ask for what they wanted budget-wise and could expect to get it – that’s no longer true. Bloomberg also comments that Ms. Hood timed her start date back in 2002 to get maximum access to the employee stock purchase plan.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">So despite what we see at conferences with Microsoft’s waving of the accessibility banner, I don’t think it’s going to be smooth sailing ahead. If it doesn’t improve growth it’s going to be ignored. <u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">The earnings reports no longer say anything about Windows, so we can assume it is gradually going to just be a framework for a browser; already most new apps are PWAS (progressive web apps) which means no installation, no data on your own
PC, but you need to be online to access any of it. <u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">This means that AT is going to need to get much better at dealing with progressive web apps and other online offerings. For keyboard users, there is no longer a consistent, reliable set of keystrokes for operating web-based applications.
For screen reader users, just to take one example, pressing Tab can take you out of the application and in to the address bar which is very confusing; imagine if a single and frequently used keystroke could dump you out of the operating system! For magnification
users, the lack of standards in a web-based interface means that you can miss important information because you weren’t looking in the right place. <u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">The full Bloomberg story is here:<u></u><u></u></p>
<p class="MsoNormal"> <a href="https://www.bloomberg.com/news/articles/2018-07-16/how-amy-hood-won-back-wall-street-and-helped-reboot-microsoft" target="_blank">https://www.bloomberg.com/news<wbr>/articles/2018-07-16/how-amy-<wbr>hood-won-back-wall-street-and-<wbr>helped-reboot-microsoft</a><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">--Debee<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
<br>______________________________<wbr>_________________<br>
athen-list mailing list<br>
<a href="mailto:athen-list@mailman12.u.washington.edu" target="_blank">athen-list@mailman12.u.washing<wbr>ton.edu</a><br>
<a href="http://mailman12.u.washington.edu/mailman/listinfo/athen-list" rel="noreferrer" target="_blank">http://mailman12.u.washington.<wbr>edu/mailman/listinfo/athen-lis<wbr>t</a><br>
<br></blockquote></div><span class="HOEnZb"><font color="#888888"><br><br clear="all"><br>-- <br><div class="m_-6786503250229018092gmail_signature" data-smartmail="gmail_signature"><div><font face="arial, helvetica, sans-serif">-*- Dan Comden <a href="mailto:danc@washington.edu" target="_blank">danc@uw.edu</a></font></div><div><font face="arial, helvetica, sans-serif"> Access Technology Center <a href="http://www.uw.edu/itconnect/accessibility/atl/" target="_blank">www.uw.edu/itconnect/<wbr>accessibility/atl/</a></font></div><div><font face="arial, helvetica, sans-serif"> University of Washington UW Information Technology</font></div><div><br></div></div>
</font></span></div>
<br>______________________________<wbr>_________________<br>
athen-list mailing list<br>
<a href="mailto:athen-list@mailman12.u.washington.edu">athen-list@mailman12.u.<wbr>washington.edu</a><br>
<a href="http://mailman12.u.washington.edu/mailman/listinfo/athen-list" rel="noreferrer" target="_blank">http://mailman12.u.washington.<wbr>edu/mailman/listinfo/athen-<wbr>list</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">Robert Spangler<br>Disability Services Technical Support Specialist<br><span><a href="mailto:rspangler1@udayton.edu" target="_blank">rspangler1@udayton.edu</a><br></span>Office of Learning Resources (OLR) - RL 023<br>Ryan C. Harris Learning & Teaching Center (LTC)<br>University of Dayton | 300 College Park | Dayton, Ohio 45469-1302 <br>Phone: 937-229-2066<br></div><div>Fax: 937-229-3270</div><div>Ohio Relay: 711 (available for individuals who are deaf or hard of hearing)<br></div><div>Web Site: <a href="http://go.udayton.edu/learning" target="_blank">http://go.udayton.edu/learning</a><br><br></div></div></div></div></div></div></div></div>
</div>