We're here to help

Articles in this section

See more

Bridge Voluntary Product Accessibility Template Follow

Avatar
Nikki Bodily
  • Updated

Web Content Accessibility Guidelines 2.1

This Voluntary Product Accessibility Template, or VPAT, is a tool that administrators and decision-makers can use to evaluate Bridge's conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 (w3.org), Level AA. This VPAT applies only to the Employee and Manager roles within Bridge.
The subject of the VPAT is the Bridge product as a “framework” thus, the content (e.g.: courses, programs, customer-specific branding, logos, animations, etc.) is out of the scope of this audit because it is the authors’ and admins’ responsibility to make them accessible.

Principle 1: Perceivable
Information and user interface component must be presentable to users in ways they can perceive.

 

GUIDELINE 1.1 TEXT ALTERNATIVES

PROVIDE TEXT ALTERNATIVES FOR ANY NON-TEXT CONTENT SO THAT IT CAN BE CHANGED INTO OTHER FORMS PEOPLE NEED, SUCH AS LARGE PRINT, BRAILLE, SPEECH, SYMBOLS OR SIMPLER LANGUAGE.

CRITERIA
 SUPPORTING FEATURES
 REMARKS AND EXPLANATIONS
1.1.1 Non-text Content: All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below. (Level A)
 Supports
 Bridge has the functionality to provide text alternatives for the images that are used with a learning item. It is an author's responsibility to include this.

 

GUIDELINE 1.2 TIME BASED MEDIA

PROVIDE ALTERNATIVES FOR TIME-BASED MEDIA.

CRITERIA SUPPORTING FEATURES REMARKS AND EXPLANATIONS
1.2.1 Audio-only and Video-only (Prerecorded): For prerecorded audio-only and prerecorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labeled as such: (Level A)

● Prerecorded Audio-only: An alternative for time-based media is provided that presents equivalent information for prerecorded audio-only content.
● Prerecorded Video-only: Either an alternative for time-based media or an audio track is provided that presents equivalent information for prerecorded video-only content.
 Supports Bridge has the functionality to provide text alternatives for prerecorded audio-only and video-only content that are used with a learning item. It is an author's responsibility to create and include these.
1.2.2 Captions (Prerecorded): 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. (Level A) Supports The intent of this success criterion is to enable people who are deaf or hard of hearing to watch synchronized media presentations. Captions provide the part of the content available via the audio track. Captions not only include dialogue but identify who is speaking and include non-speech information conveyed through sound, including meaningful sound effects.
1.2.3 Audio Description or Media Alternative (Prerecorded): 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. (Level A) Supports The intent of this success criterion is to provide people who are blind or visually impaired access to the visual information in a synchronized media presentation. This success criterion describes two approaches, either of which can be used
Bridge has the functionality to provide text alternatives for the media but the author is responsible for providing these.
1.2.4 Captions (Live): Captions are provided for all live audio content in synchronized media. (Level AA) Not Applicable
1.2.5 Audio Description (Prerecorded): Audio description is provided for all prerecorded video content in synchronized media. (Level AA) Supports Bridge has the functionality to provide meaningful captions but the author is responsible for providing them.

 

GUIDELINE 1.3 ADAPTABLE

CREATE CONTENT THAT CAN BE PRESENTED IN DIFFERENT WAYS (FOR EXAMPLE: SIMPLER LAYOUT) WITHOUT LOSING INFORMATION OR STRUCTURE.

CRITERIA
 SUPPORTING FEATURES
 REMARKS AND EXPLANATIONS
1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A)
 Does not support
1.3.2 Meaningful Sequence: When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. (Level A)
 Does not support
 When viewing the pages at 200% magnification, the menu bar appears below the main content. The menu bar receives the focus first, then the main content, which is located above it. This is inconsistent with the general top-to-bottom reading paradigm.
