Revert "Merge pull request #2855 from RushilK7/stage"

docs/accessibility-test-scheduling-crawler.md

@@ -108,7 +108,4 @@ You can drill down into individual URLs for a more detailed analysis of accessib
 > Note: The crawler functionality is available only when creating a new scheduled scan, not for scans that have already been scheduled.
 
 
-- [Test Scheduling - Sitemap (Overview)](/support/docs/accessibility-test-scheduling/)
-- [Login & Authentication for Scheduled Scans](/support/docs/accessibility-test-scheduling-login-authentication/)
-- [Create Scheduled Scan](/support/docs/accessibility-test-scheduling-scan/)
-- [Sitemap Extraction & URL Import](/support/docs/accessibility-sitemap-extraction-url-import/)
+

docs/accessibility-test-scheduling-scan.md

@@ -82,7 +82,7 @@ import BrandName, { BRAND_URL } from '@site/src/component/BrandName';
 
 ### Advanced Options
 - **Local Testing Setup (Tunnel) :** If scanning locally hosted URLs, add a Local Testing Setup/Tunnel to access non-public environments. <NewTag value="Upcoming" />
-- **Login Configuration :** For pages behind authentication, use **Add login configurations** to open the login modal, pick a saved profile, or create one (**Basic**, **Form**, or **Multi-page**). You can also manage profiles from the dashboard **Login configurations** entry. See **[Login & Authentication for Scheduled Scans](/support/docs/accessibility-test-scheduling-login-authentication/)**.
+- **Login Configuration :** For pages requiring authentication, configure the Login Settings by providing credentials or session details.
 - **Review Issues :** Enable Needs Review for areas requiring manual inspection.
 - **Best Practices Issues :** Check Best Practices to include suggestions for better accessibility.
 

docs/accessibility-test-scheduling.md

@@ -60,26 +60,7 @@ The Scheduled Accessibility Scan feature allows you to automate recurring or one
 - **Local and Authenticated Pages :** Configure scans for local environments and authenticated pages.
 - **Comprehensive Reporting :** Receive detailed scan reports via email and access them on the dashboard.
 
-## Typical workflow
-
-1. Create the scheduled scan.
-2. Add URLs manually, through CSV, or through sitemap extraction.
-3. Add **saved login configurations** (or tunnel / local access) if required—see [Login & Authentication for Scheduled Scans](/support/docs/accessibility-test-scheduling-login-authentication/).
-4. Set the schedule.
-5. Review the resulting reports.
-
-## Onboarding: schedule your first recurring scan
-
-1. Read **[Steps to Schedule an Accessibility Scan](/support/docs/accessibility-test-scheduling-scan/)** end-to-end once—menus use the same vocabulary as the live product.
-2. Seed URLs using **[Sitemap Extraction & URL Import](/support/docs/accessibility-sitemap-extraction-url-import/)** when you have more than a handful of pages.
-3. If pages sit behind login, open **Add login configurations** in Advanced options or use dashboard **Login configurations**, then attach a profile—see **[Login & Authentication for Scheduled Scans](/support/docs/accessibility-test-scheduling-login-authentication/)** (Basic, Form, Multi-page, or tunnel per your environment) before widening scope.
-4. Start with a **weekly** cadence on a **subset** of URLs; promote to daily only after noise is manageable.
-5. After the first run, open **[Navigating the Dashboard](/support/docs/accessibility-testing-navigating-dashboard/)** and confirm aggregates match expectations.
-6. Optional: enable **[Fragment Identifier](/support/docs/accessibility-fragment-identifier/)** in DevTools settings when hash routes should split reporting for SPA teams (web URL grouping only).
-
-## Related docs
-
-- [Login & Authentication for Scheduled Scans](/support/docs/accessibility-test-scheduling-login-authentication/)
-- [Steps to Schedule an Accessibility Scan](/support/docs/accessibility-test-scheduling-scan/)
-- [Sitemap Extraction & URL Import](/support/docs/accessibility-sitemap-extraction-url-import/)
-- [Crawler](/support/docs/accessibility-test-crawler/)
+## Use Case
+- **Developers :** Stay ahead of accessibility issues by scheduling regular scans and ensuring WCAG compliance throughout the development lifecycle.
+- **QA Testers :** Conduct detailed accessibility testing as part of their quality assurance workflows.
+- **Product Managers :** Monitor accessibility performance across websites to meet organizational and legal compliance requirements.

