va-radio description is not being read by screen reader

[williamphelps13]

Bug Report

• I’ve searched for any related issues and avoided creating a duplicate issue.

What happened

This PR yesNoUI and radioUI to accept description prop #30897 added the ability to have a description in the yesNoUI and radioUI but noted "However this is a half-solution. This won't be read out by screen readers. We need support from DST in order to allow that."

What I expected to happen

Whether it is a yesNoUI or a radioUI a screen reader should read the description:

Here the screen reader should read: "This is a description".

Here the screen reader should read all the text including the list.

Reproducing

• Formation version: ??
• Device: (e.g. iPhone 8, Macbook) Macbook
• Browser: (e.g. Firefox, IE 11) Chrome

Steps to reproduce:

1. Pass a description to a yesNoUI
2. Enable the screenreader

Urgency

How urgent is this request? Please select the appropriate option below and/or provide details

• This bug is blocking work currently in progress
• This bug is affecting work currently in progress but we have a workaround
• This bug is blocking work planned within the next few sprints
• This bug is not blocking any work
• Other

Details

@rhasselle-oddball will provide the technical details of what he meant by the needed support from DST he mentioned in his PR yesNoUI and radioUI to accept description prop #30897: "However this is a half-solution. This won't be read out by screen readers. We need support from DST in order to allow that."

[rhasselle-oddball]

additional info: for va-text-input, we can pass children, and it will get placed in this area and be read out by screen reader. however for va-radio, or va-checkbox-group if we try to do the same thing, it won't get read out by a screen reader. we have form-description, but that is intended for useFormsPattern - which we don't want to use since that is more than just a field, that is also page title. we just want a generic description slot to place JSX or string content that will also be read out by screen reader.

[caw310]

Hey team! Please add your planning poker estimate with Zenhub @Andrew565 @ataker @harshil1793 @it-harrison @jamigibbs @micahchiang @powellkerry @rmessina1010 @rsmithadhoc

[williamphelps13]

Note: the above PR yesNoUI description property is not working #3004 that was merged does not solve this issue. I mentioned this issue in that PR because this issue addresses the problem that was not able to be solved by that PR.

Let me know if there is any further context I can assist with on this, @rsmithadhoc!

[williamphelps13]

Hey @caw310 / @rsmithadhoc! Our PM was asking if there was a timeline estimate on this ticket so just thought I'd post here and check if there was one!

[caw310]

@williamphelps13 this is tentatively scheduled to be worked on in sprint 8 which starts mid August.