diff --git a/assets/images/accessibility-testing/features/login/basic_auth.png b/assets/images/accessibility-testing/features/login/basic_auth.png deleted file mode 100644 index fe10f78e2..000000000 Binary files a/assets/images/accessibility-testing/features/login/basic_auth.png and /dev/null differ diff --git a/assets/images/accessibility-testing/features/login/form_auth.png b/assets/images/accessibility-testing/features/login/form_auth.png deleted file mode 100644 index 4e35bfd39..000000000 Binary files a/assets/images/accessibility-testing/features/login/form_auth.png and /dev/null differ diff --git a/assets/images/accessibility-testing/features/login/login-configs.png b/assets/images/accessibility-testing/features/login/login-configs.png deleted file mode 100644 index 96700e30f..000000000 Binary files a/assets/images/accessibility-testing/features/login/login-configs.png and /dev/null differ diff --git a/assets/images/accessibility-testing/features/login/login-modal.png b/assets/images/accessibility-testing/features/login/login-modal.png deleted file mode 100644 index 2c0ab49c6..000000000 Binary files a/assets/images/accessibility-testing/features/login/login-modal.png and /dev/null differ diff --git a/assets/images/accessibility-testing/features/login/multi-page-password.png b/assets/images/accessibility-testing/features/login/multi-page-password.png deleted file mode 100644 index 83cafeebe..000000000 Binary files a/assets/images/accessibility-testing/features/login/multi-page-password.png and /dev/null differ diff --git a/assets/images/accessibility-testing/features/login/multi-page-username.png b/assets/images/accessibility-testing/features/login/multi-page-username.png deleted file mode 100644 index be50ca567..000000000 Binary files a/assets/images/accessibility-testing/features/login/multi-page-username.png and /dev/null differ diff --git a/docs/accessibility-test-scheduling-crawler.md b/docs/accessibility-test-scheduling-crawler.md index ccd81ffc5..72146959a 100644 --- a/docs/accessibility-test-scheduling-crawler.md +++ b/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/) + diff --git a/docs/accessibility-test-scheduling-login-authentication.md b/docs/accessibility-test-scheduling-login-authentication.md deleted file mode 100644 index f097039e2..000000000 --- a/docs/accessibility-test-scheduling-login-authentication.md +++ /dev/null @@ -1,208 +0,0 @@ ---- -id: accessibility-test-scheduling-login-authentication -title: Login & Authentication for Scheduled Scans -sidebar_label: Login & Authentication -description: Create reusable login configurations from the scheduler or dashboard. Choose Basic, Form, or Multi-page authentication and attach them to scheduled accessibility scans. -keywords: - - Accessibility scheduling - - Login configuration - - Form authentication - - Basic authentication - - Multi-page login - - Test scheduling - - TestMu AI -slug: accessibility-test-scheduling-login-authentication/ -url: https://www.testmuai.com/support/docs/accessibility-test-scheduling-login-authentication/ -site_name: TestMu AI -canonical: https://www.testmuai.com/support/docs/accessibility-test-scheduling-login-authentication/ ---- - -import { BRAND_URL } from '@site/src/component/BrandName'; - - - -# Login & Authentication for Scheduled Scans - -**Login configurations** are saved profiles the scanner runs **before** a scheduled accessibility test. You define credentials and selectors once, then **select** a profile from the **login modal** whenever you create or edit a scan. The same modal opens from the **scheduler** (advanced options on the URL step) or from **Login configurations** on the dashboard, so you can manage profiles without starting a new scan. - -:::note -Treat credentials as sensitive: prefer dedicated QA or read-only accounts, rotate passwords on your usual cadence, and follow your organization’s access and secrets policy. -::: - -## When to use a login configuration - -Use a saved login when: - -- **Target URLs** redirect to a sign-in page or hide content until the user is authenticated. -- **Recurring runs** should reuse the same sign-in flow without re-entering details in the wizard each time. -- Your app uses **HTTP Basic authentication**, a **single-page HTML form**, or a **username-then-password** flow that maps to **Basic**, **Form**, or **Multi-page** below. - -If the site is not reachable from the public internet, combine login with **local testing / tunnel** options in the schedule wizard where your plan supports them. - -## Open the login modal - -### From the scheduler (create or edit) - -1. In **Create scan** or **Edit scan**, go to the step where you **add URLs** (manual URLs, CSV, sitemap, or crawler—depending on your setup). -2. Expand **Advanced options**. -3. Under login settings, use **Add** next to **Add login configurations** to open the modal. - -Advanced options in the schedule wizard with Add login configurations - -### From the dashboard - -1. Open **Login configurations** from the Accessibility (or Web Scanner scheduling) area of the dashboard, as labeled in your product. -2. The **login modal** opens. You can review existing profiles or add a new one. - -Login modal listing saved configurations with option to add a new configuration - -## Create a configuration - -In the modal: - -1. Choose **New configuration** (or equivalent) to open the editor. -2. Enter a **configuration name** you will recognize in the list (for example `Staging Microsoft login`). -3. Select **Authentication type**: - - **Basic** — HTTP Basic auth (no HTML form). - - **Form** — Username and password on **one** page. - - **Multi-page** — Username step, then **Next**, then password (same or different URL). - -4. Fill the fields for that type (see tables below) and **Save**. - -The new profile appears in the list immediately. To use it on a schedule, return to the scan wizard, open **Add login configurations** again, and **select** that profile before saving the scan. - -:::tip -Confirm every CSS selector in Chrome (or Edge) DevTools on the real login page: inspect the control, copy a stable selector (`id`, `name`, `data-testid`, or a short path), then paste it into the form. -::: - -## Field reference - -### Basic authentication - -Use when the server responds with **HTTP Basic** authentication (browser-style username/password challenge), not when you only have a custom HTML login page—in that case use **Form** or **Multi-page**. - -| Field | Required | Description | -|--------|----------|-------------| -| Login Page URL | Yes | Entry URL for the protected experience (for example `https://www.yourwebsite.com/login`). | -| Username | Yes | Username sent with Basic auth. | -| Password | Yes | Password sent with Basic auth. | - -Basic authentication fields: login URL, username, and password - -### Form authentication - -Use when, after opening the **Login Page URL**, the username field, password field, and submit control are all on the **same** document. - -| Field | Required | Description | -|--------|----------|-------------| -| Login Page URL | Yes | URL where the sign-in form appears. | -| Username | Yes | Text entered into the username field. | -| Username CSS Selector | Yes | CSS selector for the username input. | -| Password | Yes | Text entered into the password field. | -| Password CSS Selector | Yes | CSS selector for the password input. | -| Login Button CSS Selector | Yes | CSS selector for the control that submits the form (for example **Sign in**). | -| Post-login URL | No | If set, helps verify navigation to a URL that indicates a successful login. | - -Form authentication with selectors and optional post-login URL - -### Multi-page authentication - -Use for **sequential** flows: enter the username, click **Next** (or equivalent), then enter the password—common with many enterprise identity providers. - -#### Step 1 — Login or username page - -| Field | Required | Description | -|--------|----------|-------------| -| Login Page URL | Yes | First page of the flow (email or username step). | -| Username | Yes | Value entered on step 1. | -| Username CSS Selector | Yes | Selector for the username or email field. | -| Next Button CSS Selector | Yes | Selector for the control that advances to the password step. | - -Multi-page login step one: username page fields - -#### Step 2 — Password page - -| Field | Required | Description | -|--------|----------|-------------| -| Password Page URL | No | Use when the password step loads at a **different** URL; leave empty if only the DOM changes on the same URL. | -| Password | Yes | Password value. | -| Password CSS Selector | Yes | Selector for the password field. | -| Login Button CSS Selector | Yes | Selector for the control that completes sign-in. | - -Multi-page login step two: password page fields - -#### Step 3 — After login - -| Field | Required | Description | -|--------|----------|-------------| -| Post-login URL | No | Same idea as **Form** authentication: optional URL used to confirm the browser reached a logged-in state. | - -## Attach a configuration to a schedule - -1. In **Create** or **Edit scan**, on the URL step, expand **Advanced options** and open **Add login configurations**. -2. In the modal, pick the **saved configuration** for this scan. -3. Save the scan. Scheduled runs use that profile for authentication. - -You can reuse one configuration on many scans or keep separate profiles per environment (for example `Prod read-only` vs `Staging QA`). - -## Edit or remove configurations - -Open **Login configurations** from the dashboard (or the same modal from a scan), select the profile you need, and use the product actions to **edit** or **delete** it. Updating a profile affects any future runs that reference it; confirm downstream scans if you change selectors or URLs. - -## Best practices - -- **Stable selectors** — Prefer `id`, `name`, `data-testid`, or short attribute-based selectors over long positional paths. -- **Least privilege** — Use automation or QA accounts, not personal admin accounts. -- **Post-login URL** — Point at a route that only appears after a successful login so failures are easier to interpret. - -## Limitations - -These are difficult or unsupported with Basic / Form / Multi-page alone: - -| Situation | Why | -|-----------|-----| -| **OTP, SMS, authenticator, CAPTCHA** | Needs human interaction or a different integration model. | -| **OAuth-only** web flows | No password fields to drive with selectors. | -| **Intermittent risk / “Verify it’s you” prompts** | Runs may succeed or fail unpredictably. | - -Use staging environments with simplified auth, or other supported access paths, when possible. - -## Troubleshooting - -| Symptom | What to check | -|--------|----------------| -| Scan fails on the first URL | Correct profile selected; **Login Page URL** is the real start of the flow. | -| Timeout or “element not found” | Selectors, spelling, or UI that loads late—verify in DevTools with throttling if needed. | -| Multi-page fails after username | **Next Button CSS Selector** targets the visible control; add **Password Page URL** if the path changes. | -| Works locally, fails on schedule | Cookie banners, geo restrictions, or MFA triggered for automated sessions. | - -## Related docs - -- [Steps to Schedule an Accessibility Scan](/support/docs/accessibility-test-scheduling-scan/) -- [Test Scheduling - Sitemap (Overview)](/support/docs/accessibility-test-scheduling/) -- [Edit an Accessibility Scan](/support/docs/accessibility-test-scheduling-edit/) -- [Crawler](/support/docs/accessibility-test-crawler/) -- [Sitemap Extraction & URL Import](/support/docs/accessibility-sitemap-extraction-url-import/) -- [Web Scanner Getting Started](/support/docs/web-scanner-getting-started/) diff --git a/docs/accessibility-test-scheduling-scan.md b/docs/accessibility-test-scheduling-scan.md index b1e741632..5f6e91d9b 100644 --- a/docs/accessibility-test-scheduling-scan.md +++ b/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. -- **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. diff --git a/docs/accessibility-test-scheduling.md b/docs/accessibility-test-scheduling.md index 6a207126a..cfaf3752a 100644 --- a/docs/accessibility-test-scheduling.md +++ b/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. diff --git a/docs/accessibility-testing.md b/docs/accessibility-testing.md index b7d564411..96a32d89d 100644 --- a/docs/accessibility-testing.md +++ b/docs/accessibility-testing.md @@ -44,33 +44,11 @@ import BrandName, { BRAND_URL } from '@site/src/component/BrandName'; }} > -- **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. +’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: diff --git a/sidebars.js b/sidebars.js index 3bb35381d..e359e90d6 100644 --- a/sidebars.js +++ b/sidebars.js @@ -1901,107 +1901,7 @@ module.exports = { { type: "category", collapsed: true, - label: "Framework Setup Guides", - items: [ - { - type: "doc", - label: "Selenium", - id: "accessibility-automation-test", - }, - { - type: "doc", - label: "Cypress v10", - id: "cypress-v10-accessibility-test", - }, - { - type: "doc", - label: "Cypress v9 (Legacy)", - id: "cypress-v9-accessibility-test", - }, - { - type: "doc", - label: "Playwright", - id: "playwright-accessibility-test", - }, - { - type: "doc", - label: "TestNG", - id: "accessibility-testng-test", - }, - { - type: "doc", - label: "JUnit 5", - id: "accessibility-junit5-test", - }, - { - type: "doc", - label: "NUnit (C#)", - id: "accessibility-nunit-csharp-test", - }, - { - type: "doc", - label: "Robot Framework", - id: "accessibility-robot-framework-test", - }, - { - type: "doc", - label: "Cucumber (Java)", - id: "accessibility-cucumber-java-test", - }, - ], - }, - { - type: "doc", - label: "Automation Settings", - id: "accessibility-automation-settings", - }, - ], - }, - { - type: "category", - collapsed: true, - label: "Test Scheduling", - link: { - type: "doc", - id: "accessibility-test-scheduling", - }, - items: [ - { - type: "doc", - label: "Sitemap Extraction & URL Import", - id: "accessibility-sitemap-extraction-url-import", - }, - { - type: "doc", - label: "Login & Authentication", - id: "accessibility-test-scheduling-login-authentication", - }, - { - type: "doc", - label: "Create Scheduled Scan", - id: "accessibility-test-scheduling-scan", - }, - { - type: "doc", - label: "Edit Scheduled Scan", - id: "accessibility-test-scheduling-edit", - }, - { - type: "doc", - label: "Crawler", - id: "accessibility-test-crawler", - }, - ], - }, - { - type: "category", - collapsed: true, - label: "Integrations with TestMu AI products", - items: [ - { - type: "category", - collapsed: true, - label: "Web Scanner", + label: "DevTools", link: { type: "doc", id: "accessibility-devtools",