<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Accessibility of apps created in web app builder (UK) in Accessibility Questions</title>
    <link>https://community.esri.com/t5/accessibility-questions/accessibility-of-apps-created-in-web-app-builder/m-p/807648#M38</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Have you heard any update on the accessibility (specifically screen reader, and keyboard navigation functionality) of widgets in WAB?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 14 Nov 2018 16:53:10 GMT</pubDate>
    <dc:creator>TimWilliams6</dc:creator>
    <dc:date>2018-11-14T16:53:10Z</dc:date>
    <item>
      <title>Accessibility of apps created in web app builder (UK)</title>
      <link>https://community.esri.com/t5/accessibility-questions/accessibility-of-apps-created-in-web-app-builder/m-p/807643#M33</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have produced a map in WAB (developer edition) and our website team want to know about how accessible it is.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In terms of being responsive, it works well on all devices, although it is better when not in an iframe on the corporate website. As it appears that the full screen widget doesn't work in when if an iframe, I think we will just also have a link to the actual web app, unless anyone else has any good ideas in this!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As for complying with the Equality Act (2010) and meeting WCAG 2.0 guidelines, I am unsure what to do. I have tried looking on here and not found much really. I see ESRI have published some templates saying how the US regulations are being addressed (&lt;A class="link-titled" href="http://www.esri.com/legal/section508/swguide" title="http://www.esri.com/legal/section508/swguide"&gt;Legal Information | Voluntary Product Accessibility Templates (VPATs) | Software&lt;/A&gt;&amp;nbsp;)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I know maps are not going to be fully accessible to those with visual imparments but I don't appear to be able to control the app without a mouse, which I was hoping to be able to do. I see there is the AccessifizrWidget (&lt;A class="link-titled" href="https://github.com/cmndrbensisko/AccessifizrWidget" title="https://github.com/cmndrbensisko/AccessifizrWidget"&gt;GitHub - cmndrbensisko/AccessifizrWidget: The Accessifizr Widget is designed to easily port Accessifizr functionality in…&lt;/A&gt;&amp;nbsp;) - does anyone know how to use this and if it does the job, or if there are any alternatives?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The other issue is screen reader compatibility. Is it possible for a screen reader to work with a mapping app?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Jan 2018 15:25:51 GMT</pubDate>
      <guid>https://community.esri.com/t5/accessibility-questions/accessibility-of-apps-created-in-web-app-builder/m-p/807643#M33</guid>
      <dc:creator>MarkCooper5</dc:creator>
      <dc:date>2018-01-24T15:25:51Z</dc:date>
    </item>
    <item>
      <title>Re: Accessibility of apps created in web app builder (UK)</title>
      <link>https://community.esri.com/t5/accessibility-questions/accessibility-of-apps-created-in-web-app-builder/m-p/807644#M34</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mark,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As a starting point, we have an article in this group:&amp;nbsp;&lt;A href="https://community.esri.com/docs/DOC-10853"&gt;The Top Five Accessibility Requirements&lt;/A&gt;. If your web app can meet those five requirements, it will be accessible to a large group of users who use keyboard only or screen readers, or have low vision or color-blindness. Those five requirements are part of the WCAG 2.0 guidelines. By working through them, you will get a better idea of how to meet other WCAG 2.0 guidelines.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Particularly, in order for you to use keyboard only to use the app, all the interactive elements in your app like links, buttons, menus, and form controls should be able to receive keyboard focus and respond to keyboard events. One common issue we see is that &amp;lt;div&amp;gt; or &amp;lt;span&amp;gt; are used for buttons or links, but they don't have "tabindex = '0'" to receive keyboard focus or JavaScript to respond to key presses.&amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As for screen readers and information on map, we have&amp;nbsp;&lt;SPAN style="background-color: #ffffff;"&gt;created a demo app to start exploring ideas around making the map accessible:&amp;nbsp;&lt;A href="https://community.esri.com/external-link.jspa?url=https%3A%2F%2Fkellyhutchins.github.io%2Fa11y-map%2Findex.html" rel="nofollow" style="color: #287433; border: 0px; text-decoration: underline; padding: 0px calc(12px + 0.35ex) 0px 0px;" target="_blank"&gt;A11y Map&lt;/A&gt;.&amp;nbsp;&lt;SPAN style="background-color: #ffffff;"&gt;We'd love if you could take some time to explore the demo map and provide us feedback on the process. If you are a developer you can access the source code on&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;A class="" href="https://community.esri.com/external-link.jspa?url=https%3A%2F%2Fgithub.com%2Fkellyhutchins%2Fa11y-map" rel="nofollow" style="color: #287433; background-color: #ffffff; border: 0px; text-decoration: none; padding: 0px calc(12px + 0.35ex) 0px 0px;" target="_blank"&gt;GitHub&lt;/A&gt;.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Jan 2018 16:37:25 GMT</pubDate>
      <guid>https://community.esri.com/t5/accessibility-questions/accessibility-of-apps-created-in-web-app-builder/m-p/807644#M34</guid>
      <dc:creator>Anonymous User</dc:creator>
      <dc:date>2018-01-24T16:37:25Z</dc:date>
    </item>
    <item>
      <title>Re: Accessibility of apps created in web app builder (UK)</title>
      <link>https://community.esri.com/t5/accessibility-questions/accessibility-of-apps-created-in-web-app-builder/m-p/807645#M35</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks, that is really helpful. I have looked at your template and it looks great.&amp;nbsp; Unfortunately we are reliant on the apps that ESRI supply and the full functionality of their widgets. It appears that it is not possible to tab to each of the widgets or navigate the map in them.&amp;nbsp;I particularly like the way you can navigate with a keyboard on your app - that would make an great custom widget for WAB (assuming you could tab to it).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We only use WAP developer to hide various elements in in the widgets or change the colour of the icons. As we are not&amp;nbsp;developers, we are unable to develop an app in the Java API. I don't suppose there is a simple change the tab index in an app created in Web App Builder?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Jan 2018 10:51:02 GMT</pubDate>
      <guid>https://community.esri.com/t5/accessibility-questions/accessibility-of-apps-created-in-web-app-builder/m-p/807645#M35</guid>
      <dc:creator>MarkCooper5</dc:creator>
      <dc:date>2018-01-25T10:51:02Z</dc:date>
    </item>
    <item>
      <title>Re: Accessibility of apps created in web app builder (UK)</title>
      <link>https://community.esri.com/t5/accessibility-questions/accessibility-of-apps-created-in-web-app-builder/m-p/807646#M36</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We heard feedback on the accessibility of WAB widgets before and I think the team are planning to address those accessibility issues.&amp;nbsp;I am not quite sure whether it is possible to set `tabindex` on existing widgets or controls.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.esri.com/migrated-users/3176"&gt;Derek Law&lt;/A&gt;‌ may have more information on this.&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Jan 2018 16:23:01 GMT</pubDate>
      <guid>https://community.esri.com/t5/accessibility-questions/accessibility-of-apps-created-in-web-app-builder/m-p/807646#M36</guid>
      <dc:creator>Anonymous User</dc:creator>
      <dc:date>2018-01-25T16:23:01Z</dc:date>
    </item>
    <item>
      <title>Re: Accessibility of apps created in web app builder (UK)</title>
      <link>https://community.esri.com/t5/accessibility-questions/accessibility-of-apps-created-in-web-app-builder/m-p/807647#M37</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Do you know if it would be possible to add your navigation tool as a widget? It would be really useful. As a non developer, I wouldn't have a clue!!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 12 Feb 2018 14:53:54 GMT</pubDate>
      <guid>https://community.esri.com/t5/accessibility-questions/accessibility-of-apps-created-in-web-app-builder/m-p/807647#M37</guid>
      <dc:creator>MarkCooper5</dc:creator>
      <dc:date>2018-02-12T14:53:54Z</dc:date>
    </item>
    <item>
      <title>Re: Accessibility of apps created in web app builder (UK)</title>
      <link>https://community.esri.com/t5/accessibility-questions/accessibility-of-apps-created-in-web-app-builder/m-p/807648#M38</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Have you heard any update on the accessibility (specifically screen reader, and keyboard navigation functionality) of widgets in WAB?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Nov 2018 16:53:10 GMT</pubDate>
      <guid>https://community.esri.com/t5/accessibility-questions/accessibility-of-apps-created-in-web-app-builder/m-p/807648#M38</guid>
      <dc:creator>TimWilliams6</dc:creator>
      <dc:date>2018-11-14T16:53:10Z</dc:date>
    </item>
    <item>
      <title>Re: Accessibility of apps created in web app builder (UK)</title>
      <link>https://community.esri.com/t5/accessibility-questions/accessibility-of-apps-created-in-web-app-builder/m-p/807649#M39</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV class=""&gt;Hi Tim,&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;FYI, in the &lt;A href="https://www.esri.com/arcgis-blog/products/arcgis-online/announcements/whats-new-in-arcgis-online-march-2019/"&gt;ArcGIS Online March 2019 update&lt;/A&gt;, Web AppBuilder for ArcGIS has been enhanced with more accessibility support. Please see this help topic for details,&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;A class="link-titled" href="http://doc.arcgis.com/en/web-appbuilder/create-apps/accessibility-support.htm" title="http://doc.arcgis.com/en/web-appbuilder/create-apps/accessibility-support.htm"&gt;Accessibility support—Web AppBuilder for ArcGIS | ArcGIS&lt;/A&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;Hope this helps,&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 07 Apr 2019 18:22:26 GMT</pubDate>
      <guid>https://community.esri.com/t5/accessibility-questions/accessibility-of-apps-created-in-web-app-builder/m-p/807649#M39</guid>
      <dc:creator>DerekLaw</dc:creator>
      <dc:date>2019-04-07T18:22:26Z</dc:date>
    </item>
    <item>
      <title>Re: Accessibility of apps created in web app builder (UK)</title>
      <link>https://community.esri.com/t5/accessibility-questions/accessibility-of-apps-created-in-web-app-builder/m-p/807650#M40</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;FYI,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There were some enhancements made to Web AppBuilder for ArcGIS in the ArcGIS Online Oct 2019 update to better support accessibility requirements,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://www.esri.com/arcgis-blog/products/web-appbuilder/sharing-collaboration/how-accessibility-features-work-in-web-appbuilder-apps/" title="https://www.esri.com/arcgis-blog/products/web-appbuilder/sharing-collaboration/how-accessibility-features-work-in-web-appbuilder-apps/"&gt;How accessibility features work in Web AppBuilder apps&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG class="image-1 jive-image" src="https://community.esri.com/legacyfs/online/467390_pastedImage_2.png" /&gt;&lt;/P&gt;&lt;P&gt;Hope this helps,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Oct 2019 20:39:14 GMT</pubDate>
      <guid>https://community.esri.com/t5/accessibility-questions/accessibility-of-apps-created-in-web-app-builder/m-p/807650#M40</guid>
      <dc:creator>DerekLaw</dc:creator>
      <dc:date>2019-10-23T20:39:14Z</dc:date>
    </item>
  </channel>
</rss>

