microsoft / microsoft/BotFramework-WebChat
[White Label - Markdown]: H1 heading is not defined on the page.
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 response
What is the PWD impact?
Screen reader users (e.g., those using JAWS, NVDA, or VoiceOver) rely on heading levels to understand page structure and quickly navigate content.
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 "Markdown" word in type your message text box.
4.Navigate to the search results.
5.Observe that, H1 heading is not defined on the page.
What do you expect?
The page should have a single, properly defined
heading that clearly conveys the main topic, appears at the top of the content, follows a logical heading hierarchy, and is accessible to assistive technologies.
What actually happened?
H1 heading is not defined on the page.
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/info-and-relationships
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 at the provided webchat-loader URL using the listed 4.18.1-main.20240927.ea7a875 version, then inspect the White Label Markdown search-results page and its heading hierarchy. Done means the page has one clear h1 at the top of the content and screen readers can identify the page structure.
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