1.1.1 Non-text Content (Level A)

Also applies to:

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Supports

Drupal allows the use of alternative text.
With rare exceptions, most images that we supply provide alternative text, or descriptions, or figure captions. We may use WAI-ARIA techniques to link some complex images with their descriptions if alternative text is unable to provide adequate context..

Background images such as icons on user interface elements are generally identified with text labels. These may be visible, visually-hidden, or supplied using WAI-ARIA techniques.

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

Also applies to:

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)

• 602.3 (Support Docs)

Supports

Drupal supports a mix of multimedia content, both self-hosted and hosted on third party sites. Video-only content is generally used to support text-based content.

Audio-only content may be used to support text-based content. Audio-only content may also be used in Podcasts across various journals. Some but not all podcasts provide transcripts.

We currently have no method of confirming the inclusion - or not - of adequate media alternatives or transcripts.

1.2.2 Captions (Prerecorded) (Level A)

Also applies to:

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)

• 602.3 (Support Docs)

Supports

Drupal supports a mix of multimedia content, both self-hosted and hosted on third party sites.

Captions and/or transcripts may be provided for some pre-recorded content, but we currently have no method of confirming the inclusion - or not - of transcripts or captions.

1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)

Also applies to:

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)

• 602.3 (Support Docs)

Supports with exception

Drupal supports a mix of multimedia content, both self-hosted and hosted on third party sites.

Audio description is not generally used across our content, but some media may provide media alternatives such as text descriptions of video content.

We currently have no method of confirming the inclusion - or not - of adequate media alternatives.

1.3.1 Info and Relationships (Level A)

Also applies to:

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)

• 602.3 (Support Docs)

Supports

We generally use progressive enhancement techniques and semantically-correct markup so that information, structure, and relationships can be understood independent of presentation.

It makes use of WAI-ARIA roles to support landmarks, and use WAI-ARIA roles and properties when required for more complex functionality such as popup menus and dialogs.

Some complex functionality may omit required WAI-ARIA roles, states, or attributes, or abuse WAI-ARIA markup and techniques. We are actively work to find and repair these problems for all projects we use Drupal for.

1.3.2 Meaningful Sequence (Level A)

Also applies to:

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)

• 602.3 (Support Docs)

Supports

The meaning of the content in the pages does not depend on the order of the sections.

We use semantically-correct markup to allow assistive technologies to interpret the meaning of content and controls within each section.

1.3.3 Sensory Characteristics  (Level A)

Also applies to:

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)

• 602.3 (Support Docs)

Supports

The pages of this product do not depend solely on sensory characteristics such as shape, size, visual location, orientation, or sound to understand content.

Icons may be displayed to control functionality, but adjacent visible text labels or WAI-ARIA labels are also provided to ensure that relationships are available to Assistive Technologies.

Some complex images supplied by research authors may rely on sensory characteristics to be understood. Examples may include images of charts, graphs, or maps. Generally, these images are used to supplement text content.

1.4.1 Use of Color (Level A)

Also applies to:

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)

• 602.3 (Support Docs)

Supports
 

Colour alone is not used to convey information in the pages of this product.

Links and icons may use colour to indicate hover or active states. These are supplemented with visible focus rings and/or text decoration underlines and/or luminosity differences per WAI techniques G183 and C15.
 

1.4.2 Audio Control (Level A)

Also applies to:

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)

• 602.3 (Support Docs)

Not Evaluated

The product has not been tested or evaluated for this requirement.

2.1.1 Keyboard (Level A)

Also applies to:

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)

• 602.3 (Support Docs)

Supports with exception
 

All functionality of the product is operable through a keyboard interface without requiring specific timings for individual keystrokes.

Exception:
where the underlying function requires input that depends on the path of the user's movement and not just the endpoints.

2.1.2 No Keyboard Trap (Level A)

Also applies to:

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)

• 602.3 (Support Docs)

Supports

Keyboard traps are prevented as follows: (Level A)

(a) In the Drupal user interface: If keyboard focus can be moved to a component using a keyboard interface, then focus can be moved away from that component using only a keyboard interface and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away; and

(b) In Editing-Views that Render Content: If an editing-view renders content (e.g. WYSIWYG view), then a documented keyboard command is provided that moves the editing-view keyboard focus to a known location (e.g. the start of the editing-view).

2.2.1 Timing Adjustable (Level A)

Also applies to:

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)

• 602.3 (Support Docs)

Supports

Drupal supports authoring session time limits. When this is turned on, it can be set to automatically save web content edits made using Drupal before the session time limits are reached.

If a time limit is set by Drupal, then at least one of the following is true:

