Skip to content

Document kobiton:accessibilityValidation capability for Appium automation - #576

Open
tiffany-kobiton wants to merge 3 commits into
mainfrom
docs/add-accessibility-validation-capability
Open

tiffany-kobiton wants to merge 3 commits into
mainfrom
docs/add-accessibility-validation-capability

Conversation

@tiffany-kobiton

Copy link
Copy Markdown
Contributor

Summary

  • Add kobiton:accessibilityValidation to the Kobiton capabilities reference (index + full entry)
  • Add a [NOTE] to the Validate accessibility page pointing Appium automation users at the capability

Context

Per Slack thread with Ngo Le (mcp-features channel), a customer at Unum reported that accessibility results were not appearing for Appium automation sessions — they show automatically for manual sessions. The fix is to add kobiton:accessibilityValidation=true to the automation script's capabilities. This capability was undocumented, so this PR fills that gap.

Files touched

  • docs/modules/automation-testing/pages/capabilities/available-capabilities.adoc — new capability entry + index update
  • docs/modules/session-explorer/pages/validations/validate-accessibility.adoc — cross-reference NOTE for Appium automation users

Test plan

  • Rendered docs show the new kobiton:accessibilityValidation entry in the Kobiton capabilities index and section
  • Rendered Validate accessibility page shows the NOTE with a working xref to the capability entry
  • Confirm capability behavior wording with Ngo Le if further clarification needed (current wording follows Ngo's Slack description)

Related

  • Slack thread: mcp-features channel, Aug 27 – Sep 4, 2026 (Erin Bailey / Ngo Le / Phuong Thao Nguyen Vu)

🤖 Generated with Claude Code

Add the kobiton:accessibilityValidation capability to the Kobiton capabilities reference and cross-reference it from the Validate accessibility page. Accessibility checks run automatically for manual sessions but are omitted from Appium automation sessions unless this capability is added to the script with value true.

Confirmed via Slack thread with Ngo Le (mcp-features channel): customer Praveen at Unum was not seeing accessibility results for Appium automation runs; adding kobiton:accessibilityValidation=true to the capabilities is the required fix.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@tiffany-kobiton tiffany-kobiton added update existing doc Update of any size made to any existing doc on any platform. ready for review Doc is ready for review labels Sep 4, 2026
Replace vague "to see results here" with explicit "so accessibility results appear on the session timeline in Session Explorer". Ties the NOTE to the specific UI location the reader will hunt for, matching the "green marker in the session timeline" step in the section below.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

@erincbailey erincbailey left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Accessibility validations must be part of the subscription currently for both manual and Appium automation. Can we add that in both places? Then happy to publish.

Per review feedback on PR #576.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@tiffany-kobiton

Copy link
Copy Markdown
Contributor Author

@erincbailey Added the subscription mention to both places. Let me know if 'paid Kobiton subscriptions' matches what you meant. Happy to reword.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready for review Doc is ready for review update existing doc Update of any size made to any existing doc on any platform.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants