Version

Date

Changes

1.0

December 14 2022

Initial WCAG

2.0

December 20 2022

Added Chapter 3, 4 and 5

Standard/Guideline

Included In Report

Web Content Accessibility Guidelines 2.0

Level A (Yes / No )

Level AA (Yes / No )

Level AAA (Yes / No )

Web Content Accessibility Guidelines 2.1

Level A (Yes / No )

Level AA (Yes / No )

Level AAA (Yes / No )

1.1.1        Non-text Content

Also applies to:

2017 Section 508*

All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except in situations listed in WCAG 2.0 1.1.1.

A

Partially Supports

• Navigation buttons are clearly labeled.
• Iconic thumbnails are accompanied by descriptive text upon hover.
• Closed-Captioning on videos can be generated when available.
• Teachers can choose appropriate assessment formats for their classes’ characteristics.
• Uploaded Images do not support Aria text for written descriptions

1.2.1 Audio-only and Video-only (Prerecorded)

Also applies to:

2017 Section 508*

All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except in situations listed in WCAG 2.0 1.1.1.

A

Partially Supports

• Closed-Captioning on videos can be generated when available.
• Teachers can choose appropriate assessment formats for their classes’ characteristics.

1.2.2 Captions (Prerecorded)

Also applies to:

2017 Section 508*

Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such.

A

Supports with Exceptions

• Closed-Captioning on videos can be generated when available.

1.2.3 Audio Description or Media Alternative (Prerecorded)

Also applies to:

2017 Section 508*

An alternative for time-based media or audio description of the prerecorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such.

A

Does Not Support

• ·        Remarks pending

1.3.1 Info and Relationships

Also applies to:

2017 Section 508*

Audio description is provided for all prerecorded video content in synchronized media.

A

Supports with Exceptions

• Design semantics allow users to establish content separation during navigation.
• Formative content is presented so that next steps are intuitive for users.
• The site’s Interfaces for user actions over dropdown, filters and other components are in direct proximity to the control mechanisms throughout the site

1.3.2 Meaningful Sequence

Also applies to:

2017 Section 508*

When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.

A

Supports

• Formative’s pages and content are sequenced to help users through an intuitive experience.
• Interactions are designed to guide users to the next intuitive steps.

1.3.3 Sensory Characteristics

Also applies to:

2017 Section 508*

Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound.

A

Supports

• Formative’s site instructions do not rely on one sensory mode. Users are presented with more than one mode of instruction across the majority of the app.

1.4.1 Use of Color 

Also applies to:

2017 Section 508*

Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

A

Supports

• Formative’s use of color to communicate meaning is accompanied by text description throughout the site.

1.4.2 Audio Control

Also applies to:

2017 Section 508*

If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently.

A

Supports with Exceptions

• Automated audio is not a feature of the site. Occasional marketing videos upon sign up, have stop/pause ability

2.1.1 Keyboard

Also applies to:

2017 Section 508*

All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints.

A

Supports

• Formative’s app can be navigated using keyboard in most part of the site
• Elements of site are navigable using the following shortcuts:

• Tab - Keyboard focus indicator present (Navigate space)
• Arrow Keys - Secondary way to navigation (interior to main element)
• Spacebar - Activate element
• Enter - Select element

2.1.2 No Keyboard Trap

Also applies to:

2017 Section 508*

If keyboard focus can be moved to a component of the page 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.

A

Supports

• Formative site does not cause a keyboard trap

2.1.4 Character Key Shortcuts

Also applies to:

2017 Section 508*

A

Supports

• No  Formative content uses only letters (including upper- and lower-case letters), punctuation, number, or symbol characters, to implement a short cut.

2.2.1 Timing Adjustable

Also applies to:

2017 Section 508*

For each time limit that is set by the content, at least one of the following is true:

– Turn off: User is allowed to turn off time limit before encountering it; or

– Adjust: The user is 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

– Extend: The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "press the space bar"), and

the user is allowed to extend the time

limit at least ten times; or

– Real-time Exception: The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or

– Essential Exception: The time limit is essential and extending it would invalidate the activity; or

– 20-Hour Exception: The time limit is

longer than 20 hours.

A

Supports

• Formative’s time limit functionality is set by teachers according to the classes’ characteristics. Teachers can adjust pause and cancel time limits.

2.2.2 Pause, Stop, Hide

Also applies to:

2017 Section 508*

For moving, blinking, scrolling, or auto-updating information, all of the following are true:

• Moving, blinking, scrolling: For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts

more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to

pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential; and

• Auto-updating: For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user

to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential.

A

Supports

