Digital Commons Voluntary Product Accessibility Template (VPAT) /Accessibility Conformance Report
Product Information and Scope
Name of Product

Digital Commons

Date Last Updated

January 26, 2023

Completed by

Jay Nemchik (Digital Accessibility Team, Dayton, OH)
Nicholas Seow (Digital Commons Consulting Services, Berkeley, CA)
Benedek Nyikos (Digital Commons Consulting Services, Berkeley, CA)

Document Description

This document rates Digital Commons according to the W3C WCAG 2.1 A and AA
requirements.

Contact for More Information

Ted Gies
Principal User Experience Specialist
ted.gies@elsevier.com
accessibility@elsevier.com
Digital Commons Consulting Services
dc-support@bepress.com

Testing Tools and Methods

Hands-on keyboard operation
Code inspection
Firefox Web Developer Toolbar (removing style sheets)
Mozilla Firefox 108 and Google Chrome 108 on Windows 10 21H2
JAWS screen reader 18
NVDA screen reader 2022.3
WAVE Extension
Color Contrast Analyzer
W3C WAI Pages
Elsevier Accessibility Checklist: http://romeo.elsevier.com/accessibility_checklist/

Document Sections

The review document below includes all WCAG 2.1 A and AA checkpoints and isorganized into 7 logical sections:• Visuals• Keyboard• Headings and Structure• Labeling• Multimedia• Usability• Mobile User Experience

Pages Covered

This VPAT outlines the compliance of the general, public-facing pages of the Digital
Commons (DC) platform:
All static pages that comprise the default DC implementation, including:• Institutional Repository (IR) Homepage• Browse Collections• Submit Research
All static pages generated with the DC template system, including:• Publication Homepageso Series/ETD series Homepage

Page 1

o Book Gallery/Image Gallery Homepageo Journal Homepage
o Event Community Homepage• Record pages (within publications)• Community Pages
All public‐facing dynamic functionality, including:• Simple/Advanced Search (Search Results)• Account Registration• My Account/Login• Edit Profile• Research Alerts
All dynamic author workflows, including:• Submission Form (submit.cgi and ir_submit.cgi—also used in revision)• Author’s View of Submission and Author Approval
Help Pages (Support Documentation):• FAQ• Search Help
• Submission Help
Page Notes

Non-main content areas generated by the Digital Commons template system thatare common to all pages—such as the Header, Footer, and Sidebar—will be noted
only for the IR Homepage so as to not repeat information. The Follow button,
readership activity map, and Slideshow/Carousel will also be noted only for the IR
Homepage. These features may be enabled for individual publications orcommunities.
Record Pages refer to individual article or record metadata pages withinpublications (series, ETD series, image galleries, book galleries, journals, and event
communities).
The Book Gallery/Image Gallery Homepage includes toggle-able grid/list index views
with thumbnail images, and a View Slideshow option.
Journal Pages include journal homepages, volume, issue, and article pages
Event Community Pages include conference/event homepages, constituent themes
and tracks (schedule pages), and individual event record pages.

Note from W3C on
Conformancehttps://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html“If there is no content to which a success criterion applies, the success criterion issatisfied.” This VPAT shows such criterion as: “Supports (N/A)”

Notes/Terminology“AT” stands for Assistive Technology such as screen readers, voice input, etc.

Page 2

WCAG 2.1 A and AA Requirements
WCAG 2.1 Success Criterion
1.1.1: Non-text Content
1.2.1: Audio-only and Video-only (Prerecorded)
1.2.2: Captions (Prerecorded)
1.2.3: Audio Description or Media Alternative
1.2.4: Captions (Live)1.2.5: Audio Description
1.3.1: Info and Relationships
1.3.2: Meaningful Sequence
1.3.3: Sensory Characteristics
1.3.4 Orientation (2.1)
1.3.5 Identify Input Purpose (2.1)
1.4.1: Use of Color
1.4.2: Audio Control
1.4.3: Contrast (Minimum)
1.4.4: Resize text
1.4.5: Images of Text
1.4.10 Reflow (2.1)
1.4.11 Non-Text Contrast (2.1)
1.4.12 Text Spacing (2.1)
1.4.13 Content on Hover or Focus (2.1)
2.1.1: Keyboard
2.1.2: No Keyboard Trap
2.1.4 Character Key Shortcuts (2.1)
2.2.1: Timing Adjustable
2.2.2: Pause, Stop, Hide
2.3.1: Three Flashes or Below Threshold
2.4.1: Bypass Blocks
2.4.2: Page Titled2.4.3: Focus Order
2.4.4: Link Purpose (In Context)
2.4.5: Multiple Ways
2.4.6: Headings and Labels
2.4.7: Focus Visible
2.5.1 Pointer Gestures (2.1)
2.5.2 Pointer Cancellation (2.1)
2.5.3 Label in Name (2.1)
2.5.4 Motion Actuation (2.1)
3.1.1: Language of Page
3.1.2: Language of Parts
Page 3

Level
A
A
A
A
AA
AA
A
A
A
AA
AA
A
A
AA
AA
AA
AA
AA
AA
AA
A
A
A
A
A
A
A
A
A
A
AA
AA
AA
A
A
A
A
A
AA

Evaluation
Partially supports
Supports (N/A)
Supports (N/A)
Supports (N/A)
Supports (N/A)
Supports (N/A)
Partially supports
Partially supports
Supports
Supports
Does not support
Supports
Supports (N/A)
Partially supports
Supports
Partially supports
Supports
Partially supports
Partially supports
Partially supports
Partially supports
Supports
Supports (N/A)
Supports (N/A)
Partially supports
Supports (N/A)
Supports
Supports
Partially supports
Partially supports
Supports
Supports
Partially supports
Supports (N/A)
Supports (N/A)
Supports
Supports (N/A)
Partially supports
Supports

WCAG 2.1 Success Criterion
3.2.1: On Focus
3.2.2: On Input
3.2.3: Consistent Navigation
3.2.4: Consistent Identification
3.3.1: Error Identification
3.3.2: Labels or Instructions
3.3.3: Error Suggestion
3.3.4: Error Prevention (Legal, Financial, Data)
4.1.1: Parsing
4.1.2: Name, Role, Value
4.1.3 Status Messages (2.1)

WCAG 2.1
Checkpoint
1.1.1: Non-Text
Content (A)Provide text
alternatives for nontext content (e.g.
images)Supporting
Features
Partially supports

Remarks

Level
A
A
AA
AA
A
A
AA
AA
A
A
AA

Evaluation
Supports
Partially supports
Supports
Supports
Partially supports
Partially supports
Supports
Supports
Supports
Partially supports
Supports (N/A)

Visuals

Some images and icons have appropriate text equivalents. Image galleries
support alternative text of images uploaded by faculty/staff through the
Description field.
Exceptions:Search Results: File type (e.g. PDF) is indicated by an image without alt
text.
IR Homepage: The DC Discipline Wheel sunburst graphic does not have alt
text. Within the readership activity map, national flag and control icons do
not have text alternatives.
Submission Form: The step-by-step background image does not haveproper alternative text.

1.3.3: Sensory
Characteristics (A)Do not rely on
sensory
characteristics ofcomponents such as
shape, size, visual
location,orientation, or
sound
1.4.1: Use of Color(A)
Color is not used as
the only visual
Page 4

Supports

There are no instructions or areas of content which rely solely on sensory
characteristics.

Supports

Color is not used as the only means of conveying information for content.

means of conveying
info
1.4.3: Color Contrast(Minimum) (AA)Text has enoughcontrast with thebackground (4.5:1
for small text and
3:1 for large text)

Partially supports

Text has enough contrast with its corresponding background in almost allareas.
Note: The Digital Commons design team customizes the visual and color
elements of IR, journal, and event community pages according to thepreferences expressed by institutions and administrators. Sufficient color
contrast is implemented as far as possible.
Exceptions:Search Results: The light gray on white background in the individual search
results does not have enough contrast at 3.54:1.
Submission Form: The green successful submission text does not haveenough contrast at 4.01:1. The red text (e.g. “Author Added”) does nothave enough contrast at 4.0:1.
Series Homepage, Book/Image Gallery Homepage: Current page indicator(greyed) on paginated publications does not have enough contrast at
2.61:1
Account registration: Password criteria check indicators do not haveenough contrast when inert at 4.47:1
Edit Profile: The red error text does not have enough contrast at 3.8:1.
Record Pages: Section titles within the PlumX Metrics popup do not haveenough contrast.

1.4.4: Resize Text
(AA)
Text can beenlarged up to 200%
without loss offunctionality.
1.4.5: Images of
Text (AA)Text is used rather
than images of text,
except where thepresentation of text
is essential, such as
logos

Supports

Text can be enlarged to 200% and content remains functional.

Partially supports

No images of text are used other than for logos or essential presentation
for almost all content.

1.4.10 Reflow(AA)
Content can bepresented without
loss of informationor functionality, andwithout requiring

Supports

Page 5

Exceptions:
Submission Form: The “Required” text is an image of text. The “Revise
Submission” and “Make Another Submission” buttons use backgroundimages of text.
A mobile-specific stylesheet supporting the reflow of content is activatedon smaller mobile devices with limited screen width.
Note: Digital Commons is not otherwise reflow-responsive and may
require horizontal scrolling for higher browser zoom levels.

scrolling in two
dimensions for:Vertical scrolling
content at a width
equivalent to 320
CSS pixels;
Horizontal scrolling
content at a heightequivalent to 256
CSS pixels.
1.4.11 Non-Text
Contrast (AA)User interface
components andgraphical objects
have a contrast ratioof at least 3:1
against adjacentcolor(s).

Partially supports

Most non-text UI components and graphical objects have at least a 3:1
contrast ratio.
Exceptions:
IR Homepage: The previous and next arrows have a light gray that is
insufficient on most common white background for the
Slideshow/Carousel (1.98:1). The Follow button’s pop up (while user is notlogged in) has a close/’X’ button with insufficient contrast at 2.84:1.
Browse Collections: The ‘+’ and ‘-‘ icons for expanding/collapsing the tree
do not have enough contrast at 2.17:1.
Submission Form: The add ‘+’ button for the Authors field does not haveenough contrast at 2.43:1.

1.4.12 Text Spacing(AA)
In content
implemented using
markup languages
that support thefollowing text styleproperties, no lossof content orfunctionality occurs
by setting all thefollowing and bychanging no otherstyle property:• Line height (linespacing) to atleast 1.5 times
the font size;• Spacingfollowing
paragraphs to atleast 2 times thefont size;• Letter spacing(tracking) to at
Page 6

Partially supports

The site allows users to adjust the text spacing without causing loss ofcontent or functionality in most areas.
Exceptions:
IR Homepage: When minimum text spacing styles are applied to thereadership activity map, record and collection information may be cut off.

least 0.12 times
the font size;• Word spacing toat least 0.16
times the fontsize.
1.4.13 Content on
Partially supports
Hover or Focus (AA)
Where receiving andthen removing
pointer hover or
keyboard focus
triggers additional
content to become
visible and thenhidden, thefollowing are true:• Dismissable• Hoverable• Persistent2.3.1: Three Flashes Supports (N/A)
or Below Threshold(A)
No more than three
flashes in a 1second period, orthe flashes are
below the defined
thresholds
WCAG 2.1
Checkpoint
1.3.2: Meaningful
Sequence (A)The correct reading
sequence can be
programmaticallydetermined

Supporting
Features
Partially supports

There is no content that appears on hover or focus on most pages.
Exceptions:
Record Pages: The PlumX Metrics popup on pointer hover cannot bedismissed by keyboard.
IR Homepage: The popup for the Digital Commons Network on pointerhover cannot be dismissed by keyboard.

No flashing content exists.

Remarks

Keyboard

The correct reading sequence is usually logical with the DOM ordermatching the visual order.
Exceptions:
IR Homepage: The Follow button, when activated while a user is notlogged in, creates a popup that does not directly come after the button in
the DOM.
Book Gallery Record Page: “Download Full Text” is after the Download
buttons in the DOM, then repositioned using CSS.

2.1.1: Keyboard (A)Partially supports
All functionality isavailable from akeyboard, except for
tasks such as
drawing

Page 7

Most content is keyboard operable.
Exceptions:
IR Homepage: Users cannot pan the readership activity map using the
keyboard. The controls for moving between recent readers/downloads
next to the map are not keyboard operable. The popup for the Digital
Commons Network cannot be activated by keyboard. Slideshow/Carouselcontrols (previous, next) cannot be reached by keyboard, as they only
appear on mouse hover.
Record Pages: The PlumX Metrics popup cannot be activated by keyboard(it only appears on pointer hover).
Submission Form: The Add Author icon cannot be reached by keyboard.
Users cannot add items to the selected list through the Discipline tree
when using a keyboard.
2.1.2: No Keyboard
Trap (A)The user can use the
keyboard to movethrough pageelements and is nottrapped on aparticular element
2.1.4 Character Key
Shortcuts (A)If a keyboard
shortcut isimplemented incontent using only
letter (including
upper- and lowercase letters),
punctuation,
number, or symbol
characters, then atleast one of thefollowing is true:• Turn off• Remap• Active only on
focus
2.4.3: Focus Order(A)
Users can tab
through theelements of a pagein a logical orderSupports

Cookies notification: Cannot be dismissed with a keyboard.
Pages do not have a keyboard trap.
Note: On the Submission Form, users cannot Shift+Tab to go back to aprevious field when focus is on a WYSIWYG Rich Text editor field.

Supports (N/A)

Partially supports

Tab order is logical on the site for the most part.
Exceptions:
IR Homepage: Users may reach visually hidden parts of the
Slideshow/Carousel. The readership activity map’s map-specific functions
should be reached after its link to the record.
Search Results: Users can reach visually hidden content and controls withthe keyboard (hidden facets, first ‘-‘ search field button while Advanced
Search is expanded). “My Saved Searches” and “Save This Search” options
are tabbed to in reverse order.
Browse Collections: Each link in the hierarchical list of collections receives
a tab stop for an expand/collapse element, regardless of its existence.

Page 8

Record Pages: Users reach the Previous and Next buttons before thebreadcrumb.
Image/Book Gallery Homepage: Users can reach the list of linked preview
images presented in the gallery’s Slideshow view without first activating
the View Slideshow link. In the Slideshow view, there are redundantPrevious and Next links. The Slideshow modal should restrict focus so thatuser focus does not go to the browser address bar.
Research Alerts: The focus order of the objects on the main part of thepage does not match their visual placement. The “Save Changes” isreached before the Saved Searches content, and “Update” “Cancel” aretabbed to in reverse order.
Submission Form: The “Remove Author” and “Show/Hide” Author buttons
are tabbed to in reverse order.
SelectedWorks Author gallery: Focus does not shift to the search facet
selection menu upon activation, so users have to tab through every profile
link in order to select a search facet.
2.4.7: Focus Visible(AA)
The page elementwith the current
keyboard focus has
a visible focus
indicator

Partially supports

Many elements use a very good visible focus.
Exceptions:
IR Homepage: The images of the Slideshow/Carousel do not have visible
focus indicators.
Browse Collections: The expand/collapse elements do not have visible
focus indicators.
Series/ETD series homepages: The optional jumplist (year/document type)element does not have a visible focus indicator.
Record Pages: The PlumX Metrics element does not have a visible focus
indicator.
Image/Book Gallery Homepage: The thumbnails for records on the index
have insufficient contrasting visible focus. The Slideshow views’ controls
do not have any visible focus indicators.
Research Alerts: The checkboxes and buttons on the page lack visible focus
indicators.
Submission Form: The ‘?’ help icon does not have a visible focus.
Cookies notification: The “use of cookies” link does not have a visible focus
indicator.
Search: The Search button and context drop-down selection in the sidebar
search section may not provide visual focus in certain web browsers.

