microsoft / microsoft/BotFramework-WebChat
White Label - Document word]: Luminosity contrast ratio is 4.1:1 of time text, which is less than 4.5:1
Nobody has claimed this yet.
- 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?
Users with low vision or color-vision deficiencies may have difficulty reading the “Time text” text due to insufficient color contrast, making the form harder to understand, complete, or navigate.
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?
No response
How to reproduce the issue?
- Open URL: https://compulim.github.io/webchat-loader/ and sign in using valid credentials.
- Navigate to web chat page and select 4.18.1-main.20240927.ea7a875 (30/9/2024) version and then select mockBot link under present label and then select open web chat in new window link at bottom.
3.Navigate to white label experience chat page and type Document-word word in type your message text box.
4.Navigate to the search results.
5.Observe that, Luminosity contrast ratio is of time text which is less than 4.5:1
What do you expect?
The time text "6 minute ago" should have a color contrast ratio of at least 4.5:1 against its background to ensure that it is accessible to all users, including those with visual impairments.
What actually happened?
Luminosity contrast ratio is 4.1:1 of time text which is less than 4.5:1.
Do you have any screenshots or recordings to repro the issue?
Did you find any DOM elements that might have caused the issue?
No response
MAS reference
No response
WCAG reference
https://www.w3.org/WAI/WCAG21/Understanding/contrast-minimum
WAI-ARIA reference
No response
Adaptive Card JSON
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue through the webchat-loader URL using the listed 4.18.1 version, mockBot, white label experience, and search results. Start by tracing the “Time text” styling and styleOptions behavior; done means the “6 minute ago” text reaches at least a 4.5:1 contrast ratio against its background.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100