• The site does not use any moving, blinking or scrolling information that starts automatically and  lasts more than five seconds

2.3.1 Three Flashes or Below Threshold

Also applies to:

2017 Section 508*

Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds.

A

Supports

• The Formative site does not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds.

2.4.1 Bypass Blocks

Also applies to:

2017 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

A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.

A

Supports

• Site allows keyboard navigation to skip repetitive component in header, Progress bar.

2.4.2 Page Titled

Also applies to:

2017 Section 508*

Web pages have titles that describe topic

or purpose.

A

Supports

• Formative site’s page titles are descriptive of the content therein.

2.4.3 Focus Order

Also applies to:

2017 Section 508*

If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.

A

Supports

• Focusable components receive focus in an order that preserves meaning and operability. Items with sequential use components tab intuitively from one step to the next.

2.4.4 Link Purpose (In Context)

Also applies to:

2017 Section 508*

The purpose of each link can be

determined from the link text alone or

from the link text together with its

programmatically determined link context,

except where the purpose of the link

would be ambiguous to users in general.

A

Supports

• The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context throughout the Formative site.

2.5.1 Pointer Gestures

A

Supports

• Formative site functionality that uses multipoint or path-based gestures for operation, can be operated with a single pointer without a path-based gesture. There are no instances where a path based gesture is essential.

2.5.2 Pointer Cancellation

A

Supports

·        For functionality that can be operated using a single pointer, there is either No Down-Event: users can Abort or Undo, perform an Up Reversal, or completing the function on the down-event is essential.

2.5.3 Label in Name

A

Supports with Exceptions

• Formative user interface components with labels that include text or images of text, the name contains the text that is presented visually, with few exceptions.

2.5.4 Motion Actuation

A

Supports with Exceptions

• Formative site functionality that can be operated by device motion or user motion can also be operated by user interface components and responding to the motion can be disabled to prevent accidental actuation, with few exceptions.

3.1.1 Language of Page

A

Supports

• Formative page language can be programmatically determined.

3.2.1 On Focus

Also applies to:

2017 Section 508

When any component receives focus, it

does not initiate a change of context.

A

Supports

• Formative’s user interface components do not initiate a change of context when they receive focus.

3.2.2 On Input

Also applies to:

2017 Section 508*

Changing the setting of any user interface

component does not automatically cause a

change of context unless the user has been

advised of the behavior before using the

component.

A

Supports

• Formative’s UI components do not change automatically with the change of context.

3.3.1 Error Identification

Also applies to:

2017 Section 508*

A

Partially Supports

• Formative’s input errors that are automatically detected, identifies the item and describes the error in text in parts of the site.

3.3.2 Labels or Instructions

Also applies to:

2017 Section 508*

Labels or instructions are provided when

content requires user input.

A

Supports

• Labels or instructions are provided when content requires user input.

4.1.1 Parsing

Also applies to:

2017 Section 508*

In content implemented using markup

languages, elements have complete start and

end tags, elements are nested according to

their specifications, elements do not contain

duplicate attributes, and any IDs are unique,

except where the specifications allow these

features.

A

Supports

• Formative’s content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features.

4.1.2 Name, Role, Value

Also applies to:

2017 Section 508*

In content implemented using markup

languages, elements have complete start and

end tags, elements are nested according to

their specifications, elements do not contain

duplicate attributes, and any IDs are unique,

except where the specifications allow these

features.

A

Partially Supports

• Formative’s UI components can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.

Criteria

Level

Conformance Level

Remarks and Explanations

1.2.4 Captions (Live)

Also applies to:

2017 Section 508*

Captions are provided for all live audio content in synchronized media.

AA

Supports with Exceptions

• Live audio content is not a feature of the app

1.2.5 Audio Description (Prerecorded)

Also applies to:

2017 Section 508*

Audio description is provided for all

prerecorded video content in synchronized

media.

AA

Does Not Support

·        Remarks pending

1.3.4 Orientation

Also applies to:

2017 Section 508*

AA

Supports

• Formative’s design aims to allow access to content on  most common screen types and orientations.

1.3.5 Identify Input Purpose

Also applies to:

2017 Section 508*

AA

Supports with Exception

• The purpose of each input field collecting information about the user can be programmatically determined.
• The content is implemented using technologies with support for identifying the expected meaning for form input data.

1.4.3 - Contrast (Minimum)

Also applies to:

2017 Section 508*

The visual presentation of text and images

of text has a contrast ratio of at least

4.5:1, except for the following:

– Large Text: Large-scale text and images

of large-scale text have a contrast ratio of

at least 3:1;

– Incidental: Text or images of text that

are part of an inactive user interface

