Identity UI uses heading elements inconsistently

[SteveSandersonMS]

This was reported as an accessibility issue. See details at https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1162883

In short, we should use HTML heading elements in order, starting from <h1>, then <h2>, etc., without gaps in the sequence. There are many parts of the identity UI that don't do this. For example the "my profile" screen has h2 then h4.

[blowdart]

The linked document doesn't say anything about heading levels not being skippable or without gaps, and does not seem to be an immediate accessibility violation. As there's no time ever set aside for identity UI this is going to be backlogged, unless you feel it is blocking,

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[SteveSandersonMS]

@blowdart I know it's not an authoritative rule, but this W3C page about accessible headings specifically gives the following example of what not to do:

Make sure that a <h2> is not followed directly by an <h4>, for example

It may be fine to leave this on the backlog but @mkArtakMSFT has more context on that.

[blowdart]

It's as much a case of time, and the cascading changes into templates. @mkArtakMSFT would need to talk with @ajcvickers about Hao's time here.

[mkArtakMSFT]

Thanks for investigation, @SteveSandersonMS.
I've resolved the related AzDO issue indicating that we will be addressing this post 5.0.

[HaoK]

So just to clarify the change we want to make eventually while things are fresh, we just want to sequentially step up or down? i.e. h1 h2 h3 h4, and always starting at h1?

[SteveSandersonMS]

Yes, that’s what I understand the requirement to be. However I’m still open to the possibility that this is a bogus requirement, as the W3C doc stating it doesn’t give any justification or evidence for the need.

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.