Restructured docs - HyperExecute Kane AI, Test Manager, Kane CLI, Acc…

docs/Device-reservation.mdx

@@ -0,0 +1,100 @@
+---
+title: "Device Reservation on Private Cloud Devices"
+description: "Learn how to reserve private cloud devices in TestMu AI to ensure uninterrupted testing, fair access, and conflict-free usage across your team."
+keywords: ['device reservation', 'private cloud', 'device booking', 'testmu ai devices', 'test scheduling']
+"og:description": "Learn how to reserve private cloud devices in TestMu AI to ensure uninterrupted testing, fair access, and conflict-free usage across your team."
+---
+
+import { BrandName } from "/snippets/BrandName.mdx";
+
+---
+
+**<BrandName /> Device Reservation** enables users to reserve private cloud devices in **advance**, ensuring uninterrupted access during critical testing windows. By scheduling devices ahead of time, teams can **prevent conflicts**, eliminate last-minute delays, and run both manual and automated tests with greater reliability. This becomes particularly valuable for time-sensitive releases, large-scale regression cycles, and continuous integration pipelines, where guaranteed device availability is essential.
+
+Beyond preventing scheduling conflicts, Device Reservation also helps organizations **optimize resource utilization**, enforce fair usage policies, and gain clearer visibility into device allocation across teams, leading to more efficient and predictable testing operations.
+
+<Note>
+Device Reservation feature is currently in **closed beta** and continuously improving based on user feedback. please reach out via <span className="doc__lt" onClick={() => window.openLTChatWidget()}>**24×7 chat**</span> or email us at **support@testmuai.com** to enable it for your organization and try it out.
+</Note>
+---
+
+## Use Cases 
+
+- **Release-Day Reliability**: Reserve devices in advance to guarantee uninterrupted testing during production releases or hotfix rollouts.  
+- **Parallel Test Execution**: Secure multiple devices for running automated test suites in parallel, speeding up regression cycles.  
+- **Cross-Team Coordination**: Schedule device bookings across QA, Dev, and Ops teams to align on shared testing timelines.  
+- **Peak Hour Management**: Prevent conflicts during high-demand periods by ensuring fair access and availability through reservations.  
+- **Optimized Resource Utilization**: Track and manage reservations to avoid idle devices and maximize the ROI of your private cloud setup.
+
+---
+## Device Reservation Workflow 
+
+### Accessing the App Live Dashboard
+1. Open the [App Live Dashboard](https://applive.lambdatest.com/app).
+2. Enable the toggle for Private Devices (**Available only for private device customers**).
+3. The User will see two buttons:
+        - **My reservations** – View all ongoing and upcoming reservations with filter options.
+        - **Go to Reservations** – Open the calendar view to explore and manage bookings.
+
+First-time visitors will see an empty calendar and must create a reservation to begin scheduling devices.
+
+![Device-Reservation-1](/assets/images/real-device-app-testing/Device-Reservations/Device-Reservation1.png)
+
+### Admin Privilege
+
+Admins have additional controls to manage device reservations, accessible inside **Go to Reservations** under the settings button (as shown below):
+
+- **Advance Booking Window** – Define how far in advance members can schedule reservations.
+- **Max Reservation Duration** – Set the maximum duration allowed for a reservation (1–48 hours).
+- **Active Reservations per Member** – Limit the number of active reservations per member (1–99).
+- **Devices per Reservation** – Define how many devices can be booked in one reservation.
+
+![Device-Reservation-5](/assets/images/real-device-app-testing/Device-Reservations/Device-Reservation5.png)
+
+### Calendar View and Permissions
+
+The **calendar** view differs for members and admins:
+
+- **Members:**
+  - The member view shows a calendar with reservation blocks for devices.
+  - `Blue blocks` represent the member’s own reservations, which can be edited or deleted.
+  - `Grey blocks` represent reservations made by other team members. Members cannot edit or delete these.
+
+     ![Device-Reservation-6](/assets/images/real-device-app-testing/Device-Reservations/Device-reservations-User.png)
+
+- **Admins:**
+  - Admins can view and manage all reservations on the calendar.
+  - They have full control to create, edit, or delete any reservation.
+
+### Creating a Reservation
+
+To create a reservation, click **Reserve Device** from the calendar view. Then choose the type of reservation:
+
+- **Immediate Reservation** – Reserve a device instantly for 1 to 12 hours.
+   ![Device-Reservation-4](/assets/images/real-device-app-testing/Device-Reservations/Device-Reservation4.png)
+- **Future Reservation** – Schedule a reservation for a later date/time within the allowed scheduling window.
+   ![Device-Reservation-3](/assets/images/real-device-app-testing/Device-Reservations/Device-Reservation3.png)
+
+Select **one or multiple devices** based on availability and confirm the reservation.
+
+### Viewing and Editing Reservations
+
+After adding reservation slots, the user can view them under **My Reservations** and make edits or cancellations if required.
+
+![Device-Reservation-2](/assets/images/real-device-app-testing/Device-Reservations/.Device-Reservation2.png)
+
+### Session Expiry and Extensions
+
+These rules apply to both admins and members, except admins can still override reservations.
+
+- In the last **15 minutes** of a reservation, a pop-up appears notifying the user that the session is about to end.
+- If no pre-booked reservation exists for the device, the user will have the option to extend the session.
+- If another booking is already scheduled for the device, the extension option will still appear, but the request will **fail**.
+- Once the reserved time ends, the device session is automatically closed and released.
+
+<Tip>
+- Reservation cannot be edited after the slot has been started.**
+
+- If an **admin** deletes any reservation, it is **cancelled** immediately.
+- In automation, reservations cannot be extended automatically in the last 15 minutes. Extensions must be handled manually.
+</Tip>

docs/Selenium-Grid-Configuration.mdx

@@ -0,0 +1,30 @@
+---
+title: "Selenium Grid Configuration Guide | How to Configure TestMu AI Automation Grid"
+sidebarTitle: "TestMu AI Selenium Grid Configuration"
+description: "This support guide tells you how can you configure TestMu AI Online Selenium Grid of 3000+ real desktop and mobile browsers."
+keywords: ['testmu ai automation', 'selenium automation grid', 'selenium grid online', 'selenium versions']
+"og:description": "This support guide tells you how can you configure TestMu AI Online Selenium Grid of 3000+ real desktop and mobile browsers."
+---
+
+import { BrandName } from "/snippets/BrandName.mdx";
+
+---
+
+We constantly upgrade our grid with the stable version of Selenium.
+
+Currently we use: **Selenium 2.53.1 updated**
+
+## Selenium Automation Grid Configuration
+--------------------------------------------
+
+| KEY                         | VALUE                                                   |
+|-----------------------------|---------------------------------------------------------|
+| Selenium version            | Selenium 2.53.1 – Updated @Date<br />[Want to change version?](https://www.testmuai.com/capabilities-generator/) |
+| IEDriver version            | Selenium 2.53.1 – Updated @Date<br />[Want to change version?](https://www.testmuai.com/capabilities-generator/) |
+| ChromeDriver version        | v2.41 – Updated @Date<br />[Want to change version?](https://www.testmuai.com/capabilities-generator/)           |
+| Firefox/GeckoDriver Version | 0.21.0 – Updated @Date<br />[Want to change version?](https://www.testmuai.com/capabilities-generator/)          |
+| HUB URI                     | [hub.lambdatest.com](https://hub.lambdatest.com/)                                      |
+| HUB Port                    | 80 (HTTPS/SSL)                                          |
+| Window Mode                 | Multi-window                                            |
+| Default Idle Timeout        | 130 seconds<br />[Want to change Idle Timeout?](https://www.testmuai.com/capabilities-generator/)                |
+| Default Screen Resolution   | 1024×768<br />[Want to change Resolution?](https://www.testmuai.com/capabilities-generator/)                     |

docs/accelq-integration.mdx

@@ -0,0 +1,62 @@
+---
+title: "ACCELQ Integration"
+sidebarTitle: "ACCELQ"
+description: "Accelerate your end-to-end digital testing journey with TestMu AI and ACCELQ.  Automate your web and mobile apps across 3000+ real browsers, devices and operating system combinations."
+keywords: ['testmu ai integration with accelq', 'testmu ai and accelq integration', 'accelq integration']
+"og:description": "Accelerate your end-to-end digital testing journey with TestMu AI and ACCELQ.  Automate your web and mobile apps across 3000+ real browsers, devices and operating system combinations."
+---
+
+import { BrandName } from "/snippets/BrandName.mdx";
+
+---
+
+ACCELQ is an AI Native Codeless automation testing and management platform. It enables you automate web, mobile, API, database, and packaged applications.
+
+By integrating <BrandName /> with ACCELQ, you can perform web and mobile app automation on an online device farm of 3000+ real browsers, devices, and OS combinations, and accelerate your end-to-end digital testing efforts.
+
+## Prerequisites
+---
+
+1. Make sure you have a <BrandName /> account.  If you don't have an account yet, [sign up for free](https://accounts.lambdatest.com/register).
+
+2. To integrate <BrandName /> with ACCELQ, you will need a <BrandName /> username and access key.
+
+<img loading="lazy" src='/assets/images/accelq-integration/key.png' alt="Image" width="1444" height="703"  className="doc_img img_center" />
+
+3. Install the ACCELQ Agent Dashboard.
+
+## Integrating <BrandName /> From ACCELQ Agent Dashboard
+---
+
+1. Open your ACCELQ Agent Dashboard.
+
+2. Once you are in the target agent, click **Edit Configuration**.
+
+<img loading="lazy" src='/assets/images/accelq-integration/accel_2.png' alt="Image" width="1444" height="703"  className="doc_img img_center" />
+
+3. You need to use the external device provider for web, mobile, or both platforms. For example, if you wish to perform web browser automation, select **Use external device provider for Web**.
+
+<img loading="lazy" src='/assets/images/accelq-integration/accel_1.png' alt="Image" width="1444" height="703"  className="doc_img img_center" />
+
+4. Now enter your <BrandName /> username and access key and save/restart the ACCELQ Agent.
+
+### Executing The Tests
+
+1. Once the agent is operable, you can choose browser, device and OS combinations from the list that <BrandName /> support.
+
+2. From the Run modal, select the agent from the AGENT/HOST section. After that, choose browser and device from the corresponding sections.
+
+## Capturing Views For Mobile Automation
+---
+
+1. From the **Record View** dialog box, click **Cloud Provider**.
+
+2. Select *<BrandName />* from the **Provider** dropdown. Enter your <BrandName /> username and access key, and click **Authenticate**.
+
+<img loading="lazy" src='/assets/images/accelq-integration/accel_3.png' alt="Image" width="1444" height="703"  className="doc_img img_center" />
+
+3. Once the authentication is successful, you can select the real devices that is fetched from the <BrandName /> platform.
+
+4. In the **App Url**, provider your <BrandName /> App URL.
+
+5. Now click **Start Capture** and it will launch your test session on the selected device.

docs/accessibility-ai-issue-detection-agent.mdx

@@ -0,0 +1,31 @@
+---
+title: "AI Issue Detection Agent"
+sidebarTitle: "AI Issue Detection Agent"
+description: "Overview of AI-assisted issue interpretation and triage for Accessibility workflows where available."
+"og:description": "Overview of AI-assisted issue interpretation and triage for Accessibility workflows where available."
+---
+
+AI-assisted issue analysis can help teams interpret findings faster, understand likely patterns, and move more quickly into triage.
+
+The guidance below describes where AI-assisted analysis fits in the Accessibility reporting workflow. It also shows how to pair automated interpretation with issue detail and human review so triage stays grounded and defensible.
+
+## Use this when
+
+Use AI-assisted issue interpretation when you want faster triage support, not as a replacement for rule-level validation or remediation review.
+
+## Important note
+
+AI issue analysis should support prioritization and understanding. It should not be treated as a substitute for manual validation, engineering review, or compliance sign-off.
+
+## How to use it in a review (onboarding)
+
+1. Open **[Issue Summary](/support/docs/accessibility-testing-dashboard-issue-summary/)** or **[All Issues](/support/docs/accessibility-testing-dashboard-all-issues/)** after a scan completes.
+2. Select an issue or cluster where the UI exposes **AI-assisted** analysis (wording may appear as summary, explanation, or suggested next step).
+3. Read the AI output as **hypothesis support**—verify against the DOM, design intent, and WCAG rule text in the **[rule repositories](/support/docs/accessibility-web-rule-repository/)** where applicable.
+4. If the suggestion is wrong, capture that feedback through your usual QA process so the team does not over-trust automation.
+5. Pair AI hints with the **[Issue Remediation Guide](/support/docs/accessibility-issue-remediation-guide/)** for engineering-ready fix order.
+
+## Related docs
+
+- [Issue Summary](/support/docs/accessibility-testing-dashboard-issue-summary/)
+- [Accessibility Issue Remediation Guide](/support/docs/accessibility-issue-remediation-guide/)

docs/accessibility-android-rule-fixed-orientation-lock.mdx

@@ -0,0 +1,40 @@
+---
+title: "Fixed Orientation Lock"
+sidebarTitle: "Fixed Orientation Lock"
+description: "Rule-level Accessibility guidance for Fixed Orientation Lock on Android."
+"og:description": "Rule-level Accessibility guidance for Fixed Orientation Lock on Android."
+---
+
+Android activities must support both portrait and landscape orientations unless a specific orientation is essential to the functionality.
+
+<Info>
+**WCAG Reference**
+**Maps to:** WCAG 1.3.4 Orientation | **Applies to:** WCAG 2.1, WCAG 2.2
+**Introduced in:** WCAG 2.1 | **Level:** AA | [Read the official specification →](https://www.w3.org/WAI/WCAG22/Understanding/orientation.html)
+</Info>
+
+## What this rule checks
+
+The scanner flags activities with `android:screenOrientation` set to a fixed value (`portrait`, `landscape`, `sensorPortrait`, `sensorLandscape`) in the manifest, preventing device rotation.
+
+## Why it matters
+
+Users with motor disabilities may mount their device in a fixed orientation (e.g., attached to a wheelchair). Users with low vision may prefer landscape to display larger text. Locking orientation removes this choice and can make the app physically uncomfortable or impossible to use.
+
+## Common failure patterns
+
+- `android:screenOrientation="portrait"` set globally on all activities
+- orientation locked programmatically with `setRequestedOrientation()` for non-essential reasons
+- splash screens or onboarding locked to portrait that propagate the lock to subsequent screens
+
+## Remediation guidance
+
+- remove `android:screenOrientation` from the manifest (defaults to user-controlled rotation)
+- only lock orientation when the content genuinely requires it (e.g., a camera viewfinder)
+- test the app in both orientations to confirm layouts adapt correctly
+- document any essential orientation requirement with a clear justification
+
+## Related docs
+
+- [Android Rule Repository](/support/docs/accessibility-android-rule-repository/)
+- [Accessibility Issue Remediation Guide](/support/docs/accessibility-issue-remediation-guide/)

docs/accessibility-android-rule-inaccessible-text-focus.mdx

@@ -0,0 +1,41 @@
+---
+title: "Inaccessible Text Focus"
+sidebarTitle: "Inaccessible Text Focus"
+description: "Rule-level Accessibility guidance for Inaccessible Text Focus on Android."
+"og:description": "Rule-level Accessibility guidance for Inaccessible Text Focus on Android."
+---
+
+Meaningful text content in Android apps must be focusable by assistive technology so users can read it sequentially.
+
+<Info>
+**WCAG Reference**
+**Maps to:** WCAG 4.1.2 Name, Role, Value | **Applies to:** WCAG 2.0, WCAG 2.1, WCAG 2.2
+**Introduced in:** WCAG 2.0 | **Level:** A | [Read the official specification →](https://www.w3.org/WAI/WCAG22/Understanding/name-role-value.html)
+</Info>
+
+## What this rule checks
+
+The scanner flags `TextView` and other text-bearing elements that are not reachable through TalkBack navigation because they are marked as not important for accessibility or are hidden behind non-focusable containers.
+
+## Why it matters
+
+If meaningful text cannot receive TalkBack focus, blind and low-vision users miss the information entirely. This is especially problematic for status messages, instructions, and error text.
+
+## Common failure patterns
+
+- `TextView` elements inside containers with `importantForAccessibility="noHideDescendants"`
+- dynamically added text views that do not inherit accessibility properties
+- text elements positioned off-screen (used for visual spacing) that are still rendered but not focusable
+- `TextView` elements with `focusable="false"` that contain meaningful information
+
+## Remediation guidance
+
+- ensure text elements containing meaningful content have `importantForAccessibility="yes"`
+- do not suppress descendant accessibility on containers that hold readable text
+- remove decorative text from the accessibility tree with `importantForAccessibility="no"` (only when truly decorative)
+- test by swiping through the screen with TalkBack and confirming all meaningful text is announced
+
+## Related docs
+
+- [Android Rule Repository](/support/docs/accessibility-android-rule-repository/)
+- [Accessibility Issue Remediation Guide](/support/docs/accessibility-issue-remediation-guide/)

docs/accessibility-android-rule-insufficient-color-ratio.mdx

@@ -0,0 +1,41 @@
+---
+title: "Insufficient Color Ratio"
+sidebarTitle: "Insufficient Color Ratio"
+description: "Rule-level Accessibility guidance for Insufficient Color Ratio on Android."
+"og:description": "Rule-level Accessibility guidance for Insufficient Color Ratio on Android."
+---
+
+Text and meaningful visual elements in Android apps must maintain sufficient contrast against their backgrounds for readability.
+
+<Info>
+**WCAG Reference**
+**Maps to:** WCAG 1.4.3 Contrast (Minimum) | **Applies to:** WCAG 2.0, WCAG 2.1, WCAG 2.2
+**Introduced in:** WCAG 2.0 | **Level:** AA | [Read the official specification →](https://www.w3.org/WAI/WCAG22/Understanding/contrast-minimum.html)
+</Info>
+
+## What this rule checks
+
+The scanner measures the contrast ratio between foreground text or icon colors and their background, flagging pairs that fall below the 4.5:1 ratio for normal text or 3:1 for large text.
+
+## Why it matters
+
+Users with low vision, color-vision deficiencies, or those using devices in bright sunlight depend on adequate contrast to read text and distinguish UI elements. Low contrast makes content illegible.
+
+## Common failure patterns
+
+- light gray text on white backgrounds in settings or list items
+- placeholder text in input fields with very low contrast
+- status indicators using pale colors on light backgrounds
+- disabled-state styling that falls below minimum ratios while the element remains interactive
+
+## Remediation guidance
+
+- verify text contrast against backgrounds using a color contrast analyzer
+- use Material Design color tokens that are pre-validated for contrast compliance
+- ensure all text states (enabled, disabled, error, hint) meet minimum ratios
+- test on multiple devices and brightness levels to catch theme-specific failures
+
+## Related docs
+
+- [Android Rule Repository](/support/docs/accessibility-android-rule-repository/)
+- [Accessibility Issue Remediation Guide](/support/docs/accessibility-issue-remediation-guide/)