Upon invoking Quick Start local C++ Workflow, Ensures That Lists are Structured Correctly.

[msftedad]

Environment Details:

OS version: Version 22H2 (OS Build 22610.1)
Microsoft Edge version: Version 101.0.1210.47 (Official build) (64 bit)

Repro steps:

1. Open URL: https://zorana-jankovic.github.io/example/#/
2. Navigate to the "first level child" control under first level and activate it.
3. Now use f12 to inspect and observe the issue.

Actual Result:

lists are structured incorrectly.

Expected Result:

Ensures that lists are structured correctly

Screenshot Attachment:

[zorana-jankovic]

Any update on this bug so far?

[sy-records]

Can you elaborate on your question?

[trusktr]

What's the bug?

[v-sudmandal]

Hi @msftedad

Please let us know your plans on fixing this bug so that our team will regress and close it which makes the product compliant.

[SritejaGolla]

Hi @trusktr & @sy-records ,

Here the issue is - the list items which are from docsify component are having direct child items to the list, which are not allowed to be inside the "li" elements

[trusktr]

What's the bug exactly?

[zorana-jankovic]

Bug that is reported is accessibility bug.
The way that nesting the list in sidebar now works is:

The problem is that the direct child of <ul> element shouldn't be another <ul> element (which is rule defined for making a list with a good structure, with a purpose to help users with disabilities), as then when an assistive technology encounters a list that is structured like that it might respond in an unexpected way.
The problem could be solved by enclosing this nested <ul> with <li> element:

Accessibility Insights for Web can be used to test accessibility.

[v-sudmandal]

Any update on this bug when it can be fixed?

[v-shamohsin]

Can you please provide update on the bug

[sy-records]

okay, I got it. Thank you @zorana-jankovic
I will try to fix it.

[v-shamohsin]

@sy-records - Can I have an ETA on the bug fix?

[v-shamohsin]

@sy-records - Can you please provide an ETA

[msftedad]

Hi Team, is there any update on this bug?