Skip to main content

ServiceNow - "skip to page content" issue with announcements on service portal

appears to be no workaround or fix at present

 

Ref:

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0994809

 

Skip to page content - button is visible on the portal home page when the announcement is dismissed in Rome - Known Error

  • Skip to page content - button is visible on the portal home page when the announcement is dismissed in Rome

KB0994809

Skip to page content - button is visible on the portal home page when the announcement is dismissed in Rome

29 Views Last updated : Mar 16, 2022 Customer Copy Permalink Subscribe

Description

Skip to page content - button is visible on the portal home page when the announcement is dismissed in Rome

Steps to Reproduce

Issue is happening from Rome version.

> Login to Rome version instance  
> Create a announcement on /sp.
> Navigate to portal /sp
> Dismiss the announcement.
> Observe that there is "Skip to page content" button visible.

Is there a way to disable this button.
This button was not visible in Paris, Quebec, Orlando after announcement dismissal.

Expected behavior: "Skip to page content" button not visible.

Actual behavior: "Skip to page content" button visible.
 

Workaround

Please be informed that according to WCAG compliant standards, the "Skip to page content" button should be the first element on the page .

That is why when a portal page is load and on click of 'Tab' from keyboard, we can see "Skip to page content" button.

This button allow differently abled people to change the focus to the index page after the announcements are dismissed on the portal. 

This feature is existing from releases prior to Rome. But in Rome, when dismissed the announcements, this is visible. 

Unfortunately there is no option to disable the same and this is a high level setting needed to qualify for the WCAG compliance. 

For more details on this button compliance: https://www.w3.org/TR/WCAG20-TECHS/G1.html 

 


Related Problem: PRB1519017


 

 

 

 

Comments

Post a Comment

Popular posts from this blog

ServiceNow check for null or nil or empty (or not)

Haven't tested these all recently within global/local scopes, so feel free to have a play! option 1 use an encoded query embedded in the GlideRecord , e.g.  var grProf = new GlideRecord ( 'x_cls_clear_skye_i_profile' ); grProf . addQuery ( 'status=1^ owner=NULL ' ); grProf . query (); even better use the glideRecord  addNotNullQuery or addNullQuery option 2 JSUtil.nil / notNil (this might be the most powerful. See this link ) example: if ( current . operation () == 'insert' && JSUtil . notNil ( current . parent ) && ! current . work_effort . nil ())  option 3 there might be times when you need to get inside the GlideRecord and perform the check there, for example if the code goes down 2 optional routes depending on null / not null can use gs.nil : var grAppr = new GlideRecord ( 'sysapproval_approver' ); var grUser = new GlideRecord ( 'sys_user' ); if ( grUser . get ( 'sys_id' , current . approver )){
Post a Comment
Read more

Get URL Parameter - server side script (portal or classic UI)

Classic UI : var sURL_editparam = gs . action . getGlideURI (). getMap (). get ( ' sysparm_aparameter ' ); if ( sURL_editparam == 'true' ) { gs . addInfoMessage ( 'parameter passed ); } Portal : var sURL_editparam = $sp . getParameter ( " sysparm_aparameter " ); if ( sURL_editparam == 'true' ) { gs . addInfoMessage ( 'parameter passed ); }
20 comments
Read more