Many publishers use an “XML-first” publishing workflow, producing a master XML file that is used to generate HTML, PDF, EPUB, and other formats.

If you receive a PDF that is untagged, or where the tag structure is incomplete or incorrect, it is usually best to return to the source document, make the necessary accessibility repairs, and then re-create the PDF.

IMPORTANT: never “Print to PDF” when exporting a Word Document to PDF. A screen reader user may still be able to access the text of a PDF created in this way, but heading structure, alternative text, and any other tag structure will be lost.

Screen readers will read out the type followed by the title, like “PDF: Open badges as credentials in Open Education systems: Case studies from Greece and Europe”.

if you publish galleys in PDF, you can set the language tag for the document as follows: Open the Document Properties dialog: Choose File > Properties Select a language from the Language menu in the Reading Options area of the Advanced tab.

If you use OJS with multiple languages, make sure to use the proper language locale for that language (e.g. French locale for the French language) as the locale determines the language tag for the page.

Assistive technologies inform users what type of list will be read before proceeding to each item.

Words separated by hyphens “-“ and by capital letters (e.g. dogShow) may be read as individual words depending on the screen reader

Making the file name identifiable and meaningful will help both screen reader users and anyone who saves the file locally for future reference

ontrast ratio as at least 4.5:1 for normal text and 3:1 for large text, for Level AA.

Image clues to write about in alt text:

reCAPTCHA. When enabled on the user registration page, reCAPTCHA presents a major barrier for screen reader users with braille devices and VoiceControl users on iPhone. Additionally reCAPTCHA is missing an iFrame title and a form label, so even those screen reader users who can use it, may encounter barriers.

The audit went much further than WCAG 2.1 or WCAG 2.2 (Draft) Level AA. It included items that are not currently included in WCAG, such colour blindness, font type and style, and lessening barriers that impact people with cognitive, neurological, intellectual and/or learning disabilities. The audit also included usability best practices, in order to make the site more accessible and usable for everyone.

audit focused on lowering barriers on the Default Theme for people with different disabilities

The Default Theme in OJS 3.3 and higher has been audited for accessibility barriers and its state of accessibility is outlined in the OJS 3.3+ Default Theme Accessibility Statement.

developed by the Public Knowledge Project through its federally funded efforts to expand and improve access to research.

The average number of articles published was 31 per year with 74% publishing 0–30 articles, and 9% 60 or more. The study also contains interesting data about the workload done, revenues etc.

Open Journal Systems