Research discovery should work for more readers

ArcXiv’s application shell and public policy pages are designed to support:

• semantic landmarks, heading order, lists, labels, and a skip-to-content link;
• keyboard navigation with visible focus indicators for interactive controls;
• responsive layouts that reflow for smaller screens and text enlargement;
• light and dark color schemes with readable text contrast as a design constraint;
• reduced-motion preferences for non-essential animation where implemented; and
• text labels or accessible names for controls that otherwise use icons.

Individual product surfaces can fall short of those goals. The presence of these patterns is not a statement that every route or state meets WCAG or has passed an independent accessibility audit.

Research metadata can contain LaTeX notation, long author lists, wide tables, and unusual symbols. AI-generated lessons can include equations, diagrams, or interactive material whose alternative text or keyboard behavior is incomplete. Dynamic loading and status updates may also vary by feature.

Paper PDFs and official records are hosted by arXiv or other third parties. ArcXiv does not control the accessibility of those destinations and cannot provide an alternate edition of a paper whose rights and source files it does not hold.

A useful report identifies the route and control, expected result, observed result, and any workaround already tried. Screenshots are optional; a text description is enough. Accessibility reports are reviewed as product defects rather than editorial corrections.

ArcXiv may repair the interface, add a label or text alternative, provide a reasonable content explanation, or document a third-party limit. No universal response or repair deadline is promised on this page.

• Contact and reporting details
• Privacy when submitting a report
• Content corrections and removal reports