Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[3] Accessibility issues: Detect UI elements that are missing descriptions #50

Open
corbyziesman opened this issue Aug 29, 2019 · 1 comment
Open

[3] Accessibility issues: Detect UI elements that are missing descriptions #50

corbyziesman opened this issue Aug 29, 2019 · 1 comment
Labels
3p Medium complexity change – significant changes including possible modifications to public API s2: proposal Rough proposal, looking for community input. t1: feature Feature or enhancement – oriented around 'ADDING value' (e.g. new or branching use-cases)

Comments

@corbyziesman
Copy link
Contributor

Detect UI elements that are missing meaningful Accessibility descriptions
@corbyziesman corbyziesman added 3p Medium complexity change – significant changes including possible modifications to public API t1: feature Feature or enhancement – oriented around 'ADDING value' (e.g. new or branching use-cases) s2: proposal Rough proposal, looking for community input. s3: in-progress Working away! and removed s2: proposal Rough proposal, looking for community input. s3: in-progress Working away! labels Aug 29, 2019
@corbyziesman
Copy link
Contributor Author

Not sure if this makes sense to do. The real way to find accessibility issues is to use Accessibility Inspector, which can find many different types of issues. It might be helpful to return an array of subviews that have nil (default) for accessibility traits, values, hints, etc (everything) to indicate views that were implemented with no accessibility in mind... or indicate a previously accessible view that got replaced with something that hasnt had any accessibility implemented yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
3p Medium complexity change – significant changes including possible modifications to public API s2: proposal Rough proposal, looking for community input. t1: feature Feature or enhancement – oriented around 'ADDING value' (e.g. new or branching use-cases)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@corbyziesman