This is the Web Content Accessibility Guidelines (WCAG) 2.0 status of the Pathbrite application.

Date: 12.12 2017

Name of Product: Pathbrite

Printable version

Guideline 1.1: Text Alternatives: Provide text alternatives for any non-text content

Guideline Status Remarks and explanations

1.1.1 Non-text Content (Level A) 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.

  • All images and form image buttons have appropriate, equivalent alternative text.
  • Images that do not convey content, are decorative, or contain content that is already conveyed in text are given null alt text (alt="") or implemented as CSS backgrounds. All linked images have descriptive alternative text.
  • Form buttons have a descriptive value.
  • Form inputs have associated text labels or, if labels cannot be used, a descriptive title attribute.

Guideline 1.2: Time-based Media: Provide alternatives for time-based media

Guideline Status Remarks and explanations

1.2.1 Prerecorded Audio-only and Video-only (Level A) 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.

  • No such audio or video exists on the Pathbrite application. Users have been notified to caption any user generated audio/video in the description field.

1.2.2 Captions (Prerecorded) (Level A) 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.

  • No such audio or video exists on the Pathbrite application. Users have been notified to caption any user generated audio/video in the description field.

1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) 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.

  • No such audio or video exists on the Pathbrite application. Users have been notified to caption any user generated audio/video in the description field.

1.2.4 Captions (Level AA) 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.

  • No such audio or video exists on the Pathbrite application. Users have been notified to caption any user generated audio/video in the description field.

1.2.5 Audio Description (Prerecorded) (Level A) 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.

  • No such audio or video exists on the Pathbrite application. Users have been notified to caption any user generated audio/video in the description field.

Guideline 1.3: Adaptable: Create content that can be presented in different ways (for example simpler layout) without losing information or structure

Guideline Status Remarks and explanations

1.3.1 Info and Relationships (Level A) Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text

  • Semantic markup is used to designate headings, lists, emphasized or special text, etc. Semantic markup is used appropriately.
  • Any instance of tables being used on the Pathbrite application include appropriate table captions and data headers. Table summary attribute is not supported in HTML5.
  • Text labels are associated with form input elements. Related form elements are grouped with fieldset/legend.

1.3.2 Meaningful Sequence (Level A) When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.

  • The reading and navigation order (determined by code order) is logical and intuitive on the Pathbrite application.

1.3.3 Sensory Characteristics (Level A) 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.

  • No instructions in Pathbrite rely upon shape, size, or visual location. No Sounds exist within Pathbrite.

Guideline 1.4: Distinguishable: Make it easier for users to see and hear content including separating foreground from background

Guideline Status Remarks and explanations

1.4.1 Use of Color (Level A) Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

  • Color is not used as the sole method of conveying content or distinguishing visual elements.
  • Color alone is not used to distinguish links from surrounding text.

1.4.2 Audio Control (Level A) 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.

  • No Audio ever automatically plays on the Pathbrite application

1.4.3 Contrast (Minimum) (Level AA) 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.

1.4.4 Resize Text (Level AA) Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality.

  • Pathbrite works well when browser zoom is implemented at 200%.

1.4.5 Resize Text (Level AA) If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text

  • No text image replacement is occurring. CSS is appropriately used; image use is minimal throughout the application. The text on the logo is considered essential.

Guideline 2.1: Keyboard Accessible: Make all functionality available from a keyboard

Guideline Status Remarks and explanations

2.1.1 Keyboard (Level A) 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.

X

Keyboard functionality currently isn't available to the following:

  • Editing order of portfolio items
  • Drag/Drop of assignments

2.1.2 No Keyboard Trap (Level A) 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.

  • Focus is never stuck on any individual page element.

Guideline 2.2: Enough Time: Provide Users enough time to read and use content

Guideline Status Remarks and explanations

2.2.1 Timing Adjustable (Level A) For each time limit that is set by the content, at least one of the following is true: 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; orEssential 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.

  • No time limits exist on the Pathbrite application.

2.2.2 Pause, Stop, Hide (Level A) 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.

  • No automatic updates to the page occur. Auto scrolling of pages does occasionally occur(i.e. notification of comments scrolls you directly to the comments), but they don't last longer than 5 seconds.

Guideline 2.3: Seizures: Do not design content in a way that is known to cause seizures

Guideline Status Remarks and explanations

2.3.1 Three Flashes or Below Threshold (Level A) 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.

  • No Flashing exists within Pathbrite

Guideline 2.4: Navigable: Provide ways to help users navigate, find content, and determine where they are

Guideline Status Remarks and explanations

2.4.1 Bypass Blocks (Level A) A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.

  • The main navigation is very limited, bypass links aren't necessary.

2.4.2 Page Titled (Level A) Web pages have titles that describe topic or purpose.

  • All pages have appropriate title attributes.

2.4.3 Focus Order (Level A) 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.

  • All navigation and form input structure is logical, top to bottom.

2.4.4 Link Purpose (In Context) (Level A) 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.

  • Links/buttons all have obvious text and also include TITLE attributes if more information needed for user.

2.4.5 Multiple Ways (Level AA) 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.

X

  • Need to add in 2 of these items.

2.4.6 Headings and Labels (Level AA) Headings and labels describe topic or purpose. 

  • Logical H1, H2, H3 headings are used throughout the application.

2.4.7 Focus Visible (Level AA) Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.

  • Correct CSS focus is used through the application.

Guideline 3.1: Readable: Make text content readable and understandable

Guideline Status Remarks and explanations

3.1.1 Language of Page (Level A) The default human language of each Web page can be programmatically determined.

  • Language attributes added to HTML markup.

3.1.2 Language of Parts (Level AA) 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.

  • Only English is being used on the Pathbrite application.

Guideline 3.2: Predictable: Make Web pages appear and operate in predictable ways

Guideline Status Remarks and explanations

3.2.1 On Focus (Level A) When any component receives focus, it does not initiate a change of context.

  • Tabbing through site never causes any major page changes.

3.2.2 On Input (Level A) 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.

  • Forms throughout the site use appropriate save/submit buttons.

3.2.3 Consistent Navigation (Level AA) 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.

  • Top Navigation, User Navigation, Toolbar Navigation, and Footer navigation are always in the same order.

3.2.4 Consistent Identification (Level AA) Components that have the same functionality within a set of Web pages are identified consistently.

  • Elements that have the same functionality across multiple web pages are consistently identified.

Guideline 3.3: Input Assistance: Help users avoid and correct mistakes

Guideline Status Remarks and explanations

3.3.1 Error Identification (Level A) 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.

  • Sufficient error identification is available on all forms.

3.3.2 Labels or Instructions (Level A) Components that have the same functionality within a set of Web pages are identified consistently.

  • Updated all required form fields with appropriate required consistency labels.

3.3.3 Error Suggestion (Level AA) 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.

  • Error messaging provided for all client-side errors, providing instructions to fix input.

Guideline 4.1: Compatible: Maximize compatibility with current and future user agents, including assistive technologies

Guideline Status Remarks and explanations

4.1.1 Parsing (Level A) 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.

  • Only meta tag errors are showing up in the W3C validator. These errors are insignificant.

4.1.2 Name, Role, Value (Level A) 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.

  • Markup is used in a way that facilitates accessibility. This includes following the HTML/XHTML specifications and using forms, form labels, frame titles, etc. appropriately.