- 
                Notifications
    You must be signed in to change notification settings 
- Fork 1.6k
Description
User Experience:
If headings are not defined programmatically on cards showing for Help keyword, then screen reader user will be disoriented and will not be able to navigate in heading mode. The user will also be facing issues while accessing and navigating on the page.
Note: Login Credentials must not be provided within the bug.
Test Environment:
OS Version: 21H1
OS Build: 19043.1110
Browser: Microsoft Edge Version 94.0.972.2 (Official build) dev (64-bit)
Screen Reader: Narrator
Repro steps:
- Open URL Provided by product owner.
- Web chat bundle will open.
- Navigate on the web chat bot and select microphone icon.
- Speak "help" keyword in Type your message box, then select send button.
- Cards related to the keyword will appear, navigate on the cards.
- Verify the issue.
Actual Result
Headings are not defined programmatically on cards showing for Help keyword. 'Accessibility' heading is not defined in heading tags.
Expected Result
Headings should be defined programmatically on cards showing for Help keyword. 'Accessibility' heading should be defined in heading tags.
Note: This issue exists with similar controls throughout the application.
MAS Reference
WCAG 2.4.6 – Headings and Labels
Reference Links
Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier.