CryptoFox believes that access to reliable cryptocurrency news and financial information should not be limited by disability or the choice of browsing technology. This Accessibility Statement describes the measures we have taken, the standards we target, the limitations we are working to address, and how you can contact us if you encounter a barrier on our Site. It covers the website at cryptofox.news and applies to all content published under that domain.
01 Our Commitment to Accessibility
Digital accessibility means ensuring that websites and applications can be used by people with a wide range of disabilities — including visual, auditory, motor, cognitive, and neurological conditions — regardless of whether they use assistive technology, specialized browsers, or non-standard input devices.
We treat accessibility as an ongoing engineering and editorial responsibility, not a compliance checkbox. Our team reviews new features and content templates for accessibility before they are shipped, and we actively solicit feedback from users who experience barriers on our platform.
Accessibility improvements are integrated into our regular development cycle. This statement is reviewed and updated at least annually, and following any major redesign or feature release.
02 Standards & Guidelines We Follow
CryptoFox uses the following internationally recognized standards and resources to guide our accessibility work:
- WCAG 2.1 Level AA — the Web Content Accessibility Guidelines published by the World Wide Web Consortium (W3C). WCAG 2.1 builds on WCAG 2.0 and adds criteria specifically addressing mobile accessibility, low vision, and cognitive disabilities.
- WAI-ARIA 1.2 — the Accessible Rich Internet Applications specification, used to add semantic meaning to dynamic and interactive UI components such as navigation menus, modal dialogs, live price tickers, and article reaction widgets.
- WCAG 2.2 — we monitor the latest version of the guidelines (published October 2023) and are incorporating relevant new success criteria, particularly around focus indicators and dragging alternatives, into our roadmap.
- Section 508 (US Federal standard) and EN 301 549 (European standard) — both of which substantially reference WCAG 2.1 AA as their technical baseline.
03 The Four WCAG Principles — Our Status
WCAG 2.1 is organized around four principles, known as POUR. Here is our current status against each:
Information and UI components must be presentable in ways users can perceive. We provide text alternatives for images, adequate color contrast, and resizable text without loss of functionality.
UI components and navigation must be operable. Core navigation is keyboard-accessible. Some interactive widgets (live ticker, chart controls) have partial keyboard support — see known issues.
Information and operation must be understandable. We use plain language, consistent navigation, error identification in forms, and provide the page language declaration on all pages.
Content must be interpretable by assistive technologies. We use semantic HTML and ARIA. Ongoing work is improving ARIA live region announcements for the price ticker and real-time data widgets.
04 Accessibility Features & Techniques
Visual design
- Color contrast ratios of at least 4.5:1 for normal text and 3:1 for large text and UI components, in compliance with WCAG 2.1 Success Criterion 1.4.3.
- Information is never conveyed by color alone — icons, labels, and patterns supplement color coding throughout the Site (e.g., positive/negative price changes also use directional arrows).
- Text can be resized up to 200% using browser zoom without loss of content or functionality.
- The Site layout is responsive and adapts to viewport widths from 320px to 4K, supporting both portrait and landscape orientations on mobile devices.
- Focus indicators are visible on all interactive elements when navigating by keyboard. We do not suppress the browser's default focus outline without replacing it with an equally visible alternative.
Semantic structure & markup
- A single <h1> heading is used on every page. Article pages expose a logical heading hierarchy (h1 → h2 → h3) that screen readers can use for navigation.
- All meaningful images include descriptive alt text. Decorative images use empty alt="" and aria-hidden="true".
- Navigation landmarks are implemented using <header>, <nav>, <main>, <aside>, and <footer> HTML5 elements.
- A visible, keyboard-accessible "Skip to main content" link appears at the top of every page to allow keyboard and screen reader users to bypass repetitive navigation.
- All form inputs have programmatically associated <label> elements. Error messages are announced to screen readers via aria-describedby.
- The page language is declared on the <html> element (lang="en") on all pages.
Dynamic content & live regions
- The live cryptocurrency price ticker uses aria-label to identify the region and includes a pause mechanism so users can stop the scrolling animation (hover pauses; keyboard focus pauses).
- Modal dialogs (search overlay, sidebar menu) trap focus correctly, return focus to the triggering element on close, and are dismissable with the Escape key.
- Interactive UI state changes (e.g., submitting a reaction vote, expanding a submenu) are communicated to assistive technologies via appropriate ARIA attributes (aria-expanded, aria-pressed).
The entire CryptoFox website can be navigated without a mouse. All interactive elements are reachable via keyboard, and focus order follows a logical reading sequence. The following shortcuts are supported:
06 Assistive Technology Compatibility
CryptoFox has been tested with the following combinations of assistive technologies and browsers. We recommend keeping both your browser and assistive technology updated to their latest versions for the best experience.
07 Known Limitations & Remediation Plan
Despite our best efforts, the following known accessibility limitations exist on CryptoFox as of the date of this statement. We document them here in the spirit of full transparency and have included our planned remediation for each.
| Issue | WCAG criterion | Impact | Status |
|---|---|---|---|
| Live price ticker lacks full ARIA live region announcements for screen readers | 4.1.3 Status Messages (AA) | Screen reader users may not hear live price updates automatically | In progress |
| Chart modal (TradingView overlay) — keyboard trap on timeframe buttons in some browsers | 2.1.2 No Keyboard Trap (A) | Keyboard users may have difficulty exiting chart timeframe control group | In progress |
| Infinite news scroll — newly loaded articles not announced to screen readers | 4.1.3 Status Messages (AA) | Screen reader users unaware that new content has loaded | Planned Q2 2026 |
| Some article thumbnail images missing descriptive alt text (legacy content) | 1.1.1 Non-text Content (A) | Screen readers announce filename rather than image description | Bulk remediation underway |
| Mobile hamburger menu — focus not returned to trigger button on close in all browsers | 2.4.3 Focus Order (A) | Keyboard and screen reader users may lose their position in the page | Planned Q2 2026 |
| Narrator (Windows) — ARIA live regions in price widget not consistently announced | 4.1.3 Status Messages (AA) | Narrator users do not receive price update announcements | Under investigation |
08 Third-Party Content
Some content and functionality on CryptoFox is provided by third-party services. While we select and configure these tools with accessibility in mind, we cannot always guarantee full WCAG conformance of externally hosted components:
- Binance API data widgets — real-time price charts and ticker data. We wrap these with semantic HTML and accessible labels where possible, but the underlying chart rendering is third-party.
- Google Analytics — operates entirely server-side and in the background; it adds no interactive UI elements and has no impact on the user-facing accessibility of the Site.
- Social media share links — links to Twitter/X, Telegram, and Threads. These open in new tabs with appropriate
rel="noopener"and are labeled with visually hidden text for screen readers. - External resources — articles may link to third-party websites, press releases, and regulatory documents. We have no control over the accessibility of those external destinations.
Where third-party tools create accessibility barriers that we cannot resolve, we aim to provide equivalent information through an accessible alternative format. Please contact us if you need information that is currently only available in an inaccessible format.
Our commitment to
expertise, trust,
and inclusion
We test our accessibility features against real assistive technologies and with users who rely on them, not just automated checkers.
Our development team applies WCAG 2.1 criteria, WAI-ARIA patterns, and HTML5 semantics throughout the build process.
We publish this statement publicly, document known issues honestly, and link to the official W3C WCAG documentation.
We respond to accessibility feedback within 5 business days and set concrete, dated remediation targets for known issues.