-
Notifications
You must be signed in to change notification settings - Fork 107
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
JAWS and NVDA not detecting heading inside legend #534
Comments
I cant replicate this issue with my set up |
Hey folks, I think we've been made aware of the same issue and will be tackling this in this issue on GOV.UK Frontend: alphagov/govuk-frontend#1605 |
Thanks @NickColley, @Fenwick17 found it to the be the When Adam was testing this, he also tested GOVUK frontend and found it not to be an issue with the GOVUK fieldset. It looks like this particular fix was made to GOVUK frontend back in September (alphagov/govuk-frontend#1548). So I'm not sure if this is a different issue but I'll leave this open for discussion and maybe we can help, Adam may be able to add more info. |
We've fixed the original issue raised in release 3.0.0. Related: alphagov/govuk-frontend#1605 (comment) I'll close this issue for now. |
Bug Report
What is the issue?
When using an
<h#>
element within the<legend>
as per the 'Fieldset as page heading' pattern Jaws and NVDA will not treat this as a heading, therefore it does not display in the list of headings.What steps are required to reproduce the issue?
Access any page with a
<h#>
inside a<legend>
with Jaws or NVDAWhat was the environment where this issue occurred?
The text was updated successfully, but these errors were encountered: