01CryptoMize Commitment to Digital Accessibility
Accessibility
Statement.
Legal Document · Accessibility Statement
Accessibility Statement
02Our Commitment to Digital Accessibility
Four foundational principles.
03Accessibility Standards and Compliance Framework
Multi-framework compliance across global jurisdictions.
04WCAG 2.1 Level AA — Implementation Status
All four POUR principles addressed.
7.1–7.4Accessibility Features — Organized by WCAG Principle
Every feature documented with its implementation approach.
The Website incorporates accessibility features organized according to the four WCAG principles: perceivable, operable, understandable, and robust.
§7.1
Perceivable Features
§7.1
Perceivable Features
Alternative Text
All meaningful images and non-text content include descriptive alternative text (alt text) that conveys the purpose and content of each element. Decorative images carry null alt attributes so that assistive technologies ignore them entirely. Complex images — including charts, diagrams, and infographics — include extended descriptions either as adjacent text, linked longdesc pages, or structured data alternatives. Alt text is audited during quarterly manual reviews to ensure descriptions remain accurate as content evolves.
Text Alternatives for Complex Content
Data visualizations, charts, graphs, and infographics include text-based alternatives alongside visual representations. These alternatives may take the form of data tables, structured summaries, or narrative descriptions that convey the same information presented visually. Where interactive visualizations are used, keyboard-accessible data table views are provided.
Semantic Structure
Content is structured using proper heading hierarchy (H1 through H4) to enable navigation by screen readers and other assistive technologies. Landmark regions — including header, navigation, main, complementary, and footer — are identified using semantic HTML5 elements supplemented by ARIA landmark roles where necessary. Heading levels follow a logical, non-skipping sequence that reflects content organization.
Color and Contrast
Information conveyed through color is also available through text, patterns, or other visual indicators. The Website remains usable when viewed in monochrome or by users with color vision deficiencies including protanopia, deuteranopia, and tritanopia. Text and interactive elements maintain contrast ratios meeting WCAG 2.1 AA requirements: minimum 4.5:1 for normal text and 3:1 for large text (18pt+ or 14pt+ bold). Non-text interactive components and graphical objects maintain a 3:1 contrast ratio against adjacent colors.
Resizable Text
The Website supports text resizing up to 200% without loss of content, functionality, or readability. Text containers reflow to accommodate enlarged text, and responsive breakpoints adjust layout to prevent horizontal scrolling at up to 400% zoom in a 1280px viewport.
§7.2
Operable Features
§7.2
Operable Features
Full Keyboard Navigation
All functionality of the Website is operable through a keyboard interface alone, without requiring specific timings or coordinated movements. This includes navigation menus, accordions, tab panels, modals, forms, search interfaces, and all interactive components. Keyboard traps are eliminated — focus can move freely into and out of all components. Custom widgets implement keyboard interaction patterns consistent with WAI-ARIA Authoring Practices.
Skip Navigation
A "Skip to Content" link is available as the first focusable element on each page, allowing users who navigate by keyboard or screen reader to bypass repetitive header and navigation content and access the main content directly. The skip link becomes visible on focus to support sighted keyboard users.
Logical Focus Order
Focus order follows a logical sequence that preserves the meaning and operability of content. Tab order follows the visual reading order of the page — top to bottom, left to right. Dynamic content updates manage focus programmatically to ensure users are not disoriented by unexpected focus movement. Modals trap focus within the dialog until dismissed, then return focus to the triggering element.
No Time Limits
The Website does not impose time limits on reading, interaction, or session duration. Users can consume content and complete interactions at their own pace without risk of timed expiration or data loss. Where session management is required for security purposes, users receive advance warning and options to extend the session.
Seizure Prevention & Motion Control
The Website does not contain content that flashes more than three times per second, minimizing the risk of seizure induction for users with photosensitive epilepsy. Any moving, blinking, or scrolling content can be paused, stopped, or hidden by the user. Autoplaying video does not play automatically; user activation is required. Parallax effects and scroll-triggered animations respect the prefers-reduced-motion media query.
§7.3
Understandable Features
§7.3
Understandable Features
Clear Language
Content is written in clear, plain language wherever the subject matter permits. Technical terms, legal terminology, and domain-specific concepts are defined on first use. The primary language of each page is declared in the HTML lang attribute. Where content includes multiple languages, lang attributes identify language shifts. Reading complexity is monitored using readability metrics, and adjustments are made where text exceeds the intended comprehension level.
Consistent Navigation
Navigation patterns are consistent across all pages. Repeated components — including the primary navigation, search interface, and footer — appear in the same relative order each time they are encountered. Navigation items with the same function are labeled consistently throughout the site. This consistency reduces cognitive load and supports users who rely on spatial memory or muscle memory when navigating.
Input Assistance
Forms include clear labels associated programmatically with their corresponding controls. Required fields are indicated both visually (with an asterisk and legend) and programmatically (using the required attribute and aria-required). Error messages are displayed inline near the relevant field, identify the specific error, and provide suggestions for correction when feasible. Successful submissions are confirmed through both visual and programmatic notifications.
Predictable Behavior
Changes of context — including opening new windows, submitting forms, or activating navigational links — occur only through deliberate user action. Automatic context changes do not occur on focus change or input selection. Users are warned in advance when an action will open a new window or launch a download.
§7.4
Robust Features
§7.4
Robust Features
Code Standards and Validation
The Website's HTML, CSS, and JavaScript are developed in accordance with W3C standards. HTML is validated against the W3C Nu HTML Checker to ensure proper element nesting, attribute usage, and structural correctness. CSS follows the W3C CSS Validation Service standards. JavaScript is implemented to ensure progressive enhancement — core content and functionality remain accessible even when scripting is unavailable or fails.
ARIA Implementation
Accessible Rich Internet Applications (ARIA) landmarks, roles, states, and properties are used to enhance semantic structure where native HTML semantics are insufficient. ARIA is applied according to the first rule of ARIA use: native HTML semantics are preferred, and ARIA is used only when native semantics do not provide the required accessibility information. All ARIA attributes are tested for correct implementation, valid values, and proper state management.
Browser and Assistive Technology Compatibility
The Website is tested for compatibility with the browser and assistive technology combinations listed in Section 8. Testing covers functional verification, content access, and interaction patterns. Issues identified during cross-platform testing are logged and prioritized for remediation in the next development cycle.
Parsing and Programmatic Determinism
All content is implemented in a way that user agents, including assistive technologies, can reliably parse and interpret. Elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and IDs are unique within each page. This ensures that programmatic determination of content and functionality is reliable across all supported technologies.
05Supported Assistive Technologies
Verified compatibility across screen readers, browsers, and operating systems.
06Testing Methodology and Evaluation Framework
Four-layer evaluation: automated + manual + user + audit.
10Accessibility Governance and Training
Embedded into organizational processes.
Accessibility at CryptoMize is embedded into organizational processes through structured governance, mandatory training, and procurement standards.
07Known Limitations and Remediation Roadmap
Transparent documentation of gaps and timelines.
Third-party embedded content
Ongoing — provider-dependentMaps, video players, social media widgets may have limited accessibility. Alternative access methods provided where possible.
Legacy documents (PDF, DOCX)
Q4 2026Documents published prior to accessibility initiative may not fully conform. Systematically reviewing and remediating.
Complex data visualizations
Q3 2026Some interactive visualizations may require additional text-based alternatives or keyboard-accessible data table views.
Older browser support
Monitored continuouslyAccessibility features optimized for current browser versions. Users >2 major versions behind may experience reduced accessibility.
Dynamic content announcements
Q3 2026Some dynamically updated content regions may not announce changes optimally in all screen reader combinations.
§11.3 · Accessibility Roadmap
| Initiative | Timeline | Status |
|---|---|---|
| Enhanced keyboard navigation for complex interactive components | Q3 2026 | In development |
| Expanded alternative text coverage for all visual content | Q2 2026 | In progress |
| Screen reader announcement refinement for dynamic content | Q3 2026 | Planned |
| Legacy document remediation (pre-accessibility-initiative content) | Q4 2026 | In review |
| Third-party integrated service accessibility documentation | Q3 2026 | In development |
| User testing program expansion with additional participant cohorts | Q3 2026 | Planned |
08Feedback and Support Channels
Report barriers. We respond within 5 business days.
14Why Accessibility Matters to CryptoMize
Not ancillary to our mission — a direct expression of our principles.
Accessibility is not ancillary to our mission — it is a direct expression of the principles that define CryptoMize as an organization.
16Changes to This Accessibility Statement
Versioned, dated, and available on request.
09Frequently Asked Questions
Accessibility questions answered.
What is WCAG 2.1 Level AA compliance?+
WCAG 2.1 Level AA is an internationally recognized set of accessibility standards published by the World Wide Web Consortium. Level AA compliance requires meeting all success criteria across Levels A and AA (approximately 38 criteria) covering perceivability, operability, understandability, and robustness of digital content.
How do I report an accessibility issue on cryptomize.com?+
Accessibility issues can be reported by emailing accessibility@cryptomize.in, calling +91-9999455667, or writing to our address in New Delhi. Include the page URL, a description of the barrier, your assistive technology configuration, and optional contact information. We acknowledge all reports within five business days.
Does cryptomize.com support screen reader software?+
Yes, the Website is tested and compatible with JAWS, NVDA, VoiceOver (macOS and iOS), TalkBack (Android), and Narrator (Windows). Testing covers navigation, content consumption, form interaction, and dynamic content across supported browser combinations.
Can I navigate cryptomize.com using only a keyboard?+
Yes, all functionality of the Website is operable through a keyboard interface alone. This includes navigation menus, accordions, tab panels, modals, forms, and search interfaces. A "Skip to Content" link is available as the first focusable element on each page.
Does cryptomize.com have any time limits on reading or interaction?+
No. The Website does not impose time limits on reading, interaction, or session duration. Users can consume content and complete interactions at their own pace without risk of timed expiration or data loss.
How often is cryptomize.com tested for accessibility compliance?+
Automated accessibility scans are executed weekly. Manual expert evaluations are conducted quarterly. Independent third-party audits are performed annually. User testing with individuals with disabilities is conducted periodically.
Does cryptomize.com comply with accessibility laws outside the United States?+
Yes. The Website is designed with reference to EN 301 549 (European standard), and our WCAG 2.1 AA baseline provides substantial alignment with accessibility regulations across jurisdictions including AODA (Ontario), JIS X 8341 (Japan), and RPwD 2016 (India).
What assistive technologies are supported on cryptomize.com?+
We support major screen readers (JAWS, NVDA, VoiceOver, TalkBack, Narrator), magnification software (ZoomText), speech recognition (Dragon Professional, Windows Speech Recognition), and alternative input devices across Windows, macOS, iOS, and Android platforms.
§17 · Final Statement — Digital Accessibility Is Not a Destination
It is an ongoing commitment to inclusion, continuous improvement, and operational excellence.
We measure our accessibility program not by the compliance frameworks we cite but by the lived experience of every user who accesses cryptomize.com. If you have suggestions for how we can improve your experience, we want to hear from you.