component, that are pure decoration, that

are not visible to anyone, or that are part

of a picture that contains significant other

visual content, have no contrast

requirement.

– Logotypes: Text that is part of a logo or

brand name has no minimum contrast

requirement.

AA

Supports

• Formative’s site displays in an range of color to create appropriate contrast. The most dense colors are found in text against a background that creates suitable separation and contrast.

1.4.4 Resize Text

Also applies to:

2017 Section 508*

Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or

functionality

AA

Supports with Exceptions

• Formative’s site text can be resized in many instances with the exception of the text content item type.

1.4.5 Images of Text

Also applies to:

2017 Section 508*

If the technologies being used can achieve

the visual presentation, text is used to

convey information rather than images of

text except for the following:

– Customizable: The image of text can be

visually customized to the user's

requirements;

– Essential: A particular presentation of

text is essential to the information being

conveyed.

AA

Supports

• Formative’s design uses text, rather than images of text to convey information .

1.4.10 Reflow

Also applies to:

2017 Section 508*

AA

Supports

• Formative’s pages are designed to be responsive content and to avoid excess horizontal or vertical scrolling.
• Once the viewport hits that defined size layouts can reconfigure. For example, teacher dashboard Class cards will decrease in width as a browser windows shrinks however once the browser hits mobile width the content will stop resizing, the cards will stack.

1.4.11 Non-text Contrast

Also applies to:

2017 Section 508*

AA

Supports

• Formative’s visuals within the UI leverage the same principles of contrast for text. This includes promotional banners, menu panels, buttons icons and graphics.
• User generated content is sometimes hard to plan for and therefore our interface elements that are leveraged in proximity or on top of user content should maintain enough contrast no matter what user content is at play

1.4.12 Text Spacing

Also applies to:

2017 Section 508*

AA

Supports

• Formative's UI leverages native font spacing as much as possible.

1.4.13 Content on Hover or Focus

Also applies to:

2017 Section 508*

AA

Supports

• Hover states in most parts of the app can be dismissed by using the Keyboard Esc key

2.1.3 Keyboard (No Exceptions)

Also applies to:

2017 Section 508*

AAA

Supports

• Formative site functional content is operable through a keyboard interface without requiring specific timings for individual keystrokes.

2.4.5 Multiple Ways

Also applies to:

2017 Section 508*

More than one way is available to locate a web page within a set of web pages except where the web page is the result of, or a step in, a process.

AA

Partially Supports

• Formative’s site provides a search mechanism
• Site links pages in a sequential rationale to some extent, opportunity for additional linking between pages

2.4.6 Heading and Labels

Also applies to:

2017 Section 508

Headings and labels describe topic or purpose

AA

Supports with Exceptions

• Formative’s headings and labels describe topic or purpose consistently throughout site.

2.4.7 Focus Visible

Also applies to:

2017 Section 508*

Any keyboard operable user interface has a

mode of operation where the keyboard focus

indicator is visible.

AA

Supports with Exceptions

• Formative’s keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible, with few exceptions.

3.1.2 Language of Parts

Also applies to:

2017 Section 508*

The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the

vernacular of the immediately surrounding text.

AA

Supports with Exceptions

• Formative provides a site where the language of a  passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text. Some question type names may fall outside this rule.

3.2.3 Consistent Navigation

Also applies to:

2017 Section 508

apply to non-web docs

Navigational mechanisms that are repeated on multiple web pages within a set of web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user.

Supports

AA

Supports with Exceptions

·       Formative’s navigation patterns remain consistent across  various positions in the interface in the majority of use cases.

3.2.4 Consistent Identification

Also applies to:

2017 Section 508*

Components that have the same functionality

within a set of web pages are identified

consistently.

AA

Supports with Exceptions

·        Formative’s icons and icon labels carry the same meaning across the app. Labels are used as frequently as possible to assist with communication in contextual changes.

3.3.3 Error Suggestion

Also applies to:

2017 Section 508*

Labels or instructions are provided when

content requires user input.

AA

Partially Supports

• Formative input errors that are automatically detected and suggestions for correction are known, provide suggestions to the user, unless it would jeopardize the security or purpose of the content.

3.3.4 Error Prevention

Also applies to:

2017 Section 508*x

For web pages that cause legal

commitments or financial transactions for

the user to occur, that modify or delete

user-controllable data in data storage

systems, or that submit user test

responses, at least one of the following is

true:

1. Reversible: Submissions are reversible.

2. Checked: Data entered by the user is

checked for input errors and the user is

provided an opportunity to correct them.

3. Confirmed: A mechanism is available for

reviewing, confirming, and correcting

information before finalizing the

