<?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 Export Layout Accessibility Prefills in ArcGIS Pro Ideas</title>
    <link>https://community.esri.com/t5/arcgis-pro-ideas/export-layout-accessibility-prefills/idi-p/1656726</link>
    <description>&lt;P&gt;I am using ArcGIS Pro 3.5.2 and I've recently started looking what ArcGIS Pro offers for exporting PDFs with accessibility metadata. For the "Accessibility" tab for the "Export Layout" tool with PDFs, I noticed that if I enter information in for the accessibility inputs in one project that it carries over what I input into other projects. The reasoning behind this might make sense because ArcGIS Pro does this for all the other settings in the "Export Layout" so that you don't have to enter in the same settings every single time.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It does not make sense for the "Accessibility" tab's "PDF Metadata" settings though as it will apply that Title, Keywords, etc to every layout I make which will 99% of the time have different titles and other metadata. If I had not realized it was doing this all my future PDFs would have a title of "Hole 1 Irrigation Utilities". Image below shows my inputs from a different project.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ExportAccessibility.png" style="width: 400px;"&gt;&lt;img src="https://community.esri.com/t5/image/serverpage/image-id/141684i5D0CCD5C41810C9B/image-size/medium?v=v2&amp;amp;px=400" role="button" title="ExportAccessibility.png" alt="ExportAccessibility.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;As an Idea, I would like to request that the "Accessibility" tab's "PDF Metadata" inputs do not carry over from other projects. Force the user to fill them out each time to ensure that the correct information is being exported.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;As a note: I will also be creating another idea requesting that the layout properties be the place for you to store this information. I can't foresee a situation where a Layout would need to be exported with different tags each time it is exported so I don't know why it was decided to put these inputs in this tool vs. layout properties.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;</description>
    <pubDate>Fri, 10 Oct 2025 19:52:49 GMT</pubDate>
    <dc:creator>BrettFrahm</dc:creator>
    <dc:date>2025-10-10T19:52:49Z</dc:date>
    <item>
      <title>Export Layout Accessibility Prefills</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/export-layout-accessibility-prefills/idi-p/1656726</link>
      <description>&lt;P&gt;I am using ArcGIS Pro 3.5.2 and I've recently started looking what ArcGIS Pro offers for exporting PDFs with accessibility metadata. For the "Accessibility" tab for the "Export Layout" tool with PDFs, I noticed that if I enter information in for the accessibility inputs in one project that it carries over what I input into other projects. The reasoning behind this might make sense because ArcGIS Pro does this for all the other settings in the "Export Layout" so that you don't have to enter in the same settings every single time.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It does not make sense for the "Accessibility" tab's "PDF Metadata" settings though as it will apply that Title, Keywords, etc to every layout I make which will 99% of the time have different titles and other metadata. If I had not realized it was doing this all my future PDFs would have a title of "Hole 1 Irrigation Utilities". Image below shows my inputs from a different project.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ExportAccessibility.png" style="width: 400px;"&gt;&lt;img src="https://community.esri.com/t5/image/serverpage/image-id/141684i5D0CCD5C41810C9B/image-size/medium?v=v2&amp;amp;px=400" role="button" title="ExportAccessibility.png" alt="ExportAccessibility.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;As an Idea, I would like to request that the "Accessibility" tab's "PDF Metadata" inputs do not carry over from other projects. Force the user to fill them out each time to ensure that the correct information is being exported.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;As a note: I will also be creating another idea requesting that the layout properties be the place for you to store this information. I can't foresee a situation where a Layout would need to be exported with different tags each time it is exported so I don't know why it was decided to put these inputs in this tool vs. layout properties.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;</description>
      <pubDate>Fri, 10 Oct 2025 19:52:49 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/export-layout-accessibility-prefills/idi-p/1656726</guid>
      <dc:creator>BrettFrahm</dc:creator>
      <dc:date>2025-10-10T19:52:49Z</dc:date>
    </item>
    <item>
      <title>Re: Export Layout Accessibility Prefills</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/export-layout-accessibility-prefills/idc-p/1693393#M38001</link>
      <description>&lt;P&gt;I like this suggestion. Having these items carry over to other projects or maps makes it possible to have incorrect information exported. Ideally this info would be saved with a specific item but otherwise should not carry over and should be filled in each time.&lt;/P&gt;</description>
      <pubDate>Mon, 30 Mar 2026 14:45:00 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/export-layout-accessibility-prefills/idc-p/1693393#M38001</guid>
      <dc:creator>jchester73</dc:creator>
      <dc:date>2026-03-30T14:45:00Z</dc:date>
    </item>
  </channel>
</rss>