Page 9

Search Results: While Advanced Search is expanded, Add ‘+’ search fieldbutton and “Sort By” Boolean options do not have visible focus indicators.
My Account: On legacy login screens, “Login” and “Sign Up” buttons haveno visible focus indicator.
3.2.1: On Focus (A)When a UI
component receives
focus, this does not
trigger unexpectedactions.

Supports

Focusable elements do not cause unexpected actions when receiving
focus.

WCAG 2.1
Checkpoint1.3.1: Information
and Relationships(A)
Info, structure, andrelationships can be
programmaticallydetermined

Supporting
Features
Partially supports

Remarks

Headings and Structure

Headings are used in some places to help distinguish content. Lists are
sometimes used to group related links or text.
Exceptions:
All Pages: Many pages lack an appropriate h1; the highest heading sectionlevel present may be h2.
IR Homepage: The Follow button occurs inaccurately within the precedingh2.
Browse by Discipline: The year heading (h4) on Browse Works by Discipline
page is out of sequence (should be h3).
Search Results: Search results lack list markup (results should be list items
within an unordered list). In Advanced Search options, “Sort By” Boolean
options are not encapsulated within a fieldset.
Browse Collections: Tables are used for page structure, although content
appears to be a hierarchical list/tree.
Series/ETD Series Homepage: Lists of records lack unordered list markup.
The year/document type heading (h4) is out of sequence (should be h3).
Community Page: The “Browse…” h4 is out of sequence (should be h3). A
community’s list of grouped structures should be in an unordered list.
Journal Pages: Lists of articles lack unordered list markup.
Event Community Pages: The collections list for a conference/event lacks
unordered list markup. Pages may have headings out of sequence (skipped
level). Track schedule tables lack scope attributes for table headers(scope="col/row"). Track schedule tables may have row headers that lacklabels, as event time text is hidden via CSS when the start time for an
event record is the same as the one that precedes it within a track.
Record Pages: Record title lacks heading markup in appropriate sequence.

Page 10

My Account: Table headers lack scope attributes. The left column lacks
row headers with scope="row" attributes.
Edit Profile: Tables are used for page structure; “About You” is a tablecaption rather than a heading.
Submission Form: The headings for each form input section (e.g. “Title”,“Authors”, etc.) lack heading markup (h3). The left column of row headers
for the submission metadata summary lacks scope="row" attributes.
Author’s View of Submission: “Current File(s)” is out of sequence (orshould not be a heading).
2.4.1: Bypass Blocks(A)
Users can bypass
repeated blocks ofcontent.
2.4.6: Headings andLabels (AA)
Headings and labels
are clear andconsistent.
3.1.1: Language ofPage (A)The language of thepage is specified

Supports

Headings exist, which allow users using Assistive Technology to jump to
the different areas of content quickly. Various ARIA landmarks are used to
identify page regions. Every page has a “Skip to Main Content” skip link.

Supports

Headings and labels used are clear and descriptive.
For example, each of the h2s on the homepage describes clearly what
content will follow.

Partially supports

The language of most pages is specified as lang="en".
Exceptions:
Submission Form, Account Registration, My Account, Research Alerts: nolanguage specified for these pages.

3.1.2: Language of
Supports
Parts (AA)Specify the languageof text passages thatare in a different
language than thedefault language ofthe page.

There are no sections of content that are in a different language than thedefault.

4.1.1: Parsing (A)Use valid, error-free
HTML

Most HTML and CSS passes concerning these 4 specific criteria:(i) elements have complete start and end tags,(ii) elements are nested according to their specifications(iii) elements do not contain duplicate attributes(iv) any IDs are unique, except where the specifications allow thesefeatures.

Supports

Note: Some sections of pages may contain content generated byauthors/administrators that is not in English (the default specified
language for most pages). Many editable sections allow administrators tomark changes in language. However, it is not possible to specify thelanguage of non-English text in metadata fields on record pages.

Note: There are other general HTML validation errors outside the scope of
this criterion.
WCAG 2.1
Checkpoint
Page 11

Supporting
Features

Remarks

Labeling

1.3.5 Identify Input
Does not support
Purpose (AA)The purpose of each
input field collecting
information about
the user can be
programmaticallydetermined when:
The input field
serves a purpose
identified in the
Input Purposes forUser Interface
Components
section; and thecontent is
implemented using
technologies withsupport for
identifying the
expected meaning
for form input data.
2.4.2: Page Titled (A) Supports
The page has a title
describing its topic
or purpose
2.4.4: Link Purpose
Partially supports(In Context) (A)The purpose of eachlink can be
determined fromthe link text orsurrounding
context.

The only pages with personal input fields are Edit Profile, AccountRegistration, and Submission Form. These fields lack autocomplete
attributes.

2.5.3 Label in Name(A)For user interface
components withlabels that include
text or images oftext, the namecontains the textthat is presented
visually.
3.2.4: Consistent
Identification (AA)UI components used
across the web site
are identified

Supports

User interface components that have visible text contain that text
consistently within the accessible name.

Supports

UI components within each resource are labelled consistently.

Page 12

Edit Profile: Personal information fields do not have autocomplete
attributes.
Account Registration: Personal information fields do not haveautocomplete attributes.
Submission Form: The “About you…” input fields do not haveautocomplete attributes.

All pages use unique and descriptive page titles.

