Accessibility

GradeHub Web Content Accessibility Guidelines (WCAG 2.0) Checklist

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

CRITERIASUPPORTING FEATURESREMARKS AND EXPLANATIONS
1.1 Text Alternatives: Provide text alternatives for any non-text content.SupportsElements have appropriate text alternatives.
1.2 Time-based Media: Provide alternatives for time-based media.N/A
1.3 Adaptable: Create content that can be presented and navigated in different ways.Supports with exceptionsA few headings are not identified correctly. Some labels or instructions are not associated correctly, or the information presented to screen reader users is not equivalent. Some labels or instructions are not associated correctly, or the information presented to screen reader users is not equivalent. Reading and navigation order is usually logical and intuitive.
1.4 Distinguishable: Make it easier for users to see and hear content, including adequately separating the foreground from the background.Support with exceptionsColor is not used as the sole method of conveying content. There are a few instances of text with insufficient contrast, even with high contrast settings enabled.

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

CRITERIASUPPORTING FEATURESREMARKS AND EXPLANATIONS
2.1 Keyboard Accessible: Make all functionality available from a keyboard.Supports with exceptionsMost, but not all, content is keyboard accessible.
2.2 Enough Time: Provide users enough time to read and use content.SupportsTime-sensitive content was not encountered.
2.3 Seizures: Do not design content in a way that is known to cause seizures.SupportsContent does not flash.
2.4 Navigable: Provide ways to help users navigate, find content, and determine where they are.Supports with exceptionsHeading structure is present, though not always complete.

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

CRITERIASUPPORTING FEATURESREMARKS AND EXPLANATIONS
3.1 Readable: Make text content readable and understandable.SupportsPages have a specified language.
3.2 Predictable: Make web pages appear and operate in predictable ways.SupportsNavigation is consistent throughout the application.
3.3 Input Assistance: Help users avoid and correct mistakes.Supports with exceptionsImportant labels and instructions are not always accessible.

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

CRITERIASUPPORTING FEATURESREMARKS AND EXPLANATIONS
4.1 Compatible: Maximize compatibility with current and future user agents, including assistive technologies.Supports with exceptionsHTML validation issues do not impact accessibility.
ARIA attributes are sometimes incorrect, which can present incorrect roles, states, or properties to screen reader users. ARIA attributes are sometimes incorrect, which can present incorrect roles, states, or properties to screen reader users.

Section 508 of the Rehabilitation Act

SECTION 1194.21 SOFTWARE APPLICATIONS AND OPERATING SYSTEMS – DETAIL

CRITERIASUPPORTING FEATURESREMARKS 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.SupportsWe strive to make sure all sections of GradeHub 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.SupportsGradeHub 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 GradeHub.
(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.SupportsWhere possible, GradeHub uses default browser focus styles. Where those styles are overridden, GradeHub provides distinct 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.SupportsProvided by the browser.
(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.SupportsGradeHub 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. Icons are accompanied by relevant text.
(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.SupportsProvided by the browser.
(g) Applications shall not override user selected contrast and color selections and other individual display attributes.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
(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.SupportsGradeHub 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.SupportsThe interface of GradeHub has been styled with CSS to comply with Section 508's contrast and color settings.
(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.SupportsGradeHub 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.SupportsGradeHub and all forms in the application work well with screen readers such as JAWS or VoiceOver.

SECTION 1194.22 WEB-BASED INTERNET INFORMATION AND APPLICATIONS – DETAIL

CRITERIASUPPORTING FEATURESREMARKS AND EXPLANATIONS
(a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content).SupportsMeaningful images in the GradeHub user interface have alt-text descriptions. Non-relevant images have no alt-text.
(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.SupportsGradeHub does not contain built-in multimedia presentations.
(c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.SupportsGradeHub 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.SupportsA user or screen reader can read and understand pages in GradeHub with the associated style sheets disabled.
(e) Redundant text links shall be provided for each active region of a server-side image map.SupportsGradeHub 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.SupportsGradeHub does not use server-side image maps.
(g) Row and column headers shall be identified for data tables.SupportsData tables, such as the list of assignments and their due dates in the "syllabus" page, are marked up with informative column and row headers.
(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.SupportsGradeHub has no data tables with two or more logical levels of row or column headers.
(i) Frames shall be titled with text that facilitates frame identification and navigationSupportsGradeHub does not use frames.
(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.SupportsGradeHub 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.SupportsGradeHub 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.SupportsGradeHub 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).SupportsGradeHub does not require any applet or plug-in to work with its default functionality.
(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.SupportsGradeHub 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.SupportsGradeHub has a "skip to content" link at the top of every page that will bypass all site and course navigation. GradeHub also uses semantic HTML5 elements such as
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.NA

SECTION 1194.31 FUNCTIONAL PERFORMANCE CRITERIA – DETAIL

CRITERIASUPPORTING FEATURESREMARKS 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.SupportsGradeHub has been optimized to work well with screen readers such as JAWS 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.SupportsGradeHub 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.SupportsGradeHub 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.SupportsGradeHub does not use any audio for its default operation.
(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.SupportsGradeHub 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.GradeHub does not require fine motor control or simultaneous actions. It is accessible via keyboard.

SECTION 1194.41 INFORMATION, DOCUMENTATION AND SUPPORT – DETAIL

CRITERIASUPPORTING FEATURESREMARKS AND EXPLANATIONS
(a) Product support documentation provided to end-users shall be made available in alternate formats upon request, at no additional chargeSupports, with exceptionsProduct support in an accessible text-based format is available online at https://gradehub.drift.help/. Alternative formats may require an additional charge.
(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.SupportsAll support content at https://gradehub.drift.help/ is available in an accessible HTML, text-based format.