The main issue with the Happy Point block is that it lives inside a frame. The frame is accessible, but it's a bit cumbersome because you have to "enter that web area" and "exit" it to continue browsing trough the top frame. I guess there is no way around it so far, unless we can load that content dynamically into the DOM or write our own form and just send the data.
That said, the easily fixable issues are:
The image caption is read but it should have something like "Image of..." or "Image: [the caption here]" (in the frontend)
The titles, fields and button are ok. The part with a checkbox, a legend, and a link to the privacy policy should be enclosed in a div or span with a role=text attribute so it's read as a single text and not separately. However this depends on the iframe URL, and even the default one varies from NRO to NRO so it's probably not possible to fix. 🤔
The main issue with the Happy Point block is that it lives inside a frame. The frame is accessible, but it's a bit cumbersome because you have to "enter that web area" and "exit" it to continue browsing trough the top frame. I guess there is no way around it so far, unless we can load that content dynamically into the DOM or write our own form and just send the data.
That said, the easily fixable issues are:
Potentially affected repositories: planet4-plugin-gutenberg-blocks
Testing
Add a Happypoint block to a page and test it out (with and without an iframe) with a screen reader. You can check out the docs for more details.