search

microsoft / BotFramework-WebChat

A highly-customizable web-based client for Azure Bot Services.
https://www.botframework.com/
MIT License
1.59k stars 1.54k forks source link

The Bot response time "A minute ago" is not announced by screen reader NVDA in both Focus and Browse mode. #5015

Closed Kirank915 closed 7 months ago

Kirank915 commented 8 months ago

Is it an issue related to Adaptive Cards?

No.

What is the PWD impact?

Visually challenged users who rely on screen readers will be impacted if the bot response time is not announced by screen reader NVDA in both Focus and Browse mode.

What browsers and screen readers do this issue affect?

Windows: Edge with Windows Narrator

Are there any code-based customization done to Web Chat?

No, I am using Web Chat without any customizations except "styleOptions".

What version of Web Chat are you using?

Latest production

Which area does this issue affect?

Others or unrelated

What is the public URL for the website?

https://airtuserexpdev.azurewebsites.net/Dashboard

How to reproduce the issue?

Step 1: Open the URL: https://airtuserexpdev.azurewebsites.net/Dashboard in Edge Browser.

Step 2: AIRT Dashboard page will appear, Navigate to “Chat with Sage” chat box at the bottom of the page.

Step 3: Enable browse mode and navigate to "A minute ago" using down arrow key.

Step 4: Verify whether the Bot response time "A minute ago" is announcing by screen reader NVDA in both Focus and Browse mode or not.

What do you expect?

The Bot response time "A minute ago" should be announced by screen reader NVDA. NVDA should announce as "A minute ago" upon focusing on the "A minute ago" text in browse mode.

Note: Issue repro with all screen readers

What actually happened?

The Bot response time "A minute ago" is not announced by screen reader NVDA in both Focus and Browse mode.

Do you have any screenshots or recordings to repro the issue?

MAS 1 3 1_Bot response time is not announced by both focus and browse mode

Did you find any DOM elements that might have caused the issue?

No response

MAS reference

MAS 1.3.1 – Info and Relationships

WCAG reference

No response

WAI-ARIA reference

No response

Adaptive Card JSON

No response

Additional context

No response

Kirank915 commented 8 months ago

Bug copied from Accenture team: BUG 11645889

Kirank915 commented 8 months ago

A11yMAS;#A11ySev3;#MAS1.3.1;#HCL;#Accessibility;#FeatureBotframeworkwebchat-Apr23;

compulim commented 7 months ago

This is by design. We discussed with accessibility team and they suggested narrating an absolute timestamp, rather than a relative timestamp. This is because the relative timestamp will change from time to time.

Instead of narrating "a minute ago", we narrate the time, for example "three twenty P-M" for (3:20 PM).