You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current hmpoRadios version always uses the fieldset hint property when rendering the aria-describedby html tag, which is used by accessibility screen readers to describe the fieldset in question. If the hint property is removed in the code like so:
{{ hmpoRadios(ctx, {
id: "couldNotMatchChoice",
namePrefix: "couldNotMatchChoice",
fieldset: {
legend: {
html: "<h2 class="govuk-!-margin-bottom-0">What would you like to do?",
isPageHeading: false,
classes: "govuk-fieldset__legend--m"
}
}
}) }}
then the aria-described still populates with value couldNotMatchChoice-hint. This means that nothing is read out, but there is no way to use other values as is a current requirement in a BAV CRI screen. Can this component be updated to accept other values or no values at all for the aria-describedby element in the HTML?
The text was updated successfully, but these errors were encountered:
The current hmpoRadios version always uses the fieldset hint property when rendering the aria-describedby html tag, which is used by accessibility screen readers to describe the fieldset in question. If the hint property is removed in the code like so:
{{ hmpoRadios(ctx, {
id: "couldNotMatchChoice",
namePrefix: "couldNotMatchChoice",
fieldset: {
legend: {
html: "<h2 class="govuk-!-margin-bottom-0">What would you like to do?",
isPageHeading: false,
classes: "govuk-fieldset__legend--m"
}
}
}) }}
then the aria-described still populates with value couldNotMatchChoice-hint. This means that nothing is read out, but there is no way to use other values as is a current requirement in a BAV CRI screen. Can this component be updated to accept other values or no values at all for the aria-describedby element in the HTML?
The text was updated successfully, but these errors were encountered: