microsoft / microsoft/BotFramework-WebChat

Timestamp is only visible to screenreaders

Open
#4,985 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area-accessibility Bot Services bug customer-reported
Dominant language
HTML
Stars
1.8k
Forks
1.6k
Avg merge
22h 58m
Merged PRs (30d)
2

Description

Is it an issue related to Adaptive Cards?

No.

What is the PWD impact?

No response

What browsers and screen readers do this issue affect?

No response

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?

Transcript navigation, Others or unrelated

What is the public URL for the website?

https://edfinancial.com

How to reproduce the issue?

This is feedback from the accessibility company Allyant who has been testing our website and has people who use screenreaders and other assistive technologies as a part of their testing team.

The timestamp is only visible to screenreaders and is on the page as transparent text for visual users. If the timestamp is intended to be hidden from the user, it needs to also be hidden from screenreaders through the use of display:none or visibility:hidden.

timestamp-only-visible-to-screenreaders

What do you expect?

Screen readers should not be able to read the timestamp text that appears as "hidden" to the visual user.

What actually happened?

See other responses.

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

No response

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

No response

MAS reference

No response

WCAG reference

https://www.https://www.w3.org/WAI/WCAG22/Understanding/name-role-valuew3.org/WAI/WCAG22/Understanding/name-role-value

WAI-ARIA reference

No response

Adaptive Card JSON

No response

Additional context

No response

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

Reproduce the issue at https://edfinancial.com and inspect the transcript timestamp in the rendered DOM and accessibility tree. Verify how the timestamp is exposed to screen readers while remaining transparent to visual users. Done means the timestamp is no longer exposed to screen readers and the visual transcript remains unchanged.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
accessibility, frontend
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.