<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Aptos;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Aptos",sans-serif;
mso-ligatures:standardcontextual;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#467886;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Aptos",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:11.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link="#467886" vlink="#96607D" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal>Hello, Federationists,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>It appears that a new accessibility issue has reared its ugly head over the past few months…<o:p></o:p></p><p class=MsoNormal>It has to do with Toast!<o:p></o:p></p><p class=MsoNormal>And I’m not talking about the breakfast staple.<o:p></o:p></p><p class=MsoNormal>Toast is an extremely popular point-of-sale system for restaurants that’s used almost ubiquitously around the country and here in Colorado.<o:p></o:p></p><p class=MsoNormal>Recently, they changed their customer ordering screens both on restaurant websites and in their new app, Local by Toast, such that all the radio buttons and checkboxes you would use to customize your order are now completely inaccessible to screen readers without using OCR or screen recognition. This makes it damn near impossible for anyone using a screen reader to place an order.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Below is a letter I wrote them yesterday. I encourage anyone who has also had this problem and would like them to expedite a solution to write them as well at: <a href="mailto:support@toasttakeout.zendesk.com">support@toasttakeout.zendesk.com</a><o:p></o:p></p><p class=MsoNormal>That’s their support system, so it will undoubtedly take some tenacity to get this issue elevated to someone who can actually do something about it, but hey, we’re Federationists; this is what we do!<o:p></o:p></p><p class=MsoNormal>Oh, and if anyone out there can still order via Toast, please let me know if I’m overblowing this. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Here’s my letter. Feel free to use it as a template, and let me know if I missed anything that you feel we should highlight.<o:p></o:p></p><div style='mso-element:para-border-div;border:none;border-bottom:solid windowtext 1.0pt;padding:0in 0in 1.0pt 0in'><p class=MsoNormal style='border:none;padding:0in'><o:p> </o:p></p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Subject: Urgent: Toast Customer Ordering Screens Inaccessible<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Hi there,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I’m writing to inform you about a critical accessibility issue with your item ordering screen. This problem affects both the app and the website.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Within the last few months, you made changes to how the controls on this screen are labeled, specifically the radio buttons and checkboxes which enable the customer to customize an item. These labels are now completely unreadable by screen readers for the blind. I’ve confirmed this on Voiceover for the iPhone as well as Jaws and NVDA for the PC.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>What this means in practice is that it is now impossible for blind people to place orders with any of your client restaurants, and as you may or may not know, takeout and delivery is very popular within our ever-widening demographic. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>To get a little technical for a sec: Each control anywhere in your application, (web, IOS, Android and otherwise,) should have a text label or some sort of alternative attribute, such as an “alt” tag in HTML,) that enables screen readers to associate an understandable text label with each control, whether that be the Add button, a quantity edit field, or a checkbox for a particular pizza topping. When a label solely consists of an icon, as many now appear to, it’s useless to a blind person with a screen reader. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Your apps worked just fine in the past, so hopefully you can undo whatever you did to cause this situation. I’m sure the solution will be more complex than that, but I, along with members of the National Federation of The Blind, stand ready to assist if your dev team needs anyone to help test any solution they come up with.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>So, please, escalate this to the proper team so that we can resolve this in short order. Thousands of blind people, not to mention your client restaurants, will appreciate it.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks for your time and attention.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Cheers,<o:p></o:p></p><p class=MsoNormal>Tim<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>