Need help removing text above header

[PK6]

Hello All,

I am attempting to adjust my storymap to meet accessibility guidelines. At the very top of every storymap page, there is some text which is automatically applied, and is the same as the title of my storymap. There is a hidden button/ “Skip-to” link associated with this text in the HTML, which might be meant the focus down to the main content (starting at the <h1>). I cannot change the HTML code and cannot figure out how to remove this text bar at the top. The text I am referring to is outlined in red. Any help would be much appreciated!

[OwenGeo]

@PK6 -- Thanks for contacting us about this. The "skip to content" button is a standard part of many web sites and web pages. See this site, for example: WebAIM: Web Accessibility In Mind

Can you share a bit more about why you want to remove or change this button? I'm not sure what you were referring to by the text "outlined in red." Did you perhaps forget to add a screenshot?

[PK6]

Thank you for your reply! My webmaster told me that the button causes the StoryMap (all storymaps do I suppose) to violate a certain criteria of the Level-A and Level-AA WCAG Criteria (more specifically: Understanding Criteria 2.4.1).

Unfortunately the ESRI website tells me I do not have permission to upload images. I am happy to send it over via email, however my agency does not give me access to ESRI support tickets/chat.

Thank you!

PK

[OwenGeo]

@PK6 - Thanks for explaining more about this situation. We are not aware of any violation related to the skip to content button. In fact, it's there to comply with criteria 2.4.1 so readers can skip over the header and jump right to the story content.

Is there any more specific information you can provide about how your webmaster believes that criteria is not being met? I've connected with you on the community so you can direct message me with additional information.

[OliviaWang]

we have the same issues. the link jump to nowhere. the link needs to be fixed because it does not operate correctly meet to the accessibility standards. 

[OwenGeo]

@OliviaWang - The Skip to content button jumps over the header elements and focuses on the cover content. Since there are no interactive elements on the cover, there will be no visible focus ring unless the reader is using a screen reader. However, if a screen reader is active you will see the screen reader focus ring on the cover and hear it announce the cover text. If you continue to press TAB (even without a screen reader active) you will see that keyboard focus ring goes to the first interactive element in the body of the StoryMap.

We believe this is the expected behavior of this type of button -- to skip over text and elements in the header and place focus on the first content of the page, which is the cover. 

Could you please share your expectation of how this button should work differently from what I've described and reference any specific standards that it does not follow so we can understand your perspective?