anchor.diff:          <p><b>Interactive tools and transactions</b></p>
           <p>Our maps are difficult to navigate using a keyboard. For example, because some form controls are missing a ‘label’ tag.</p>
           <p>Our maps are built and hosted through third party software and ‘skinned’ to look like our website. This fails WCAG 2.1 success criterion 1.3.1 (information and relationships).</p>
  -        <p>We’ve assessed the cost of fixing the issues with navigation and accessing information, and with interactive tools and transactions. We believe that doing so now would be a <a href="www.legislation.gov.uk/uksi/2018/952/regulation/7/made" target="_BLANK">disproportionate burden</a> within the meaning of the accessibility regulations. We will make another assessment in March 2020.</p>
  +        <p>We’ve assessed the cost of fixing the issues with navigation and accessing information, and with interactive tools and transactions. We believe that doing so now would be a <a href="www.legislation.gov.uk/uksi/2018/952/regulation/7/made" target="_BLANK">disproportionate burden</a> within the meaning of the accessibility regulations. We will make another assessment in late 2020.</p>
           <h3>Content that’s not within the scope of the accessibility regulations</h3>
           <p><b>PDFs and other documents</b></p>
           <p>Many of our older PDFs and Word documents do not meet accessibility standards - for example, they may not be structured so they’re accessible to a screen reader. This does not meet WCAG 2.1 success criterion 4.1.2 (name, role value).</p>
           <p>The accessibility regulations <a href="www.legislation.gov.uk/uksi/2018/952/regulation/4/made" target="_BLANK">do not require us to fix PDFs or other documents published before 23 September 2018</a> if they’re not essential to providing our services. For example, we do not plan to fix project documents.</p>
           <h3>How we tested this website</h3>
  -        <p>This website was last tested on8 November 2019. The test was carried out by DFID.</p>
  +        <p>This website was last tested on8 November 2019. The test was carried out by FCDO (The Department for International Development, at the time).</p>
           <p>We tested every page type on DevTracker using <a href="https://wave.webaim.org/" target="_BLANK">WAVE</a>.</p>
           <h3>What we’re doing to improve accessibility</h3>
           <p>We are currently working  to continue to improve DevTrackers accessibility. In particular we are looking to engage our users more, to understand what remaining accessibility issues are affecting them most, so we can better prioritise.</p>
  -        <p>This statement was prepared on 11 November 2019. It was last updated on 11 November 2019.</p>
  +        <p>This statement was prepared on 11 November 2019. It was last updated on 11 August 2020.</p>
       </div>
   </div>
  
positive.code:         <h3>Enforcement procedure</h3>
          <p>The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the ‘accessibility regulations’). If you’re not happy with how we respond to your complaint, <a href="https://www.equalityadvisoryservice.com/" target="_BLANK">contact the Equality Advisory and Support Service (EASS)</a>.</p>
          <h3>Technical information about this website’s accessibility</h3>
          <p>DFID is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.</p>
          <p>This website is partially compliant with the <a href="https://www.w3.org/TR/WCAG21/" target="_BLANK">Web Content Accessibility Guidelines version 2.1</a> AA standard, due to the non-compliances listed below.</p>
          <h3>Non accessible content</h3>
          <p>The content listed below is non-accessible for the following reasons.</p>
          <h3>Non compliance with the accessibility regulations</h3>
          <p>Some images, and the maps available on activity pages, do not have a text alternative, so people using a screen reader cannot access the information. This fails WCAG 2.1 success criterion 1.1.1 (non-text content).</p>
          <p>We plan to add text alternatives for all images by September 2020. When we publish new content we’ll make sure our use of images meets accessibility standards.</p>
          <h3>Disproportionate burden</h3>
          <p><b>Navigation and accessing information</b></p>
          <p>There’s no way to skip the repeated content in the page header (for example, a ‘skip to main content’ option). This fails WCAG 2.1 success criterion 2.4.1 (bypass blocks).</p>
  
negative.code: <div class="row">
      <div class="twelve columns">
          <h3>Accessibility statement for DevTracker</h3>
          <p>This website is run by the Foreign, Commonwealth and Development Office (FCDO). We want as many people as possible to be able to use this website. For example, that means you should be able to:</p>
          <ul class="pad-30">
              <li>change colours, contrast levels and fonts</li>
              <li>zoom in up to 500% without the text spilling off the screen</li>
  