We do not build software. We build the conditions under which intelligence can be trusted. Trust begins with access.
Section 01
Our commitment.
MATRIX is committed to ensuring that this website and the studio's published materials are accessible to the widest possible audience — regardless of ability, technology, or circumstance.
We hold that accessibility is not a compliance exercise. It is part of what it means to design trustworthy intelligence systems. An interface that excludes some of its users is an interface that has not finished its work.
In plain language
We design this site so that anyone — using a screen reader, keyboard-only navigation, high-contrast mode, larger text, or assistive technology of any kind — can read, navigate, and understand everything we publish.
◆
Section 02
Standards we follow.
We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA — the internationally recognised standard published by the World Wide Web Consortium (W3C).
Where a content type or interaction is not fully covered by WCAG 2.2 AA, we look to EN 301 549 (the European accessibility standard for ICT) and the UN Convention on the Rights of Persons with Disabilities for additional guidance.
Where local regulation applies — including the Rights of Persons with Disabilities Act, 2016 (India) and the Guidelines for Indian Government Websites (GIGW) — we take account of those obligations in the design of our public materials.
◆
Section 03
Accessibility principles.
The following design principles are held across the studio's public materials. They apply to this website, the manifesto, research publications, and portfolio documents.
01 · Perceivable
Content is available to the senses.
Text is legible, contrast is sufficient, and information is never conveyed by colour alone. Images and decorative elements have appropriate alternative text or are marked as decorative. Video and audio content carries captions or transcripts.
02 · Operable
The interface works for every input.
Every interactive element is reachable and usable via keyboard alone. Focus is always visible. No content flashes more than three times per second. Navigation is consistent and predictable. Sufficient time is provided for any timed interaction.
03 · Understandable
Language and behaviour are clear.
Content uses plain language where possible, and technical language deliberately. Headings and landmark regions are properly structured. Error messages explain what happened and what to do. Interaction patterns are conventional and predictable.
04 · Robust
Works across assistive technology.
Semantic HTML is used wherever possible. ARIA roles and properties are applied only where necessary and always correctly. Content is tested with current screen readers, browser zoom, and text-resize tools. The site does not break when users adjust their environment.
◆
Section 04
Current status.
An honest record. Where a feature is fully supported, it is marked pass. Where support is partial, it is marked partial. Where work is ongoing, it is marked in progress.
Text contrast
Body and headline text meets WCAG 2.2 AA contrast ratios (4.5:1 minimum for body text, 3:1 for large text).
Verified against the studio's ink and gold palette.
Pass
Keyboard navigation
All interactive elements are reachable and operable by keyboard. Focus indicators are visible and meet contrast requirements.
Skip-link provided at the top of every page.
Pass
Semantic HTML & landmarks
Pages use proper heading hierarchy, landmark regions (header, nav, main, footer), and semantic elements throughout.
Pass
Screen-reader compatibility
Tested with VoiceOver (macOS/iOS), NVDA (Windows), and TalkBack (Android). ARIA used sparingly and correctly.
Pass
Responsive & text resize
Content remains legible and functional at up to 200% zoom, at all viewport widths from 320px upward.
Pass
Reduced motion
Respects the user's prefers-reduced-motion setting. Animations and transitions are disabled or minimised when requested.
Pass
High contrast mode
Responds to the prefers-contrast setting with an adjusted palette.
Pass
Forms & labels
All form inputs have associated labels. Error messages are programmatically associated and describe what to correct.
Where a form appears on a MATRIX platform, accessibility is addressed in the platform's own statement.
Pass
Language declaration
Page language is declared. Where a passage is in a language other than the primary language, it is marked appropriately.
Pass
PDF publications
Research whitepapers and portfolio PDFs are being progressively remediated for accessibility.
Not all historical PDFs are yet fully tagged. Where an accessible version is needed urgently, please contact us.
In Progress
Interactive data visualisations
Data tables in research publications are accessible. Interactive chart components are being upgraded with text alternatives.
Available as an option on request while upgrades complete.
Partial
Third-party embedded content
Embedded media and third-party components are tested for accessibility where possible.
We do not control the accessibility of third-party platforms linked from our site.
Partial
This statement reflects the status of the studio's public website as of the effective date. The status is reviewed annually and updated when material changes occur.
◆
Section 05
How we test.
Accessibility is not self-declared. It is verified. Our testing combines automated tooling, manual review, and — where possible — engagement with users of assistive technology.
Automated testing
Pages are scanned with current automated accessibility tools to catch structural issues — missing labels, colour contrast failures, incorrect ARIA usage, and landmark errors.
Manual testing
Every page is reviewed by hand: keyboard navigation, screen reader walkthroughs, focus order, zoom behaviour, and reduced-motion behaviour.
Assistive technology
Testing is performed with current versions of VoiceOver, NVDA, TalkBack, and major browser accessibility features.
User feedback
Feedback from users of assistive technology is treated as primary evidence — not a secondary signal.
◆
Section 06
Known limitations.
We publish our limitations plainly. Where we know a barrier exists, we say so — and we say what we are doing about it.
Historical PDF publications
Some earlier whitepapers and portfolio documents were not originally produced as tagged, accessible PDFs. We are remediating them progressively. If you need an accessible version of any specific publication, write to us — we will provide one promptly.
Interactive visual components
A small number of data-visualisation and interactive-graphic components on the site do not yet have full screen-reader equivalents. Text alternatives are being added. In the interim, the underlying data is available in tabular form on request.
Third-party content
Content hosted on third-party platforms (linked tools, embedded media, external registries) is outside our direct control. Where we recommend a third-party resource, we aim to note accessibility-relevant information where known.
◆
Section 07
Feedback & contact.
If you encounter an accessibility barrier on this website, in a publication, or in any MATRIX material — we want to hear from you. Feedback from users is treated as primary evidence, and we will respond plainly.
Report an Accessibility Issue
Tell us what didn't work.
Please include the page or document, what you were trying to do, and the assistive technology or browser you were using. We aim to acknowledge every report within five working days, and to indicate a remedy or a timeline within thirty days.
Where you are not satisfied with our response, you may escalate the matter to the Founder directly via [email protected]. We treat accessibility complaints with the same seriousness as any other formal concern.
◆
Section 08
Enforcement & remedies.
Where we fail to meet the standards set out in this statement, we will:
-
◆
Acknowledge the failure plainly, and not dismiss it as an edge case.
-
◆
Provide a reasonable interim alternative — an accessible version of the content, or a direct human channel.
-
◆
Correct the underlying issue in the next review cycle, or sooner where the impact is material.
-
◆
Record the issue and the remedy in our internal accessibility register.
Where a specific legal obligation applies to your jurisdiction — including the Indian Rights of Persons with Disabilities Act, 2016, the European Accessibility Act, or the US ADA — we take those obligations seriously and address them within the timeline required.
◆
Section 09
A final word.
The real revolution is the evolution of consciousness. Access is a form of consciousness in practice.
An intelligence architecture firm cannot claim to design for civilisation and then exclude part of it. This statement is a commitment — not a claim of perfection. Where we have not yet reached the standard we set ourselves, we have said so. Where we fall short in future, we will say so again.
If you have read this far and something still doesn't work, write to us. That is the whole point.