Accessibility Statement

Our commitment to ensuring the IICTP website and digital credential registry are accessible to everyone.

All legal documents

DocumentLEGAL-ACCESSIBILITY

Details

Version: 0.10
Last updated: 16 October 2026
Owner: Accessibility Lead
Sections: 10

IICTPEN

At a glance

The short version.

A plain summary. The full text below is what applies.

WCAG 2.2 AA target

We design and test against the Web Content Accessibility Guidelines 2.2 Level AA standard.

Screen reader and keyboard tested

Key user journeys are navigable using only keyboard and compatible with assistive technology.

Continuous audit

We run automated and manual accessibility audits on all newly released pages and templates.

Feedback welcome

If you encounter an accessibility barrier, email accessibility@iictp.org for assistance.

01Our commitment#

IICTP’s standard is for technical practitioners everywhere, including people who use assistive technology. We want the site and the exam information on it to be usable by as many people as possible, and we treat a barrier as a defect to be fixed, not a favour to be granted.

02Why this is a legal duty#

Accessibility is not only good practice. In many places it is required, and a statement like this one is evidence of what the organisation knew and promised. The laws below are the ones most likely to be relied on. We name them so that the standard we are measured against is clear.

Laws and standards
Source	What it requires or provides
Rights of Persons with Disabilities Act, 2016 (India)	Requires accessibility of information and communication technology, and prohibits discrimination on the ground of disability. Bodies serving the public are expected to meet the Government’s accessibility guidelines (GIGW) and standards
Americans with Disabilities Act (US), Titles II and III	US courts have applied the Act to websites of businesses open to the public. Claims are made on the basis of inaccessible sites
Equality Act 2010 (UK)	Requires reasonable adjustments so that disabled people are not put at a substantial disadvantage in using a service
European Accessibility Act (Directive 2019/882) and EN 301 549	Sets accessibility requirements for certain products and services, with EN 301 549 as the harmonised standard. It points to WCAG 2.1 AA as the web baseline
WCAG 2.2 (W3C, 2023)	The technical test we use. It has testable success criteria at levels A, AA and AAA, grouped as perceivable, operable, understandable and robust
UN Convention on the Rights of Persons with Disabilities, Art. 9	The international principle that access to information and communication technology is a right

03The standard we aim for#

We are working towards conformance with WCAG 2.2 at level AA, which covers perceivable, operable, understandable and robust content.

What conformance would and would not mean

Conformance means that every page in scope passes every level A and AA success criterion, as tested by people and tools, for the combinations of browser and assistive technology we list. Partial conformance means some pages or criteria do not pass, and the failures are listed. We will use the exact term that is true. We will not say “fully accessible”, because no site can honestly claim that for every user.

04What we have designed in#

These are design intentions that we are checking in the audit, not claims of conformance. Each row names the WCAG area it addresses so that it can be tested.

Accessibility features
Area	What we do	WCAG area
Keyboard	Interactive elements are reachable by keyboard and show a visible focus ring	2.1.1 Keyboard; 2.4.7 Focus Visible; 2.4.11 Focus Not Obscured
Structure	Pages use headings and landmarks, and long documents have an “on this page” list	1.3.1 Info and Relationships; 2.4.1 Bypass Blocks; 2.4.6 Headings and Labels
Forms	Fields have labels, including labels that are read by screen readers but not shown	1.3.1; 3.3.2 Labels or Instructions; 4.1.2 Name, Role, Value
Colour and contrast	Text colours are chosen for contrast, with separate light and dark themes	1.4.3 Contrast (Minimum); 1.4.11 Non-text Contrast
Motion	Animations are reduced for people who ask their device to reduce motion	2.3.3 Animation from Interactions; 2.2.2 Pause, Stop, Hide
Text size	Pages are designed to reflow and remain readable when text is enlarged	1.4.4 Resize Text; 1.4.10 Reflow
Images and icons	Decorative graphics are hidden from assistive technology, and meaningful ones have text alternatives	1.1.1 Non-text Content
Print	Each legal document can be printed or saved as PDF from the page	1.4.8 guidance; supports alternative access

05Known limitations#

We will list known issues here once the audit is done, with a note of when each will be fixed. Stating a known failure is better than hiding it: it lets you plan around it and shows we are acting. Areas we are checking first include:

the animated contour and plate graphics on page headers (WCAG 2.2.2, 2.3.3);
the header menus, which open on hover and on click (1.4.13 Content on Hover or Focus, 2.1.1);
data tables, which can be wide on small screens (1.4.10 Reflow);
drag or pointer-only actions, if any are found (2.5.7 Dragging Movements, 2.5.8 Target Size);
PDF or downloadable documents, none of which are published yet.

06If you cannot use something#

If a part of the site is not accessible to you, we will provide the same information or service another way, such as by email, in another format, or with help from a person. Ask at accessibility@iictp.org. You are not required to explain or prove your reason, and you will not be charged.

07Exams and adjustments#

Exams are invigilated. If you need an adjustment, such as extra time, a different format, a screen reader or other assistive technology, ask when you apply. A request for an adjustment is treated as confidential, is used only to arrange the adjustment, and does not count against you. A senior member of staff decides, normally within 48 hours. We ask only for the evidence needed to arrange the adjustment.

08Feedback and contact information#

How

Email accessibility@iictp.org and tell us the page, what you were trying to do, what got in the way, and the browser or assistive technology you use. You do not need to explain your reasons or use technical terms. A report in any form is accepted.

What to expect

We aim to acknowledge you within 48 hours.
We offer another way to get the information or service you need straight away, as set out in Section 6.
We give you a date for a fix where one is needed, and tell you if it slips.
We keep a record of the report and of what we did, so that a pattern can be seen and the outcome shown.

09If you are not satisfied: escalation#

Ask for review. Write to us again and ask for the reply to be reviewed by a senior person who was not involved. We aim to answer in 15 working days.
Go to the regulator or equality body. You may contact the body for your country.
Legal remedy. You may have a right to bring a claim in court or before a tribunal. Nothing in this statement limits that right, and it is not a waiver of any claim.

10Technical details#

Technical specification
Item	Detail
Technologies relied on	HTML, CSS, JavaScript and WAI-ARIA
Conformance target	WCAG 2.2, level AA
Browsers and assistive technology	Current Chrome, Firefox, Safari and Edge. We aim to work with screen readers such as NVDA, VoiceOver and TalkBack
Evaluation method	Manual checks and automated tools against the WCAG success criteria. No independent audit has been done yet
Pages in scope	All public pages
Last reviewed	16 October 2026
Statement prepared	16 October 2026

This statement should be read with the Terms and Conditions, which do not reduce any right in it.

↺Version history

Version history
Version	Date	Change
0.10	16 October 2026	First published.
0.9	16 October 2026	First published.