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.

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

[Accessibility][Info&Relationship-Filter Dialog]: Aria label and place holder both are defined same in the code on 'Filter Dialog' edit box. #2054

Closed
ashish315 opened this issue Feb 23, 2020 · 2 comments

Comments

@ashish315
Copy link

ashish315 commented Feb 23, 2020

User Experience
Screen reader users will get confused if the same information is convey by the narrator twice.

Test Environment
Browser: Microsoft Edge Canary Version: 82.0.425.0 (Official build)
OS build: 2004 (19564.1005)
Screen Reader: Narrator
URL: Bot Framework Composer
Prerequisite Here

Repro Steps:

  1. Open the above mentioned URL in EDGE and set the zoom at 400%.
  2. Select 'Design Flow' from left navigation.
  3. Now, navigate to the filter dialog edit field.
  4. Observe the narrator narration and find the issue.

Actual:
Aria label and place holder both are defined same in the code on 'Filter Dialog' edit box due to which screen reader is conveying the same information twice.

Expected:
Aria label and place holder both should be defined differently so that same information will not be convey twice. In Aria Label it should be 'Search available filters'.

Observation:
Same issue observed with NVDA.

MAS Impacted: MAS1.3.1

Attachment:
MAS1.3.1_Aria lable and placeholder both are same.zip

@beyackle
Copy link
Contributor

Is this problem now fully fixed and we can move this into Waiting for Verification, or is there more?

@ashish315
Copy link
Author

As checked now the aria label and placeholder are different but due to "placeholder narrated twice" know issue it still announces placeholder twice already raised issue for this.
So, HCL is closing this issue.

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

No branches or pull requests

6 participants