Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Programmatic Access - BOT Framework - Web Chat > Enter Keyword]: Multiple H1 headings are defined for the controls like 'Accessibility', 'Adaptive card', 'Animation card' and etc. #4721

Closed
KattaBhargav opened this issue May 4, 2023 · 1 comment · Fixed by #4747
Assignees
Labels
area-accessibility blocked currently prevented from making progress bug Indicates an unexpected problem or an unintended behavior.

Comments

@KattaBhargav
Copy link

User Experience:

If the heading level is incorrect & multiple H1 headings are defined, then it will be difficult for screen reader users to understand the relevance of the content they are interacting with.

Note

User credentials should NOT be included in the bug.

Repro Steps:

  1. Launch URL: https://microsoft.github.io/BotFramework-WebChat/01.getting-started/a.full-bundle/ on edge dev.
  2. Web chat page opens.
  3. Press 4-tab keys to reach 'Type your message' field. Enter the "Help" keyword on it. Press 1-tab key to reach the 'send' button and activate it with the enter key.
  4. Press 2-shift tabs and 1-down arrow to reach the received card.
  5. Verify whether multiple H1 headings are defined or not.

Actual Result:

Multiple H1 headings are defined for the controls like 'Accessibility', 'Adaptive card', 'Animation card' etc.

Expected Result:

All the H1 headings should be defined under H2 headings for the controls like 'Accessibility', 'Adaptive card', 'Animation card' etc.

MAS Reference:

MAS 1.3.1 – Info and Relationships

Reference Links:

  • Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier.
  • External Bug Process: If this bug belongs to the external team, mark it as resolved/done and assign it back to the tester with notes on where to file/route the bug. For more information, please use this link. “HCL Staff should not log any third-party external bugs. Should be routed to edad team”.
  • Please reach out to the C&AI Teams channel for any process-related queries.

Test Environment:

  • OS: Windows 11 Enterprise 22H2 (OS build: 22621.1555)
  • Browser: Edge Version 114.0.1807.6 (Official build) dev (64-bit)
  • URL: Web Chat: Full-featured bundle (microsoft.github.io)
  • Tools: Developer Tool
  • Screen Readers: Narrator, JAWS, NVDA
  • Matrix: Edge dev+ Narrator.
@KattaBhargav
Copy link
Author

KattaBhargav commented May 4, 2023

#A11yMAS;#A11ySev3;#HCL;#MAS1.3.1;#Accessibility;#Benchmark;#Win11-Edge(Chromium);#BotFrameworkWebChat-May23;

@compulim compulim self-assigned this Jun 15, 2023
@compulim compulim added area-accessibility bug Indicates an unexpected problem or an unintended behavior. labels Jun 15, 2023
@compulim compulim added the blocked currently prevented from making progress label Jun 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-accessibility blocked currently prevented from making progress bug Indicates an unexpected problem or an unintended behavior.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants