Accessibility (WCAG 2.1 AA) Compliance for Scientific Publications
Detailed manual for making OJS journals compliant with WCAG 2.1 Level AA. Learn how to optimize color contrast, configure ARIA attributes, and ensure screen reader support.
Real Problem
Many academic journals fail basic accessibility standards: missing alt tags on figures, low text-contrast ratios, keyboard navigation traps, and untagged PDF galleys.
Practical Solution
Audit and retrofit your OJS theme to meet WCAG 2.1 Level AA standards: enforce 4.5:1 text contrast ratios, implement ARIA landmarks, enable full keyboard navigation, and provide structured HTML/XML galleys.
The Ethical and Legal Mandate of Accessible Science
Open access publishing is founded on the principle that scientific research should be freely accessible to everyone. Yet, when an academic platform fails basic web accessibility standards, researchers with visual, motor, or cognitive impairments are effectively locked out of scholarly discourse.
Furthermore, university presses and institutional publishers are increasingly subject to legal accessibility mandates:
- United States: Section 508 of the Rehabilitation Act and Title II of the ADA.
- European Union: European Accessibility Act (EAA) and Web Accessibility Directive (EN 301 549).
- International: United Nations Convention on the Rights of Persons with Disabilities.
Core Pillars of WCAG 2.1 Level AA in OJS
1. Perceivable: Color Contrast and Visual Sizing
The most common accessibility failure on academic portals is faint gray text on white backgrounds.
- Regular text (under 18pt) must have a contrast ratio of at least 4.5:1 against the background.
- Large text (18pt+ or 14pt bold) must achieve at least 3:1.
- Interactive UI components (borders of form inputs, buttons) must achieve 3:1 against adjacent background colors.
2. Operable: Full Keyboard Navigability
Every interactive element on your OJS journal must be fully operable without a mouse:
- Visible Focus Indicators: Never set outline: none in your CSS! Provide a high-contrast focus ring (e.g., 2px solid #2563eb) when users Tab into buttons or navigation links.
- Skip to Content Links: Ensure the first focusable element on every page is a "Skip to Main Content" anchor allowing screen reader users to bypass repetitive header navigation.
3. Understandable: Semantic HTML and ARIA Landmarks
Screen readers rely on semantic structure to understand page hierarchy. Ensure your child theme templates use:
- <header> for the journal masthead.
- <nav aria-label="Main Navigation"> for menu links.
- <main> for article content and submission forms.
- <footer> for copyright and licensing details.
Heading tags (<h1> through <h6>) must follow a strict logical hierarchy:
- <h1>: The Article Title (only one per page).
- <h2>: Main sections (Abstract, References, Author Details).
- <h3>: Subsections within main sections.
4. Robust: Accessible Document Galleys
True accessibility extends beyond the web page into the published galleys themselves:
- Provide HTML galleys: HTML is inherently more accessible than static PDF files.
- Tagged PDFs: When generating PDFs in InDesign or Word, export them as "Tagged PDFs" to preserve heading outlines and alternative text for figures.
Step-by-Step Action Plan
Audit Color Contrast Ratios
Verify all body text meets a minimum 4.5:1 contrast ratio against backgrounds, and large text meets 3:1.
Implement Semantic HTML & ARIA Landmarks
Add <main>, <nav>, <header>, <aside>, and role="region" landmarks across all Smarty templates.
Enable Full Keyboard Navigability
Ensure all links, dropdowns, and submission modals can be navigated smoothly using Tab and Shift+Tab keys.
Mandate Alt Text for Scientific Figures
Require authors and copyeditors to input descriptive alternative text for all embedded figures and charts.
Adopt Accessible Galley Formats
Provide structured HTML and tagged PDF galleys to enable seamless reading by screen-reader assistive devices.
Questions People Usually Ask
What is WCAG 2.1 Level AA and why does it matter for university journals?
WCAG 2.1 Level AA is the internationally recognized benchmark for web accessibility. In the US (ADA Section 508), EU, and UK, public university publications are legally required to comply with these standards.
Can visually impaired researchers read mathematical formulas in OJS?
Yes, if formulas are rendered using MathML or MathJax with semantic speech support, rather than static flat images.
How can editors verify whether an uploaded PDF is accessible?
Use Adobe Acrobat’s Accessibility Full Check tool. An accessible PDF must be tagged, feature a logical reading order, have alt text on figures, and define a base document language.
Audit Your Journal for Accessibility Compliance
AcademiaTech audits and certifies OJS platforms to meet WCAG 2.1 AA, Section 508, and European EN 301 549 accessibility mandates.