docs/accessibility-testing.md

@@ -44,33 +44,11 @@ import BrandName, { BRAND_URL } from '@site/src/component/BrandName';
     }}
 ></script>
 
-- **Manual Testing (DevTools)** -- browser-based scanning and assisted testing for websites and web apps.
-- **Automation** -- automated accessibility checks in supported test frameworks (Selenium, Cypress, Playwright, and more).
-- **Test Scheduling** -- recurring site scans driven by sitemaps, crawlers, or manual URL lists inside the Accessibility product (not the same doc set as the standalone Web Scanner product).
-- **Web Scanner** -- the separate **Web Scanner** product in the docs sidebar, where you add URLs and run accessibility scans on that surface. Use Accessibility **Test Scheduling** when your workflow is native to Accessibility scheduling, not Web Scanner.
-- **Mobile App Testing** -- manual and automated accessibility testing for native Android and iOS apps, including KaneAI-authored flows.
-- **Reports** -- dashboard, issue views, [exporting and sharing](/support/docs/accessibility-exporting-sharing-reports/), passed tests, and bug reporting (issue-tracker connections live under **External integrations** in the sidebar, not inside Reports).
-- **Integrations** (sidebar) -- **Integrations with TestMu AI products** (Web Scanner, KaneAI, HyperExecute with Selenium, and related surfaces) and **External integrations** (CI/CD, Jira/Slack) for how Accessibility connects to the rest of your toolchain.
-- **Features** (sidebar: **Web**, then **Mobile**, then **Common**) -- **Web**: hide/restore, AI issue detection, capture screenshot, web score, fragment identifier, and PDF scanning; **Mobile**: scan tags; **Common**: remediation guidance and analytics widgets.
-- **Checklists** -- coverage summaries, WCAG rule repositories, and manual verification guidance.
-- **Accessibility MCP Server** -- AI-assisted accessibility analysis only. For installing and configuring the **platform-wide** TestMu AI MCP Server (all tools), use [TestMu AI MCP Server](/support/docs/testmu-mcp-server/) in the main docs sidebar.
+<BrandName />’s Accessibility Testing Suite ensures digital experiences are accessible to everyone. Whether it's a website, web app, or mobile app, the suite simplifies the process of testing and improving accessibility. It offers various types of accessibility testing, including support for NVDA, VoiceOver, and TalkBack, ensuring seamless experiences for users with visual, motor, and hearing impairments. It helps businesses adhere to global accessibility standards while enhancing usability across platforms. Additionally, automated accessibility checks for both web and mobile apps streamline the testing process, ensuring compliance with global standards like WCAG.
 
 ## What is Accessibility Testing?
 
-| If you want to... | Start here |
-|-----|-----|
-| Test a website manually | [Manual Testing (DevTools)](/support/docs/accessibility-devtools/) |
-| Run your first browser scan quickly | [Run a Quick Scan](/support/docs/accessibility-testing-run-quick-scan/) |
-| Run automated web tests | [Automation](/support/docs/accessibility-automation/) |
-| Schedule recurring scans | [Test Scheduling](/support/docs/accessibility-test-scheduling/) |
-| Use Web Scanner for scans | [Web Scanner](/support/docs/web-scanner-getting-started/) |
-| Test a mobile app manually | [Manual App Scanner](/support/docs/accessibility-app-scanner/) |
-| Run mobile automation | [Appium Automation](/support/docs/accessibility-native-app-automation-test/) |
-| Author mobile flows in KaneAI | [KaneAI Mobile App Testing](/support/docs/kaneai-mobile-app-accessibility/) |
-| View reports and issues | [Reports](/support/docs/accessibility-testing-navigating-dashboard/) |
-| Connect CI/CD or Jira/Slack | [CI/CD Integration Guide](/support/docs/accessibility-cicd-integration-guide/) · [Integrations (Jira / Slack)](/support/docs/accessibility-report-integrations/) |
-| Look up supported rules and gaps | [Web](/support/docs/accessibility-web-what-we-cover/) · [iOS](/support/docs/accessibility-ios-what-we-cover/) · [Android](/support/docs/accessibility-android-what-we-cover/) |
-| Use AI-assisted analysis | [Accessibility MCP Server](/support/docs/accessibility-mcp-server/) |
+Accessibility testing is the process of evaluating and improving web apps, websites, and mobile apps to ensure they are usable by everyone, including individuals with disabilities.
 
 This includes people with: