How to Report an Accessibility Issue

Modified on Mon, 17 Aug at 9:02 AM

Netop Knowledge Base

Submitting a support ticket for accessibility barriers – WCAG 2.2 Level AA

Overview

Netop is committed to making its websites and products accessible to everyone, in line with the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. If you encounter a barrier – for example, content that does not work with your screen reader, elements you cannot reach by keyboard, or text with insufficient contrast – please tell us. This article explains how to submit an accessibility ticket on the Netop Support site.

Before you start

Reports are easier to act on when they include a few details. Where possible, note the following before submitting:

The exact page URL or product screen where the issue occurs.
Your browser and operating system (e.g. Chrome on Windows 11).
Any assistive technology you were using (e.g. NVDA, JAWS, VoiceOver, screen magnifier, keyboard-only navigation).
The steps you took before the problem appeared, and what you expected to happen instead.
A screenshot or recording, if you can capture one.

Submitting the ticket

Go to support.netop.com in your browser.
Select Submit a ticket in the navigation bar at the top of the page. You do not need an account, but logging in lets you track your ticket later.
In the Requester field, enter your email address.
In the Subject field, enter a short summary of the problem.
In the Type drop-down, select Accessibility issue. This step is important – it sends your report directly to the accessibility team.
In the Description field, describe the issue using the details you gathered above. Attach screenshots or recordings if you have them.
Select Submit at the bottom of the form. You will receive a confirmation email with your ticket number.

Form fields at a glance

Fields marked "Yes" are mandatory on the form.

Field	Required	What to enter
Requester	Yes	Your email address, so our team can follow up with you.
Subject	Yes	A short summary, e.g. "Screen reader cannot read the login form labels".
Type	Yes	Select "Accessibility issue" from the drop-down. This routes your ticket to the team responsible for accessibility.
Affected Part	–	The area of the product or website where you found the issue, if listed.
Impact	Yes	How severely the issue affects your ability to use the product or site.
Description	Yes	Full details of the issue – see the checklist in "Before you start".

Writing a useful description

A good accessibility report answers three questions: where the issue is, what happens, and how it affects you. For example:

“On the pricing page (netop.com/pricing), the ‘Compare plans’ table is announced by NVDA as a single block of text with no row or column headers. I cannot tell which price belongs to which plan. Chrome 126 on Windows 11, NVDA 2025.1.”

If you know which WCAG 2.2 success criterion is affected (for example, 1.4.3 Contrast or 2.1.1 Keyboard), feel free to mention it – but this is not required. A plain description of what went wrong is all we need.

What happens next

Accessibility tickets are reviewed by the team responsible for WCAG 2.2 AA compliance. You will receive a confirmation email when the ticket is created, and a team member will follow up at the email address you provided if more information is needed. You can also check your ticket status any time by logging in at support.netop.com.

Netop Accessibility Statement
Web Content Accessibility Guidelines (WCAG) 2.2 – w3.org/TR/WCAG22