H1 in legend not available using shortcut key or elements list dialog with JAWS

[shabana-ali]

E.g. https://design-system.service.gov.uk/patterns/dates/default/index.html

[adamliptrot-oc]

Also an issue with Chrome (JAWS 2020)

[adamliptrot-oc]

@shabana-ali found that the removal of the overflow: hidden rule from the legend fixes this (confirmed in Chrome with JAWS 2020).
However this was added as a fix to a bug in webkit browsers which collapses margins on legends. Removing this will cause headings inside legends to lose their margin and so lose the spacing between them and following content.
This rule is being added by GovUK Elements:

// Hack to let legends or elements within legends have margins in webkit browsers
legend {
  overflow: hidden;
}

https://github.com/alphagov/govuk_elements/blob/master/assets/sass/elements/_forms.scss#L33

There is an alternative fix for the one provided in Elements:

legend + * {
  -webkit-margin-collapse: separate;
}

necolas/normalize.css#168

But this only seems to work if the contained element's margin is known in advance so it can be added to the legend.

More investigation required.

[adamliptrot-oc]

It looks like in Gov Frontend the margins are now placed on the legend itself rather than allowing the contained elements to set them, which would likely be the long-term fix for this.

[adamliptrot-oc]

Created test page at https://liptrot.org/demos/legends/

Results:

JAWS 2020 and JAWS 2019

• IE11 headings were not exposed at all in either case
• Chrome and Edge headings were exposed only in the second example

JAWS 2018

headings were exposed in all cases in all browsers

[chrismoorembe]

Therefore it could be a JAWS bug? You can report them here: https://support.freedomscientific.com/Forms/TechSupport

…

Sent from my iPhone

On 2 Oct 2020, at 2:07 pm, Adam Liptrot ***@***.***> wrote:  Created test page at https://liptrot.org/demos/legends/ Results: JAWS 2020 and JAWS 2019 IE11 headings were not exposed at all in either case Chrome and Edge headings were exposed only in the second example JAWS 2018 headings were exposed in all cases in all browsers — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[adamliptrot-oc]

Reported as a bug in JAWS to Freedom Scientific.

[adamliptrot-oc]

Freedom Scientific have recorded bug as 117537 and development team are investigating.

[adamliptrot-oc]

Related: w3c/html-aria#350

[adamliptrot-oc]

alphagov/govuk-frontend#1605 (comment)

update from Freedom Scientific which suggests that this bug will be looked at as part of their 2022 cycle (i.e: released as an update at some point to version 2022).

[ashfaqhussain357]

To be tested with Jaws 2022 and update findings here.

[ashfaqhussain357]

Issue resolved in Jaws 2022.