1.3.3 Sensory Characteristics: 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. (Level A)
 Does not support
 All major icons are explained but some are purely cosmetic and require no action from a user's perspective. These cosmetic icons may not be explained properly.
1.3.4 Orientation: Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation
is essential. (Level AA)
 Does not support
 Bridge does not fully support this requirement because there are a few places where Bridge uses a horizontal scrollbar, which could make the navigation a bit inconvenient.
1.3.5 Identify Input Purpose: The purpose of each input field collecting information about the user can be programmatically determined when (Level AA):

● The input field serves a purpose identified in
the Input Purposes for User Interface Components section; and
● The content is implemented using technologies with support for identifying the expected meaning for form input data.
 Not applicable

 

GUIDELINE 1.4 DISTINGUISHABLE

MAKE IT EASIER FOR USERS TO SEE AND HEAR CONTENT INCLUDING SEPARATING FOREGROUND FROM BACKGROUND.

CRITERIA SUPPORTING FEATURES REMARKS AND EXPLANATIONS
1.4.1 Use of Color: Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. (Level A) Does not support
            
                                                            

There are a few places within Bridge Perform where links appear in the text and are only identified by color. 

                       

All links within Bridge Learn are identifiable via color and are underlined. 

                                               
        
1.4.2 Audio Control: 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 from the overall system volume level. (Level A) Not applicable

1.4.3 Contrast (Minimum): The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following: (Level AA)

 ● 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 contrast requirement.


 Does not support
1.4.4 Resize text: Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality. (Level AA) Does not support This success criterion defines, if the built-in magnification function of the browser is used up to 200 percent, the text can be read conveniently without using the horizontal scrollbar.

1.4.5 Images of Text: 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: (Level AA)

● 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.
Supports		 Bridge has the functionality to provide text alternatives for images that are used in the learning item. It is the author's responsibility to fill it out properly.

1.4.10 Reflow: Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for (Level AA):

● Vertical scrolling content at a width equivalent to
320 CSS pixels;
● Horizontal scrolling content at a height equivalent to
256 CSS pixels.


Except for parts of the content which require two-dimensional layout for usage or meaning.
 Does not support
 Bridge does not fully support this requirement because there are a few places where Bridge uses a horizontal scrollbar, which could make the navigation a bit inconvenient.

1.4.11 Non-text Contrast: The visual presentation of the following have a contrast ratio of at least 3:1 against adjacent colour(s) (Level AA):

● User Interface Components:
Visual information required to
identify user interface components and st ates, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author;
● Graphical Objects: Parts of graphics required to understand the content, except when a particular presentation of graphics
is essential to the information being conveyed.

 Does not support

1.4.12 Text Spacing: In content implemented using markup languages that support the following text style properties, no loss of content or functionality occurs by setting all of the following and by changing no other style property (Level AA):

● Line height (line spacing) to at least 1.5 times the font size;
● Spacing following paragraphs to at least 2 times the font size;

● Letter spacing (tracking) to at least 0.12 times the font size;

● Word spacing to at least 0.16 times the font size


 Supports
 Supports due to the responsive template.

1.4.13 Content on Hover or Focus: Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true (Level AA):

● Dismissable:
A mechanism is available to dismiss the additional content without moving pointer hover or keyboard focus, unless the additional content communicates an input error or does not obscure or replace other content;
● Hoverable: If pointer hover can trigger the additional content, then the pointer can be moved over the additional content without the additional content disappearing;

● Persistent: The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid.

 Supports

 

 

Principle 2: Operable
User interface components and navigation must be operable.

 

GUIDELINE 2.1 KEYBOARD ACCESSIBLE

MAKE ALL FUNCTIONALITY AVAILABLE FROM A KEYBOARD.

CRITERIA
 SUPPORTING FEATURES
 REMARKS AND EXPLANATIONS
2.1.1 Keyboard: 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. (Level A)
 Does not support
