Screen Reader inserting Lectora Course Name into various pages and buttons

I was actually able to force new text to be read by JAWS as the CourseName by manually editing the Published index.html file.

By changing the 'frame title' of the 'contentframe' to something like "bla bla bla" it would read by JAWS this way on the load of every page of the course, including every button selection (Submit click would read as "bla bla bla That's incorrect." when revealing the incorrect text block).

But why would it be reading me the Frame Title at every page-load and interaction in the first place?

I'm mystified.

-Darrell

...

frameset id="trivTitleMgrFrameset" rows="0,*" border="0" frameborder="0" framespacing="0" onResize="ReFlow()"

frame title="CourseName" name="titlemgrframe" src="titlemgr.html" resize="no" scrolling='no' marginwidth='0' marginheight='0' /

frame title="bla bla bla" name="contentframe" src="content.html" resize="no" /

noframes

...

Mystify... Mystify Me... INXS but not Accessibility Please!

I need perfection, not twisted selection...

Anyway, I think it reads the frame title when that frame gets focus, so it seems something must be affecting the focus, maybe JAWS. I would be interested to know if it happens with NVDA, I will try that with your example in a moment.

I'll also have QA look at this and see if they have any insight, and if we can reproduce it we will get you a workaround shortly and look into fixing it. We haven't changed anything there in a long time, but it's possible some other change or platform (browser, JAWS, etc) might be affecting it.

More soon.

- Joe

I should add, this is Published with HTML Option to "Include Title Manager Frame" (same as it would Publish Title to SCORM). Therefore, it loads in my Chrome with a local host (http://localhost:3750/PREVIEW/). Selecting an individual html file from within the published folder does not read the Course Name text, but this is not how the course can be viewed, especially when SCORM Published over an LMS.

-Darrell

Hi Darrell @Web-Foley

This has us puzzled as to why it hasn't been an issue before. We did hear the title name read, but only on the load of the page, and then when tabbing to the first button (which doesn't sound right). I do have something for you to try since you are seeing something a little different.

Following your analysis we wrote a script that removes the title from the frame. Can you try it and let us know what result you see?

Add a HTML Extension object at the title level of type Custom DIV and set it to Initially hidden.

Edit the HTML Extension and put in the following:

undefined
triv$(';frame';,myTop[';trivTitleMgrFrameset';]).attr(';title';,';';);
//triv$(';frame';,myTop[';trivTitleMgrFrameset';]).removeAttr(';title';);
undefined

See the attached screenshot.

@Darrell,

When I started using Lectora years ago, I read it somewhere or learned from someone to always un-check "Include Title Manager Frame" for my accessible titles. I also check "Convert page names..." Since I followed this rule, I didn't have any issues with our "rigid" accessible team!

Hope that helps,

Thanks guys!

@wheels - Joe, this is a better fix (the HTML extension) then I was fearing which would have been editing the index.html file manually at each re-publish/edit... and I'm sure our course maintenance team would thank you too.

@tmichael9734 - for us and our required SCORM publish that's a default/set to always have the “Include Title Manager Frame”... It's likely why I never noticed during my builds as I was doing a straight HTML publish. Ugg.

Just and update into my newbie late night research, I was also able to stop the Frame being read on page load using JAWS via the JAWS settings, there are some HTML verbosity levels that allow for deeper customizations, including not reading the Frame on page load. It's a bit tricky when you don't exactly know what the audience has set for their JAWS preferences, and I guess by default they were on. Frames can apparently be quite useful for accessibility when used for things like describing menu.html pages etc., but when used as a container which has the potential to be read by screen readers it may be confusing or irritatingly repetitive. I learned a wee bit more about them last night (https://webaim.org/techniques/frames).

The only lingering question (at this point) is to ensure it does not try and read the Frame name on every button interaction. My last outstanding mystery. I'll keep this thread posted if the fix doesn't rectify that too.

As usual, I appreciate the support! Thanks again.

-Darrell