(a) Turn Off: Authors are allowed to turn off the time limit before encountering it; or

(b) Adjust: Authors are allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or

(c) Extend: Authors are warned before time expires and given at least 20 seconds to extend the time limit with a simple action (e.g. "press the space bar"), and authors are allowed to extend the time limit at least ten times; or

(d) Real-time Exception: The time limit is a required part of a real-time event (e.g. a collaborative authoring system), and no alternative to the time limit is possible;

2.2.2 Pause, Stop, Hide (Level A)

Also applies to:

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)

• 602.3 (Support Docs)

Supports

There is no moving, blinking or scrolling content that is started automatically.

There is no auto-updating information that is started automatically.

Some designs require JQuery banners that starts automatically and plays through a set of slides. Navigation controls are always added to such banners to allow the user to pause or skip between slides.

2.3.1 Three Flashes or Below Threshold (Level A)

Also applies to:

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)

• 602.3 (Support Docs)

Supports

The Drupal CMS allow developers to create web pages that do not cause the browser screen to flicker.
 

The htmLawed Module uses the htmLawed PHP library to restrict and purify HTML for compliance with site administrator policy and standards and for security. Use of the htmLawed library allows for highly customizable control of HTML markup

2.4.1 Bypass Blocks (Level A)

Also applies to:

Revised Section 508

• 501 (Web)(Software) – Does not apply to non-web software
• 504.2 (Authoring Tool)

• 602.3 (Support Docs) – Does not apply to non-web docs

Supports

The Drupal 8 UI contains a skip navigation element at the top of the editing window.  Drupal enables users to create sites and applications with skip navigation elements.
 

This allow users to skip repetitive content and jump to the next block on content.

2.4.2 Page Titled (Level A)

Also applies to:

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)

• 602.3 (Support Docs)

Supports

The default content editor in Drupal 8 is set up to allow users to add page long or short page titles which describes the purpose of each page.

2.4.3 Focus Order (Level A)

Also applies to:

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)

• 602.3 (Support Docs)

Supports

The meaning or operation of the pages on Drupal sites is generally unaffected by focus order. The focus order of all page content matches the visual order.

2.4.4 Link Purpose (In Context) (Level A)

Also applies to:

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)

• 602.3 (Support Docs)

Supports

Generally, the purpose of each link that we provide can be determined by its descriptive text label; linked images or icons have alternative text or similar to provide this context.

In research articles, anchor links that refer to same-page supplementary figures or tables may have insufficient context in their link text. Repetitive links (e.g. "show more" or "view all" type links in lists of content) may not be differentiated from each other. In limited cases we may support poor link text with the use of WAI-ARIA labels. We are actively working to repair these problems.

3.1.1 Language of Page (Level A)

Also applies to:

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)

• 602.3 (Support Docs)

Supports

Drupal 8 is built on HTML5 and so provides the lang attribute on the html element.

3.2.1 On Focus (Level A)

Also applies to:

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)

• 602.3 (Support Docs)

Supports

Components in the interface of the pages of this product that receive focus do not initiate a change of context.

3.2.2 On Input (Level A)

Also applies to:

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)

• 602.3 (Support Docs)

Supports

Changes in the value of user interface components does not result in a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window

In circumstances where changing the value of the components causes a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window, warning is given prior to the user interacting with those user-interface components

3.3.1 Error Identification (Level A)

Also applies to:

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)

• 602.3 (Support Docs)

Supports

The product was tested that for each appropriate area, at least one of the following is true:

Data is checked for input errors with an opportunity for the user to correct them.

Data can be reviewed, corrected, and confirmed by the user before they are finalized.

3.3.2 Labels or Instructions (Level A)

Also applies to:

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)

• 602.3 (Support Docs)

Supports

Labels or instructions are provided when the product requires user input.

For elements like forms, It allows for titles as well as labels for each form fields. This makes it easy for the user to understand what is required for each form field.

Also on forms, Drupal supports client side validation and alerts to show required and incomplete fields.

4.1.1 Parsing (Level A)

Also applies to:

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)

• 602.3 (Support Docs)

Supports

Drupal strictly adheres the HTML5 rules to create layout that is well structured.
Also, markup content validates to the appropriate markup specification(s).

4.1.2 Name, Role, Value (Level A)

Also applies to:

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)

• 602.3 (Support Docs)

Supports

HTML controls have a programmatically associated name, derived from the appropriate HTML elements and attributes including LABEL, TITLE, SUMMARY, CAPTION, etc.

Additional state information is programmatically exposed for HTML controls, such as whether a field is ‘required’.

Custom controls have a meaningful programatically exposed name.