Bridge Learn fully supports this criteria. Perform and Career partially support this criteria.
2.1.2 No Keyboard Trap: 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 of the method for moving focus away. (Level A)
 Does not support
 Bridge strives to ensure that all elements can be entered and left via the use of a keyboard.

2.1.4 Character Key Shortcuts: If
a keyboard shortcut is implemented in content using only letter (including upper- and lower-case letters), punctuation, number, or symbol characters, then at least one of the following is true (Level A):

● Turn off: A mechanism is available to turn the shortcut off;
● Remap: A mechanism is available to remap the shortcut to use one or more non-printable keyboard characters (e.g., Ctrl, Alt, etc);

● Active only on focus: The keyboard shortcut for
a user interface component is only active when that component has focus.


 Not applicable
 Bridge does not have the functionality of using shortcuts.

 

GUIDELINE 2.2 ENOUGH TIME

PROVIDE USERS ENOUGH TIME TO READ AND USE CONTENT.

CRITERIA
 SUPPORTING FEATURES
 REMARKS AND EXPLANATIONS

2.2.1 Timing Adjustable: For each time limit that is set by the content, at least one of the following is true: (Level A)

● Turn off: The user is allowed to turn off the 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.

 Not applicable

2.2.2 Pause, Stop, Hide: For moving, blinking, scrolling, or auto-updating information, all of the following are true: (Level A)

● 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.

 Does  not support
 Preloaders are included within Bridge that include animations as page content loads. Bridge does not include other animations.

 

GUIDELINE 2.3 SEIZURES

DO NOT DESIGN CONTENT IN A WAY THAT IS KNOW TO CAUSE SEIZURES.

CRITERIA
 SUPPORTING FEATURES
 REMARKS AND EXPLANATIONS
2.3.1 Three Flashes or Below Threshold: 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. (Level A)
 Not applicable
 Bridge as a “framework” does not have built-in animations. Although, the user has the capability to upload animations, hence, it’s the user's responsibility to upload fully accessible animation.

 

GUIDELINE 2.4 NAVIGABLE

PROVIDE WAYS TO HELP USERS NAVIGATE, FIND CONTENT, AND DETERMINE WHERE THEY ARE.

CRITERIA
 SUPPORTING FEATURES
 REMARKS AND EXPLANATIONS
2.4.1 Bypass Blocks: A mechanism is available to bypass blocks of content that are repeated on multiple Web pages. (Level A)
 Does not support
 It may be confusing or frustrating for screen-reader users since they navigate web content in a virtual buffer mainly using the arrow keys.
In most of the cases, after activating this button, focus is lost.
2.4.2 Page Titled: Web pages have titles that describe topic or purpose. (Level A)
 Does not support
2.4.3 Focus Order: 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. (Level A)
 Supports
 There is no page where the user is navigated sequentially and the navigation sequence affects meaning or operation and focusable components do not receive focus in an order that preserves meaning and operability.
2.4.4 Link Purpose (In Context): 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. (Level A)
 Does not support
 There are a couple of links that open on a new page without warning the user.
2.4.5 Multiple Ways: 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. (Level AA)
 Supports
 Besides menu items, there are a lot of cross-reference links to locate a web page.
2.4.6 Headings and Labels: Headings and labels describe topic or purpose. (Level AA)
 Supports
 Headings – if present – describe topic or purpose.
2.4.7 Focus Visible: Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. (Level AA)
 Does not support
 here are focus indicators on the pages, but these are not uniform in all of the cases.

Guideline 2.5: Input Modalities

MAKE IT EASIER FOR USERS TO OPERATE FUNCTIONALITY THROUGH VARIOUS INPUTS BEYOND KEYBOARD

CRITERIA
 SUPPORTING FEATURES
 REMARKS AND EXPLANATIONS
2.5.1 Pointer Gestures:
All functionality that uses multipoint or path-based gestures for operation can be operated with
a single pointer without a path-based gesture, unless a multipoint or path-based gesture
is essential. (Level A)
 Not applicable

