[Feature] Improve accessibility labels and high-contrast support for network analysis

[AnaFerreira015]

Short title

Accessibility and Readability Enhancement

Is your feature request related to a problem? Please describe.

Yes. I’m Ana Ferreira, a Master's student in Computer Science conducting research on mobile accessibility. Currently, WiFiAnalyzer presents barriers for users with visual impairments:

1. Unlabelled Controls: Several buttons on the main scanning screen (like pause/play, frequency band toggles, and filters) lack text descriptions. TalkBack announces them only as "Unlabelled" (violating WCAG 4.1.2).
2. Low Contrast: Some signal level indicators and technical labels do not meet the minimum 4.5:1 contrast ratio, making them hard to read in bright environments or for users with low vision (WCAG 1.4.3).

Describe the solution you'd like

would like the app to implement the following:

1. Accessible Labels: Add android:contentDescription to all interactive icons and status indicators so screen readers can convey their purpose.
2. High-Contrast Theme Support: Adjust the color palette for technical lists and graphs to ensure all text meets WCAG AA contrast standards.
3. Dynamic Scaling: Ensure technical data (like SSID names and MAC addresses) scales properly when the system font size is increased (WCAG 1.4.4).

Alternatives considered

I considered using a third-party accessibility "overlay" app, but these are often unreliable and don't fix the underlying code issues. Integrating these fixes directly into the app using Material Design's accessibility standards is the most robust and sustainable solution.

During my analysis, I also identified 5 other technical issues (including Target Size and Overlapping Elements). I can provide the technical details or open new specific tickets if the maintainers prefer.

How I can help

No response

Reproduction / Occurrence frequency

None

Priority / Impact

None

Device model

No response

Android version

No response

Android API level

No response

WiFiAnalyzer version

No response

Build variant

No response

Additional context

No response

Screenshots / Mockups / Attachments (optional)

No response

[VREMSoftwareDevelopment]

Thanks for reporting these accessibility concerns.

All active contributors are currently focused on other work, so we can’t take this on right now. Contributions are welcome — feel free to fork the project and open a PR.

Looking forward to your PR.