Investigate solution for operating the details component with Dragon

[owenatgov]

What

Investigate if it's possible to enhance the details component in order for it to be operable via Dragon.

Why

This is in response to https://github.com/alphagov/govuk-design-system/issues/4029. This was raised in a recent DAC audit that dictation software Dragon doesn't recognise the details component and can't operate it. More detail is available in that issue.

Notes

As mentioned in the linked issue, we'd like to avoid DAC's suggestion to convert the details component from a literal details element into an accordion-like component as this will add extra weight to govuk-frontend and undo work we did to remove the details polyfill for 5.0.

Timebox

1 week (preliminary)

Questions to answer

• [ ] Can we make Dragon recognise the details component as a details element?
• [ ] Is there a way to reimplement the polyfill progressively?

Done when

• [ ] Questions have been answered or we have a clearer idea of how to get to our goal
• [ ] Findings have been reviewed and agreed with at least one other person
• [ ] Findings have been shared, e.g: via a write-up on the ticket, at a show & tell or team meeting

[owenatgov]

Update

Alongside desk research to see if there are other solutions we could try, we'll be experiementing with reverting the removal of the details polyfill to see if that version of the details component works.

This isn't a guarantee that we'll merge that reversion as there are other downsides to including the details polyfill.

Something we could also potentially explore is distributing an extension that contails the details polyfill for end users so that they can use them with Dragon without adding weight to govuk-frontend.