{
  "doc": {
    "id": "accessibility/guides/production-monitoring",
    "title": "Production monitoring | Cypress Accessibility Documentation",
    "description": "Monitor accessibility issues in production by running scheduled Cypress tests against live environments, capturing dynamic content changes, and generating automated reports for a comprehensive accessibility overview.",
    "section": "accessibility",
    "source_path": "/llm/markdown/accessibility/guides/production-monitoring.md",
    "version": "24a73f8a97175663aaffd3b016289fb2a523a4ea",
    "updated_at": "2026-05-14T20:17:33.301Z",
    "headings": [
      {
        "id": "accessibility/guides/production-monitoring#production-monitoring-and-website-crawling",
        "text": "Production monitoring and website crawling",
        "level": 1
      },
      {
        "id": "accessibility/guides/production-monitoring#using-cypress-for-production-monitoring",
        "text": "Using Cypress for production monitoring",
        "level": 2
      },
      {
        "id": "accessibility/guides/production-monitoring#example-automated-sitemap-based-testing",
        "text": "Example: Automated Sitemap-Based Testing",
        "level": 2
      }
    ]
  },
  "chunks": [
    {
      "id": "accessibility/guides/production-monitoring#using-cypress-for-production-monitoring",
      "doc_id": "accessibility/guides/production-monitoring",
      "heading": "Using Cypress for production monitoring",
      "heading_level": 2,
      "content_markdown": "## Using Cypress for production monitoring\n\nCypress Accessibility enables you to test dynamic content seamlessly. By visiting a production URL within your Cypress tests and performing minimal UI interactions, you can capture the page's accessibility state in reports. This allows teams to detect accessibility issues introduced outside the regular development lifecycle.\n",
      "section": "accessibility",
      "anchors": [
        "using-cypress-for-production-monitoring"
      ],
      "path": "/llm/json/chunked/accessibility/guides/production-monitoring.json",
      "token_estimate": 68
    },
    {
      "id": "accessibility/guides/production-monitoring#example-automated-sitemap-based-testing",
      "doc_id": "accessibility/guides/production-monitoring",
      "heading": "Example: Automated Sitemap-Based Testing",
      "heading_level": 2,
      "content_markdown": "## Example: Automated Sitemap-Based Testing\n\nIf your project lacks existing Cypress tests, a common approach is to generate test coverage from a sitemap or an array of target URLs. These URLs can be used to perform light interactions and capture accessibility reports. Below is an example of how to automate this process by using a sitemap and scrolling to the footer on each page:\n\n```\ndescribe('Accessibility Scan', () => {  it('Checks accessibility with the sitemap.xml', () => {    cy.request('https://<YOUR_WEBSITE>/sitemap.xml').then((response) => {      const xmlString = response.body      const parser = new DOMParser()      const xmlDoc = parser.parseFromString(xmlString, 'application/xml')      const URLs = Array.from(xmlDoc.querySelectorAll('loc')).map(        (loc) => loc.textContent      )      Cypress._.each(URLs, (URL) => {        cy.visit(URL)        cy.contains('<YOUR_FOOTER_CONTENT>').scrollIntoView()        // perform some repeatable actions here that influence accessibility, for example:        //  - change from light mode to dark mode        //  - modify the viewport size to simulate mobile screens and higher zoom levels      })    })  })})\n```\n\nThe outcome of this is a first-page-load accessibility report for every URL in the site. Any Cypress UI tests for specific workflows will increase the coverage area automatically to include the states and variations reached during the workflows.\n",
      "section": "accessibility",
      "anchors": [
        "example-automated-sitemap-based-testing"
      ],
      "path": "/llm/json/chunked/accessibility/guides/production-monitoring.json",
      "token_estimate": 247
    }
  ]
}