submission.

AA

Partially Supports

• Formative subscription plan pages prevents some errors by allowing reversals, checks and confirmations.

4.1.3 Status Messages

Also applies to:

2017 Section 508*

AA

Supports with Exceptions

• Formative’s content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus.

Criteria

Conformance Level

Remarks and Explanations

302.1 Without Vision

Supports

Formative uses standard HTML attributes to describe the identity, operation, and state of user interface elements to Assistive Technologies.

302.2 With Limited Vision

Supports

Formative supports standard browser magnification and contrast adjustments.

302.3 Without Perception of Color

Supports

Color is only used as a decorative or supplemental attribute of user interface elements. A textual representation is always used as the primary mechanism for conveying information.

302.4 Without Hearing

Does Not Support

Formative does not include support for its audio-only features that requires hearing to be used.

302.5 With Limited Hearing

Does Not Support

Formative does not provide support for its audio-only features that require hearing to be used.

302.6 Without Speech

Supports with Exception

Formative allows multiple modes of response and does not require speech only interactions

302.7 With Limited Manipulation

Supports

Formative supports standard input mechanisms such as user-provided keyboards and pointing devices. Usage of the product does not require fine motor controls nor simultaneous actions.

302.8 With Limited Reach and Strength

Not Applicable

302.9 With Limited Language, Cognitive, and Learning Abilities

Supports

Criteria

Conformance Level

Remarks and Explanations

501.1 Scope Incorporation of WCAG 2.0 AA

See WCAG 2.0 section

See information in WCAG section

502 Interoperability with Assistive Technology

502.2.1 User Control of Accessibility Features[TL1]

IS Formative a platform software

502.2.2 No Disruption of Accessibility Features

Supports

Formative is compatible with operating system and browser accessibility features configured by the user.

502.3 Accessibility Services

502.3.1 Object Information

Supports

Formative uses HTML attributes to describe the description of user interface elements to Assistive Technologies.

502.3.2 Modification of Object Information

Supports

Formative uses standard HTML object roles for maximum compatibility with assistive technologies.

502.3.3 Row, Column, and Headers

Supports

Formative uses standard HTML attributes to define table structure and relationships, including column and row headers, to Assistive Technologies.

502.3.4 Values

Supports

Formative uses standard HTML object attributes for maximum compatibility with assistive technologies.

502.3.5 Modification of Values

Supports

Formative uses standard HTML object attributes for maximum compatibility with assistive technologies.

502.3.6 Label Relationships

Supports

Formative uses standard HTML attributes to describe label relationships of user interface elements to Assistive Technologies. This includes the use of <label> attributes.

502.3.7 Hierarchical Relationships

Supports

Formative uses standard HTML markup to express hierarchical relationships.

502.3.8 Text

Supports

Formative renders strings as plain text values in HTML for maximum compatibility with assistive technologies.

502.3.9 Modification of Text

Supports

Formative renders strings as plain text values in HTML for maximum compatibility with assistive technologies.

502.3.10 List of Actions

Supports

Formative uses standard HTML object attributes for maximum compatibility with assistive technologies.

502.3.11 Actions on Objects

Supports

Formative uses standard HTML object attributes for maximum compatibility with assistive technologies.

502.3.12 Focus Cursor

Supports

Formative uses visual changes to elements to indicate the current position of focus.

502.3.13 Modification of Focus Cursor

Supports

Formative uses standard HTML elements with standard cursor controls for user input.

502.3.14 Event Notification

Supports with Exceptions

Formative has a session timeout alert to notify users when a session is about to end. Assistive technologies do not announce this message as an alert, although users may navigate via mouse or keyboard to read the message and choose to extend their session.

502.4 Platform Accessibility Features

{  }

Is Formative a platform software according to 508

503 Applications

503.2 User Preferences

Supports

Formative respects user preferences from platform or OS settings. For example, if a user enables high contrast mode, Formative user interface will display with high contrast.

503.3 Alternative User Interfaces

Not Applicable

Formative does not provide any alternative user interfaces that function as assistive technology.

503.4 User Controls for Captions and Audio Description

503.4.1 Caption Controls

Does Not Support

Formative does not provide capabilities for captioning or defining audio descriptions of user-specified video content.

503.4.2 Audio Description Controls

Does Not Support

Formative does not provide capabilities for captioning or defining audio descriptions of user-specified video content.

504 Authoring Tools

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

Not Applicable

504.2.1 Preservation of Information Provided for Accessibility in Format Conversion

Not Applicable

504.2.2 PDF Export

Not Applicable

504.3 Prompts

Not Applicable

504.4 Templates

Not Applicable