Most links used have an identifiable purpose from the link text orsurrounding context.
Exceptions:
IR Homepage: The “View Larger” and “</> Embed” links for the readership
activity map are not specific about their purpose.

consistently on
every page.
3.3.1: Error
Identification (A)Input errors areclearly marked anddescribed to theuser.

Partially supports

Errors are displayed to the user and presented with a summary.
Note: On the Submission Form, Edit Profile, and legacy AccountRegistration form, error summaries are presented in text toward the
beginning of the page after form submission—and visually distinguished
via different text and/or background colors. On Account Registration, error
messages are presented in text below each associated input (except for
password fields). Error states are not programmatically announced to AT,
nor is focus management used for convenient error indication.
Exceptions:
Account Registration: Password criteria check indicators are visible, but
are hidden from AT via aria-hidden="true". Entering a password with too
few characters may lead to incorrect error message on the legacy accountregistration form.
Search: Performing a search from the sidebar with no value leads to an
empty search results page, without any indication that a search term isrequired.

3.3.2: Labels andInstructions (A)Items requiring user
input are clearlylabeled or haveclear instructions.

Partially supports

Most input areas have clear labels which are programmatically assigned.
Exceptions:Search: The label for the context drop-down selection in the sidebar
search section is hidden with CSS, which also hides it from AT.
Search Results: The search input label is hidden with CSS, which also hides
it from AT.
Account Registration: Form fields lack labels on the legacy accountregistration form.
Edit Profile: Current Password and New Password lack labels for theirrespective inputs.
My Account: The Upload Document drop-down menu lacks labels.
Research Alerts: The checkboxes in the My Saved Searches have hidden
labels (via CSS). The Alerts checkbox lacks a sufficiently descriptive label.
Submission Form: The Submission Agreement checkbox is not labelled.
Required inputs lack the required or aria-required="true" attributes.
Several inputs have labels hidden via CSS, which makes them inaccessible
to AT, such as the author search and author details inputs. The author
ordering inputs do not have any labels. The keywords field lacks an ariadescribed by description of how to add keywords (the instructions appear
only as text before the input). The "for" attribute for the “Import file fromremote site” label does not reference the proper input ID. Radio inputs(e.g. Publication Status) may lack a group label. Checkbox inputs (e.g.

Page 13

Additional Files) may lack a proper label: adjacent label text may notreference the proper input ID.
3.3.3: Error
Suggestion (AA)When the user
makes an input
error, givesuggestions for valid
input.
4.1.2: Name, Role,
Value (A)For all UI
components, thename, value, androle can be
programmaticallydetermined.

Supports

There is no content that would give error suggestions.

Partially supports

Most UI components communicate their state programmatically.
Exceptions:
IR Homepage: The Previous and Next buttons for the slideshow are not<button> elements (or lack role="button").
Search Results: Links that cause same-page content changes are not<button> elements (or lack role="button"), such as the More/Fewer
toggles, and search facet selection and removal. The search facet removal‘X’ button does not include "remove" in the button label.
Browse Collections: The Expand/Collapse elements are not implemented
as buttons, and lack accessible names.
Image/Book Gallery Homepage: The Slideshow modal lacks role="dialog"
and aria-modal="true". View Slideshow and its controls are not
implemented as <button> elements (or lack role="button").
Submission Form: The “Add author”, “Remove author” and “Show/hide
details” buttons are not <button> elements (or lack role="button"). The“Show/Hide details” button label lacks an appropriate label (which shouldbe “Edit author”), and the aria-expanded="true/false" attribute. The
Disciplines taxonomy is not clearly communicated to AT; the Discipline
tree does not use ARIA 1.1 Authoring Practices for Treeviews. While
toolbar buttons within the Rich Text editor have aria-labelledby attributes,
the attributes reference <span> elements that are hidden with CSS,
potentially causing them to not be interpreted by AT. On the submission
confirmation screen, the “Revise Submission” and “Make AnotherSubmission” button labels use hidden text with CSS, which makes theminaccessible to AT.
SelectedWorks Author Gallery: “View more” links within the search facet
selection menu do not contain href attributes.

4.1.3 Status
Messages (AA)In content
implemented using
markup languages,
status messages canbe programmatically
Page 14

Supports (N/A)

There are no status messages of the kind described by this criterion on
Digital Commons.

determined throughrole or properties
such that they canbe presented to theuser by assistive
technologies
without receiving
focus.
WCAG 2.1
Checkpoint1.2.1: Audio-only orVideo-only(Prerecorded) (A)Provide alternatives
for pre-recorded
audio-only or videoonly content.

1.2.2: Captions(Prerecorded) (A)Provide captions for
pre-recorded audio

Supporting
Features
Supports (N/A)

Multimedia

Remarks

Digital Commons utilizes JW Player, which supports multiple audio tracks,
for its native streaming capability. (Embedded multimedia hosted on
external sources may also utilize JW Player.) For instance, one track may
contain an audio description to accompany video content. Other
alternatives, such as transcripts, may be uploaded as supplemental files on
the same record, and/or included within the record metadata.
Commonly embedded third-party streaming content platforms (e.g.
YouTube) may provide similar alternatives.

Supports (N/A)

