Forum Replies Created

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #382198 Score: 2
    Profile photo of Ann Sisco
    Ann Sisco
    Member
    beginner
    intermediate
    friend finder
    wise owl
    curious george
    contributor
    profile
    8 pts
    @prg1792

    please, please, please test thoroughly! i have had a v17 license for a year now but have not been able to use it out-of-the-box to deliver accessible courseware due to issues with tab order (for keyboard-only users) and reading order (for screen reader users). i’ve got tickets in, even for v17.1.1, and could add custom code workarounds, but i’m still using v16.2.2 which is a much better tool for creating accessible content. i feel like i wasted a year of maintenance.

    i, too, am a long-time Lectora user so i really hope future versions are worth the investment.

    This post has received 2 votes up.
    #414410 Score: 2
    Profile photo of Ann Sisco
    Ann Sisco
    Member
    beginner
    intermediate
    friend finder
    wise owl
    curious george
    contributor
    profile
    8 pts
    @prg1792

    I tested a version of my courseware, so this is not necessarily an exhaustive list. I have submitted these to the WCAG team, and got an immediate reply that these would be looked at right away.

    Here is what my testing showed…

    Keyboard-only:

    1. The visual indicators for focus are not visible if the object is on top of another object. The box-shadows draw as the bottom-most layer behind everything else. For a workaround, I used the trivantis-focus.css provided with v17 which includes an outline definition that gives a visual indication of focus.
    2. There is no focus indicator visible for transparent buttons which tend to be on top of other objects (same box-shadow issue as above). To fix, I edited the HTML file to set the opacity of the surrounding DIV to be 1 instead of 0.01. That shows the outline defined in the v17 trivantis-focus.css.
    3. Audio DIV container has tabindex=0 instead of -1. For a workaround, I edited mediaelement-and-player.js line 2439.

    Screen Reader:

    1. An HTML extension object (custom DIV) is incorrectly written to the top of the HTML instead of with the page objects where it should be. To fix, I edited the HTML file to move the object.

     

    This post has received 2 votes up.
    #412296 Score: 1
    Profile photo of Ann Sisco
    Ann Sisco
    Member
    beginner
    intermediate
    friend finder
    wise owl
    curious george
    contributor
    profile
    8 pts
    @prg1792

    I am anxious to test v18 for accessibility. I have not used v17 for production at all due to all of its accessibility issues. Fingers crossed that v18 is truly fixed in that regard.

    Storyline and Captivate are still ahead in features, ease of use, etc. As for Lectora as a whole, I do like that it is the only major tool to publish HTML content that uses objects recognized by the DOM. Both Storyline and Captivate publish HTML, but not in such a way that JAWS recognizes the structure. So a definite plus for Lectora. However, the HTML that is published is far from good, even for simple things. Adding a margin to a text object results in an TABLE object wrapping the text with padding on the TD. Unordered sub-bullets are not written as nested lists. So plenty of cleanup that could still be done there.

    But I wonder what is the vision for Lectora? What is the direction of the tool, fixes aside? What’s the next major design move? (I don’t regard Vaast and CenarioVR as improvements to the core tool.)

    This post has received 1 vote up.
    #433886 Score: 1
    Profile photo of Ann Sisco
    Ann Sisco
    Member
    beginner
    intermediate
    friend finder
    wise owl
    curious george
    contributor
    profile
    8 pts
    @prg1792

    Hi, Monica (@mspencer.2813)

    To attach the JS file to your title, perform the following steps:

    1. Select the Insert ribbon.
    2. Way over on the right, select Attachment.
    3. A window will open. Navigate to the folder where you saved your new JavaScript file.
    4. Select the file.
    5. Select Open.

    The JavaScript file is now attached to your title. You can verify this by selecting the Tools ribbon, then Resources. The file should be listed under Attachments/Other.

    When a file is attached to a title, it is copied into the root folder of the published files each time you publish. If it is not attached, it is not copied into this folder, and you will get an error message for any corresponding JavaScript calls.

    Hope this helps.

    This post has received 1 vote up.
    #433890 Score: 1
    Profile photo of Ann Sisco
    Ann Sisco
    Member
    beginner
    intermediate
    friend finder
    wise owl
    curious george
    contributor
    profile
    8 pts
    @prg1792

    @mspencer.2813

    I just published my test title in v18.2.1 using the code I had posted. It is not working with this version. I’ll have to dig a bit to see what changed since I posted my example. Sorry!

    UPDATE: Be sure that any smart quotes are replaced with straight quotes both in the code of your new JavaScript file and in the HTML Extension text. That’s what caused my recent attempt to fail.

    This post has received 1 vote up.
    • This reply was modified 9 months, 1 week ago by Profile photo of Ann Sisco Ann Sisco.
    #434047 Score: 1
    Profile photo of Ann Sisco
    Ann Sisco
    Member
    beginner
    intermediate
    friend finder
    wise owl
    curious george
    contributor
    profile
    8 pts
    @prg1792

    You’re welcome 🙂 Glad that worked for you!

    This post has received 1 vote up.
    #429216 Score: 0
    Profile photo of Ann Sisco
    Ann Sisco
    Member
    beginner
    intermediate
    friend finder
    wise owl
    curious george
    contributor
    profile
    8 pts
    @prg1792

    @rboyd4570-ok, I have been using some jQuery to augment the HTML output by Lectora v18.1.2. I took a look at setting the title attribute for image and button objects based on their alt and aria-label attributes, respectively. This might be a work-around for you until a formal solution is in place.

    1) Open a text editor and copy/paste the following code (comments included to explain what’s going on):

    //–need to do this to avoid conflicts
    $ = triv$.noConflict();
    //–this will fire when the DOM structure loads
    $(“document”).ready(function(){
    //–a slight delay (1.5 sec) is needed here because the content is drawn dynamically
    setTimeout(function() {
    //–for every image, set its title to the value of its alt tag
    $(“img”).attr(“title”, function(){
    return $(this).attr(“alt”);
    });
    //–for every button, set its title to the value of its aria-label
    $(“button”).attr(“title”, function() {
    return $(this).attr(“aria-label”);
    });
    }, 1500);
    });

     

    2) save as a JavaScript file (.js), like my-custom-code.js

    3) attach the JS file to your title so it is included in publishing

    4) create an HTML Extension object at the title-level. Set Type to Bottom of file scripting (so that it comes after the jquery include that Lectora inserts automatically. Set File to None.

    5) Click Edit and add the following line (change to match your filename):
    <script type=”text/javascript” src=”my-custom-code.js”></script>

    6) Save and publish your title.

    Give it a try. (Sorry, the Forum editor has removed the indentations i included to make the code more readable.)

    • This reply was modified 1 year ago by Profile photo of Ann Sisco Ann Sisco.
    • This reply was modified 1 year ago by Profile photo of Ann Sisco Ann Sisco.
Viewing 7 posts - 1 through 7 (of 7 total)

Ann Sisco

Profile picture of Ann Sisco

@prg1792

active 2 months ago