Alt text (“alternative text”) is a machine-readable tag that describes an image in words if the image cannot be displayed for any reason, including slow internet connection, error in the HTML code, or the use of assistive technology.
alt="Graph of quarterly temperature changes. Discussion available below.".
Image positioning matters for text documents (e.g. Word, PDF) when read by screen readers.
Only images with the Wrap Text style of “In Line with Text” are recognized by screen reader software. When exported to PDF, images with other wrapping styles will be skipped by a screen reader even when an alt tag is present.
When creating video and audio content, it is important to ensure that it is accessible to users with visual, auditory, and neurological disabilities. Make sure that the video does not play automatically, as people should be able to choose when to play the content. A hearing impaired person may not be aware of the audio volume; users with physical or cognitive disabilities may not be as fast to stop the video and may impact other people in their environment, as well as feel embarrassed by the situation.
Captions. Captions are text alternatives to the spoken word presented within multimedia. They are beneficial to those who cannot hear the audio, those who may not be fluent in the language or those who prefer to receive information via text over sound.
You can have automated captions generated that will then need to be reviewed and corrected by a human reader, using tools like:
Transcripts. Transcripts contain the full text of the spoken word (not necessarily verbatim) that could be accessed and read separately from the multimedia itself. Transcripts allow deaf/blind users to get content through the use of refreshable Braille devices. They are also useful for searching and navigating to a specific part of the text.
When planning a video/audio recording, it is a good idea to have the transcript written out ahead of time. It can then be used both for the multimedia creation and to be made available afterwards.
Audio descriptions. Audio descriptions are meant to provide additional information about content that is visible on the screen for users with visual disabilities. They typically take the form of a narrator that describes visual-only content in the multimedia and can be provided with the primary video, or in another audio track.
When producing a video, the need for audio descriptions can often be avoided by describing or presenting the visual content via spoken audio. For example instead of saying “click here and then here”, you can say “click File and then Save” thus conveying visual content through audio.
Sign language interpretation. While closed captions or transcripts provide a suitable alternative for users with hearing disabilities who are comfortable reading written language, they may not be sufficient for deaf users who rely on sign language as their primary (or only) language of communication. In this case an alternative can be provided via sign language interpretation or other tools outlined in the Accessibility for Sign Language users section.
Users who navigate using a screen reader must be able to unambiguously understand the purpose of the link and skip links they are not interested in. To achieve this, link text needs to be:
Descriptive. When writing URL text, make sure it can be understood without additional context. E.g.:
Concise. Use keyword(s) as linked text rather than longer sentences. For text that is meant to be printed, hyperlink the text and add a full URL. E.g.:
Unique. Avoid similarly named hyperlinks if they link to different places.
Visually distinct. Use the default blue underlined style for hyperlinks. If you change it, make sure the links are still high contrast and underlined. Don’t use underline for non-hyperlinked text.
Contrast and colour use are vital to accessibility. Having insufficient contrast may affect users with visual disabilities. Having content that relies on colour to convey meaning may affect users with colour vision deficiencies (CVD) and those who rely on screen readers.
Text colour against the background may appear as sufficiently distinct to a sighted reader, but may present issues to a reader with visual disabilities. To help evaluate it, WCAG 2.1 Guidelines quantify accessible contrast ratio as at least 4.5:1 for normal text and 3:1 for large text, for Level AA.
You can use WebAim’s Contrast Checker, Contrast Ratio Checker, or the Colour Contrast Analyser to check the contrast ratio between your website’s background and text colours. Here is an example of a check done using WebAim’s Contrast Checker:
Example of WebAim’s Colour Contrast Checker interface options
In this example, normal text of purple colour #666FF is not sufficiently distinct against the white background #FFFFFF and fails the Level AA standard, but large text of the same colour passes. To fix the issue, you can darken the text colour or increase the font size.
Similarly, you can use the WebAIM Link Contrast Checker to evaluate the visibility of your links.
We often use colour in web content or in published content to convey meaning. Using coloured graphs or illustration is one such example. When making the choice to use colour, consider whether a reader with colour vision deficiencies (CVD) or using a screen reader would still be able to understand the meaning conveyed. It is essential for the colour to not be the only means of conveying the information - consider adding other textual queues (e.g. numbers or % on a graph).
Don’t do this:
Other tools, such as the Spectrum Chrome extension allow you to emulate different types of CVD on any website. This is particularly useful if your articles contain data visualisations. The following two figures, obtained from an article published in the journal Polar Research, illustrate how CVD can affect a user’s understanding of a graph or a chart.
In this figure, the original (1) is still accessible and legible to users with deuteranopia, a green blindness, as shown in (2).
In this figure, the original’s (1) colour legend is not as clear for users with achromatopsia, total colour blindness, as shown in (2). Some of the data’s categories are too similar to each other.
Certain web-based tools like ColorBrewer provide accessible colour palettes for data visualisation, adapted to different types of datasets (sequential, diverging, qualitative). When in doubt, you may also fall back on different shapes or patterns to indicate delimitations in large groups of data points.
Understandably, text writing and formatting for a journal will likely follow conventions of a particular scholarly community. But there are general principles we can follow to make it more readable and legible.
Start by ensuring the text is free from spelling and grammar errors. You can use the built-in spell check in MS Word or Google Docs or free online tools such as GrammarCheck.
Shorter paragraphs will make the text easier to read on small screens and will help people with cognitive, neurological and/or learning disabilities. Similarly, expanding acronyms and abbreviations on first use and keeping a list of acronyms as an appendix for reference is a common and helpful practice.
WebAim’s Writing Clearly and Simply guide contains other helpful tips for writers to achieve clarity and simplicity. Additionally, tools like Hemingway App can help evaluate your text for complexity and suggest ways of improving its general readability.
Headings help users understand how the content of a page is organized. Also, they provide in-page navigation which is used by web browsers, plug-ins, and assistive technologies. When creating web content, using heading hierarchy in rank order will help users navigate the document with more ease.
Headings can provide a clearer idea about the content once it shows an outline of it. For that reason, rather than write a long main heading, it is advised to use subheadings.
It is possible to create content sections using subheadings, and these can connect related paragraphs.
Example of heading formatting for JMIR papers from JMIR Publications Knowledge Base and Help Center.
In accessible HTML documents, headings are structured using the following tags:
<h6>. They are nested according to their rank or level. Rank level is defined by the number of heading tags. Hence,
<h1> is the highest level in importance and
<h6> is the lowest subheading in the structure rank of headings.
Avoid skipping headings in a document structure to prevent confusion, even if you prefer the visual presentation. A
<h2> must be followed by a
<h3> as the next subheading in the same section. However, it is fine that a
<h4> is followed directly by a
<h2> when it opens a new section, as long as
<h4> closes the previous one.
<h1> heading should be used per document, because it is the document title or article title.
The example below shows an article structure with headings where the Article title is the highest rank heading and the most important info of the structure.
(h1) Article title
The example below demonstrates how to nest sections, with the lowest level closing the previous section. In this example, the “(h4) Background by region” closes the “(h2) Introduction” section and is fine in accessibility terms.
(h1) Article title
(h4) Background by region
There are many Text Editors available to create documents, including Microsoft Word, Apple Pages, LibreOffice, and online editors like Google Docs. You can use any editor you like to create documents with accessible heading structures.
Other editors will typically follow the same concept of heading ranking and nesting. You will usually have the option to select a portion of text and format it as a heading.
The following image shows the heading options for Google Docs:
The heading hierarchy for documents on text editors should follow the same concept of rank level for HTML documents:
According to the content presented and how the content creator wants to organize it, there are three types of lists for web content. The type of list used depends on the kind of information that is being organized and its purpose.
Assistive technologies inform users what type of list will be read before proceeding to each item. It also describes how many items are on a list, the current item, and how many list items are still remaining.
In an unordered list, the elements order is not important and is used to show a group or a set of elements. This list usually shows a bullet for each element.
This list is coded using
<ul> for the main element and
<li> for each item. Example:
<ul> <li>Researchers</li> <li>Students</li> <li>Editors</li> <li>Authors</li> </ul>
The main purpose is to show a hierarchy or sequential information. It can also show steps of instruction to follow or proceedings. It can show a number or a letter for each element listed.
This list is coded using
<ol> for the main element and
<li> for each item. Example:
<ol> <li>Accept submission</li> <li>Assign reviewers</li> <li>Send to review</li> <li>Set a due date</li> </ol>
- Accept submission
- Assign reviewers
- Send to review
- Set a due date
A description list consists of grouping terms and their descriptions. It is possible to associate one or more terms to one or more descriptions of the terms.
The markup for description lists includes the
<dl> tag for the start of the list, the
<dt> tag for the term(s), and the
<dd> tag for the description(s).
A term can be grouped to more than one description. Likewise, one or more terms can be grouped with one description. Many terms to many descriptions is also acceptable.
Screen readers will announce the number of terms as well as the descriptions. Below are some examples for description lists:
One term, multiple descriptions:
<dl> <dt>Authors</dt> <dd>John</dd> <dd>Kevin</dd> <dd>Juan</dd> <dt>Editor</dt> <dd>James</dd> </dl>
Multiple terms, one description:
<dl> <dt>OJS</dt> <dt>OMP</dt> <dd>Publishing software platforms developed by PKP.</dd> </dl>
- Publishing software platforms developed by PKP.
Multiple terms, multiple descriptions:
<dl> <dt>Authors</dt> <dt>Editors</dt> <dd>James</dd> <dd>Michael</dd> </dl>
While newer screen readers are typically compatible with multi-column layout, some older screen readers may read the page left-to-right, line by line, rendering the text out of order.
Tables are frequently used to create column formatting, but this is a common misuse. Tables (as detailed below) should be used exclusively for tabular data or content. Screen readers are expected to announce this as a “Table” and interpret the first row of a Table as the Table Header, causing potential confusion.
If you determine that columns are the best way to present your web content, the preferred way is to use CSS to format multiple columns. However, it is important to ensure that the text is ordered coherently, even when CSS is inactive.
For text documents (e.g. Word, PDF) it is important to create columns using the Columns formatting tool rather than by using the tab key or spacebar to create whitespace between lines of text.
Tables should be used exclusively to present tabular data or content. Tables can help organize content with a logical relationship in grids, making it easier to read and understand. For more on accessibility in tables see the W3C/WAI Tables Concepts page.
It is possible to use tables to position elements visually in a document or page, although it is not advisable. It can cause confusion for assistive technologies that would announce the element as a “table” where it may in fact contain different content. It may give a sense of missing data in the wrapping element.
Different types of data or content can be presented in a different structure of tables. The complete structure set of this element involves:
Below is an example of a table with elements of a table described above: Caption, Header, Body and Footer.
Table example with: Caption, Header, Body and Footer (summarizing) - Source: https://developer.mozilla.org/en-US/docs/Learn/HTML/Tables/Advanced
For HTML documents the following tags are used to define a table main structure:
<tfoot>. The last 3 elements are always wrapped by the
<table> tag. You can find further technical info about how to generate HTML tables for visually impaired users on the Mozilla web docs.
Adding metadata to your document increases its searchability. It also allows software applications and adaptive technologies to give the users the key information about the document, so they can easily find the desired document and determine if it is what they need. To learn more, see the Better Practices in Journal Metadata guide.
To add or modify the title, author, or subject of an MS Office document, navigate to:
Adding the following information in MS Word should be transferred to the PDF on conversion:
Note on using capitalization in titles
If your discipline often displays article titles in all caps, you may want to avoid entering the titles in all caps manually, as screen readers may read this as an acronym rather than a title. Instead, the title and subtitle should be entered with upper and lower-case characters, e.g. “The Trolley Problem of Climate Change”, and then made upper-case through your journal’s stylesheet. This will also ensure the title is made available in its original form for downstream indexers like Crossref and Google Scholar.
A screen reader that supports multiple languages will rely on the web pages’ language tag to know in which language to read it. 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.
Additionally, if you publish galleys in PDF, you can set the language tag for the document as follows:
If you publish galleys in HTML or XML, it is best practice to set the lang, global language attribute, to the root element of each document. This declares the language of the entire galley, and helps assistive technologies determine how to pronounce words. It also helps search engines and web browsers.
You can also add the language attribute to specific elements, when the language changes mid-document. For example, an English language document may quote a paragraph in French.
<p lang="fr">Ceci est un paragraphe.</p>
<section id="test" xml:lang="fr"> <title>En Français</title> <p>Ceci est un paragraphe.</p> </section>
For some people with auditory disabilities, sign language may be the primary language, and they may not read the written language fluently or at all. Here are some of the strategies to make your content accessible to them:
Use signwriting where available for the sign language of your country. For further resources see the Sutton’s SignWriting site.