2.5.2 Pointer Cancellation:
For functionality that can be operated using a single pointer, at least one of the following is true (Level A):

● No Down-Event:
The down-event of the pointer is not used to execute any part of the function;
● Abort or Undo: Completion of the function is on
the up-event, and
a mechanism is available to abort the function before completion or to undo the function after completion;

● Up Reversal: The up-event reverses any outcome of the preceding down-event;

● Essential: Completing the function on the
down-event is essential.

 Supports
2.5.3 Label in Name: For user interface
components with labels that include text or images of text,
the name contains the text that is presented visually. (Level A)
 Supports

2.5.4 Motion Actuation: 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, except when (Level A):

● Supported Interface: The motion is used to operate functionality through
an accessibility supported interface;
● Essential: The motion
is essential for the function and doing so would invalidate the activity.

 Not applicable
 Bridge does not have any built-in functionality that can be operated by device motion or user motion.

   

 

Principle 3: Understandable
Information and the operation of the user interface must be understandable.

 

GUIDELINE 3.1 READABLE

MAKE TEXT CONTENT READABLE AND UNDERSTANDABLE.

CRITERIA
 SUPPORTING FEATURES
 REMARKS AND EXPLANATIONS
3.1.1 Language of Page: The default human language of each Web page can be programmatically determined. (Level A)
 Supports
 The language of all pages changes after changing the language in the Settings section.
3.1.2 Language of Parts: 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. (Level AA)
 Supports
 Bridge can be used in many languages but the author has the responsibility to create the content in the appropriate language.

 

GUIDELINE 3.2 PREDICTABLE

MAKE WEB PAGES APPEAR AND OPERATE IN PREDICTABLE WAYS.

CRITERIA SUPPORTING FEATURES REMARKS AND EXPLANATIONS
3.2.1 On Focus: When any component receives focus, it does not initiate a change of context. (Level A) Does not support
 When a date field receives focus, a calendar component appears.
3.2.2 On Input: 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. (Level A) Does not support
 Bridge does not use the changing of input fields for initiating context changes.
3.2.3 Consistent Navigation: 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. (Level AA) Does not support
 A part of the calendar component can be operated with the arrow keys, whereas another part with the Tab key. The Tab key can also be used to leave the component. This could confuse the screen-reader users.
3.2.4 Consistent Identification: Components that have the same functionality within a set of Web pages are identified consistently. (Level AA) Does not support
 In some cases, when a field gets completed with content then it gets submitted automatically, whereas in other cases there’s a button that must be activated. This functionality is not consistent, hence, it may confuse the user.

 

GUIDELINE 3.3 INPUT ASSISTANCE

HELP USERS AVOID AND CORRECT MISTAKES.

CRITERIA SUPPORTING FEATURES REMARKS AND EXPLANATIONS
3.3.1 Error Identification: If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text. (Level A)

Does not support
3.3.2 Labels or Instructions: Labels or instructions are provided when content requires user input. (Level A) Does not support
3.3.3 Error Suggestion: If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content. (Level AA) Supports

3.3.4 Error Prevention (Legal, Financial, Data): 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: (Level AA)

● Reversible: Submissions are reversible.
● Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.

● Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.


 Not Applicable

 

 

Principle 4: Robust
Content must be robust enough that it can interpreted reliably by a wide variety of user agents, including assistive technologies.

 

GUIDELINE 4.1 COMPATIBLE

MAXIMIZE COMPATIBILITY WITH CURRENT AND FUTURE USER AGENTS, INCLUDING ASSISTIVE TECHNOLOGIES.

CRITERIA SUPPORTING FEATURES REMARKS AND EXPLANATIONS
4.1.1 Parsing: 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. (Level A) Does not support
4.1.2 Name, Role, Value: For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that 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. (Level A) Does not support
4.1.3 Status Messages: In 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. (Level AA)
 Supports

 

 

Section 508 of the Rehabilitation Act

