Structure and labels
Pages use headings, sections, lists, tables, landmarks, descriptive link text, form labels, and table captions to preserve meaning beyond visual layout.
Chart context
should stay readable.
Auction Foundry aims to make its website usable across keyboard, touch, zoom, small screens, and assistive technology. WCAG 2.2 Level AA informs the work, but this page does not claim full conformance or third-party certification.
- Keyboard visible focus
- Text readable contrast
- Reflow small-screen layouts
- Motion reduced-motion support
01
Current support
Keyboard operation
Links, buttons, form controls, disclosure summaries, and scrollable reference tables are keyboard reachable with visible focus treatment.
Responsive reading
Layouts reflow for desktop, tablet, and phone widths. Dense settings and comparison tables scroll within a labeled region instead of forcing page-level horizontal movement.
Color and state
Important status and risk language is stated in text rather than communicated by color alone. Primary text and controls are designed around readable contrast.
Images and motion
Informative images include text alternatives; decorative marks use empty alternatives. When reduced motion is requested, cards and headings appear without rising into view and the homepage theme explorer switches without transitions.
Error prevention
The risk planner labels inputs, explains invalid geometry, confirms reset, names saved-browser behavior, and keeps modeled estimates separate from executed results.
02
Known limitations
- The market-context collage has a concise text alternative, but it is illustrative and does not provide a data table for every visual mark.
- Large settings matrices and indicator comparisons require contained horizontal scrolling on narrow screens.
- TradingView publications and other external destinations are outside Auction Foundry’s interface control.
- No complete third-party accessibility audit or assistive-technology matrix has been recorded for the current release.
- Automated tests and browser checks can identify regressions, but they do not establish full WCAG conformance.
03
Standard and testing
WCAG 2.2 Level AA is used as a practical reference for text alternatives, contrast, reflow, keyboard access, focus visibility, target size, predictable navigation, labels, and error assistance.
Release checks include responsive browser review at desktop, tablet, and phone widths; page-level overflow inspection; keyboard focus review; route and link tests; and contrast contracts for key status surfaces. Those checks are reported as specific evidence, not as certification.
Read the W3C WCAG 2.2 quick reference ↗04
Scope and status of this statement
An accessibility statement is only useful if it says who wrote it, what it covers, and how far it has been checked. This one covers every page served from auction-foundry.io, including the indicator manuals, the research library, and the risk planner.
Conformance status
Partially conformant with WCAG 2.2 Level AA. Parts of the site meet the standard; the limitations in section 02 are the parts not yet confirmed against it.
How this was assessed
Self-evaluation by the person who builds and maintains the site, using browser review, keyboard walkthrough, and the automated route and contrast checks that run on every release. No external audit has been commissioned.
Statement prepared
August 15, 2026; revised October 9, 2026, against the site as deployed that day. It is revised when the site changes in a way that changes an answer here, not on a schedule.
Outside this scope
TradingView’s own website, where the indicators are published and run, is built and operated by TradingView, Inc. and is outside our control. The same applies to any other external destination linked from these pages.
There is no accessibility overlay, toolbar, or automatic-remediation widget on this site, and there will not be one. Those products are marketed as a fix for exactly this situation, and disability-advocacy organizations have consistently reported that they interfere with the screen readers and browser settings people already have configured. Where this site falls short, the honest answer is to fix the page.
05
Report a barrier
If something is difficult to perceive, navigate, operate, or understand, send the page address, what you were trying to do, the barrier you encountered, and—if you are comfortable sharing it—the browser, device, and assistive technology used.
Use the feedback page or email support@auction-foundry.io. Do not include brokerage credentials, account access, or unrelated sensitive information.
Reports go to the person who builds the site, not to a queue. Where a barrier can be fixed quickly it is fixed and shipped; where it cannot, we would rather say so plainly than leave a report unanswered. No reply date is guaranteed, and this statement is not a formal complaints procedure.
If a page on this site is unusable for you, ask for the content itself and we will send it another way — the settings table for an indicator, the text of a manual, or the numbers a planner would have produced — in plain text by email. Every page here is a document at heart, and a document can be delivered without the page around it.