Skip Nav Help

smcculley1282
smcculley1282 Community Member Posts: 14 ☆ Roadie ☆
 

Hello.

Attached I have a file with a Skip Navigation setup that worked great in Lectora 16. In Lectora 18, it doesn’t work though. The skip nav button (you have tab to it to make it appear) shows up fine, but when I select the enter button and hit the tab button again, instead of the focus going to the page content, the focus goes to the navigation buttons instead.

Has anybody had success with a skip nav in Lectora 18, and if so, can you look at my code and see what I might be doing wrong?

Thanks.

 

-Shawn

Comments

  • tea
    tea Community Member Posts: 128
    @smcculley1282  thanks for including the title, I was able to see it work in v16 and not work in v18.  We'll take a look at this today
  • smcculley1282
    smcculley1282 Community Member Posts: 14 ☆ Roadie ☆
    Hi Tea. I was wondering if you had had a chance to look into my Skip Nav issue some more. Does this seem like an issue I should kick up to Trivantis' support team?

    Thanks.

    -Shawn
  • tea
    tea Community Member Posts: 128
    I'm looking at it now, but not familiar with a lot of the custom css you have. You can contact support and they'll open a ticket - probably best way to track it. I'll keep looking at in the mean time.
  • drheckert
    drheckert Community Member Posts: 5
    Has there been any resolution to this? We are having the same issue.

     
  • prg1792
    prg1792 Community Member Posts: 43 ♪ Opening Act ♪
    Hi, Shawn--

    If you examine the HTML in Developer mode, you'll see that the publishing order of the "MainContent" HTML Extension objects is incorrect. It appears before the navigation buttons, even though the buttons are between the SkipTheMainContent HTML object and the MainContent HTML object in your title. The only two objects between look like the groups you have for Resources and Glossary, which are both set to "Always on Top", which explains why.

    I believe this is a bug in v18 with how the HTML Extension object (when used as a Custom Div) is written out. It does not adhere to the order in the Title Manager, but instead is written first, as if it is set to "Always on Top". If you put an HTML Ext Custom Div at the page-level, it will be written with title-level objects.

    As a work-around, you could switch MainContent to a text object, and then change your SkipTheMainContent href to point to that object by name (e.g. text612925anc).

    So instead of: a class="ms-skip" href="#mainContent" SKIP TO MAIN CONTENT /a

    Use: a class="ms-skip" href="#text612925anc"  SKIP TO MAIN CONTENT /a

    (sorry, had to remove HTML tags so that the hyperlink can be viewed)