Accessibility Statement
Nexaliq Identity is committed to providing a website experience that is usable by as many people as reasonably possible, including people who use assistive technologies. Accessibility is treated as an ongoing practice involving design, content, code, testing, and response to feedback.
1. Accessibility goal
Nexaliq Identity uses the Web Content Accessibility Guidelines, currently WCAG 2.2 Level AA, as an ongoing reference for the public website where reasonably applicable. Referencing that standard is a goal and working method, not a claim that every page, third-party component, device combination, or future update is perfectly conformant at all times.
The website will be reviewed as content and functions evolve. Priority is given to barriers that prevent a person from obtaining essential service information, reviewing prices, navigating sections, reading legal terms, or submitting an inquiry.
2. Design and interaction features
The supplied website design includes semantic headings and landmarks, visible labels, keyboard-operable buttons, focus indicators, high-contrast core text, plain-language navigation labels, descriptive control names, responsive layouts, and modal dialogs designed to return focus when closed.
Motion is used to express the visual identity, but a reduced-motion media query stops or simplifies non-essential animation for visitors whose systems request reduced motion. Moving decorative text does not carry information that is unavailable elsewhere in static text.
3. Keyboard navigation
Visitors should be able to move through links, buttons, form fields, accordions, menu controls, and modal dialogs using a keyboard. Focus should remain visible and follow a logical order. Modals should be closable using the displayed close control or Escape key, and focus should return to the control that opened the modal.
If a keyboard trap, missing focus state, unreachable control, or unexpected order is encountered, please report the page, control, browser, and steps needed to reproduce the problem.
4. Text, color, and zoom
Body text and important interface labels are designed for readable contrast against their backgrounds. Color is not intended to be the sole method of communicating required fields, selected states, errors, or completion. Layouts use responsive sizing so text can enlarge and content can reflow on narrower screens.
Brand colors may be used in decorative surfaces, while critical reading areas preserve stronger contrast. Device settings, browser zoom, high-contrast modes, custom styles, and font rendering can affect appearance; the site should remain understandable when those settings are used.
5. Forms and status messages
Forms include visible field labels and required-field indicators. Submission controls remain unavailable until required fields are valid, reducing preventable incomplete submissions. After a valid demonstration submission, a text confirmation appears in the current interface.
The supplied forms do not transmit information. If a processing service is connected during Shopify implementation, validation errors, processing status, privacy disclosure, success messages, and failure recovery should be tested with keyboard and screen-reader workflows.
6. Images, logos, and decorative content
Informative images should have concise alternative text that describes their purpose. Decorative visuals should be hidden from assistive technologies when they add no content. The uploaded brand logo should have alternative text identifying Nexaliq Identity without repeating adjacent text unnecessarily.
Complex identity examples, diagrams, or documents added later should include an equivalent text explanation or an accessible alternative where needed.
7. Motion and sensory effects
The website uses kinetic typography inspired by the work itself. Essential instructions do not depend on recognizing motion, direction, shape, sound, or color. Visitors can request reduced motion through their operating system or browser, and the design includes styles intended to respect that preference.
Future video or audio content should include captions, transcripts, audio description, or another suitable alternative according to the content and applicable requirements.
8. Plain language and structure
Service descriptions, pricing, process steps, deliverable details, and legal pages are organized with headings and grouped content. Technical design terms are explained where practical. The same home-page links are used in the header and footer so visitors can find major sections consistently.
9. Third-party content and limitations
Some functions may be provided by Shopify, a browser, a payment provider, a consent tool, a file-delivery service, or another third party. Nexaliq Identity may not control the complete code, update schedule, or accessibility behavior of those services. Reasonable efforts will be made to select appropriate tools, configure them accessibly, and provide an alternative path when a material barrier is identified.
PDFs, client-supplied assets, old file formats, or embedded vendor interfaces may have limitations that require remediation or an alternate format. The absence of a known issue does not mean no issue exists.
10. Compatibility
The site is intended to work with current versions of widely used browsers and assistive technologies. Very old browsers, unsupported operating systems, custom extensions, or unusual combinations may behave differently. Keeping browsers and assistive software updated can improve interoperability but is not a condition for reporting a barrier.
11. Requesting assistance or an alternative
If website content or a function is difficult to access, you may request assistance or information in another reasonably available format. Describe the page or content, the barrier encountered, the format or accommodation that would help, and a way to respond. Do not include sensitive information that is not needed to address the request.
Examples include asking for service information in plain text, requesting clarification of a visual chart, reporting a keyboard issue, or requesting help with a website form. The same service prices and project consideration apply regardless of a person’s use of an accessibility accommodation.
12. Review and response process
Accessibility feedback will be acknowledged and reviewed in good faith. The review may include reproducing the issue, checking the source content or third-party component, assessing available alternatives, prioritizing the impact, and communicating a reasonable resolution or status.
Some corrections can be made quickly; others may require platform support, vendor action, content reconstruction, or additional testing. When an immediate permanent correction is not feasible, an interim method of accessing the information will be considered.
13. Ongoing improvement
Accessibility considerations are included when new pages, forms, images, motion, documents, or integrations are added. Periodic review may include keyboard checks, zoom and reflow checks, automated testing, contrast review, semantic inspection, and feedback from people using assistive technology.
This Statement may be revised to reflect material design changes, testing results, resolved issues, new third-party functions, or evolving standards. The date at the top identifies the current version.
Accessibility feedback is welcome
When reporting a barrier, include the page title, a short description of what happened, the device or browser if known, and the outcome you were trying to reach. That information helps identify and prioritize a practical response.