Note: Audio and Video content is generated by authors and not by Digital
Commons. Authors/administrators may provide, and are responsible for,alternatives to Audio and Video content.
Digital Commons utilizes JW Player, which supports closed captioning, for
its native streaming capability. (Embedded multimedia hosted on externalsources may also utilize JW Player.)
Commonly embedded third-party streaming content platforms (e.g.
YouTube) may provide closed captioning or other alternatives.
Note: Audio and Video content is generated by authors and not by Digital
Commons. Authors/administrators may provide, and are responsible for,alternatives (e.g. closed captioning) to Audio and Video content.

1.2.3: Audio
Description orMedia Alternative(Prerecorded) (A)Provide alternatives
for pre-recorded
synchronizedaudio/video

Supports (N/A)

Digital Commons utilizes JW Player, which supports multiple audio tracks,
for its native streaming capability. (Embedded multimedia hosted on
external sources may also utilize JW Player.) Digital Commons also
supports uploading a separate video including an audio description (e.g. an
extended audio-described video) as a supplemental file on the same
record. Other alternatives, such as transcripts, may be uploaded as
supplemental files on the same record, and/or included within the record
metadata.
Digital Commons allows linking to external sources on third-party content
platforms (e.g. YouTube) that may provide audio-described tracks or otheralternatives.
Note: Audio and Video content is generated by authors and not by Digital
Commons. Authors/administrators may provide, and are responsible for,audio descriptions or media alternatives to Audio and Video content.

Page 15

1.2.4: Captions(Live) (AA)Provide captions forlive audio in
synchronizedaudio/video.
1.2.5: Audio
Description(Prerecorded) (AA)Provide an audio
description of prerecorded video.

Supports (N/A)

There is no live audio in synchronized audio/video.

Supports (N/A)

Digital Commons utilizes JW Player, which supports multiple audio tracks,
for its native streaming capability. (Embedded multimedia hosted on
external sources may also utilize JW Player.) Digital Commons also
supports uploading a separate video including an audio description (e.g. an
extended audio-described video) as a supplemental file on the same
record.
Digital Commons allows linking to external sources on third-party content
platforms (e.g. YouTube) that may provide audio-described tracks.
Note: Audio and Video content is generated by authors and not by Digital
Commons. Authors/administrators may provide, and are responsible for,audio descriptions or media alternatives to Audio and Video content.

1.4.2: Audio Control(A)
Audio can bepaused andstopped, or theaudio volume canbe changed.
2.2.2: Pause, Stop,
Hide (A)Users can stop,pause, or hide
moving, blinking,scrolling, or autoupdating
information.

Supports (N/A)

There is no audio that plays automatically on the site.

Partially supports

Most pages do not use any moving, blinking, scrolling or auto-updating
information.

WCAG 2.1
Checkpoint
2.2.1: Timing
Adjustable (A)Users are warned oftime limits shorter
than 20 hours andtime limits can beturned off or
extended
2.4.5: Multiple Ways(AA)
More than one way
is available toSupporting
Features
Supports (N/A)

Remarks

Supports

All pages can be accessed in multiple ways. For example, main navigation
links appear on both the navigation tab and footer. There is also searchfunctionality for finding specific pages.

Page 16

Exceptions:
IR Homepage: The Slideshow/Carousel does not have controls to allow it
to stop, pause, or hide. The readership activity map, which auto-updates,
does not have pause control until the first reader is presented.

Usability

There is no session timeout.

navigate to otherweb pages.
3.2.2: On Input (A)Changing the settingof a checkbox, radio
button, or other UI
component does
not trigger
unexpected changes
in context.
3.2.3: Consistent
Navigation (AA)Navigation menus
are in the same
location and orderon every web page.

Partially supports

Exceptions:
Submission Form: Pressing Enter after keyboard selection of a saved form
value will cause the entire form to be submitted, instead of selecting thevalue within the field.
Series Homepage: Arrow key navigation of jumplists (year/document type)brings a user to an anchor heading as soon as an option is selected.
Supports

3.3.4: Error
Supports
Prevention (Legal,
Financial, Data) (AA)For web pages withlegal or financial
commitments, input
can be reviewed andcorrected before
final submission,and submissions canbe reverted.
WCAG 2.1
Checkpoint
1.3.4 Orientation(AA) Content does
not restrict its view
and operation to asingle display
orientation, such as
portrait orlandscape, unless a
specific display
orientation isessential.
2.5.1 Pointer
Gestures (A) All
functionality thatuses multipoint or
path-based gestures
for operation can be
operated with aPage 17

Most user inputs do not cause unexpected actions.

Navigation menus are consistent across most pages. Main navigation links
in the header, navigation tab, and footer are consistent across pages.
Note: Navigation links may be customized for individual journals and event
communities, and may appear in a different order than the IR homepage’s
defaults. Links in the Author Corner sidebar section may depend on
options configured for each publication.
There are no submissions which require legal or financial commitments.

Mobile User Experience

Supporting
Features
Supports

Remarks

Supports (N/A)

Digital Commons does not use any multipoint or path-based gestures.

Digital Commons does not restrict its view to a single orientation.

single pointerwithout a pathbased gesture,unless a multipoint
or path-based
gesture is essential.
2.5.2 PointerCancellation (A)For functionalitythat can be
operated using asingle pointer, atleast one of thefollowing is true:• No Down-Event• Abort or Undo
• Up Reversal• Essential
2.5.4 Motion
Actuation (A)Functionality thatcan be operated bydevice motion oruser motion canalso be operated byuser interface
components andresponding to the
motion can bedisabled to prevent
accidental
actuation, except
when:• Supported
Interface• Essential

