Alert title is forcing a h4 tag even if a h4 isn't appropriate in context

[kdoberst]

Describe the issue. What is the expected and unexpected behavior?
When I use the Alert component, the text entered at the title prop is rendered inside an h4 tag. This may not be the appropriate heading or a heading may not be appropriate for the content.

For example, if my page looks like this:

<h2>My header</h2>
content 
ALERT GOES HERE

I would need the alert to render an h3 as the title with the child content below.

In other cases, as in the inline alert with no children elements. The content in the title attribute isn't a header at all, in that it doesn't describe the content below it.

See WCAG 2.1 1.3.1 and 2.4.6

Expected
I expect that I can override the default h4 tag with another tag that may be more appropriate in the context the alert is being used.

Please provide the steps to reproduce. Feel free to link CodeSandbox or another tool.
You can view this behavior on the Alert demo page

Is this a bug or enhancement? If this issue is a bug, is this issue blocking you or is there a work-around?
I would call this a bug because it can lead to accessibility issues. The current workaround is not to use the Alert component and use custom code.

What is your product and what release version are you targeting?
OpenShift 4.10

[kdoberst]

@tlabaj @nicolethoen @mcarrano I don't think the merge fix fully addresses this issue. Please consider reopening.

I don't think this use case was not addressed:

In other cases, as in the inline alert with no children elements. The content in the title attribute isn't a header at all, in that it doesn't describe the content below it.

So if I have an inline alert, the content below the alert may not be described by the alert itself.

Here's an example:

<dl>
<dt>Service Level Agreement</dt>
<dd>
   Self-support, 60 day trial
   <Alert variant="warning" isInline isPlain title="1 day remaining" />
</dd>
<dt>Cluster ID</dt>
<dd>
my_crazy_long_cluster_id
</dd>
</dl>

The alert warning text of "1 day remaining" doesn't really describe what is below - in this case, the cluster ID. I'm not sure a header at any level is appropriate in this case.

[kdoberst]

Can we please reopen this issue? It is causing accessibility issues in OCM.