Updated the Accessibility Testing docs#869
Conversation
WalkthroughDocumentation updates restructure accessibility testing guides to emphasize enabling accessibility checks at test steps. New subsections added (Overview Tab, All Issues Tab, Global Header Actions), step-by-step guidance reorganized, navigation links updated, and image references modified to reflect revised terminology and structure. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20–25 minutes
Possibly related PRs
Suggested reviewers
Poem
Pre-merge checks and finishing touches❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (2)
src/pages/docs/accessibility-testing/accessibility-testing.md (1)
36-42: Refactor prerequisites list to reduce repetitive phrasing.Items 2–4 all begin with "Documentation on," which creates awkward repetition. Additionally, the structure is inconsistent: item 1 uses "You have enabled..." while items 2–4 are documentation links. Restructure for clarity and better parallelism.
> Before you begin, ensure that you have referred to: > 1. You have enabled **Web Accessibility Testing - Step Level** from **Settings > Preferences > Web Accessibility Testing**. > 2. [Documentation on creating test plans](https://testsigma.com/docs/test-management/test-plans/overview/). > 3. [Documentation on creating test suites](https://testsigma.com/docs/test-management/test-suites/overview/). > 4. [Documentation on creating test machine](https://testsigma.com/docs/test-management/test-plans/manage-test-machines/). +> Before you begin, ensure that you have: +> 1. Enabled **Web Accessibility Testing - Step Level** from **Settings > Preferences > Web Accessibility Testing**. +> 2. Reviewed [test plan creation documentation](https://testsigma.com/docs/test-management/test-plans/overview/). +> 3. Reviewed [test suite creation documentation](https://testsigma.com/docs/test-management/test-suites/overview/). +> 4. Reviewed [test machine setup documentation](https://testsigma.com/docs/test-management/test-plans/manage-test-machines/).src/pages/docs/accessibility-testing/mobile-accessibility-testing.md (1)
35-38: Apply the same prerequisites refactoring as the web accessibility doc.Lines 35–38 exhibit the same "Documentation on" repetition issue present in the web file. For consistency across both accessibility documentation files, apply the same restructuring here.
> Before you begin, ensure that you have referred to: > 1. You have enabled **Web Accessibility Testing - Step Level** from **Settings > Preferences > Web Accessibility Testing**. > 2. [Documentation on creating test plans](https://testsigma.com/docs/test-management/test-plans/overview/). > 3. [Documentation on creating test suite](https://testsigma.com/docs/test-management/test-suites/overview/). > 4. [Documentation on creating test machines](https://testsigma.com/docs/test-management/test-plans/manage-test-machines/). +> Before you begin, ensure that you have: +> 1. Enabled **Web Accessibility Testing - Step Level** from **Settings > Preferences > Web Accessibility Testing**. +> 2. Reviewed [test plan creation documentation](https://testsigma.com/docs/test-management/test-plans/overview/). +> 3. Reviewed [test suite creation documentation](https://testsigma.com/docs/test-management/test-suites/overview/). +> 4. Reviewed [test machine setup documentation](https://testsigma.com/docs/test-management/test-plans/manage-test-machines/).
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
src/pages/docs/accessibility-testing/accessibility-testing.md(2 hunks)src/pages/docs/accessibility-testing/mobile-accessibility-testing.md(2 hunks)
🧰 Additional context used
🪛 LanguageTool
src/pages/docs/accessibility-testing/mobile-accessibility-testing.md
[style] ~38-~38: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...anagement/test-suites/overview/). > 4. [Documentation on creating test machines](https://test...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
src/pages/docs/accessibility-testing/accessibility-testing.md
[style] ~42-~42: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...anagement/test-suites/overview/). > 4. [Documentation on creating test machine](https://tests...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[style] ~115-~115: Consider using a different verb for a more formal wording.
Context: ...splays detailed information to help you fix the issue. - **Previous / Next:*...
(FIX_RESOLVE)
🪛 markdownlint-cli2 (0.18.1)
src/pages/docs/accessibility-testing/mobile-accessibility-testing.md
97-97: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
98-98: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
99-99: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
105-105: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
105-105: Headings must start at the beginning of the line
(MD023, heading-start-left)
107-107: Unordered list indentation
Expected: 2; Actual: 7
(MD007, ul-indent)
108-108: Unordered list indentation
Expected: 2; Actual: 7
(MD007, ul-indent)
109-109: Unordered list indentation
Expected: 2; Actual: 7
(MD007, ul-indent)
111-111: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
111-111: Headings must start at the beginning of the line
(MD023, heading-start-left)
113-113: Unordered list indentation
Expected: 2; Actual: 6
(MD007, ul-indent)
114-114: Unordered list indentation
Expected: 2; Actual: 6
(MD007, ul-indent)
115-115: Unordered list indentation
Expected: 2; Actual: 6
(MD007, ul-indent)
116-116: Unordered list indentation
Expected: 2; Actual: 6
(MD007, ul-indent)
117-117: Unordered list indentation
Expected: 2; Actual: 6
(MD007, ul-indent)
119-119: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
119-119: Headings must start at the beginning of the line
(MD023, heading-start-left)
121-121: Unordered list indentation
Expected: 2; Actual: 6
(MD007, ul-indent)
122-122: Unordered list indentation
Expected: 2; Actual: 6
(MD007, ul-indent)
123-123: Unordered list indentation
Expected: 2; Actual: 6
(MD007, ul-indent)
124-124: Unordered list indentation
Expected: 2; Actual: 6
(MD007, ul-indent)
125-125: Unordered list indentation
Expected: 2; Actual: 6
(MD007, ul-indent)
130-130: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
131-131: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
src/pages/docs/accessibility-testing/accessibility-testing.md
97-97: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
98-98: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
99-99: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
105-105: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
105-105: Headings must start at the beginning of the line
(MD023, heading-start-left)
107-107: Unordered list indentation
Expected: 2; Actual: 7
(MD007, ul-indent)
108-108: Unordered list indentation
Expected: 2; Actual: 7
(MD007, ul-indent)
109-109: Unordered list indentation
Expected: 2; Actual: 7
(MD007, ul-indent)
111-111: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
111-111: Headings must start at the beginning of the line
(MD023, heading-start-left)
113-113: Unordered list indentation
Expected: 2; Actual: 6
(MD007, ul-indent)
114-114: Unordered list indentation
Expected: 2; Actual: 6
(MD007, ul-indent)
115-115: Unordered list indentation
Expected: 2; Actual: 6
(MD007, ul-indent)
116-116: Unordered list indentation
Expected: 2; Actual: 6
(MD007, ul-indent)
117-117: Unordered list indentation
Expected: 2; Actual: 6
(MD007, ul-indent)
119-119: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
119-119: Headings must start at the beginning of the line
(MD023, heading-start-left)
121-121: Unordered list indentation
Expected: 2; Actual: 6
(MD007, ul-indent)
122-122: Unordered list indentation
Expected: 2; Actual: 6
(MD007, ul-indent)
123-123: Unordered list indentation
Expected: 2; Actual: 6
(MD007, ul-indent)
124-124: Unordered list indentation
Expected: 2; Actual: 6
(MD007, ul-indent)
125-125: Unordered list indentation
Expected: 2; Actual: 6
(MD007, ul-indent)
130-130: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: CI
🔇 Additional comments (4)
src/pages/docs/accessibility-testing/accessibility-testing.md (2)
46-62: Strong structure for step-by-step test steps guidance.The new "Steps to Enable Accessibility Testing in Test Steps" section clearly outlines the workflow with 4 numbered steps, screenshots, and a helpful note. This is well-organized and should be easy for users to follow.
15-17: Contextual link and intro updates are clear and well-aligned.The new contextual link for "Steps to Enable Accessibility Testing in Test Steps" fits the documentation hierarchy. The updated intro now emphasizes step-level checking and includes a helpful Salesforce note, which improves clarity and scope-setting for users.
Also applies to: 28-31
src/pages/docs/accessibility-testing/mobile-accessibility-testing.md (2)
42-66: Strong mobile-specific guidance with clear step-by-step structure.The "Steps to Enable Accessibility Testing in Test Steps" section effectively addresses the mobile context (kebab menu, test step settings, bulk select via Recorder). The additional notes about Bulk Actions and Recorder options are helpful for users familiar with those workflows.
16-23: Navigation and intro updates align well with the web file.The contextual links match the web documentation structure, and the intro now emphasizes step-level checking for mobile applications. This maintains consistency across both accessibility testing docs while preserving platform-specific language (e.g., "Android and iOS").
Also applies to: 28-28
| ## **Interacting with Accessibility Report** | ||
|
|
||
|  | ||
| The **Accessibility Report** page displays the results of your accessibility report. It allows you to review errors, check severity levels, and identify the specific user interface elements that need attention. | ||
|
|
||
| - **Violations**: This lists all accessibility issues that need immediate action. | ||
| The page is organized into two main tabs: **Overview** and **All Issues**. | ||
|
|
||
| - **Review Required**: This lists all accessibility issues that need manual review. Although Testsigma has identified these issues, we recommend a closer review for accuracy. | ||
| ### **Overview Tab** | ||
|
|
||
| [[info | **NOTE**:]] | ||
| | The issues are color-coded with labels to indicate their severity level. You can also filter the issues based on severity and category. | ||
| The **Overview** tab provides a visual summary of the test execution. Use this tab to quickly check the overall status of the application. | ||
|
|
||
| --- | ||
| - **Issue Overview:** Displays a donut chart that summarizes all issues found during the test. The chart groups issues by severity: **Critical, Serious, Moderate, Minor,** and **Success**.  | ||
| - **Issues by WCAG Principle:** Organizes findings by WCAG principles, such as **Perceivable, Operable, Understandable,** and **Robust**. This section lists the specific criteria violations and the number of failed checks for each principle.  | ||
| - **Issues by Pages:** Lists every URL scanned during the test and the number of accessibility checks that failed on that page. You can use this list to find pages with the most errors.  | ||
| - **Issues by Components:** Categorizes issues by HTML element types. This helps you see if specific code components cause repeated errors. | ||
|
|
||
| ### **Issue Navigation Panel** | ||
| ### **All Issues Tab** | ||
|
|
||
|  | ||
| The **All Issues** tab displays a detailed list of every violation found. You can use this tab to investigate specific bugs and view relevant code. This tab includes search tools, an issues list, and a details pane. | ||
|
|
||
| - **Pagination Controls**: Provides navigation between the individual issues of specific issues selected under Violations and Review Tabs. | ||
| - #### **Search and Filter Options** | ||
| The top bar helps you locate specific issues: | ||
| - **Dropdown Filters:** Select **All TestCases** or **All Pages** to view all issues. You can also select a specific test case or page to filter the results for that item only. | ||
| - **Filter and Search:** Select **Filters** to apply specific criteria, or use the **Search** box to find issues by keyword. | ||
| - **View Options:** The **Step Level** label confirms the issues are currently being shown at the test step level. You can use the status dropdown to filter the list by issue status. | ||
|
|
||
| - **Next/Previous Buttons**: Allows users to scroll through the list of identified issues. | ||
| - #### **Issues List** | ||
| The main table on the left lists the violations based on your search criteria. | ||
| - **WCAG Criteria:** Shows the specific rule ID. You can sort the list by this column. | ||
| - **Check Description:** Provides a summary of the rule violation. | ||
| - **Status:** Indicates the result of the check. | ||
| - **No of Checks:** Shows the number of times this specific issue occurred. | ||
| - **Severity:** Displays a color-coded label indicating the impact level.  | ||
|
|
||
| - **Issue Details**: This section briefly explains the detected issue with the affected **URL**, **page**, **element details**, and **screenshots**. | ||
|
|
||
| <br> | ||
| - #### **Issue Details** | ||
| When you select a row in the **Issues List**, the pane on the right displays detailed information to help you fix the issue. | ||
|
|
||
| Here's a quick GIF demonstrating how to enable the Accessibility Testing in Testsigma. | ||
| - **Previous / Next:** Select these buttons to look through all the instances of the single selected issue. If the **No of Checks** shows that the issue occurred multiple times (e.g., 15 times), you can use these buttons to cycle through and inspect all of those instances. | ||
| - **Description:** Displays the full definition of the violation. | ||
| - **Tags:** Shows the **WCAG Version**, the **Conformance Level**, and the specific Rule ID. | ||
| - **Affected Test Step:** Identifies the specific Test Case and Test Step where the failure occurred. | ||
| - **Element Details:** Displays the HTML code details for the element causing the issue. | ||
| - **Screenshot:** Shows an image of the page element at the time the error was detected. | ||
|
|
||
|  | ||
| ### **Global Header Actions** | ||
|
|
||
| The top-right corner of the page provides global actions for the report: | ||
| - **Compare Runs:** Select this to compare the current report against previous test runs to track improvements. | ||
| - **Export:** Select the export icon to save the report data. | ||
|
|
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
# First, read the file at the specified lines
sed -n '80,129p' src/pages/docs/accessibility-testing/accessibility-testing.md | cat -nRepository: testsigmahq/testsigma-docs
Length of output: 5424
🏁 Script executed:
# Check for markdownlint configuration files
find . -maxdepth 2 -type f \( -name ".markdownlint*" -o -name "markdownlint*" \) 2>/dev/nullRepository: testsigmahq/testsigma-docs
Length of output: 52
🏁 Script executed:
# Look for other documentation files to understand the style guide
fd -e md src/pages/docs/ | head -20Repository: testsigmahq/testsigma-docs
Length of output: 435
🏁 Script executed:
# Search for markdownlint config files more broadly
find . -type f \( -name ".markdownlint*" -o -name "markdownlint.config.*" \) 2>/dev/null | head -10Repository: testsigmahq/testsigma-docs
Length of output: 52
🏁 Script executed:
# Also check for linting config in package.json or similar
find . -maxdepth 2 -type f \( -name "package.json" -o -name ".eslintrc*" -o -name "prettier.config.*" \) 2>/dev/nullRepository: testsigmahq/testsigma-docs
Length of output: 84
🏁 Script executed:
# Examine a few other .md files to see the indentation pattern used
fd -x head -80 {} \; -e md src/pages/docs/ 2>/dev/null | head -150Repository: testsigmahq/testsigma-docs
Length of output: 52
🏁 Script executed:
# Let me fix the fd command to explore the docs directory structure
fd . src/pages/docs/ -e md 2>/dev/null | head -10Repository: testsigmahq/testsigma-docs
Length of output: 946
🏁 Script executed:
# Check package.json for markdownlint dependencies and scripts
cat package.json | grep -A 20 -B 5 "lint\|markdown" || cat package.jsonRepository: testsigmahq/testsigma-docs
Length of output: 2145
🏁 Script executed:
# Look at one FAQ file to compare markdown structure
head -100 src/pages/docs/FAQs/general/how-to-handle-browser-related-pop-up-issues.mdRepository: testsigmahq/testsigma-docs
Length of output: 1504
🏁 Script executed:
# Let me verify the actual indentation pattern in the file more clearly
# Show the exact spacing for lines 20, 26, 35 (the problematic subheadings)
sed -n '20p;26p;35p' src/pages/docs/accessibility-testing/accessibility-testing.md | od -c | head -30Repository: testsigmahq/testsigma-docs
Length of output: 110
🏁 Script executed:
# Also check lines 11-14 (top-level bullets) for comparison
sed -n '11p;12p' src/pages/docs/accessibility-testing/accessibility-testing.md | od -c | head -20Repository: testsigmahq/testsigma-docs
Length of output: 110
🏁 Script executed:
# Show the raw indentation with visible spaces
sed -n '11,14p;20,24p;26,32p;35,43p' src/pages/docs/accessibility-testing/accessibility-testing.md | cat -ARepository: testsigmahq/testsigma-docs
Length of output: 1463
🏁 Script executed:
# Get the exact section we need (lines 80-129) with visible spaces
sed -n '80,129p' src/pages/docs/accessibility-testing/accessibility-testing.md | cat -ARepository: testsigmahq/testsigma-docs
Length of output: 5124
Restructure the markdown to separate subheadings from bullet lists.
The indentation pattern at lines 99–129 uses non-standard spacing (3-space and 6-space increments) and embeds subheadings as bullet items (e.g., - #### **Search and Filter Options**). Subheadings should be separated from bullet lists and start at the left margin, with nested content properly indented by consistent 2-space increments following standard markdown conventions.
Restructure as follows:
- Top-level bullet points (e.g.,
- **Issue Overview:**) at column 0 with 2-space indentation for nested items - Subheadings (e.g.,
#### **Search and Filter Options**) at column 0, not nested within bullets - Description text and nested bullets under each section indented consistently by 2 spaces
🧰 Tools
🪛 LanguageTool
[style] ~115-~115: Consider using a different verb for a more formal wording.
Context: ...splays detailed information to help you fix the issue. - **Previous / Next:*...
(FIX_RESOLVE)
🪛 markdownlint-cli2 (0.18.1)
97-97: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
98-98: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
99-99: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
105-105: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
105-105: Headings must start at the beginning of the line
(MD023, heading-start-left)
107-107: Unordered list indentation
Expected: 2; Actual: 7
(MD007, ul-indent)
108-108: Unordered list indentation
Expected: 2; Actual: 7
(MD007, ul-indent)
109-109: Unordered list indentation
Expected: 2; Actual: 7
(MD007, ul-indent)
111-111: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
111-111: Headings must start at the beginning of the line
(MD023, heading-start-left)
113-113: Unordered list indentation
Expected: 2; Actual: 6
(MD007, ul-indent)
114-114: Unordered list indentation
Expected: 2; Actual: 6
(MD007, ul-indent)
115-115: Unordered list indentation
Expected: 2; Actual: 6
(MD007, ul-indent)
116-116: Unordered list indentation
Expected: 2; Actual: 6
(MD007, ul-indent)
117-117: Unordered list indentation
Expected: 2; Actual: 6
(MD007, ul-indent)
119-119: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
119-119: Headings must start at the beginning of the line
(MD023, heading-start-left)
121-121: Unordered list indentation
Expected: 2; Actual: 6
(MD007, ul-indent)
122-122: Unordered list indentation
Expected: 2; Actual: 6
(MD007, ul-indent)
123-123: Unordered list indentation
Expected: 2; Actual: 6
(MD007, ul-indent)
124-124: Unordered list indentation
Expected: 2; Actual: 6
(MD007, ul-indent)
125-125: Unordered list indentation
Expected: 2; Actual: 6
(MD007, ul-indent)
🤖 Prompt for AI Agents
In src/pages/docs/accessibility-testing/accessibility-testing.md around lines 80
to 129 the markdown mixes subheadings into bullet lists and uses inconsistent 3-
and 6-space indentation; move all subheadings (e.g., "#### **Search and Filter
Options**") to column 0 (no leading dash), place top-level bullets (e.g., "-
**Issue Overview:**") at column 0, and re-indent nested description text and
bullet items using consistent 2-space increments so headings are not nested
under list items and nested content aligns with standard Markdown conventions.
| ## **Interacting with Accessibility Report** | ||
|
|
||
| ### **Top Bar** | ||
|
|
||
|  | ||
|
|
||
| - **Title**: Displays the title of the report (e.g., Demo MAT). | ||
|
|
||
| - **Run Information**: Indicates the specific test run ID (e.g., Run - 45). | ||
|
|
||
| --- | ||
|
|
||
| ### **Test Cases Dropdown** | ||
|
|
||
|  | ||
| The **Accessibility Report** page displays the results of your accessibility scans for Android and iOS applications. You can use this page to review errors, check severity levels, and identify the specific UI elements that need attention. | ||
|
|
||
| - This dropdown helps you filter the report by specific test cases that are tested for accessibility compliance. | ||
| The page is organized into two main tabs: **Overview** and **All Issues**. | ||
|
|
||
| [[info | **NOTE**:]] | ||
| | By default, all test cases are selected, but you can choose a specific test case from the dropdown to focus on issues with one URL at a time. | ||
|
|
||
| --- | ||
| ### **Overview Tab** | ||
|
|
||
| ### **Issue Overview** | ||
| The **Overview** tab provides a visual summary of the test execution, helping you quickly check the overall status of the application. | ||
| - **Issue Overview:** Displays a donut chart that summarizes all issues found during the test. The chart groups issues by severity: **Critical, Serious, Moderate, Minor,** and **Success**.  | ||
| - **Issues by WCAG Principle:** Organizes findings by WCAG principles, such as **Perceivable, Operable, Understandable,** and **Robust**. This section lists the specific criteria violations and the number of failed checks for each principle.  | ||
| - **Issues by Components:** Categorizes issues by native UI element types. This helps you see if specific mobile components cause repeated errors.  | ||
|
|
||
|  | ||
| ### **All Issues Tab** | ||
|
|
||
| - **Total Issues**: The Donut Chart displays the total number of issues detected during the test. Depending on severity, issues are categorized as Critical, Serious, Moderate, and Minor. | ||
|
|
||
| - **Issues by Category**: This categorization provides users insights into specific accessibility challenges that were identified with a horizontal progress bar showing the number of issues under that category. | ||
|
|
||
| --- | ||
|
|
||
| ### **Violations/Review Tabs** | ||
|
|
||
|  | ||
|
|
||
| - **Violations**: This lists all accessibility issues that need immediate action. | ||
|
|
||
| - **Review Required**: This lists all accessibility issues that need manual review. Although Testsigma has identified these issues, we recommend a closer review for accuracy. | ||
|
|
||
| [[info | **NOTE**:]] | ||
| | The issues are color-coded with labels to indicate their severity level. You can also filter the issues based on severity and category. | ||
|
|
||
| --- | ||
|
|
||
| ### **Issue Navigation Panel** | ||
|
|
||
|  | ||
|
|
||
| - **Pagination Controls**: Provides navigation between the individual issues of specific issues selected under **Violations** and **Review Tabs**. | ||
|
|
||
| - **Next/Previous Buttons**: Allows users to scroll through the list of identified issues. | ||
|
|
||
| - **Issue Details**: This section briefly explains the detected issue with the affected **Affected Test Step**, **Element Details**, and **Screenshots**. | ||
|
|
||
|
|
||
| --- | ||
| The **All Issues** tab displays a detailed list of every violation found. You can use this tab to investigate specific bugs and view relevant code. This tab includes search tools, an issues list, and a details pane. | ||
|
|
||
| ## **Accessibility Rules** | ||
| - #### **Search and Filter Options** | ||
| The top bar helps you locate specific issues: | ||
| - **Dropdown Filters:** Select **All TestCases** to view all issues, or select a specific test case to filter the results.  | ||
| - **Filter and Search:** Select **Filters** to apply specific criteria, or use the **Search** box to find issues by keyword.  | ||
| - **View Options:** Use the status dropdown to filter the list by issue status.  | ||
|
|
||
| | **Rule ID** | **Description** | **Platform** | **WCAG Compliance** | | ||
| |------------------------------|-------------------------------------------------------------------------|------------------|----------------------| | ||
| | TEXT\_COLOR\_CONTRAST | Ensures text contrast meets minimum readability standards. | Android & iOS | 2.0 – 1.4.3 AA | | ||
| | NESTED\_CONTROL | Ensures interactive elements are not nested within each other. | Android | 2.0 – 2.1.1 A | | ||
| | IMAGE\_VIEW\_DESCRIPTION | Ensures images have meaningful descriptions for assistive technologies. | Android & iOS | 2.0 – 1.1.1 A | | ||
| | INTERACTIVE\_ELEMENT\_LABEL | Ensures interactive elements have clear accessibility labels. | Android | 2.1 – 2.4.6 AA | | ||
| | LABEL\_IN\_NAME | Ensures text labels match their accessibility labels. | Android & iOS | 2.1 – 2.5.3 A | | ||
| | BUTTON\_IN\_NAME | Ensures button labels start with capital letters. | Android | 2.1 – 3.1.6 AAA | | ||
| | EDITABLE\_TEXT\_LABEL | Ensures editable elements have both name and value. | Android | 2.0 – 4.1.2 A | | ||
| | DUPLICATE\_TEXT\_LABEL | Ensures no duplicate accessibility labels exist on the same screen. | Android | 2.1 – 4.1.2 A | | ||
| | TOUCH\_TARGET\_SIZE | Ensures interactive elements have a minimum tappable area. | Android & iOS | 2.1 – 2.5.5 AAA | | ||
| | NESTED\_ELEMENT\_NAME | Ensures visible text is included in accessible names. | iOS | 2.0 – 1.3.2 A | | ||
| | ACTIVE\_CONTROL | Ensures interactive elements have accessible names. | iOS | 2.0 – 4.1.2 A | | ||
| | COLLIDING\_ELEMENT | Ensures elements do not overlap. | iOS platform guideline | – | | ||
| - #### **Issues List** | ||
| The main table on the left lists the violations based on your search criteria. | ||
| - **WCAG Criteria:** Shows the specific rule ID. You can sort the list by this column. | ||
| - **Check Description:** Provides a summary of the rule violation. | ||
| - **Status:** Indicates the result of the check. | ||
| - **No of Checks:** Shows the number of times this specific issue occurred. | ||
| - **Severity:** Displays a color-coded label indicating the impact level.  | ||
|
|
||
| - #### **Issue Details** | ||
| When you select a row in the **Issues List**, the pane on the right displays detailed information to help you fix the bug. | ||
| - **Previous / Next:** Select these buttons to look through all the instances of the single selected issue. If the No of Checks shows that the issue occurred multiple times, you can use these buttons to cycle through and inspect all of those instances. | ||
| - **Description & Tags:** Shows the full definition of the violation, along with tags for the WCAG Version and Conformance Level. | ||
| - **Affected Test Step:** Identifies the specific Test Case and Test Step where the failure occurred. | ||
| - **Element Details:** Displays the actual native code for the element causing the issue. | ||
| - **Screenshot:** Shows an image of the mobile screen element at the time the error was detected.  | ||
|
|
||
| ### **Global Header Actions** | ||
|
|
||
| The top-right corner of the page provides global actions for the report: | ||
| - **Compare Runs:** Select this to compare the current report against previous test runs to track improvements. | ||
| - **Export:** Select the export icon to save the report data. |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
# First, let's find the file and check its structure
find . -name "mobile-accessibility-testing.md" -type fRepository: testsigmahq/testsigma-docs
Length of output: 140
🏁 Script executed:
# Also search for the web file mentioned in the comment
find . -name "*accessibility*" -type f | grep -E "(web|html)" | head -20Repository: testsigmahq/testsigma-docs
Length of output: 52
🏁 Script executed:
# Read the specific file section mentioned
sed -n '88,131p' src/pages/docs/accessibility-testing/mobile-accessibility-testing.md | cat -ARepository: testsigmahq/testsigma-docs
Length of output: 4663
🏁 Script executed:
# Search for web version or similar accessibility testing file
find . -name "*accessibility*" -type f | head -20Repository: testsigmahq/testsigma-docs
Length of output: 369
🏁 Script executed:
# Check if there's a web version of this file
git log --oneline --all -- "*accessibility*testing*" | head -10Repository: testsigmahq/testsigma-docs
Length of output: 351
🏁 Script executed:
# Let's look at other markdown files in the same directory to see the standard indentation pattern
ls -la src/pages/docs/accessibility-testing/Repository: testsigmahq/testsigma-docs
Length of output: 340
🏁 Script executed:
# Check another file in the docs directory to see standard indentation
head -150 src/pages/docs/accessibility-testing/web-accessibility-testing.md | tail -80 | cat -ARepository: testsigmahq/testsigma-docs
Length of output: 194
🏁 Script executed:
# Let's read accessibility-testing.md to find the similar section
grep -n "Interacting with Accessibility Report" src/pages/docs/accessibility-testing/accessibility-testing.mdRepository: testsigmahq/testsigma-docs
Length of output: 168
🏁 Script executed:
# Check the structure of accessibility-testing.md around similar content
sed -n '1,200p' src/pages/docs/accessibility-testing/accessibility-testing.md | cat -ARepository: testsigmahq/testsigma-docs
Length of output: 9362
🏁 Script executed:
# Let me verify markdown rendering by checking if there are any linting configs
find . -name ".markdownlint*" -o -name "prettier*" -o -name ".mdl*" | head -10Repository: testsigmahq/testsigma-docs
Length of output: 52
🏁 Script executed:
# Check standard indent patterns in other doc sections to establish best practice
sed -n '80,150p' src/pages/docs/accessibility-testing/accessibility-testing.md | grep -E "^[[:space:]]*(-|[0-9]+\.)" | head -20Repository: testsigmahq/testsigma-docs
Length of output: 3442
Fix inconsistent list indentation in the "All Issues Tab" section.
The nested bullets under "Search and Filter Options" (lines 102–104) use 7 spaces, while the nested bullets under "Issues List" and "Issue Details" (lines 108–112, 116–120) use 6 spaces. This inconsistency will cause rendering problems. Use 6 spaces consistently for all nested bullets to match the web version (accessibility-testing.md). Additionally, line 123 ("The top-right corner of the page...") is indented with 2 spaces before the bullets that follow; it should have no indentation to match the web version structure.
🧰 Tools
🪛 markdownlint-cli2 (0.18.1)
97-97: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
98-98: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
99-99: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
105-105: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
105-105: Headings must start at the beginning of the line
(MD023, heading-start-left)
107-107: Unordered list indentation
Expected: 2; Actual: 7
(MD007, ul-indent)
108-108: Unordered list indentation
Expected: 2; Actual: 7
(MD007, ul-indent)
109-109: Unordered list indentation
Expected: 2; Actual: 7
(MD007, ul-indent)
111-111: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
111-111: Headings must start at the beginning of the line
(MD023, heading-start-left)
113-113: Unordered list indentation
Expected: 2; Actual: 6
(MD007, ul-indent)
114-114: Unordered list indentation
Expected: 2; Actual: 6
(MD007, ul-indent)
115-115: Unordered list indentation
Expected: 2; Actual: 6
(MD007, ul-indent)
116-116: Unordered list indentation
Expected: 2; Actual: 6
(MD007, ul-indent)
117-117: Unordered list indentation
Expected: 2; Actual: 6
(MD007, ul-indent)
119-119: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
119-119: Headings must start at the beginning of the line
(MD023, heading-start-left)
121-121: Unordered list indentation
Expected: 2; Actual: 6
(MD007, ul-indent)
122-122: Unordered list indentation
Expected: 2; Actual: 6
(MD007, ul-indent)
123-123: Unordered list indentation
Expected: 2; Actual: 6
(MD007, ul-indent)
124-124: Unordered list indentation
Expected: 2; Actual: 6
(MD007, ul-indent)
125-125: Unordered list indentation
Expected: 2; Actual: 6
(MD007, ul-indent)
130-130: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
131-131: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
🤖 Prompt for AI Agents
In src/pages/docs/accessibility-testing/mobile-accessibility-testing.md around
lines 88 to 131, the nested bullet indentation is inconsistent: change the three
nested bullets under "Search and Filter Options" (lines ~102–104) from 7 spaces
to 6 spaces so they match the nested bullets used in "Issues List" and "Issue
Details" (~108–112, ~116–120), and remove the two-space indentation before the
"The top-right corner of the page..." paragraph (line ~123) so the following
bullets ("Compare Runs" and "Export") are aligned as top-level bullets; ensure
all nested list items use exactly 6 leading spaces and top-level
paragraphs/bullets have no leading spaces to match the web version.
2 participants
Updated the Accessibility Testing docs as per the ticket https://testsigma.atlassian.net/browse/DOC-713
Summary by CodeRabbit
Documentation
✏️ Tip: You can customize this high-level summary in your review settings.