microsoft / microsoft/AdaptiveCards

[Android][Accessibility] WCAG 1.3.1,WCAG 3.3.2: Active views must have a name that's available to assistive technologies. (android.widget.EditText)

Open
#4,110 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

AccessibilityInsightsGenerated Area-Accessibility Bug Platform-Android
Dominant language
C#
Stars
2k
Forks
595
Avg merge
1d 19h
Merged PRs (30d)
1

Description

Platform

  • Android

Version

master

Details

Issue

Active views must have a name that's available to assistive technologies. (ActiveViewName)

image

Target application

io.adaptivecards.adaptivecardssample

Element path

android.widget.EditText

How to fix
The view is active but has no name available to assistive technologies. Provide a name for the view using its contentDescription, hint, labelFor, or text attribute (depending on the view type)
Environment

This accessibility issue was found using Accessibility Insights for Android 2020.527.10 (axe-android), a tool that helps find and fix accessibility issues. Get more information & download this tool at http://aka.ms/AccessibilityInsights.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The report identifies the Android sample application io.adaptivecards.adaptivecardssample and an android.widget.EditText, but names no source file or test. Start by locating that view in the Android sample and verify it with Accessibility Insights; done when the EditText exposes a name to assistive technologies.

Written by the indexing model from the issue text.

Assessment

Tech stack
android
Domain
accessibility, mobile
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.