Survey123 and ADA Accessibility

[ZachBodenner]

Hello,

This one might be more the Survey123 product owners: We are of course working on making sure that all of our web mapping applications meet ADA accessibility standards by next Spring. ESRI's Conformance Reports are really useful to see where we need to direct our efforts, but going through the Survey123 report, it's clear there are a number of areas where the product only partially meets requirements. 

I'm a little unsure of what exactly this means for continuing to use this product. If a web application does not completely, fully, meet these standards, do we need to scrap using it altogether? Is partially meeting some criteria sufficient enough to keep using a thing? If the answer is that we really should be using it in a public-facing manner, what are ESRi's plans to address the partial sufficiency? 

To other Members of the community, what have you done to bring your public Survey123 surveys into ADA compliance? Have any members of your organization given you any pushback on continued use of Survey123 or other ESRI products for this reason?

[SarahHurley1]

Hi Zach, 

I am also curious on others thoughts about this. At my office, we are working on putting together a guidance so other agencies can follow to create their web apps accessible to meet the deadline. However, I'm still not sure what to recommend for apps that have obvious spots that do not meet the accessibility guidelines. For example, the map element for Survey123 is not accessible because it's not keyboard operable. Do we recommend to not use the map element? Kind of a tough ask in the GIS industry. So I'm interested to hear others thoughts!

Sarah

[KeepItSimple_35]

I'd really love to see some suggestions here because I'm under the same pressures. I have a survey that I've created and spent a long time putting together to have it rejected by our technical services department and put on back burner for about 1.5-2 years. Then when I got back around to fixing it up and trying again it got rejected because we're also trying to go ADA compliant. I'm at a loss for how to implement some of the requirements for this project. 

Mark