Jivaro Trust Center
Accessibility Statement
Jivaro aims to make its website, content, apps, tools, store, research pages, digital resources, and user-facing features usable by as many people as practical.
Jivaro uses WCAG 2.2 as a reference point for accessibility improvements, but does not claim full WCAG conformance across every page, app, tool, game, download, store feature, third-party service, or interactive experience unless a specific feature says otherwise.
Jivaro uses WCAG 2.2 as a practical reference for accessibility improvements.
Jivaro does not claim full conformance without a specific review or audit.
Users can report accessibility barriers through the Contact page or Discord ticket system.
Accessibility improvements may be made during redesigns, content updates, and app updates.
Scope of this statement
This Accessibility Statement applies to Jivaro-controlled pages and features, including main website pages, blog articles, news articles, research pages, Jivaro Journal pages, apps, tools, games, store pages, checkout-related experiences, downloadable files, digital products, and interactive features.
Some parts of the user experience may involve third-party services, embeds, payment providers, newsletter tools, advertising systems, affiliate links, videos, forms, analytics tools, or store features. Jivaro does not fully control every third-party component, but aims to choose, configure, or improve third-party experiences with accessibility in mind where practical.
Core accessibility goal
Jivaro’s goal is to reduce unnecessary barriers and make content, tools, and digital resources easier to access, understand, navigate, and use.
Accessibility reference point
WCAG 2.2 as a guide
Jivaro uses the Web Content Accessibility Guidelines 2.2 as a reference point when improving pages, layouts, tools, forms, and interactive experiences.
No blanket conformance claim
Jivaro does not claim that every part of the website, every app, every game, every download, or every third-party component fully conforms to WCAG 2.2.
Practical improvement
Jivaro prioritizes practical improvements that make the site more usable for real visitors, including people using assistive technologies, mobile devices, keyboard navigation, zoom, high-contrast settings, or alternative input methods.
Known variation
Accessibility may vary across static content, custom code blocks, apps, tools, games, store features, downloadable resources, older pages, and third-party services.
Accessibility practices Jivaro aims to support
Jivaro aims to improve accessibility through content, design, layout, code, and review practices that make pages easier to use and understand.
Clear headings and structure
Pages should use meaningful headings, logical section order, and structure that helps users understand the page and navigate it more easily.
Readable text and spacing
Jivaro aims to use readable content, practical spacing, responsive layouts, and theme-based typography that adapts across devices.
Keyboard navigation
Where practical, pages, links, forms, apps, tools, and interactive elements should be usable with a keyboard or alternative input method.
Meaningful links
Links should generally describe where they go or what they do, instead of relying only on vague language that is hard to understand out of context.
Image descriptions
Meaningful images should include appropriate alternative text where practical. Decorative images may be treated differently when they do not add useful information.
Reduced unnecessary motion
Jivaro aims to avoid unnecessary flashing, distracting motion, or effects that create avoidable accessibility barriers.
Color and contrast
Jivaro aims to maintain sufficient color contrast where practical and avoid relying only on color to communicate important information.
Responsive layouts
Pages should adapt across desktop, tablet, and mobile screens without requiring unnecessary horizontal scrolling or fixed-width layouts.
Forms and instructions
Forms should use clear labels, useful instructions, understandable error messages, and reasonable input behavior where practical.
Custom code blocks
Jivaro aims to avoid creating unnecessary accessibility barriers in custom-coded sections, tools, and interactive layouts.
Plain language
Where appropriate, Jivaro aims to explain complex topics in direct language that helps readers understand what matters and what actions they may need to take.
Apps, tools, calculators, and interactive features
Interactive tools may vary
Jivaro apps, tools, calculators, generators, file utilities, browser utilities, and games may be less accessible than static pages because they often rely on custom interfaces or interactive behavior.
Keyboard access
Jivaro aims to make apps and tools keyboard-accessible where practical, especially for core controls, forms, buttons, links, and navigation elements.
Labels and instructions
Jivaro aims to provide readable labels, instructions, status messages, and error messages so users can better understand how a tool works.
Experimental features
Jivaro does not guarantee that every experimental tool, early app, prototype, game, or visual utility is fully accessible.
Visual and game limitations
Some visual tools, media tools, games, animations, graphics utilities, or highly interactive features may not be usable by all users.
Issue reporting
Users can report app or tool accessibility issues through the Contact page or by opening a ticket in the Jivaro Discord support system.
Third-party content and services
Third-party components
Jivaro may use third-party embeds, payment providers, newsletter tools, analytics providers, ad systems, affiliate links, videos, forms, store features, social media links, or other services.
Limited control
Jivaro does not fully control the accessibility of third-party services, external websites, embedded content, payment flows, advertising systems, or linked platforms.
Practical selection and configuration
Where practical, Jivaro aims to choose or configure third-party services with accessibility, usability, and reader experience in mind.
Report barriers
Users are encouraged to report accessibility barriers even when an issue appears to involve a third-party component, so Jivaro can review possible workarounds or alternatives.
Downloadable files and digital products
Accessibility may vary
Digital products, PDFs, templates, spreadsheets, prompt packs, downloads, files, and other resources may vary in accessibility depending on the format, age, platform, and design.
New resources
Jivaro aims to improve the accessibility of new digital products and downloadable resources where practical.
Older resources
Older downloads, older templates, archived resources, or legacy files may not meet the same accessibility expectations as newly updated materials.
Help and issue reports
Users can request help or report accessibility problems with a digital product, download, template, spreadsheet, or file through the Contact page or Jivaro Discord ticket system.
Known limitations
Jivaro is actively improving the site, but some areas may still have accessibility limitations.
Older pages
Some older pages, legacy layouts, archived content, or older code blocks may need accessibility updates.
Custom apps and tools
Some custom apps, tools, calculators, generators, games, or interactive features may have limitations related to keyboard access, screen reader behavior, labels, focus order, or visual layout.
Third-party services
Third-party embeds, checkout systems, payment providers, ads, videos, forms, newsletter tools, or social platforms may vary in accessibility.
Generated and downloadable files
Generated outputs, downloaded files, PDFs, spreadsheets, templates, and digital products may vary in accessibility depending on the tool, file format, and user settings.
How to report an accessibility issue
If you encounter an accessibility barrier on Jivaro, you can report it through the Contact page or by joining the Jivaro Discord and opening a support ticket.
Helpful reports include the page URL, the issue you encountered, what you were trying to do, your browser and device, any assistive technology used, and screenshots or details that may help reproduce the issue.
Feedback review
Jivaro reviews accessibility feedback, but cannot guarantee that every request can be resolved immediately. Accessibility fixes may be prioritized by severity, user impact, feasibility, and available resources.
Continuous improvement
Periodic review
Jivaro may periodically review pages, layouts, tools, apps, store resources, and digital products for accessibility and usability improvements.
Design and content updates
Accessibility improvements may be handled during redesigns, content refreshes, app updates, bug fixes, template updates, and store-product revisions.
User-driven priorities
User feedback helps Jivaro identify barriers, prioritize improvements, and focus on the issues that most affect real visitors.
Relationship to other Jivaro policies
Privacy Policy
The Privacy Policy explains how Jivaro handles privacy, data, cookies, forms, tools, store purchases, and third-party services.
Apps Data Policy
The Apps Data Policy explains how Jivaro apps and tools may handle local storage, user inputs, files, share links, analytics, and external services.
Terms of Use
The Terms of Use govern use of Jivaro content, apps, tools, store products, services, downloads, and interactive features.
Contact
The Contact page is the main route for accessibility feedback, support requests, corrections, media requests, and general inquiries.
Jivaro Trust Center
Trust Center pages
These pages explain how Jivaro handles editorial standards, corrections, disclosures, privacy, accessibility, monetization, research standards, and user-facing policies.