This Voluntary Product Accessibility Template, or VPAT, is a tool that administrators and decision-makers can use to evaluate Bridge's conformance with Section 508 Standards. This VPAT only applies to the Learner role, and not the Author or Administrative roles.

SECTION 1194.21 SOFTWARE APPLICATIONS AND OPERATING SYSTEMS

CRITERIA SUPPORTING FEATURES REMARKS AND EXPLANATIONS
(A) When software is designed to run on a system that has a keyboard, product functions shall be executable from a keyboard where the function itself or the result of performing a function can be discerned textually. Supports We strive to make sure all sections of Bridge can be navigated and controlled with only a keyboard.
(B) Applications shall not disrupt or disable activated features of other products that are identified as accessibility features, where those features are developed and documented according to industry standards. Applications also shall not disrupt or disable activated features of any operating system that are identified as accessibility features where the application programming interface for those accessibility features has been documented by the manufacturer of the operating system and is available to the product developer. Supports Bridge does not interfere with any operating system or browser shortcuts. Accessibility features such as sticky keys, magnifiers, screen readers, cursor sizes and virtual keyboards are not disabled or disrupted by Bridge.
(C) A well-defined on-screen indication of the current focus shall be provided that moves among interactive interface elements as the input focus changes. The focus shall be programmatically exposed so that Assistive Technology can track focus and focus changes. Supports Bridge provides distinct, custom focus styles.
(D) Sufficient information about a user interface element including the identity, operation and state of the element shall be available to Assistive Technology. When an image represents a program element, the information conveyed by the image must also be available in text. Supports Contextual information about user interface elements is provided via HTML5 or ARIA (as needed).
(E) When bitmap images are used to identify controls, status indicators, or other programmatic elements, the meaning assigned to those images shall be consistent throughout an application's performance. Supports Bridge uses icons to help depict the purpose of certain interface elements, such as "+" add buttons. The use of these icons is consistent throughout the site. Whenever a single graphic is used, such as a lone "+" graphic, alt text or CSS text replacement is used to enable screen readers to read the purpose of the link/button to the user.
(F) Textual information shall be provided through operating system functions for displaying text. The minimum information that shall be made available is text content, text input caret location, and text attributes. Supports Provided by the browser.
(G) Applications shall not override user selected contrast and color selections and other individual display attributes. Not Applicable Not Applicable.
(H) When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user. Not Applicable Not Applicable.
(I) Color coding shall not be used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. Supports Bridge does not use color alone to distinguish the importance of a visual element.
(J) When a product permits a user to adjust color and contrast settings, a variety of color selections capable of producing a range of contrast levels shall be provided. Supports Account-level branding does not affect the Bridge Accessible Learner Experience.
(K) Software shall not use flashing or blinking text, objects, or other elements having a flash or blink frequency greater than 2 Hz and lower than 55 Hz. Supports Bridge does not use flashing or blinking text.
(L) When electronic forms are used, the form shall allow people using Assistive Technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues. Supports Bridge and all forms in the application work well with screen readers such as JAWS, NVDA or VoiceOver.

 

SECTION 1194.22 WEB-BASED INTERNET INFORMATION AND APPLICATIONS

CRITERIA SUPPORTING FEATURES REMARKS AND EXPLANATIONS
(A) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content). Supports Meaningful images in the Bridge user interface have alt-text descriptions. Non-relevant images in the user interface have no alt-text.
(B) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. Supports Bridge does not contain built-in multimedia presentations. Users upload their own content and are responsible for ensuring the accessibility of the uploaded content.
(C) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup. Supports Bridge does not use color alone to distinguish the importance of a visual element.
(D) Documents shall be organized so they are readable without requiring an associated style sheet. Supports A user or screen reader can read and understand pages in Bridge with the associated style sheets disabled.
(E) Redundant text links shall be provided for each active region of a server-side image map. Supports Bridge does not use server-side image maps.
(F) Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape. Supports Bridge does not use server-side image maps.
(G) Row and column headers shall be identified for data tables. Not Applicable
 Not Applicable.
