Backend - Some seemingly normal HTML course content is not readable with TalkBack
Ticket to look at:
With a current Android phone, start TalkBack.
Go to https://courses.edx.org/courses/course-v1:W3Cx+WAI0.1x+3T2019/courseware/85d4f1355dd94682837926790ba9257c/b284a609c9344bb8939f6e701031921e/9?activate_block_id=block-v1%3AW3Cx%2BWAI0.1x%2B3T2019%2Btype%40vertical%2Bblock%40bd6de7c089a744f583506f25d5703a0f
The main issue is that the contents of the Webview (for this and apparently all other “book” icon course units) are not read by TalkBack.
The same content is readable using TalkBack on Chrome on the same Android phone, and with VoiceOver on iPad, and VoiceOver on Mac OS.
You will note that the contents of the page (the webview) is readable for some units (such as 2.3.5) but not for others (such as 2.3.7, 2.3.8)
These parts of the unit content seem to be common either way:
WAI01x courseware edx. Webview
Skip to main content, link.
And then we have the issue: Some of the units read more content after 'Content. Main.' and some don't. So for some units, effectively all of the contents are unreadable. The surrounding navigation controls (outside the webview) are still there though.
I note that for some units there seems to be a Skip to Main Content link, and for some units there is not. I don't know if this is related to the main issue, but it seems interesting because it isn't in the main web view.
I investigated a theory that this might be due to the fact that some units have inline styles in the HTML. Temporarily removing the styles didn't seem to make a difference, but I'm not sure if it was a solid test because I don't know how edX's caching works.
This is a bug report from a low-vision learner who is an educator in Ghana. The course is obviously accessibility-related, so this issue will get the course creators' full attention.
I shared PR with Jeff to keep him in loop with which solution I implemented so he can test it. I’ll share it today after testing.
please make sure you loop in #tnl-squad, I expect someone from that team will want to review the changes. Thanks!
I implemented first approach suggested by you and it worked. I have created a PR and assigned you a reviewer.
Changed the title to indicate that its a backend ticket now.
yes we can pick this.