What problem does this solve in your TCC permission workflow?
Users who rely on VoiceOver need the permission table and interactive controls in the WKWebView layer to expose meaningful labels, roles, and state. Without that, core auditing and editing flows are harder or impossible to use.
What behaviour do you want?
Ensure all table cells and interactive controls in the WKWebView layer are accessible via VoiceOver.
That should include, at minimum:
- accessible labels for app rows and permission cells
- announced state for granted, denied, and never-prompted values
- clear focus order and keyboard navigation
- accessible names for edit actions and pending-change indicators
Why does this fit a local macOS TCC editor instead of a system tool or third-party service?
Accessibility is a core quality requirement of the local app experience. This improves the primary workflow for users on macOS without introducing any network or service dependency.
Scope check
Please confirm this request fits the project scope in CONTRIBUTING.md: local file workflow, no network dependency, and no writes to system TCC files.
Additional context
It may help to define acceptance criteria around VoiceOver announcements for table navigation, cell activation, and pending edits so regressions can be tested consistently.
What problem does this solve in your TCC permission workflow?
Users who rely on VoiceOver need the permission table and interactive controls in the WKWebView layer to expose meaningful labels, roles, and state. Without that, core auditing and editing flows are harder or impossible to use.
What behaviour do you want?
Ensure all table cells and interactive controls in the WKWebView layer are accessible via VoiceOver.
That should include, at minimum:
Why does this fit a local macOS TCC editor instead of a system tool or third-party service?
Accessibility is a core quality requirement of the local app experience. This improves the primary workflow for users on macOS without introducing any network or service dependency.
Scope check
Please confirm this request fits the project scope in
CONTRIBUTING.md: local file workflow, no network dependency, and no writes to system TCC files.Additional context
It may help to define acceptance criteria around VoiceOver announcements for table navigation, cell activation, and pending edits so regressions can be tested consistently.