Related Github Documents
Document Properties
Last Modified
Added to KB
Public Access
Doc Type
Guidelines, Concepts & Cookbooks
Intershop Progressive Web App
Guide - Intershop Progressive Web App - Accessibility

The goal of accessibility is to unlock the full potential of the Web and enable people with disabilities to participate equally.
The @angular-eslint repo contains a number of linting rules that can help enforce accessibility best practices in Angular component templates.

The accessibility rules that are enabled in the Intershop PWA are listed/described in this document and configured in the .eslintrc.json file of the project.
To check whether the rules are followed in your custom code or not, run npm run lint.

General Rules


This rule makes sure that all aria-* attributes used are valid.
The rule will fail if a non-existent aria-* attribute is used, or a valid aria-* attribute is given an unexpected value.

Content Rules


Interactivity Rules

The navigation is the most important way to find and access the different contents of the website.
For this reason, it is essential that the navigation is accessible.


This rule ensures that tabindex is set to 0 (element is tab focusable) or -1 (element is not tab focusable), and not a positive value that interferes with the automatic tab order of elements.

How to fix problems with unreachable elements

To make HTML elements tab-focusable that are not reachable by default (like <a> tags, <button>, etc.), tabindex="0" can be added to most HTML tags like <div> or <span>.


This rule ensures, that elements with click event handlers also handle at least one key event (keyup, keydown or keypress).

How to fix click-events-have-key-events problems

To fix this, all of the <a> tags in the HTML files should have a routerLink attribute.
If adding a meaningful routerLink is not possible, [routerLink]="[]" should be added to fix the error.

Other HTML elements (<div>, <span>, etc.) with a click() event that report this ESLint error can be fixed by adding a (keydown.enter) event that should be assigned with the click() event's method.
In addition a tabindex="0" needs to be added to such elements to make them tab focusable.

The outcome is testable when navigating the page in the browser with the tabulator key.
The clickable areas will be focused and a click event is triggered by pressing the Enter key.


Requires any element with a mouseout event handler to also handle blur events, and any element with a mouseover event handler to also handle focus events.

Form Submission using the key "Enter"

Implicit form submission using the "Enter" key is vital to assistive technologies, see also HTML5 specification.
Therefore, the form tag has to include an input of type="submit", for example

  <label for="foo">Name:</label>
  <input type="text" name="foo" id="foo" />
  <input type="submit" value="Submit" />

or a button of type "submit"

  <label for="foo">Name:</label>
  <input type="text" name="foo" id="foo" />
  <button type="submit">Submit</button>

Form submission in dialogs

Dialogs (or modals) are separated into three sections:

  • modal header
  • modal body
  • modal footer

where the form is positioned inside the model body and the buttons are positioned inside the modal footer.
The following simplified example shows the wrong HTML structure:

⚠️ Wrong HTML structure

<div class="modal-body">
  <form (ngSubmit)="submit()">
<div class="modal-footer">
  <button type="button" (click)="submit()">Submit</button>
  <button type="button" (click)="cancel()">Cancel</button>

The button with the text "Submit" calls the same function foo() as the form (ngSubmit) but the form would not be submitted using the "Enter" key because the submit button is positioned outside the form tag.
The following example shows the correct HTML structure:

✔️ Correct HTML structure

<form (ngSubmit)="submit()">
  <div class="modal-body">
  <div class="modal-footer">
    <button type="submit">Submit</button>
    <button type="button" (click)="cancel()">Cancel</button>


  • the form tag surrounds both the formly form (including the form elements) and the submit button
  • the function submit() is only called at the form tag
  • the "Submit" button is correctly defined using type="submit" and does not call submit() using (click)=""
  • the "Cancel" button is only defined as type="button" to prevent any default behavior

Further References


The information provided in the Knowledge Base may not be applicable to all systems and situations. Intershop Communications will not be liable to any party for any direct or indirect damages resulting from the use of the Customer Support section of the Intershop Corporate Web site, including, without limitation, any lost profits, business interruption, loss of programs or other data on your information handling system.

The Intershop Customer Support website uses only technically necessary cookies. We do not track visitors or have visitors tracked by 3rd parties.

Further information on privacy can be found in the Intershop Privacy Policy and Legal Notice.
Customer Support
Knowledge Base
Product Resources