OJS/OMP/OPS Editorial View Accessibility Conformance Report
Based on VPAT® 2.4
On this page
- Name of Product/Version
- Report Dates and Version
- Product Description
- Contact Information
- Notes
- Evaluation Methods Used
- Applicable Standards/Guidelines
- Terms
- WCAG 2.1 Report
- Legal Disclaimer
- Repository
- Feedback
Name of Product/Version
OMP/OJS/OPS Editorial View 3.5
Report Dates and Version
- Report Date: 2026-03-05
- Last Modified Date: 2026-07-03
- Version: omp/ojs/ops editorial view-3.5-1
Product Description
The Editorial View that ships with OJS, OMP, and OPS is designed to work great for a broad range of users. It employs a common, straightforward design style that should fit user needs and ensures the content is easy-to-access no matter what. This report covers the administrative (Editorial View) interfaces evaluated during the March 2026 accessibility audit.
Contact Information
Author Information
- Name: Israel Cefrin
- Company: Public Knowledge Project
- Email: icefrin@sfu.ca
- Website: http://pkp.sfu.ca/
Vendor Information
- Name: Teresa YH Lee
- Company: Public Knowledge Project, Simon Fraser University
- Email: lee_ty@sfu.ca
- Website: http://pkp.sfu.ca/
Notes
OJS, OMP, and OPS are authoring platforms — authors submit manuscripts, editors compose announcements and editorial decisions, and reviewers contribute structured feedback. As such, the Authoring Tool Accessibility Guidelines (ATAG) 2.0 are relevant to a comprehensive accessibility evaluation of these products.
This WCAG 2.1 conformance report evaluates the accessibility of content rendered and interacted with by end users, including authoring interfaces such as submission forms, rich text editors, and reviewer workflows. Where applicable, WCAG criteria in the tables below include authoring-tool component findings that overlap with ATAG Part B concerns — particularly around rich text editor operability (2.1.1), programmatic labels on editing fields (3.3.2), and content validation feedback (3.3.1).
A separate ATAG 2.0 Part B assessment is planned as part of PKP’s broader accessibility roadmap. This assessment will evaluate the platform’s capacity to support authors in producing accessible content, including: guidance for non-text alternatives, heading structure preservation through the rich text editor, and accessibility-aware content transformation during import/export. Until that assessment is complete, ATAG conformance is not claimed.
The Backend administrative interfaces audit found many barriers requiring remediation. While the frontend reader interface has some improvements, the admin interfaces remain critically non-compliant in several areas. If you encounter barriers, or need accommodations, please report them via the PKP accessibility report form: https://pkp.sfu.ca/accessibility-report/.
Evaluation Methods Used
Reviewer’s Testing Technologies
- Mac Air
- iPhone 15 Pro
- iPhone 14 Pro
- Windows 10 and 11 laptops
- Apple Mac Mini (M1, 2020)
- iPad Pro 12.9” (5th Generation)
- Different accessibility related apps, plugins, extensions, as well as online checking software, were used in Chrome, Edge, Safari, and Firefox.
Third Party Testers Testing Technologies
- JAWS 2026 on Microsoft Edge on Windows 10 (updated February 2026)
- VoiceOver on Safari on iPhone 14, iOS 26 (updated February 2026)
- Screen Reader with Braille Device (Deaf-Blind)
- VoiceOver on Safari on iPhone 13 Pro, iOS 17.6.1 with Focus 14 Blue braille display (updated March 2025)
- Screen Reader with Braille Device
- JAWS 2022 on Google Chrome on Windows 11 Pro with Mantis braille display (updated February 2025)
- VoiceOver on Safari on iPhone 14 Pro, iOS 26.3
- Windows Narrator on Microsoft Edge on Windows 11 version 25H2 (up to date March 2026)
- NVDA 2025.3.3 on Google Chrome on Windows 11 version 25H2 (updated February 2025)
- VoiceOver on Safari on iPad Pro 12.9″ (5th Generation), iPadOS 26.3, Chrome with pinch-to-zoom and Dynamic Type enabled (19pt+ font)
- Safari on macOS 26.0.1 on Apple Mac Mini (M1, 2020) with 27″ external monitor at 1280×720p, increased display contrast, and browser zoom (Ctrl +)
Testers disabilities
- Fully blind
- Deaf-Blind
- Almost fully blind (near fully blind)
- Low vision
- ADD
- Panic and anxiety disorders
Applicable Standards/Guidelines
This report covers the degree of conformance for the following accessibility standard/guidelines:
| Standard/Guideline | Included In Report |
|---|---|
| Web Content Accessibility Guidelines 2.0(opens in a new window or tab) | Level A (Yes) Level AA (Yes) Level AAA (No) |
| Web Content Accessibility Guidelines 2.1(opens in a new window or tab) | Level A (Yes) Level AA (Yes) Level AAA (No) |
| Web Content Accessibility Guidelines 2.2(opens in a new window or tab) | Level A (No) Level AA (No) Level AAA (No) |
Terms
The terms used in the Conformance Level information are defined as follows:
- Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
- Partially Supports: Some functionality of the product does not meet the criterion.
- Does Not Support: The majority of product functionality does not meet the criterion.
- Not Applicable: The criterion is not relevant to the product.
- Not Evaluated: The product has not been evaluated against the criterion. This can be used only in WCAG 2.x Level AAA.
WCAG 2.1 Report
Table 1: Success Criteria, Level A
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.1.1 Non-text Content(opens in a new window or tab) | Web:Partially Supports Electronic Documents:Not Applicable Software:Supports Authoring Tool:Partially Supports | Web:Graphs and charts used for statistics (e.g., Monographs, Preprints) lack text alternatives, rendering data points inaccessible to screen reader users. Small action icons (edit, delete, view) often lack descriptive labels, forcing reliance on visual cues alone. Broken links and missing href attributes were also identified. Platforms: OJS, OPS, OMP All open WCAG 1.1.1 issue(s): 12596, 12649 Software:Data structures expose values correctly when properly labeled in the UI layer. Authoring Tool:Authors and editors interacting with submission metadata, announcements, and editorial guidance encounter unlabeled action icons (edit, delete, view) and inaccessible statistical graphs. These barriers affect content production workflows where authors upload files and editors manage publication assets. |
| 1.2.1 Audio-only and Video-only (Prerecorded)(opens in a new window or tab) | Web:Not Applicable Authoring Tool:Not Applicable | Web:Audio-only media content is not present in the administrative interfaces. Authoring Tool:No audio-only media authoring in Editorial View interfaces. |
| 1.2.2 Captions (Prerecorded)(opens in a new window or tab) | Web:Not Applicable Authoring Tool:Not Applicable | Web:Video content without audio transcripts are not commonly present in admin interfaces. Authoring Tool:No video captioning workflows in Editorial View. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded)(opens in a new window or tab) | Web:Not Applicable Authoring Tool:Not Applicable | Web:Media synchronization alternatives are not required for admin workflow interfaces. Authoring Tool:No media synchronization in authoring workflows. |
| 1.3.1 Info and Relationships(opens in a new window or tab) | Web:Partially Supports Software:Supports Authoring Tool:Partially Supports | Web:Critical structural failures exist in table semantics and form labeling. Table headers frequently misuse the scope attribute on data cells instead of header cells. Rich text editors (used for Author Guidance, Announcements) are unreadable by screen readers, often labeled only as “clickable application” without exposing content. Filter controls behave incorrectly, and navigation submenus fail to announce their expandable state or auto-expand confusingly. Duplicate headings and improper heading hierarchies are prevalent. Platforms: OJS, OPS, OMP All open WCAG 1.3.1 issue(s): 9355, 9357, 12467, 12839 Software:Backend data structures maintain proper relationships when semantic markup is correctly implemented. Authoring Tool:Rich text editors used for Author Guidance, Announcements, and editorial decisions are unreadable by screen readers, labeled only as “clickable application.” This directly impedes content authors who rely on these editors to produce published material. Table semantics and form labeling failures also affect authoring contexts. |
| 1.3.2 Meaningful Sequence(opens in a new window or tab) | Web:Supports Authoring Tool:Supports | Web:Navigation order generally follows logical visual flow. Authoring Tool:Navigation order follows logical flow for authoring tasks. |
| 1.3.3 Sensory Characteristics(opens in a new window or tab) | Web:Supports Authoring Tool:Supports | Web:Buttons and breadcrumbs provide complementary text to screen reader users. Authoring Tool:Instructions in authoring forms don’t rely solely on sensory characteristics. |
| 1.4.1 Use of Color(opens in a new window or tab) | Web:Partially Supports Authoring Tool:Partially Supports | Web:Dashboard notification indicators lack explicit context, relying primarily on color to convey meaning. Red bubbles do not define their status or urgency through text or icons, creating barriers for users with color vision deficiencies. Platforms: OJS, OPS, OMP All open WCAG 1.4.1 issue(s):12703 Authoring Tool:Color-only notification indicators affect content authors monitoring submission queues. |
| 1.4.2 Audio Control(opens in a new window or tab) | Web:Not Applicable Authoring Tool:Not Applicable | Web:No audio playback features require pause controls in administrative workflows. Authoring Tool:No audio playback in authoring workflows. |
| 2.1.1 Keyboard(opens in a new window or tab) | Web:Partially Supports Software:Partially Supports Authoring Tool:Partially Supports | Web:Complex interactions are not fully keyboard accessible. Reordering components (drag-and-drop) lacks a keyboard alternative, and rich text editors trap focus or require undocumented key combinations to exit. Some navigation tabs and dropdowns do not respond correctly to standard tab/enter navigation. Platforms: OMP, OJS, OPS All open WCAG 2.1.1 issue(s): 12601, 12681, 12838 Software:System functions do not provide full keyboard operability for all interactive elements. Focus management requires improvement across complex workflows. Authoring Tool:Drag-and-drop reordering lacks keyboard alternatives, affecting editors who arrange submission files and chapter orders. Rich text editors trap focus, preventing authors from completing content production tasks efficiently via keyboard alone. |
| 2.1.2 No Keyboard Trap(opens in a new window or tab) | Web:Supports Authoring Tool:Supports | Web:No keyboard traps were identified; users can generally navigate away from all focused elements. Authoring Tool:No keyboard traps beyond RTE focus issues already captured under 2.1.1. |
| 2.1.4 Character Key Shortcuts(opens in a new window or tab) | Web:Not Applicable Authoring Tool:Not Applicable | Web:No custom keyboard shortcuts are implemented in the administrative interfaces. Authoring Tool:No custom keyboard shortcuts in Editorial View authoring interfaces. |
| 2.2.1 Timing Adjustable(opens in a new window or tab) | Web:Not Applicable Authoring Tool:Not Applicable | Web:No time-based limits are enforced on user sessions in the administrative interface. Authoring Tool:No session timeouts enforced. |
| 2.2.2 Pause, Stop, Hide(opens in a new window or tab) | Web:Not Applicable Authoring Tool:Not Applicable | Web:Moving, blinking, scrolling, or auto-updating information is not commonly used. Authoring Tool:No auto-updating content in authoring contexts. |
| 2.3.1 Three Flashes or Below Threshold(opens in a new window or tab) | Web:Not Applicable Authoring Tool:Not Applicable | Web:No content flashes above three times per second in administrative interfaces. Authoring Tool:No flashing content in Editorial View interfaces. |
| 2.4.1 Bypass Blocks(opens in a new window or tab) | Web:Supports Authoring Tool:Supports | Web:Bypass blocks are available but functionality may vary in complex workflow contexts. Authoring Tool:Bypass blocks available in authoring contexts, though may vary in complex workflows. |
| 2.4.2 Page Titled(opens in a new window or tab) | Web:Partially Supports Software:Partially Supports Authoring Tool:Partially Supports | Web:Dynamic administrative pages share identical page titles regardless of the current view (e.g., “Submissions | OJS…” appears for Active, Needs Review, and Published stages). This prevents screen reader users from distinguishing between different workflow stages or contexts. Platforms: OJS, OPS All open WCAG 2.4.2 issue(s): 12840 Software:System-generated page titles do not dynamically update to reflect specific view context. Each unique admin view should receive a distinct title identifier. Authoring Tool:Identical page titles across workflow stages prevent authors and editors from programmatically identifying which submission or authoring context is currently active, increasing cognitive load during content production. |
| 2.4.3 Focus Order(opens in a new window or tab) | Web:Supports Authoring Tool:Supports | Web:Focus order generally maintains logical sequence through workflow steps. Authoring Tool:Focus order follows logical sequence through authoring steps. |
| 2.4.4 Link Purpose (In Context)(opens in a new window or tab) | Web:Partially Supports Software:Supports Authoring Tool:Partially Supports | Web:Dashboard is presenting non-descriptive “View” links that all read identically, making it impossible to identify which specific submission they refer to. Duplicate links per item increase the cognitive load and physical effort required for keyboard navigation. Platforms: OJS, OPS, OMP All open WCAG 2.4.4 issue(s): 9339, 9341, 12749, 12836 Software:Hyperlink destinations resolve correctly; naming convention is the primary presentation issue. Authoring Tool:Non-descriptive “View” links in the submission dashboard make it difficult for authors and editors to navigate to specific submissions during content review and production workflows. Duplicate links per item increase tabbing effort for keyboard-dependent content producers. |
| 2.5.1 Pointer Gestures(opens in a new window or tab) | Web:Not Applicable Authoring Tool:Not Applicable | Web:Pointer gestures are not required to operate core administrative functions. Authoring Tool:Focus order follows logical sequence through authoring steps. |
| 2.5.2 Pointer Cancellation(opens in a new window or tab) | Web:Supports Authoring Tool:Supports | Web:No single-pointer path-based gestures are required to complete workflows. Authoring Tool:No path-based pointer gestures required. |
| 2.5.3 Label in Name(opens in a new window or tab) | Web:Not Applicable Authoring Tool:Not Applicable | Web:Label-in-name is not applicable as there are no dynamic label changes triggered by pointer movement. Authoring Tool:No dynamic label changes from pointer interaction. |
| 2.5.4 Motion Actuation(opens in a new window or tab) | Web:Not Applicable Authoring Tool:Not Applicable | Web:Motion activation is not used to trigger administrative workflows. Authoring Tool:No motion-activated authoring functions. |
| 3.1.1 Language of Page(opens in a new window or tab) | Web:SupportsAuthoring Tool:Supports | Web:Dashboard supports 68 different languages and writing systems.Authoring Tool:68 languages supported, including for authoring interfaces. |
| 3.2.1 On Focus(opens in a new window or tab) | Web:Supports Authoring Tool:Supports | Web:Focusing on components does not cause unexpected context changes without user confirmation. Authoring Tool:No unexpected context changes on focus in authoring forms. |
| 3.2.2 On Input(opens in a new window or tab) | Web:Supports Authoring Tool:Supports | Web:Changing settings does not automatically initiate unintended context changes. Authoring Tool:No unintended context changes from form input in authoring workflows. |
| 3.3.1 Error Identification(opens in a new window or tab) | Web:Partially Supports Software:Partially Supports Authoring Tool:Partially Supports | Web:Error messages appear but are displayed inconsistently (sometimes under a single field rather than listing all errors). Critical feedback like password requirements may not be clearly indicated. Platforms: OMP, OJS, OPS All open WCAG 3.3.1 issue(s):12599 Software:Focus does not automatically shift to error messages upon validation failure. Users must manually discover and correct errors without systematic guidance. Authoring Tool:Users creating content (e.g., announcements, submissions) receive inconsistent validation feedback through the admin interface. |
| 3.3.2 Labels or Instructions(opens in a new window or tab) | Web:Partially Supports Software:Supports Authoring Tool:Partially Supports | Web:Rich text editor fields lack descriptive labels, making it impossible to know which section is being edited. Fieldsets are often missing legends, and filter inputs do not provide hints on available options. Platforms: OMP, OJS, OPS All open WCAG 3.3.2 issue(s): 9347, 9347, 9349, 9362, 9363, 12613, 12640, 12725 Software:Form label associations function correctly when HTML structure is properly implemented in templates. Authoring Tool:Users editing content in rich text areas cannot reliably determine which fields require input due to missing programmatic labels. |
| 4.1.1 Parsing(opens in a new window or tab) | Web:Supports Authoring Tool:Supports | Web:Parsing is successful for most dynamic content; no critical duplicate IDs detected. Authoring Tool:Parsing successful; no critical duplicate IDs in authoring templates. |
| 4.1.2 Name, Role, Value(opens in a new window or tab) | Web:Partially Supports Software:Partially Supports Authoring Tool:Partially Supports | Web:Programmatic accessibility is compromised by non-descriptive ARIA labels and landmark misconfiguration. Multiple main regions exist where only one should be present. Incorrect aside placements confuse screen readers. Dynamic components like radio buttons are incorrectly announced as “invalid” even when functional. Platforms: OJS, OPS, OMP All open WCAG 4.1.2 issue(s): 9330, 12646, 12709, 12719, 12723, 12837 Software:Several interactive elements lack necessary role and property definitions. Custom widgets (filters, graphs) do not expose proper state changes to assistive technologies. Authoring Tool:Content created through admin interfaces may inherit accessibility issues if authors rely on improperly labeled rich text editors. |
Table 2: Success Criteria, Level AAAnchor link
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.4 Captions (Live)(opens in a new window or tab) | Web:Not Applicable Authoring Tool:Not Applicable | Web:Live captions are not required as live streaming is not part of administrative workflows. Authoring Tool:No live streaming in authoring workflows. |
| 1.2.5 Audio Description (Prerecorded)(opens in a new window or tab) | Web:Not Applicable Authoring Tool:Not Applicable | Web:Audio descriptions are not required as video content is minimal in admin interfaces. Authoring Tool:No video content requiring audio descriptions. |
| 1.3.4 Orientation(opens in a new window or tab) | Web:Supports Authoring Tool:Supports | Web:The interface provides support for both portrait and landscape orientation across screen sizes. Authoring Tool:Orientation support applies to authoring interfaces. |
| 1.3.5 Identify Input Purpose(opens in a new window or tab) | Web:Supports Authoring Tool:Supports | Web:Input purpose is properly recognized and autofill-ready for common fields. Authoring Tool:Autofill-ready fields benefit authoring forms. |
| 1.4.3 Contrast (Minimum)(opens in a new window or tab) | Web:Partially Supports Software:Supports Authoring Tool:Supports | Web:There are UI elements failing contrast requirements, including pink graph lines on dark blue backgrounds, blue text links blending into body text, and red warning banners that are too small or low contrast. Table text, search boxes against dark backgrounds, and notification bubbles are consistently too light or small to be legible. Platforms: OJS, OPS, OMP All open WCAG 1.4.3 issue(s): 9333, 9353, 12650 Software:Color selection logic renders correctly; contrast failures are CSS implementation issues. Authoring Tool:Content produced through admin interfaces inherits whatever contrast styling is applied. |
| 1.4.4 Resize text(opens in a new window or tab) | Web:Partially Supports Software:Supports Authoring Tool:Supports | Web:Text throughout the administrative interface is frequently below the recommended 1rem size. This affects critical areas such as form labels, button text, table data, error messages, and warning banners. Platforms: OJS, OPS, OMP All open WCAG 1.4.4 issue(s): 12710, 12711 Software:Font sizing is handled by browser typography engines; minimum size recommendations are not programmatically enforced. Authoring Tool:Text scaling works as expected through standard browser controls. |
| 1.4.5 Images of Text(opens in a new window or tab) | Web:Supports Authoring Tool:Supports | Web:Buttons include both icons and text labels related to the actions they perform. Authoring Tool:No images of text used in authoring interface buttons. |
| 1.4.10 Reflow(opens in a new window or tab) | Web:Partially Supports Software:Partially Supports Authoring Tool:Supports | Web:The administrative interface is completely unusable at 200% and 400% magnification. Content is pushed off-screen, scrolling is restricted in key views (e.g., “View Submission”), and layouts collapse requiring endless horizontal scrolling. On small screens (320px), submission pages and dashboard grids are rendered unusable. Platforms: OJS, OPS, OMP All open WCAG 1.4.10 issue(s): 12559 Software:System layout rendering fails to adapt gracefully to high magnification levels. Responsive breakpoints need expansion. Authoring Tool:Content reflows appropriately within the viewport constraints. |
| 1.4.11 Non-text Contrast(opens in a new window or tab) | Web:Supports | Web:Most icons utilize sufficient contrast ratios, though specific instances fall short. |
| 1.4.12 Text Spacing(opens in a new window or tab) | Web:Supports | Web:Text spacing does not block content when adjusted by users. |
| 1.4.13 Content on Hover or Focus(opens in a new window or tab) | Web:Supports | Web:Hoverable content remains visible until dismissed; no accidental dismissals reported. |
| 2.4.5 Multiple Ways(opens in a new window or tab) | Web:Supports | Web:Multiple ways exist to navigate to administrative pages (main menu, breadcrumbs, dashboard links). |
| 2.4.6 Headings and Labels(opens in a new window or tab) | Web:Partially Supports Software:Supports Authoring Tool:Supports | Web:Navigation labels are sometimes ambiguous and template configurations do not currently enforce inclusion of descriptive headings on dashboard landing pages. Platforms: OJS, OMP, OPS All open WCAG 2.4.6 issue(s): 9342, 9344, 9346, 9351, 9356, 9358, 12727 Software:Label generation logic is sound; templating inconsistencies require manual enforcement. Authoring Tool:Headings can be applied by content creators using available formatting options. |
| 2.4.7 Focus Visible(opens in a new window or tab) | Web:Partially Supports Software:Partially Supports Authoring Tool:Supports | Web:Focus indicators are inconsistent and sometimes invisible. Top account icon dropdown focus states are barely visible, and some interactive elements lack a clear focus ring entirely. Platforms: OMP, OJS, OPS All open WCAG 2.4.7 issue(s): 12748 Software:System focus management renders CSS styles that may not meet visibility thresholds for low-vision users. Authoring Tool:Focus indicators apply consistently to user-editable elements. |
| 3.1.2 Language of Parts(opens in a new window or tab) | Web:Supports | Web:Language changes are properly communicated to assistive technologies. |
| 3.2.3 Consistent Navigation(opens in a new window or tab) | Web:Supports | Web:Same navigation placement is maintained across all administrative pages. |
| 3.2.4 Consistent Identification(opens in a new window or tab) | Web:Not Applicable | Web:Consistent identification across multiple pages is maintained for repeating components. |
| 3.3.3 Error Suggestion(opens in a new window or tab) | Web:Partially Supports Software:Partially Supports Authoring Tool:Partially Supports | Web:When submitting forms, errors occur and the system provides minimal guidance on how to correct them. A generic “fill out this field” message is usually presented, but there are no actionable suggestions to help users resolve validation failures. Platforms: OMP, OJS, OPS Software:Error suggestion logic is incomplete; additional context should be programmatically communicated alongside error messages. Authoring Tool:Users editing content receive limited guidance when validation errors occur, potentially hindering correction efforts. |
| 3.3.4 Error Prevention (Legal, Financial, Data)(opens in a new window or tab) | Web:Not Applicable | Web:No financial transactions are processed on the administrative reader interface. |
| 4.1.3 Status Messages(opens in a new window or tab) | Web:Supports Authoring Tool:Supports | Web:Status messages are conveyed through roles and properties where programmatically determinable. Authoring Tool:Status messages in authoring workflows are programmatically conveyed. |
Table 3: Success Criteria, Level AAA
Legal Disclaimer (Public Knowledge Project, Simon Fraser University)
To the maximum extent permitted by applicable law, in no event will Simon Fraser University or any of its affiliates, or any of their respective governors, directors, employees, or agents, be liable for the failure of any content on applications implementing this theme to meet these accessibility standards, to the extent that such content was submitted or uploaded by a third party.
Repository
https://github.com/pkp/ojs (opens in a new window or tab)
https://github.com/pkp/pkp-lib(opens in a new window or tab)
Feedback
We welcome feedback on the accessibility of our software and website. If you encounter an accessibility barrier or need accommodations, please report them to us.
Visit our support page to access assistance with PKP software. If you would like to report an accessibility issue, please use our Accessibility report form. For all other inquiries, please use our contact form.
OpenACR (opens in a new window or tab) is a format maintained by the GSA (opens in a new window or tab). The content is the responsibility of the author.
This content is licensed under a Creative Commons Attribution 4.0 International (opens in a new window or tab).