hhast

Regarding the feature suggestion — yes, that’s the feature I was thinking of, assuming users have the video and transcript/statement block positioned horizontally. Otherwise, if it’s vertically, then it would just be a matter of displaying/not displaying.

Actually, multiple accessibility blocks seem to work every time except in this specific view. Previews work and refreshing the page/visiting the page (even while signed in to WP) also works. These are the errors I’m receiving:

Uncaught TypeError: Cannot read properties of null (reading 'removeAttribute')
    at t.goTo (view-script.js?ver=23b3733ea130a964357e:1:3594)
    at t.panelLengthCheck (view-script.js?ver=23b3733ea130a964357e:1:2701)
    at new t (view-script.js?ver=23b3733ea130a964357e:1:2067)
    at view-script.js?ver=23b3733ea130a964357e:1:3937
    at NodeList.forEach (<anonymous>)
    at HTMLDocument.<anonymous> (view-script.js?ver=23b3733ea130a964357e:1:3924)

• This reply was modified 7 months ago by hhast. Reason: clarification

Thank you for the response! Both points sound good to me.

Regarding your question, since the screenshots included them (example text: “Visible and PDF transcript”), I would expect them to automatically be created and link to the file uploaded. However, if you note that users can add things like the button block (and other WP blocks) to your documentation, then that is equally sufficient.

A useful feature I could think of is toggling the transcript/accessibility statement block’s view (i.e. the block doesn’t appear until users click on the relevant buttons). We can code this ourselves, but there may be users who don’t know how to do such who may benefit from it.

Also, I have another question – can users only use 1 video accessibility block on a given page? I tried testing with 2, and it seems to break.