Page 18

Supports (N/A)

All interactive content functions through the Up-Event, allowing users topotentially move their pointer off the component to cancel.

Supports (N/A)

There is no content on Digital Commons that utilizes device or user
motion.

US 508 Chapter 3: Functional Performance Criteria
Criteria

Conformance
Level
Partially
supports

302.1 Without Vision

Supports
302.2 With Limited Vision

302.3 Without Perceptionof Color

Partially
supports
Supports

302.4 Without Hearing

302.5 With Limited
Hearing302.7 With Limited
Manipulation
302.8 With Limited Reach
and Strength
302.9 With Limited
Language, Cognitive, andLearning Abilities
Page 19

Digital Commons’ user interface and content is mostly accessible
with screen readers. There are a few instances of missing alt text
and incomplete keyboard support. PDFs may have Digital Commons
cover pages that are properly tagged; authors/administrators are
responsible for tagging PDF content. Authors/administrators are
responsible for including alternative text within the description field
for content figures. Authors/administrators are responsible forproviding downloadable media alternative as text equivalents forvideo content.
Style sheets separate presentation from content. Personal style
sheets and Operating System contrast can be applied. Browser
Zoom and Screen magnification applications are supported. Digital
Commons does not have a responsive design and may require
horizontal scrolling for higher browser zoom levels. A mobilespecific stylesheet is activated on smaller mobile devices withlimited screen width.
Digital Commons does not require perception of color to use almost
all content. Some exceptions exist in a few instances, such as linkcolor not sufficiently contrasting with surrounding text.
There is no content in Digital Commons that requires hearing. Audioand Video content is generated by authors. Authors/administrators
may provide alternatives (e.g. closed captioning or supplemental
transcripts) to Audio-only and Video-only content.
Digital Commons utilizes JW Player, which supports closed
captioning, for its native streaming capability. Commonly embedded
third-party streaming content platforms (e.g. YouTube) may provide
closed captioning or other alternatives.

Supports

302.6 Without Speech

Remarks and Explanations

There is no content in Digital Commons that requires hearing. Audioand Video content is generated by authors. Authors/administrators
may provide alternatives (e.g. closed captioning or supplemental
transcripts) to Audio-only and Video-only content.
Independent volume control is provided in the JW media player andon commonly embedded 3rd party streaming platforms.

Supports
Partially
supports
Supports (N/A)
Supports

There is no content in Digital Commons that requires speech input.
Digital Commons provides labels to make form controls easier toselect. Most elements have accessible names and can be operatedusing speech input.
Does not apply.
Digital Commons offers compatibility with text to speech literacy
programs (e.g. Read and Write Gold).

US 508 Chapter 6: Support Documentation and Services
Criteria
601.1 Scope
602 Support
Documentation

Conformance
Level
Heading cell – noresponse
required
Heading cell – noresponse
required602.2 Accessibility andCompatibility Features

Supports

602.3 Electronic Support
Documentation

Partially
supports

602.4 Alternate Formats
for Non-Electronic Support
Documentation

Supports

603 Support Services

Heading cell – noresponse
required603.2 Information on
Accessibility andCompatibility Features

Supports

603.3 Accommodation ofCommunication Needs

Supports

Page 20

Remarks and Explanations
Heading cell – no response required
Heading cell – no response required
Details on Digital Commons accessibility and compatibility features
are found on the Accessibility Statement page:https://bepress.com/accessibility-statement/. The Accessibility
Statement is linked to from the footer of Digital Commons sites.
This document (VPAT) provides additional details on the accessibility
and compatibility features of Digital Commons.
See information in next section.
All forms of support documentation are electronic. Please contact
Digital Commons Consulting Services (dc-support@bepress.com) torequest alternate formats for documentation or for any additionalquestions on accessibility and assistive technology compatibility
features.
Heading cell – no response required
This document (VPAT) describes information on the accessibility andcompatibility features.
The Digital Commons Accessibility Statement, with a description ofaccessibility features, is available at:https://bepress.com/accessibility-statement/. The Accessibility
Statement is linked to from the footer of Digital Commons sites.
Users may contact Digital Commons Consulting Services for support
via• Email: dc-support@bepress.com• Phone: +1 (510) 665-1200 ext. 2.

WCAG 2.1 Success Criterion

602.3 Electronic Support Documentation
Level

Evaluation

RemarksA

Supports

No non-text content on support pages.

1.2.1: Audio-only and Video-only (Prerecorded)A

Supports (N/A)

No multimedia on support pages.

1.2.2: Captions (Prerecorded)A

Supports (N/A)

No multimedia on support pages.

1.2.3: Audio Description or Media AlternativeA

Supports (N/A)

No multimedia on support pages.

1.2.4: Captions (Live)AA

Supports (N/A)

No multimedia on support pages.

1.2.5: Audio Description

AA

Supports (N/A)

No multimedia on support pages.

1.3.1: Info and Relationships

A

Partially supports

Support pages are missing h1s.

1.3.2: Meaningful SequenceA

Supports

Screen reader reading sequence is logical.

1.3.3: Sensory Characteristics

A

Supports

Content does not rely on sensory characteristics.

1.3.4: Orientation (2.1)

AA

Supports

Display orientation is not fixed.

1.3.5: Identify Input Purpose (2.1)

AA

Supports (N/A)

