14.1 Purpose and Scope
- We are committed to providing equitable access to all users—authors, reviewers, editors, and readers—regardless of disability, device, bandwidth, or location. This policy covers our websites, submission systems, article files, and communications.
14.2 Standards We Meet
- Conform to WCAG 2.2 Level AA across web properties and content templates.
- Apply relevant EN 301 549 / Section 508 requirements for customers who rely on them.
- Publish an up-to-date Accessibility Conformance Report (VPAT) for major platforms and formats.
14.3 Core Web Experience
- Keyboard accessibility for all interactive components; visible focus indicators; logical tab order.
- Skip-to-content and landmark navigation (header, main, nav, footer).
- Sufficient color contrast; no information conveyed by color alone.
- Responsive layouts that work on mobile, tablet, and desktop without loss of content or functionality.
- Respect user preferences: reduced motion, dark/system themes, text sizing without content loss.
14.4 Screen Reader & Semantic Support
- Clean semantic HTML, correct heading hierarchy, descriptive link text, meaningful button labels.
- ARIA used minimally and correctly (no duplicate or conflicting roles).
- Programmatic labels, instructions, and error messages for all forms; errors described in text and associated with fields.
- Language attributes set correctly and updated when passages switch language.
14.5 Documents and Article Files
- PDFs are tagged with proper reading order, headings, lists, table headers, alt text, and bookmarks; exported as PDF/UA where feasible.
- HTML articles are first-class deliverables with accessible math, figures, and tables.
- Math rendered as MathML (with a TeX fallback) and readable by assistive technologies.
- Tables include scope and headers; complex tables provide summaries or split views.
- Vector formats preferred for figures; raster images at adequate resolution with alt text or long descriptions.
- Provide machine-readable references and structured metadata (authors, ORCIDs, affiliations, funders, license).
14.6 Media (Audio/Video/Interactive)
- Closed captions and transcripts for audio/video; audio descriptions for essential visuals where needed.
- Media players support keyboard control, transcripts download, and no auto-play by default.
- Interactive figures/visualizations: keyboard operable, screen-reader discernible states, and accessible fallbacks (e.g., static images + data tables).
14.7 Images and Alt Text
- Every informative image has concise alt text conveying its function.
- Complex figures include long descriptions (within captions or supplementary materials).
- Decorative images marked with empty alt (alt="") and excluded from reading order.
14.8 Captchas, Timeouts, and Authentication
- Provide non-visual CAPTCHA alternatives (e.g., logic or email challenge).
- Adjustable or extendable session timeouts; warnings before expiry; re-authentication preserves user progress.
- Authentication flows do not rely on cognitive or sensory tests alone.
14.9 Submission & Peer Review Systems
- Accessible submission forms, error recovery, and autosave; progress indicators announced to assistive tech.
- File uploaders support keyboard operation and screen-reader feedback.
- Guidance for accessible manuscripts at submission (see 14.12) with quick checks before finalization.
14.10 Content That Could Induce Seizures or Discomfort
- No content flashes more than three times per second.
- Motion/animation effects are optional and respect “reduce motion” preferences.
14.11 Reader Controls
- Adjustable font size/line height; reflow without horizontal scrolling.
- Toggle for high-contrast mode; support for system dark mode.
- Downloadable accessible formats (HTML, tagged PDF; EPUB where available).
14.12 Author Guidelines for Accessible Articles
Authors must:
- Supply alt text for figures and meaningful captions; include scale bars and units in images.
- Provide data tables or CSVs for charted data when feasible.
- Use semantic structure (headings, lists), real text (not images of text), and concise, plain language abstracts.
- Ensure color-independent encodings in charts (patterns/markers).
- Submit MathML or LaTeX that can be converted reliably; avoid inline images of equations.
- Tag tables properly; avoid complex merged cells where possible.
- Provide transcripts for multimedia; describe essential audio/visual cues in the text.
- Declare any language switches in the text for accurate pronunciation.
14.13 Accessible Data & Code (Cross-refs Section 7)
- Datasets accompanied by data dictionaries, units, and accessible formats (CSV/JSON/Parquet with documentation).
- Repositories include README files in plain language; code examples runnable with minimal steps.
14.14 Communications & Customer Support
- All author and reviewer communications available in accessible HTML emails and web views.
- Provide multiple contact channels (email and web form) for accessibility assistance.
- Offer reasonable accommodations (extended deadlines, alternative submission formats).
14.15 Procurement & Third-Party Tools
- New platforms, plugins, and analytics tools undergo accessibility review before deployment.
- Third-party content (widgets, embeds) must meet WCAG 2.2 AA or have accessible alternatives.
- Contracts include accessibility service-level commitments and remediation timelines.
14.16 Testing, Monitoring, and Remediation
- Continuous automated testing (linting, axe, pa11y or equivalent) plus manual audits with assistive technologies.
- User testing with people who use screen readers, keyboard-only navigation, and switch devices.
- Issue tracker for accessibility bugs with public-facing summaries and expected fix timelines.
- Prioritize fixes that block core tasks (submission, reading, downloading).
14.17 Training & Governance
- Annual training for product, editorial, design, and engineering teams on accessibility principles and tools.
- A named Accessibility Lead coordinates audits, remediation, and responses.
- Change log on the accessibility page with dates and scope of improvements.
14.18 Exceptions & Alternative Access
- If a legacy artifact cannot be made fully accessible without disproportionate burden, we provide equivalent access (e.g., structured HTML, transcripts, or data tables) upon request and schedule a plan for remediation or replacement.
14.19 Feedback and Complaints
- Dedicated accessibility contact with response targets (acknowledge within 2 business days, substantive update within 10 business days).
- Escalation path to the Accessibility Lead for unresolved issues; outcomes documented and used to improve processes.
14.20 Transparency
- Public Accessibility Statement describing conformance status, known limitations, planned fixes, and the date of the last audit.
- Links to VPAT/ACR reports for major properties.