Draft — subject to legal review
This text is a working draft and may change before final publication. If anything is unclear, please contact us.
What standard do we aim to meet?
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, published by the World Wide Web Consortium (W3C), across the website and the customer portal.
WCAG 2.2 level AA describes how content should be perceivable, operable and understandable for people who use screen readers, keyboards, magnification, voice control or other assistive technology.
What have we done to make the site accessible?
Accessibility is part of how we build every page, not an add-on.
- every function works with a keyboard, with a clearly visible focus indicator that sticky headers do not hide;
- every form field has a visible label; errors are explained in text, linked to the field and summarised when you submit;
- normal text meets a contrast ratio of at least 4.5:1;
- buttons and links have a target size of at least 24 by 24 pixels;
- Arabic and Persian pages use a right-to-left layout and the correct language tags, so screen readers use the right voice;
- animations respect your device’s reduced-motion setting;
- sign-in lets you paste passwords and use a password manager, with no puzzle CAPTCHAs;
- results that load in the background, such as tracking searches, are announced to screen readers;
- frequently asked questions use standard expandable elements, and maps load only when you ask, with the address also given as text.
What are the known limitations?
Some parts are not yet fully accessible, and we are working on them.
| Area | Limitation | What you can do meanwhile |
|---|---|---|
| Documents from third parties | bills of lading, invoices, certificates and other PDFs issued by carriers, suppliers or authorities are often scanned images without a text layer | ask your coordinator to read out or summarise the content |
| Codes and references | screen readers may read container numbers, HS codes and references (kept in Latin characters) letter by letter or unevenly on Arabic and Persian pages | your coordinator can give the same information by phone, WhatsApp or email |
| Wide tables | on small screens, cost sheets and document lists may need scrolling inside the table | ask your coordinator for the details in a simpler format |
| Third-party services | WhatsApp, embedded maps and carrier websites are outside our control | the same information is given as text on our pages |
| Independent audit | no independent accessibility audit has been completed yet | we test ourselves and fix issues as we find them |
How do we test?
Every new page must pass our accessibility checklist, based on WCAG 2.2 AA, before release.
- automated accessibility checks during development;
- keyboard-only checks of the main journeys: quote request, tracking, sign-in, the portal case file, document upload and support tickets;
- checks in all three languages, in left-to-right and right-to-left layouts, at mobile and desktop widths.
We intend to commission an independent audit and will update this statement with its results.
How can I report a problem or ask for another format?
Tell us what you were trying to do and where it went wrong, and we will help.
- email info@niloceanshipping.com with the subject “Accessibility”;
- or message your coordinator on WhatsApp, or open a support ticket in the portal.
If you can, include the page address and the device and assistive technology you use. We will reply as soon as we can and, in the meantime, help you complete your task by phone, WhatsApp or email.
When was this statement prepared?
This statement was prepared on 1 November 2026. We will review it at least once a year and after any major change to the website or the portal.
Questions about this page?
Contact us and we’ll answer in English, Arabic or Persian.