Skip to content

feat: improve accessibility across app components and screens - #103

Closed
Opulencechuks wants to merge 3 commits into
ecotask-network:mainfrom
Opulencechuks:feature/accessibility-improvements
Closed

feat: improve accessibility across app components and screens#103
Opulencechuks wants to merge 3 commits into
ecotask-network:mainfrom
Opulencechuks:feature/accessibility-improvements

Conversation

@Opulencechuks

Copy link
Copy Markdown

Closes #96

Description

This PR addresses crucial accessibility issues to ensure that EcoTask is usable by visually impaired users relying on screen readers (like VoiceOver and TalkBack).
We audited and updated all interactive elements and dynamic content across the src/screens/ and src/components/ directories. Specifically:

  • Added accessibilityLabel and accessibilityRole="button" to all TouchableOpacity components.
  • Added accessibilityLabel to all TextInput elements.
  • Wrapped raw emoji icons in <Text> components with accessible={true}, an appropriate accessibilityLabel, and accessibilityRole="image".
  • Added accessibilityLiveRegion="polite" to loading and error states to properly announce dynamic content changes.

Closes #95

Type of Change

  • Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (fix or feature that breaks existing functionality)
  • Documentation update
  • Chore (deps, tooling, refactoring)

How Has This Been Tested?

  • Unit tests added / updated
  • Integration tests added / updated
  • Manual testing on Android
  • Manual testing on iOS

Checklist

  • My code follows the project's code style
  • I have performed a self-review of my own code
  • I have commented on complex or non-obvious code
  • I have updated the documentation where needed
  • My changes generate no new warnings or lint errors
  • All existing and new tests pass

Screenshots

nil

Additional Context

Out of scope for this PR: Full WCAG 2.1 AA audit and keyboard navigation for web. The focus here was entirely on making interactive elements screen-reader friendly for our core mobile audience in developing regions.

@cybermax4200 cybermax4200 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.

The ci check is failing, please kindly fix it

@cybermax4200 cybermax4200 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.

The ci checks are failing, please kindly fix it

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

Labels

None yet

Projects

None yet

2 participants