Document kobiton:accessibilityValidation capability for Appium automation - #576
Open
tiffany-kobiton wants to merge 3 commits into
Open
tiffany-kobiton wants to merge 3 commits into
tiffany-kobiton wants to merge 3 commits into
Conversation
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>
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
requested changes
Sep 8, 2026
erincbailey
left a comment
Contributor
There was a problem hiding this comment.
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>
Contributor
Author
|
@erincbailey Added the subscription mention to both places. Let me know if 'paid Kobiton subscriptions' matches what you meant. Happy to reword. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
kobiton:accessibilityValidationto the Kobiton capabilities reference (index + full entry)[NOTE]to the Validate accessibility page pointing Appium automation users at the capabilityContext
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=trueto 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 updatedocs/modules/session-explorer/pages/validations/validate-accessibility.adoc— cross-reference NOTE for Appium automation usersTest plan
kobiton:accessibilityValidationentry in the Kobiton capabilities index and sectionRelated
mcp-featureschannel, Aug 27 – Sep 4, 2026 (Erin Bailey / Ngo Le / Phuong Thao Nguyen Vu)🤖 Generated with Claude Code