Browser document titles

[SOjaHPE]

There is hole in our guidance, there is a need to generate useful Browser Tab Titles for Browser window title text string. It should be meaningful, follow a well structured syntax formate that is smart / contextual to indicate to the user where they are located at any given time.

Why should we do this?

The browser window title text is the first thing read by a screen reader when a user navigates to a new page. See W3C Web Accessibility Guidelines

Reference Links

https://www.w3.org/WAI/test-evaluate/preliminary/#title

https://accessibility.iu.edu/creating-content/web-content/titles.html

A terse description of the content or function of a page allows the user to differentiate it from other pages in the HPE GLCP aaS offering or across HPE .com pages. OTHER PAGE TYPES: Syntax related to Wizard flows; master detail layouts will need to be covered.. didn't have the time to do an exhaustive analysis of all the required browser tab variations.

In many ways, a product's page header 'page title' and the Browser Tab Title strings are related.

Page Titles and Browser tab titles should -

• Short yet descriptive • Describes the current context • Distinguishes one page from another • Put key words up front • Avoid unneeded words

Browser Tab Title

Overview

This topic covers the requirement for the HPE GLCP aaS functional areas to auto-generate the appropriate Browser Window/Tab Title for all product screens. Since the platform global header shell doesn't know the contents of a page, in some use cases the underlying BU application page will need to pass contextual information to the platform shell. The shell will then concatenate/append the appropriate browser window title to provide necessary context for the user.

We will need to have a common platform widget? Or Central (HFS) layer to pass the window title, based on the current location of the user interface, e.g. nested tabs. Updated strings are pushed for display as the user navigators around Storage Central, task flows.

Additional Examples will be added