1.2.4 Captions (Live) (Level AA)

Also applies to:

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)

• 602.3 (Support Docs)

Not Evaluated

The product has not been tested or evaluated for this requirement.

1.2.5 Audio Description (Prerecorded) (Level AA)

Also applies to:

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)

• 602.3 (Support Docs)

Not Evaluated

The product has not been tested or evaluated for this requirement.

1.4.3 Contrast (Minimum) (Level AA)

Also applies to:

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)

• 602.3 (Support Docs)

Supports

Drupal can be used to achieve the following scale ratio:

• Large-scale text and images of large-scale text can have a contrast ratio of at least 3:1
• All other text and images of text can have a contrast ratio of at least 4.5:1

1.4.4 Resize text (Level AA)

Also applies to:

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)

• 602.3 (Support Docs)

Supports

Drupal 8 functionality is extended with modules that allow text to be resized up to 200% without loss of content or functionality.

1.4.5 Images of Text (Level AA)

Also applies to:

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)

• 602.3 (Support Docs)

Supports

Drupal 8 CKEditor provides the full functionality required to provide detailed descriptions with text using HTML elements.

Unless explicitly required, by default text content is favored over images in Drupal Editor.

It also allows inline CSS and external CSS to be used to control text and images if used.

2.4.5 Multiple Ways (Level AA)

Also applies to:

Revised Section 508

• 501 (Web)(Software) – Does not apply to non-web software
• 504.2 (Authoring Tool)

• 602.3 (Support Docs) – Does not apply to non-web docs

Supports

The product supports internal linking of pages. Using HTML elements such as anchor tags, reference can be made to items within the same page.

With absolute and relative links, content can be linked from one page to the other.

2.4.6 Headings and Labels (Level AA)

Also applies to:

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)

• 602.3 (Support Docs)

Supports

Drupal 8 allows for labels or instructions to be provided when the section requires user input.

2.4.7 Focus Visible (Level AA)

Also applies to:

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)

• 602.3 (Support Docs)

Not Evaluated

The product has not been tested or evaluated for this requirement.

3.1.2 Language of Parts (Level AA)

Also applies to:

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)

• 602.3 (Support Docs)

Supports

Drupal 8 supports the use of HTML lang attribute to define the language for specific content blocks.

3.2.3 Consistent Navigation (Level AA)

Also applies to:

Revised Section 508

• 501 (Web)(Software) – Does not apply to non-web software
• 504.2 (Authoring Tool)

• 602.3 (Support Docs) – Does not apply to non-web docs

Supports

Drupal allows for navigational menus to be organized hierarchically. It supports navigation labelling which makes organization easily. 

3.2.4 Consistent Identification (Level AA)

Also applies to:

Revised Section 508

• 501 (Web)(Software) – Does not apply to non-web software
• 504.2 (Authoring Tool)

• 602.3 (Support Docs) – Does not apply to non-web docs

Supports

Features are consistent across the project. As an example, button and title styles are the same across.

3.3.3 Error Suggestion (Level AA)

Also applies to:

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)

• 602.3 (Support Docs)

Supports

Drupal developers can use HTML5 and ARIA techniques to suggest for fixing input errors that are known.

Errors come with text and color that highlights the affected area and states issue that happens.

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

Also applies to:

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)

• 602.3 (Support Docs)

Not Evaluated

The product has not been tested or evaluated for this requirement.

302.1 Without Vision

 Partially Supports

The majority of content is marked up for Assistive Technology. Third party scripts may inject content with inadequate accessible alternatives.

302.2 With Limited Vision

Partially Supports

Markup is written with support for assistive technology. Text is resizable by the user. Fonts are set as rems and use pixels as a fallback if not supported. The product does not impede the user from zooming into page. Third party scripts may inject content with inadequate accessibility support.

302.3 Without Perception of Color

Supports

Color perception is not needed to use this product.

302.4 Without Hearing

Partially Supports

Some but not all audio is supported by captions or transcripts.

302.5 With Limited Hearing

Partially Supports

Some but not all audio is supported by captions or transcripts.

302.6 Without Speech

Not Applicable

Speech is not needed to use this product

302.7 With Limited Manipulation

Partially Supports

This product supports standard input mechanisms such as keyboards, pointing devices, and speech input. Fine motor control and simultaneous actions are not required to operate this product. Third party scripts may inject content that is difficult to use without a pointing device.

302.8 With Limited Reach and Strength

Partially Supports

This product supports standard input mechanisms such as keyboards, pointing devices, and speech input. Third party scripts may inject content that is difficult to use without a pointing device.