(H) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers. Not Applicable Not Applicable.
(I)Frames shall be titled with text that facilitates frame identification and navigation. Not Applicable Not Applicable.
(J) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. Supports Bridge does not cause the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.
(K) A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes. Supports Bridge is compliant with all provisions of this section, so a text-only version is unnecessary.
(L) When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by Assistive Technology. Supports Bridge uses javascript, WAI-ARIA and the most modern HTML5 techniques to provide feedback from interactive elements and to allow Assistive Technology such as screen readers to read and transmit information back to the user.
(M) When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with §1194.21(a) through (l). Supports Bridge does not require any applet or plug-in to work with its default functionality. Users can upload their own multimedia content using Flash, but if users do not have Flash installed on their computer, they will be prompted with a link to download Flash.
(N) When electronic forms are designed to be completed on-line, the form shall allow people using Assistive Technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues. Supports Bridge and all forms in the application work with screen readers such as JAWS, NVDA or VoiceOver.
(O) A method shall be provided that permits users to skip repetitive navigation links. Supports Bridge has a "skip to content" link at the top of every page that will bypass all site and course navigation. Bridge also uses semantic HTML5 elements such as <nav>, <aside> and <footer>.
(P) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. Not Applicable Not Applicable.

 

SECTION 1194.31 FUNCTIONAL PERFORMANCE CRITERIA

CRITERIA SUPPORTING FEATURES REMARKS AND EXPLANATIONS
(A) At least one mode of operation and information retrieval that does not require user vision shall be provided, or support for Assistive Technology used by people who are blind or visually impaired shall be provided. Supports The Bridge Accessible Learning Experience has been optimized to work well with screen readers such as JAWS, NVDA or VoiceOver.
(B) At least one mode of operation and information retrieval that does not require visual acuity greater than 20/70 shall be provided in audio and enlarged print output working together or independently, or support for Assistive Technology used by people who are visually impaired shall be provided. Supports Bridge supports screen magnification and browser-provided zoom functionality.
(C) At least one mode of operation and information retrieval that does not require user hearing shall be provided, or support for Assistive Technology used by people who are deaf or hard of hearing shall be provided. Supports Bridge does not require hearing for operation.
(D) Where audio information is important for the use of a product, at least one mode of operation and information retrieval shall be provided in an enhanced auditory fashion, or support for assistive hearing devices shall be provided. Supports Bridge does not use any audio for its default operation. Users can upload their own content and are responsible for ensuring the accessibility of the uploaded content.
(E) At least one mode of operation and information retrieval that does not require user speech shall be provided, or support for Assistive Technology used by people with disabilities shall be provided. Supports Bridge does not require speech for operation.
(F) At least one mode of operation and information retrieval that does not require fine motor control or simultaneous actions and that is operable with limited reach and strength shall be provided. Supports Bridge is accessible via keyboard without the need for simultaneous actions.

 

SECTION 1194.41 INFORMATION, DOCUMENTATION AND SUPPORT

CRITERIA SUPPORTING FEATURES REMARKS AND EXPLANATIONS
(A) Product support documentation provided to end-users shall be made available in alternate formats upon request, at no additional charge

Supports

 Product support in an accessible text-based format is available online at:  https://bridgeapp.zendesk.com/hc/en-us  
(B) End-users shall have access to a description of the accessibility and compatibility features of products in alternate formats or alternate methods upon request, at no additional charge. Supports
(C) Support services for products shall accommodate the communication needs of end-users with disabilities. Supports All support content at https://bridgeapp.zendesk.com/hc/en-us is available in an accessible HTML, text-based format.
Was this article helpful?
0 out of 0 found this helpful
Return to top

Related articles

Comments

0 comments

Please sign in to leave a comment.