Skip to content

Commit

Permalink
remove unwanted line
Browse files Browse the repository at this point in the history
Co-authored-by: Rory Abraham <[email protected]>
  • Loading branch information
robertKozik and roryabraham authored Sep 18, 2023
1 parent 13845d3 commit a464bba
Showing 1 changed file with 0 additions and 1 deletion.
1 change: 0 additions & 1 deletion contributingGuides/ACCESSIBILITY.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,6 @@ For iOS, you can use the `accessibility inspector` app to test for accessibility
For Android, you can use the [accessibility scanner](https://support.google.com/accessibility/android/answer/6376570) app to test for accessibility. You can find it in the Google Play Store. This app allows you to inspect the accessibility properties of any element on the screen. You can also use it to simulate different accessibility settings, such as TalkBack, color blindness, and more. It's a great tool for testing whether created component has accessibility properties set correctly. The [result of the accessibility scanner](https://support.google.com/accessibility/android/answer/6376559) app has information about content labeling, implementation, touch target size and low contrast
This tool requires an installed APK to test on.


- **Web/Desktop**
On Mac, you can use the [VoiceOver](https://www.apple.com/accessibility/mac/vision/) app to test for accessibility. You can find it in the Mac menu under `System Preferences > Accessibility > VoiceOver` or by pressing `Cmd + F5`. This app allows you to inspect the accessibility properties of any element on the screen. You can also use it to simulate different accessibility settings, such as VoiceOver, color blindness, and more. It's a great tool for testing whether created component has accessibility properties set correctly.

Expand Down

0 comments on commit a464bba

Please sign in to comment.