302.9 With Limited Language, Cognitive, and Learning Abilities

Partially Supports

The pages of this product generally have a consistent presentation with clear labels, titles, and accessible names for controls. Third party scripts may inject content with inconsistent or absent labelling of interface components.

501.1 Scope – Incorporation of WCAG 2.0 AA

See WCAG 2.0 section

See information in WCAG section

502 Interoperability with Assistive Technology

Heading cell – no response required

Heading cell – no response required

502.2.1 User Control of Accessibility Features

Not Applicable

This product is not considered platform software as defined by Section 508.

502.2.2 No Disruption of Accessibility Features

Not Applicable

This product has no platform features as defined by Section 508. The product is compatible with operating system and browser accessibility features configured by the user.

Third party scripts may inject content that disrupts standard operating system and browser accessibility features. See information in WCAG section for complete details.

502.3 Accessibility Services

Heading cell – no response required

Heading cell – no response required

502.3.1 Object Information

Partially Supports

Object role, state(s), properties, boundary, name, and description are generally programmatically determinable.

502.3.2 Modification of Object Information

Partially Supports

The pages of this product use standard HTML or WAI-ARIA object roles for maximum compatibility with assistive technologies.

502.3.3 Row, Column, and Headers

Partially Supports

Data tables in original research or editorial content may not be marked up with adequate table header information.

Data tables in dynamic templates are rare, but where they do appear, they are marked up with standard HTML table elements. Row headers are present and associated with rows and columns as necessary.

502.3.4 Values

Supports

The pages of this product use standard HTML or WAI-ARIA object attributes for maximum compatibility with assistive technologies.

502.3.5 Modification of Values

Support

The pages of this product use standard HTML or WAI-ARIA object attributes for maximum compatibility with assistive technologies.

502.3.6 Label Relationships

Partially Supports

Generally, the pages in this product use labels on components that require user input. Some exceptions may exist.

502.3.7 Hierarchical Relationships

Partially Supports

The pages of this product generally use standard HTML to express hierarchy. Third party scripts may inject content that obscures the relationships between components.

502.3.8 Text

Supports

The pages of this product use standard plain text in HTML.

502.3.9 Modification of Text

Supports

The pages of this product use standard HTML for user input.

502.3.10 List of Actions

Supports

The pages of this product use standard HTML or WAI-ARIA object attributes for maximum compatibility with assistive technologies.

502.3.11 Actions on Objects

Partially Supports

The pages of this product use standard HTML or WAI-ARIA object attributes for maximum compatibility with assistive technologies.

Some third party scripts may inject content that cannot be interacted with easily or at all by keyboard or by some assistive technologies.

502.3.12 Focus Cursor

Partially Supports

We provide focus styles on all focusable elements. Third party scripts may inject components that remove focus styles or alter focus in a way that makes them difficult to perceive by all users.

502.3.13 Modification of Focus Cursor

Supports

The pages of this product use standard HTML elements and cursor controls for user input that may be overriden by assistive technology.

502.3.14 Event Notification

The pages of this product use standard HTML and WAI-ARIA attributes to describe the identity, operation, and state of user interface elements to Assistive Technologies.

Rarely, components may omit or misuse WAI-ARIA attributes in a way that prevents users of some Assistive Technologies from being able to percieve changes in state. We are actively working to find and repair these problems.

Some third party scripts may inject content that fails to notify users of changes in state.

See WCAG sections 1.3.1 Info and Relationships and 4.1.2 Name, Role, Value for further detail.

502.4 Platform Accessibility Features

Not Applicable

This product is not considered platform software as defined by Section 508. See E103 Definitions, section E103.4.

503 Applications

Heading cell – no response required

Heading cell – no response required

503.2 User Preferences

Supports

This product does not override user selected contrast and color selections and other individual display attributes.

503.3 Alternative User Interfaces

Not Applicable

We do not provide any alternative user interface for this product that functions as assistive technology.

503.4 User Controls for Captions and Audio Description

Heading cell – no response required

Heading cell – no response required

503.4.1 Caption Controls

503.4.2 Audio Description Controls

504 Authoring Tools

Heading cell – no response required

Heading cell – no response required

504.2 Content Creation or Editing (if not authoring tool, enter “not applicable”)

See WCAG 2.0 section

See information in WCAG section

504.2.1 Preservation of Information Provided for Accessibility in Format Conversion

Not Applicable

This product is not used as an authoring tool.

504.2.2 PDF Export

Not Applicable

This product is not used as an authoring tool.

504.3 Prompts

Not Applicable

This product is not used as an authoring tool.

504.4 Templates

Not Applicable

This product is not used as an authoring tool.