Version
3.5.x
Release Date
2026-07-01
This tool listing was updated on 18 November 2026.
Authoring tool user interface accessibility
Web-based functionality is accessible
partially
Description: OJS is fully web-based. Most core editing, submission, and editorial-workflow screens are keyboard operable, honour browser text scaling and text spacing, and were tested by independent auditors with disabilities using JAWS, NVDA, Narrator, VoiceOver, and braille displays (audit completed March 2026). The tool does not yet fully conform to WCAG 2.2 AA: known gaps include drag-and-drop reordering without a keyboard alternative, rich text editors that are hard for screen readers to use, reflow problems at 200–400% zoom in editorial views, and incomplete form error messages. Each gap is documented per WCAG success criterion (with linked GitHub issues) in our public
Accessibility Conformance Report. Remediation is underway; fixes are tracked on our public roadmap, and the report is updated as releases ship.
Non web-based functionality is accessible
not applicable
Alternative content available to editors
partially
Description: Most essential controls and images expose text alternatives, but several gaps remain. Small action icons (edit, delete, view) often lack descriptive labels, forcing reliance on visual cues alone; statistics graphs and charts lack text alternatives, making data points inaccessible to screen reader users; and some logos, and institution (ROR) icons are missing alt text.
The dashboard presents many identical "View" links that screen reader users cannot distinguish. Each issue is tracked publicly in our Accessibility Conformance Report with linked GitHub issues; fixes are part of the ongoing remediation cycle.
Editing-view presentation can be programmatically determined
partially
Description: Status and save notifications are announced programmatically, but some custom widgets and dynamic components expose state incorrectly to assistive technologies; tracked in our public
Accessibility Conformance Report.
Works with keyboard
partially
Description: All core functions are operable by keyboard, and no keyboard traps were identified. However, some complex interactions are not yet fully keyboard-accessible: reordering by drag-and-drop lacks a keyboard alternative, and rich text editors can trap focus or require undocumented key combinations to exit.
Enough time
partially
Description: No time-based limits are enforced on user sessions in the editorial interface. An auto-save timer announces itself in a way testers found distracting; this is tracked for improvement in the Q2 2027 remediation cycle
Flashing content optional
not applicable
Content can be navigated by structure
partially
Description: Focus order and navigation order generally follow a logical sequence, and multiple ways to reach pages exist (menu, breadcrumbs, dashboard links). But heading hierarchy has known problems: missing or invisible page H1s, duplicate headings, and over-use of H2 on landing pages, and page titles in the editorial dashboard do not change per view. Tracked in the Github issues Accessibility Roadmap to be included in constant release for the LTS version.
Content searchable
yes
Supports display preferences
not applicable
Previews are accessible
partially
Description: Published galleys (HTML, PDF) are previewed/read in the browser. The accessibility of generated galleys depends partly on files uploaded by authors. We will assess and update this answer.
Helps editor prevent and correct mistakes
partially
Description: Rich text editors include standard undo/redo for content edits, and destructive workflow actions (declining or deleting a submission) require explicit confirmation before taking effect. However, there is no general undo for workflow actions themselves.
Changes like sending a submission to a new review stage, modifying settings, or bulk edits to submissions generally cannot be reversed by the user.
Some form flows also lose edits when errors occur. These limitations are noted in our audit and will inform upcoming remediation work.
(Accessibility) features documented
yes
Support for producing accessible content
Generates accessible markup
partially
Description: OJS generates published article pages, journal homepages, and email communications from the Default Theme. The front end was audited (March 2026) and performs well overall but does not yet fully conform to WCAG 2.2 AA.
Accessibility of submitted manuscript files (e.g., author-produced PDFs) remains the responsibility of each author/journal, as documented in PKP's accessibility statement scope.
Preserves accessibility information
partially
Description: Preservation is not guaranteed for all accessibility information, e.g. alternative text for embedded images can be lost or become non-descriptive during a copy-and-paste process, and table semantics from the source document are not reliably retained. Authors are advised to review pasted output, but no in-tool warnings flag dropped accessibility information.
Accessible content production is possible
partially
Description: Structured metadata fields and rich text formatting with headings/lists make accessible content production possible, but accessibility-relevant options (like image alt text) are not prominently surfaced or prompted; authors can produce accessible content without being guided to it.
Editors guided
no
Text alternatives can be managed
partially
Description: Alt text and caption fields are available for image uploads and rendered in published output, but there is no mechanism for the dashboard's statistics charts, and providing alternatives is not enforced; tracked in our public Accessibility Conformance Report.
Accessible templates available
yes
Accessible components/plug-ins available
partially
Description: Core built-in components were independently audited (March 2026; see our Accessibility Conformance Report), but third-party plugins are not evaluated, and the plugin gallery does not indicate accessible options; plugin accessibility varies and relies on plugin developers to comply.
Checks accessibility automatically
no
Provides suggestions to content editor about accessibility problems
no
Accessibility features prominent
partially
Description: Semantic structure, responsive layout, and labelled metadata fields are on by default in the standard theme, but accessibility features are not surfaced or explained in the editing workflow; users must consult documentation to discover them.
Documentation promotes accessibility
partially
Description: PKP Docs and the accessibility documentation aim to be accessible; PKP's website statement notes its own web properties are still working toward verified WCAG 2.1 AA conformance end-to-end.