No input fields on support pages.

1.4.1: Use of ColorA

Supports

No elements rely on color alone to convey
information.

1.4.2: Audio Control

A

Supports (N/A)

No auto-playing audio exists.

1.4.3: Contrast (Minimum)AA

Supports

All text passes minimum 4.5:1 ratio.

1.4.4: Resize text

AA

Supports

Text can be enlarged to 200% without loss offunctionality.

1.4.5: Images of Text

AA

Supports

No images of text are on support pages.

1.4.10: Reflow (2.1)

AA

Supports

Digital Commons has an adaptive view for small
screens.

1.4.11: Non-Text Contrast (2.1)

AA

Supports (N/A)

There are no icons or elements that are non-text.

Supports

Minimum text spacing styles can be applied
without error.

1.1.1: Non-text Content

1.4.12: Text Spacing (2.1)

AA

1.4.13: Content on Hover or Focus (2.1)

AA

Supports (N/A)

No content has hover or focus popups.

2.1.1: Keyboard

A

Supports

All elements can be reached and activated by
keyboard.

2.1.2: No Keyboard Trap

A

Supports

No keyboard traps exist.

2.1.4: Character Key Shortcuts (2.1)

A

Supports (N/A)

There are no custom key shortcuts using one
character key.

2.2.1: Timing Adjustable

A

Supports

There is no session timeout.

2.2.2: Pause, Stop, HideA

Supports (N/A)

No elements on supports pages are moving orchanging.

2.3.1: Three Flashes or Below Threshold

A

Supports (N/A)

There is no flashing content.

2.4.1: Bypass Blocks

A

Supports

Several means of skipping content exist.

2.4.2: Page TitledA

Supports

All support pages have descriptive and uniquetitles.

2.4.3: Focus OrderA

Supports

Tab order on support pages is logical.

2.4.4: Link Purpose (In Context)

A

Supports

Link text is clear and descriptive.

2.4.5: Multiple WaysAA

Supports

There are multiple ways to reach all content.

2.4.6: Headings and LabelsAA

Supports

All headings and labels are descriptive andconsistent.

2.4.7: Focus Visible

AA

Supports

All elements have a visible focus.

2.5.1: Pointer Gestures (2.1)

A

Supports (N/A)

No content requires pointer gestures.

2.5.2: Pointer Cancellation (2.1)

A

Supports

All actions can be cancelled properly.

Page 21

WCAG 2.1 Success Criterion

Level

Evaluation

Remarks

2.5.3: Label in Name (2.1)

A

Supports

Visible labels appear in the accessible names forelements.

2.5.4: Motion Actuation (2.1)

A

Supports (N/A)

Nothing requires device motion.

3.1.1: Language of Page

A

Supports

All support pages have a defined page language.

3.1.2: Language of Parts

AA

Supports (N/A)

No areas use a language different from thedefault.

3.2.1: On Focus

A

3.2.2: On Input

A

3.2.3: Consistent Navigation

AA

3.2.4: Consistent IdentificationAA

3.3.1: Error Identification

Supports

No unexpected changes happen when receiving
focus.

Supports

No unexpected changes when changing input
settings.

Supports

All navigation menus are consistent across thesite.

Supports

All UI elements are labelled and usedconsistently.

A

Supports (N/A)

Support pages do not have input fields or errors.

3.3.2: Labels or Instructions

A

Supports (N/A)

Support pages do not have input fields.

3.3.3: Error SuggestionAA

Supports (N/A)

Error text that appears are sufficient suggestions.

3.3.4: Error Prevention (Legal, Financial, Data)AA

Supports (N/A)

No submission requires legal or financial
commitments.

4.1.1: Parsing

A

Supports

No duplicate IDs or other parsing errors occur.

4.1.2: Name, Role, ValueA

Supports

Native HTML is always used, labels and roles areaccurate.

4.1.3: Status Messages (2.1)

AA

Supports (N/A)

No status messages are on the site.

Page 22

•
•

•

•
•

Page 23

Version History

1/26/2023
o Notes: Updated evaluation and various noted exceptions based on remediation efforts, particularly for2.4.4.
6/30/2021
o Authors: Jay Nemchik, Nicholas Seow, Benedek Nyikoso Notes: Added 12 WCAG 2.1 A/AA criteria evaluations. Added sections for Chapter 3: Functional
Performance Criteria, Chapter 6: Support Documentation and Services, 602.3 Electronic Support
Documentation. Updated evaluation and various noted exceptions based on remediation efforts.
Revised 2.1.2 to “Supports” as in the noted instance, focus may still be moved away from the element.
Revised 3.1.2 to “Supports” to reflect the default state of compliance, and users’ responsibility forspecifying language of user-editable sections as appropriate.
8/29/2019o Authors: Jay Nemchik, Nicholas Seow, Benedek Nyikoso Notes: Digital Commons ceased release numbering; this document assessed the current production
release at the time of publication according to 38 WCAG 2.0 A/AA criteria. Clarified scope of pages andfunctionality covered by evaluation. Updated evaluation and various noted exceptions based on
remediation efforts.
2/14/2014
o Authors: William Wong, Allen Spragueo Notes: Assessed Digital Commons version 7.10
6/24/2011, 5/28/2010, 1/15/2010, 4/2/2008
o Author: Samira Vijgheno Notes: Assessed Digital Commons versions 6.11, 6.8, 6.7, 5.9