<?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>idea Set/Choose Reading Order for Screen Readers in ArcGIS Experience Builder in ArcGIS Experience Builder Ideas</title>
    <link>https://community.esri.com/t5/arcgis-experience-builder-ideas/set-choose-reading-order-for-screen-readers-in/idi-p/1717324</link>
    <description>&lt;P data-unlink="true"&gt;The ability to set/choose the reading order of screen readers (an accessibility tool) is currently available for PDF Layouts in ArcGIS Pro 3.7: &lt;A title="Provide the ability to set the reading order for screen readers" href="https://community.esri.com/t5/arcgis-pro-ideas/provide-the-ability-to-set-the-reading-order-for/idi-p/1271498" target="_self"&gt;ArcGIS Idea&lt;/A&gt;&amp;nbsp;&amp;amp; &lt;A title="Updates to Accessible PDFs in ArcGIS Pro 3.7" href="https://www.esri.com/arcgis-blog/products/arcgis-pro/mapping/updates-to-accessible-pdfs-in-arcgis-pro-3-7" target="_self"&gt;Esri Documentation&lt;/A&gt;. The same functionality would be extremely beneficial in Experience Builder. According to the Esri Community post&amp;nbsp;&lt;A title="Accessibility best practices for ArcGIS Experience Builder" href="https://community.esri.com/t5/arcgis-experience-builder-blog/accessibility-best-practices-for-arcgis-experience/ba-p/1300778" target="_self"&gt;Accessibility best practices for ArcGIS Experience Builder&lt;/A&gt;, "&lt;SPAN&gt;By default, in a fixed layout, the tab order follows the order widgets/elements are added."&lt;/SPAN&gt;&lt;/P&gt;&lt;P data-unlink="true"&gt;The Experience Builder A11Y setting is helpful, but is not perfect. It often requires reformatting to trigger corrections if the setting is turned on after app building has begun. More information about the A11Y tool can be found in the &lt;A title="Accessibility best practices for ArcGIS Experience Builder: Evaluate your layout designs for the app" href="https://community.esri.com/t5/arcgis-experience-builder-blog/accessibility-best-practices-for-arcgis-experience/ba-p/1300778#:~:text=To%20resolve%20this,calculate%20the%20orders." target="_self"&gt;Evaluate your layout designs for the app&lt;/A&gt; section of the post referenced above.&lt;/P&gt;&lt;P data-unlink="true"&gt;&lt;STRONG&gt;The ability to set/choose the reading order of screen readers or to make modifications to the default or A11Y reading order, whether for unique use cases or to implement corrections, is critical to producing accessible web applications.&lt;/STRONG&gt;&amp;nbsp;State and local governments must comply with &lt;A title="Accessibility of Web Content and Mobile Apps Provided by State and Local Government Entities: A Small Entity Compliance Guide" href="https://www.ada.gov/resources/small-entity-compliance-guide/" target="_self"&gt;Title II of the Americans with Disabilities Act (ADA)&lt;/A&gt; (effective April 26th, 2027 for total populations of 50,000+) and the federal government must comply with&amp;nbsp;&lt;A title="Section 508" href="https://www.section508.gov/" target="_self"&gt;Section 508&lt;/A&gt;. Regardless of requirements, accessible content improves the experience for all users, and this addition to the accessibility settings of Experience Builder would do exactly that.&lt;/P&gt;</description>
    <pubDate>Wed, 29 Jul 2026 15:40:00 GMT</pubDate>
    <dc:creator>AuroraB</dc:creator>
    <dc:date>2026-07-29T15:40:00Z</dc:date>
    <item>
      <title>Set/Choose Reading Order for Screen Readers in ArcGIS Experience Builder</title>
      <link>https://community.esri.com/t5/arcgis-experience-builder-ideas/set-choose-reading-order-for-screen-readers-in/idi-p/1717324</link>
      <description>&lt;P data-unlink="true"&gt;The ability to set/choose the reading order of screen readers (an accessibility tool) is currently available for PDF Layouts in ArcGIS Pro 3.7: &lt;A title="Provide the ability to set the reading order for screen readers" href="https://community.esri.com/t5/arcgis-pro-ideas/provide-the-ability-to-set-the-reading-order-for/idi-p/1271498" target="_self"&gt;ArcGIS Idea&lt;/A&gt;&amp;nbsp;&amp;amp; &lt;A title="Updates to Accessible PDFs in ArcGIS Pro 3.7" href="https://www.esri.com/arcgis-blog/products/arcgis-pro/mapping/updates-to-accessible-pdfs-in-arcgis-pro-3-7" target="_self"&gt;Esri Documentation&lt;/A&gt;. The same functionality would be extremely beneficial in Experience Builder. According to the Esri Community post&amp;nbsp;&lt;A title="Accessibility best practices for ArcGIS Experience Builder" href="https://community.esri.com/t5/arcgis-experience-builder-blog/accessibility-best-practices-for-arcgis-experience/ba-p/1300778" target="_self"&gt;Accessibility best practices for ArcGIS Experience Builder&lt;/A&gt;, "&lt;SPAN&gt;By default, in a fixed layout, the tab order follows the order widgets/elements are added."&lt;/SPAN&gt;&lt;/P&gt;&lt;P data-unlink="true"&gt;The Experience Builder A11Y setting is helpful, but is not perfect. It often requires reformatting to trigger corrections if the setting is turned on after app building has begun. More information about the A11Y tool can be found in the &lt;A title="Accessibility best practices for ArcGIS Experience Builder: Evaluate your layout designs for the app" href="https://community.esri.com/t5/arcgis-experience-builder-blog/accessibility-best-practices-for-arcgis-experience/ba-p/1300778#:~:text=To%20resolve%20this,calculate%20the%20orders." target="_self"&gt;Evaluate your layout designs for the app&lt;/A&gt; section of the post referenced above.&lt;/P&gt;&lt;P data-unlink="true"&gt;&lt;STRONG&gt;The ability to set/choose the reading order of screen readers or to make modifications to the default or A11Y reading order, whether for unique use cases or to implement corrections, is critical to producing accessible web applications.&lt;/STRONG&gt;&amp;nbsp;State and local governments must comply with &lt;A title="Accessibility of Web Content and Mobile Apps Provided by State and Local Government Entities: A Small Entity Compliance Guide" href="https://www.ada.gov/resources/small-entity-compliance-guide/" target="_self"&gt;Title II of the Americans with Disabilities Act (ADA)&lt;/A&gt; (effective April 26th, 2027 for total populations of 50,000+) and the federal government must comply with&amp;nbsp;&lt;A title="Section 508" href="https://www.section508.gov/" target="_self"&gt;Section 508&lt;/A&gt;. Regardless of requirements, accessible content improves the experience for all users, and this addition to the accessibility settings of Experience Builder would do exactly that.&lt;/P&gt;</description>
      <pubDate>Wed, 29 Jul 2026 15:40:00 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-experience-builder-ideas/set-choose-reading-order-for-screen-readers-in/idi-p/1717324</guid>
      <dc:creator>AuroraB</dc:creator>
      <dc:date>2026-07-29T15:40:00Z</dc:date>
    </item>
    <item>
      <title>Re: Set/Choose Reading Order for Screen Readers in ArcGIS Experience Builder</title>
      <link>https://community.esri.com/t5/arcgis-experience-builder-ideas/set-choose-reading-order-for-screen-readers-in/idc-p/1717441#M5620</link>
      <description>&lt;P&gt;It is very nice and convenient if users can choose the reading order in&amp;nbsp;Experience Builder as well, it also helps working efficiently&lt;BR /&gt;&lt;BR /&gt;If this idea can be done, it will definitely be helpful for my Experience Builder project. The mismatching PDF&amp;nbsp;&lt;SPAN&gt;accessibility&lt;/SPAN&gt;&amp;nbsp;between the ArcGIS Pro and Experience Builder could cause our end users more confusion when they navigate the&amp;nbsp;Experience Builder Apps.&lt;/P&gt;</description>
      <pubDate>Wed, 29 Jul 2026 19:18:26 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-experience-builder-ideas/set-choose-reading-order-for-screen-readers-in/idc-p/1717441#M5620</guid>
      <dc:creator>zhouy</dc:creator>
      <dc:date>2026-07-29T19:18:26Z</dc:date>
    </item>
  </channel>
</rss>

