Displays the current application name, links to the user's profile, My Turas, and other applications.
Examples
The header (global) is a standard component of all Turas page templates. Always include this component on the page unless there is a very strong use case to deviate from the standard templates. Changes to the standard templates must be discussed with the experience team.
Usage
Before signing in the user should see:
the 'Turas' logo followed by 'My Turas'
a link to sign in
If the user is signed into My Turas it includes:
the 'Turas' logo followed by 'My Turas'
the applications dropdown
a user profile dropdown
If the user has signed into an application it includes:
the 'Turas' logo followed by the application name
a link to 'My Turas'
the applications dropdown
a user profile dropdown
This should also include the Skip to main content component which can be accessed by pressing the tab key on your keyboard when loading the page to make the component.
Do:
Use the global header code exactly as supplied.
Avoid:
Adding or removing any elements to the global header.
The header (global), footer and helpdesk are added by installing the NES.Turas.UiComponents nuget package. A README file and assistance to set this up will be supplied at time.
This component is fully compliant with the WCAG 2.2 standard.
Testing
check keyboard navigation to ensure the header does not trap focus and that all interactive elements within the header are accessible with a keyboard , for example any links or buttons
check focus is visible
test header with screen readers to ensure content is announced as expected within the header
Developer considerations
make sure that the header is consistently in the same place on every page
make sure header code is semantically correct by using the HTML <HEADER> tag for the header <NAV> element for the menu
make sure appropriate ARIA is added such as role="navigation" and aria-label="Global menu" this enhances the experience for screen reader users who like to browse by roles and landmarks
if there is a dropdown menu in the navigation make sure that it communicates aria-expanded "false" and "true" states and that it can also be closed /opened with the keyboard