Accessibility Statement

In short. We are working towards WCAG 2.1 Level AA. We are not fully there yet — the site is partially conformant, and the known gaps are listed below with a remediation plan. If something on this site blocks you, tell us and we will respond within 5 business days and provide the content another way.

1. Our commitment

1.1 Statement of intent

Artham Fintech Consulting Private Limited is committed to making arthamfintech.com usable by as many people as possible, including people who use screen readers, magnification, speech input, keyboard-only navigation or switch devices, and people with cognitive, hearing or motor differences. Accessibility is treated as a requirement of the site, not an optional enhancement.

1.2 Why it matters to us

Our clients include finance and operations teams whose members use assistive technology daily. A site that cannot be read by a screen reader or operated without a mouse excludes people from a commercial relationship, and we regard that as a defect.

1.3 Applicable standards

We take the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, published by the World Wide Web Consortium, as our target standard. We also have regard to the Rights of Persons with Disabilities Act, 2016 and the Guidelines for Indian Government Websites where relevant, to the Standard on Accessibility EN 301 549 for clients in Europe, and to the practice expected under the Americans with Disabilities Act for clients in the United States.

2. Conformance status

2.1 Current status

This website is partially conformant with WCAG 2.1 Level AA. “Partially conformant” means that some parts of the content do not fully conform to the standard. We state this openly rather than claim a level of conformance we have not verified.

2.2 Basis of the assessment

Our assessment is based on self-evaluation, combining automated testing with manual keyboard and screen-reader checks. Testing covered the home page, the service catalogue, an individual service page, cart, checkout, the contact page and a policy page using Chrome with NVDA on Windows, Safari with VoiceOver on macOS and iOS, and Chrome with TalkBack on Android. The date of the most recent assessment is 5 August 2026.

2.3 What has been implemented

• A single H1 per page and a logical heading structure that reflects the reading order.
• Text alternatives for meaningful images, and empty alternative text for decorative ones.
• Keyboard operability for navigation, forms and the store, with a visible focus indicator.
• Semantic HTML for lists, tables and form labels, with table headers associated to cells.
• Text contrast against background reviewed against the 4.5:1 ratio for body text and 3:1 for large text.
• Responsive layout that reflows at 320 CSS pixels width and supports 200 per cent text resize without loss of content.
• Descriptive link text rather than “click here”.
• Page language declared, and form errors described in text rather than by colour alone.

3. Known limitations

We are aware of the following limitations. Each is listed with what we intend to do about it.

Limitation	Effect on users	Planned remediation
Some PDF deliverables and downloadable documents are not tagged for accessibility	Screen reader users may encounter unstructured reading order in downloads	New documents tagged from 5 August 2026; existing documents remediated on request
Third-party embedded components, such as the payment gateway checkout, scheduling widget and any chat tool, are outside our direct control	Focus handling and labelling in embedded frames may not meet Level AA	Raised with providers; alternative completion route offered by email or telephone
Some data tables in reports and comparison sections are complex	Relationships between headers and cells may be harder to follow with a screen reader	Simplification and caption or summary text being added
Older articles published before our accessibility review	Possible missing image alternatives and non-descriptive links	Backfill in progress; priority given to most-read pages
Video or audio material, where published, may lack captions or a transcript	Content inaccessible to deaf and hard-of-hearing users	Captions and transcripts to be provided for all new media from 5 August 2026
Colour contrast on some interface states, such as placeholder text and disabled controls	Reduced legibility for low-vision users	Included in the next design pass

This list is not exhaustive. If you find a barrier that is not listed, please report it under section 6 — reports from users are the most reliable source of issues we have.

4. Remediation plan

4.1 Approach

Accessibility work is prioritised by the severity of the barrier and the importance of the journey affected. Barriers that prevent a task from being completed at all — contacting us, purchasing a service, reading a service description — are treated as the highest priority.

4.2 Ongoing measures

• Accessibility checks are included in the review of new pages and templates before publication.
• Automated testing is run on key templates using axe DevTools, at quarterly.
• Manual keyboard and screen reader testing is carried out on the purchase and contact journeys at annually.
• Content authors follow guidance on headings, link text, image alternatives and plain language.
• Accessibility requirements are raised with third-party providers when tools are selected or renewed.

4.3 Target

Our target for full WCAG 2.1 Level AA conformance across the primary templates is within 12 months of the date of this statement. We will update this statement as items are closed rather than leave it static.

5. Compatibility and technical specification

The site is designed to work with recent versions of Chrome, Edge, Firefox and Safari, on desktop and mobile, in combination with the screen readers commonly used on those platforms, including NVDA, JAWS, VoiceOver and TalkBack. Accessibility relies on HTML, CSS, JavaScript and WAI-ARIA being supported by your browser and assistive technology. Older browsers and unsupported assistive technology combinations may produce a degraded experience. Combinations we have tested are Chrome with NVDA, Safari with VoiceOver, and Chrome with TalkBack.

6. Feedback and how to reach us

6.1 Tell us what did not work

If you encounter a barrier, contact us with the page address, a description of the problem, and the browser, device and assistive technology you were using. That detail helps us reproduce the issue quickly, but do not delay reporting because you lack it.

• Email: info@arthamfintech.com — please put “Accessibility” in the subject line
• Telephone and WhatsApp: +91 7303967800
• Post: 41 & 42, 1st Floor (L-Type), Prem Nagar, Uttam Nagar, Near Metro Station, West Delhi, New Delhi, Delhi – 110059, India
• Accessibility contact: the Grievance Officer, info@arthamfintech.com

6.2 Our response timeline

We acknowledge accessibility feedback within 2 business days and provide a substantive response, including a fix or a planned fix date, within 10 business days. Where a fix will take longer, we will tell you why and give an expected date.

6.3 Alternative access to content

If any part of this site is inaccessible to you, we will supply the same information and complete the same transaction through another channel — by email, by telephone, in an alternative document format, or through a guided call with a member of our team — at no additional cost and without disadvantage to you.

6.4 Escalation

If you are not satisfied with our response, escalate to our Grievance Officer, The Grievance Officer, Artham Fintech Consulting Private Limited — info@arthamfintech.com, under our Grievance Redressal Policy. Grievances are acknowledged within 48 hours and resolved within 15 days.

7. Review of this statement

This statement is reviewed every 12 months, after any significant redesign, and whenever a listed limitation is resolved. It was prepared on 5 August 2026 using the approach described in section 2.2. This statement describes the current state of the website honestly, including where it falls short; it is not a claim of full conformance and is not legal advice.