.default})
+
diff --git a/docs/accessibility-android-rules.md b/docs/accessibility-android-rules.md
new file mode 100644
index 000000000..8adadc1b6
--- /dev/null
+++ b/docs/accessibility-android-rules.md
@@ -0,0 +1,64 @@
+---
+id: accessibility-android-rules
+title: Android Accessibility Rules - Quick Reference
+sidebar_label: Android
+description: Use LambdaTest Accessibility DevTools to detect and report accessibility issues with automation, following WCAG guidelines.
+keywords:
+ - LambdaTest
+ - Accessibility
+ - Testing
+ - Manual
+ - Accessibility Testing Settings
+url: https://www.lambdatest.com/support/docs/accessibility-android-rules/
+site_name: LambdaTest
+slug: accessibility-android-rules/
+---
+
+import CodeBlock from '@theme/CodeBlock';
+import {YOUR_LAMBDATEST_USERNAME, YOUR_LAMBDATEST_ACCESS_KEY} from "@site/src/component/keys";
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+
+
+| Rule Name | WCAG | Level | Impact | Description |
+|-----------|------|-------|--------|-------------|
+| Missing Image Alt | 1.1.1 | A | Critical | Images lack alternative text descriptions that screen readers can announce to users. Add `android:contentDescription` to meaningful images or set to empty string for decorative images to ensure proper accessibility support. |
+| Missing View Accessibility | 4.1.2 | A | Serious | Interactive elements like buttons, clickable views, or custom controls lack proper accessibility labels that describe their purpose. Ensure all interactive Views have clear `android:contentDescription` or associated labels for screen readers. |
+| Unlabeled Checkbox Element | 4.1.2 | A | Serious | Checkbox controls are missing accessible names that describe their purpose or current state. Provide descriptive labels using `android:text`, `android:contentDescription`, or associated TextView labels so users understand what they're selecting. |
+| Insufficient Color Ratio | 1.4.3 | AA | Serious | Text elements don't meet minimum contrast ratio requirements making them difficult to read for users with visual impairments. Maintain 4.5:1 ratio for normal text and 3:1 for large text by adjusting colors or background. |
+| Missing Field Label | 3.3.2 | A | Serious | Input fields like EditText lack descriptive labels that identify their purpose to users. Provide clear labels using `android:hint`, associated TextView with `android:labelFor`, or TextInputLayout to describe expected input. |
+| Non-accessible Interaction | 4.1.2 | A | Serious | Custom interactive elements, buttons, or gesture-based controls cannot be accessed or activated through assistive technology. Ensure all interactive elements have proper focus handling, role definition, and descriptive labels. |
+| Missing Screen Title | 2.4.2 | A | Serious | Activities or screens lack descriptive titles that help users understand their current location in the app. Set meaningful titles using `setTitle()` or `supportActionBar?.title` for proper navigation context. |
+| Unlabeled Toggle Control | 4.1.2 | A | Serious | Switch, toggle, or similar controls are missing accessible names that explain what they control and their current state. Provide descriptive labels that clearly indicate what the toggle affects (e.g., "Wi-Fi enabled"). |
+| Mismatched Label Text | 2.5.3 | A | Serious | The visible text label on a control differs from the programmatically accessible name, causing confusion for screen reader users. Ensure the accessible name includes or matches the visible text exactly. |
+| Missing Input Value | 4.1.2 | A | Moderate | Text fields are missing programmatic values that assistive technology can read, making it difficult for users to understand current input state. Ensure EditText values are properly exposed and announced by screen readers. |
+| Inaccessible Text Focus | 4.1.2 | A | Moderate | Text elements that receive focus lack proper accessibility properties, confusing screen reader users about their purpose. Either provide clear interactive roles and descriptions or remove focus capability for non-interactive text. |
+| Misplaced Field Label | 3.3.2 | A | Moderate | Form labels are not positioned correctly relative to their controls or lack proper programmatic association. Ensure labels appear visually before controls and use `android:labelFor` for proper screen reader announcement order. |
+| Nested Control Issues | 4.1.2 | A | Moderate | Interactive elements are incorrectly nested inside other interactive elements, creating focus traps and navigation confusion. Separate interactive elements into distinct, non-nested components to ensure proper accessibility navigation. |
+| Unnamed Nested Element | 4.1.2 | A | Moderate | Elements within containers lack their own accessible names when they should be independently accessible. Provide distinct labels for nested interactive elements or mark decorative elements as non-focusable. |
+| Fixed Orientation Lock | 1.3.4 | AA | Moderate | App restricts viewing to only portrait or landscape orientation without accessibility justification. Support both orientations or provide alternative access methods for users who cannot rotate their devices due to physical constraints. |
+| Undersized Touch Target | 2.5.5 | AAA | Moderate | Interactive elements are smaller than the recommended minimum touch target size, making them difficult to activate for users with motor impairments. Ensure all touch targets are at least 48dp x 48dp. |
+| Insufficient Target Spacing | 2.5.5 | AAA | Moderate | Interactive elements are placed too close together without adequate spacing, increasing risk of accidental activation. Provide sufficient spacing between adjacent touch targets to prevent targeting errors for users with limited dexterity. |
\ No newline at end of file
diff --git a/docs/accessibility-android-test.md b/docs/accessibility-android-test.md
new file mode 100644
index 000000000..d5ca6b2f6
--- /dev/null
+++ b/docs/accessibility-android-test.md
@@ -0,0 +1,94 @@
+---
+id: accessibility-android-test
+title: Accessibility Testing Using App Manual Testing
+sidebar_label: Manual
+description: Use LambdaTest Accessibility DevTools to detect and report accessibility issues with automation, following WCAG guidelines.
+keywords:
+ - LambdaTest
+ - Accessibility
+ - Testing
+ - Manual
+ - Accessibility Testing Settings
+url: https://www.lambdatest.com/support/docs/accessibility-android-test/
+site_name: LambdaTest
+slug: accessibility-android-test/
+---
+
+import CodeBlock from '@theme/CodeBlock';
+import {YOUR_LAMBDATEST_USERNAME, YOUR_LAMBDATEST_ACCESS_KEY} from "@site/src/component/keys";
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+
+LambdaTest offers a powerful Accessibility Scanner for native Android apps, integrated seamlessly with our manual app testing environment. This helps QA teams and developers identify accessibility issues directly during real-time testing sessions. Follow this guide to understand how to perform accessibility scans manually.
+
+## Prerequisites
+- You must have access to the LambdaTest Real Device Cloud.
+- Your Android app (.apk or .aab) should be uploaded to the platform.
+- Ensure you have enabled the Accessibility feature from your account or project settings, if applicable.
+
+## Steps to perform Accessibility Testing using the App Scanner
+### Step 1: Navigate to the Accessibility Section
+- Log in to your LambdaTest dashboard.
+- From the left-hand menu, click on Accessibility.
+- Select the **App Scanner** tab under the Accessibility tab.
+
+### Step 2: Upload your Application
+- To start accessibility testing, you need to upload your application first.
+- Click on the **Upload** button to upload it from your local system.
+- You can also install via Playstore or Firebase or upload via URL.
+
+.default})
+
+### Step 3: Launch Manual App Testing
+- Choose the target Android device and select your application.
+- Click on the **Start** button to launch the manual testing session on the selected device.
+
+### Step 4: Scan the App Screens
+- Once the session is started and your app is launched on the device, click on the **Start Scanning** button to start the scanning of current page.
+.default})
+.default})
+
+### Step 5: Review Accessibility Issues
+After scanning, you’ll see a categorized list of issues based on severity (Critical, Serious, Moderate, Minor). Each issue includes:
+- Description of the accessibility problem.
+- List of affected element.
+- Suggested fix or recommendation.
+
+Continue testing by navigating to additional screens in the app and scanning them one-by-one. This helps ensure that your entire app meets accessibility standards across all flows and use cases.
+
+.default})
+
+### Step 6: Accessibility Report
+After completion of your scanning, click on the **Save Test** button.
+- Go to the **Manual Reports** tab under the Accessibility tab.
+- Select your desired report
+- You can also share the report over email, export it in JSON, CSV and PDF format, and also you create an issue as well for that report.
+
+.default})
\ No newline at end of file
diff --git a/docs/accessibility-ios-rules.md b/docs/accessibility-ios-rules.md
new file mode 100644
index 000000000..041dbb1b1
--- /dev/null
+++ b/docs/accessibility-ios-rules.md
@@ -0,0 +1,54 @@
+---
+id: accessibility-ios-rules
+title: iOS Accessibility Rules - Quick Reference
+sidebar_label: iOS
+description: Use LambdaTest Accessibility DevTools to detect and report accessibility issues with automation, following WCAG guidelines.
+keywords:
+ - LambdaTest
+ - Accessibility
+ - Testing
+ - Manual
+ - Accessibility Testing Settings
+url: https://www.lambdatest.com/support/docs/accessibility-ios-rules/
+site_name: LambdaTest
+slug: accessibility-ios-rules/
+---
+
+import CodeBlock from '@theme/CodeBlock';
+import {YOUR_LAMBDATEST_USERNAME, YOUR_LAMBDATEST_ACCESS_KEY} from "@site/src/component/keys";
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+
+
+| Rule Name | WCAG | Level | Impact | Description |
+|-----------|------|-------|--------|-------------|
+| Missing Accessibility Labels | 4.1.2 | A | Serious | Interactive UI elements lack proper accessibility labels, hints, or descriptions that VoiceOver can announce to users. Set `accessibilityLabel` for meaningful descriptions and `accessibilityHint` for usage guidance. In SwiftUI use `.accessibilityLabel()` and `.accessibilityHint()`. For images, provide descriptive text. For buttons, ensure labels describe the action, not just visual appearance. |
+| Color Contrast Issues | 1.4.3 | AA | Serious | Text and background color combinations fail to meet WCAG minimum contrast ratios for visual accessibility. Use Apple's Color Contrast Calculator or online tools to verify 4.5:1 ratio for normal text, 3:1 for large text. Implement system colors that adapt to accessibility settings and test in high contrast mode. Consider using semantic colors like `UIColor.label` and `UIColor.systemBackground`. |
+| Touch Target Sizing | 2.5.5 | AAA | Moderate | Touch target areas are smaller than Apple's recommended 44pt minimum size or lack adequate spacing from adjacent elements. Ensure interactive elements are at least 44x44 points by increasing button frame size or adding transparent padding. Use constraints to maintain minimum spacing between adjacent touchable elements. In SwiftUI, use `.frame(minWidth: 44, minHeight: 44)` and test on actual devices. |
+| Assistive Technology Access | 4.1.2 | A | Serious | UI components cannot be properly detected, focused, or activated by VoiceOver and other assistive technologies. Set `isAccessibilityElement = true` for custom views, ensure proper view hierarchy, and avoid blocking accessibility elements. Implement `accessibilityActivate()` for custom interactions and use `accessibilityElements` array to define focus order. Test navigation with VoiceOver gestures. |
+| Text Truncation Issues | 1.4.4 | AA | Serious | Text content becomes truncated or cut off when users increase font sizes through iOS Dynamic Type settings. Use `adjustsFontForContentSizeCategory = true` on text elements and implement flexible layouts with priority constraints. Use `UIFont.preferredFont(forTextStyle:)` for scalable system fonts. Test with largest accessibility text sizes and avoid fixed height constraints on text containers. |
+| Accessibility Role Definition | 4.1.2 | A | Moderate | UI elements lack appropriate accessibility traits that define their role, state, or behavior for assistive technology interaction. Set correct `accessibilityTraits` (.button, .link, .header, .selected, .disabled) and combine traits when needed. Update traits dynamically based on state changes. In SwiftUI, use `.accessibilityAddTraits()` and `.accessibilityRemoveTraits()` to ensure custom controls communicate their purpose clearly. |
+| Dynamic Type Support | 1.4.4 | AA | Serious | App interface fails to properly scale or adapt when users enable larger text sizes in iOS accessibility settings. Enable Dynamic Type support using `traitCollectionDidChange` to respond to size changes and use Auto Layout with flexible constraints. Implement `adjustsFontForContentSizeCategory` on text elements. Test with Settings > Accessibility > Display & Text Size > Larger Text and design layouts that reflow gracefully. |
\ No newline at end of file
diff --git a/docs/accessibility-testing.md b/docs/accessibility-testing.md
index c7ba5831b..eac61ea26 100644
--- a/docs/accessibility-testing.md
+++ b/docs/accessibility-testing.md
@@ -64,10 +64,28 @@ Accessibility testing ensures that your product is usable by people with disabil
Get a comprehensive accessibility analysis via browser extension.
- +Get the accessibility check for automated tests and scripts.
+Get a comprehensive accessibility analysis for your app.
+Get the accessibility check for automated webapp tests and scripts.
+Get the accessibility check for your automated app tests and scripts.
+Streamline your accessibility testing by automating checks and generating comprehensive reports.
Getting Started
Accessibility DevTools
-Accessibility Automation
-Accessibility Scheduling
Accessibility Web Automation
+Sitemap Scheduling
+Native App Scanner
Native App Automation
Screen Reader
-Navigating Dashboard
-FAQ