Config option - injecting document.domain

docs/accessibility/changelog.mdx

@@ -7,10 +7,6 @@ sidebar_position: 200
 
 # Changelog
 
-## Week of 11/11/2024
-
-- A "Share Issue" button has been added to the element details section for each reported rule violation. This allows for easily copying the key details and related links for a particular issue into your clipboard to add to a message or to a ticket in your issue tracking system.
-
 ## Week of 10/28/2024
 
 - Our [Axe Core® versioning policy](/accessibility/core-concepts/how-it-works#Axe-Core-updates) has been published, providing a 30-day buffer between any Axe Core® releases and the adoption of those releases in Cypress Cloud.

docs/accessibility/configuration/axe-core-configuration.mdx

@@ -8,7 +8,7 @@ sidebar_label: 'Axe Core® configuration'
 
 <AccessibilityAddon />
 
-Configuration for Axe-Core® rules is available through your Account Executive. We are happy to have a call with you to dial in your report config to make sure you are getting the most useful reports possible, and we find this onboarding very effective.
+Configuration for Axe-Core® rules is available through your Account Executive. We we are happy to have a call with you to dial in your report config to make sure you are getting the most useful reports possible, and we find this onboarding very effective.
 
 In most cases, configuration of these rules as they run in Cypress Cloud isn't needed, because your implementation of any policies about what should "fail a build" is handled using the [Accessibility Results API](/accessibility/results-api), where you have full control over how to parse the results and what rules need to be reacted to. Keeping the results in Cypress Cloud broad helps you to still be able to see and understand all of the accessibility information, even if only a subset of the results would be considered blocking.
 
@@ -24,7 +24,7 @@ In most cases, configuration of these rules as they run in Cypress Cloud isn't n
 
 ## Component Testing
 
-Cypress Accessibility works great with component testing. In addition the rules that are off by default, "page-level" rules do not run for component tests, since a component is usually a fragment mounted in an empty page that would not be expected to have things like headings or a `main` element.
+Cypress Accessibility works great with component testing. In addition the the rules that are off by default, "page-level" rules do not run for component tests, since a component is usually a fragment mounted in an empty page that would not be expected to have things like headings or a `main` element.
 
 ## Updates to the Axe Core® library
 

docs/accessibility/core-concepts/how-it-works.mdx

@@ -11,7 +11,7 @@ The stages of the Cypress Accessibility process are as follows:
 
 1. As your run is recorded and specs are uploaded to Cypress Cloud, accessibility checks begin, based on the incoming [Test Replay](/cloud/features/test-replay) data, on the Cypress Cloud servers.
 1. When your run completes, the final specs are processed for accessibility checks. All earlier specs have already entered processing and are likely completed by the end of the run.
-1. Cypress Cloud organizes all the Views (pages and components) that were rendered during the run, merging and deduplicating across tests so that page-level results and live DOM snapshots can be grouped together.
+1. Cypress Cloud organizes all the the Views (pages and components) that were rendered during the run, merging and deduplicating across tests so that page-level results and live DOM snapshots can be grouped together.
 1. A combined "rule-level" report is created.
 1. The completed results are displayed in Cypress Cloud and are flagged in integrations such Slack as GitHub/Gitlab comments, and available CI via the Results API so that you can optionally fail your pipeline if your standards are not met.
 

docs/accessibility/get-started/introduction.mdx

@@ -15,7 +15,7 @@ Looking for a general guide for Accessibility testing in Cypress App? [Go here](
 
 <Btn
   label="Request trial ➜"
-  variant="indigo-dark"
+  variant="purple-dark"
   href="https://www.cypress.io/accessibility?utm_medium=intro-cta&utm_source=docs.cypress.io&utm_content=Request%20trial"
 />
 <Btn
@@ -42,8 +42,6 @@ You'll start your [free trial](https://www.cypress.io/accessibility?utm_medium=i
 from our sales team and your existing test data to instantly see full accessibility reports for all your Cypress projects.
 From there, you can integrate with CI to set your own standards for handling the results.
 
-[Get started with Cypress Accessibility ➜](/accessibility/get-started/setup)
-
 ## How it Works
 
 Cypress Accessibility provides organized, visual, and actionable accessibility reports, based completely on the tests you record to Cypress Cloud, and powered by Axe Core® by Deque Systems. This is the documentation page for that product. To learn about the general topic of accessibility testing using the Cypress App, see [our guide on this topic](/app/guides/accessibility-testing).