Criteria | Level of Support | Notes 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 with exceptions | On the Web Portal, feature tabs within a classroom, such as Engagement and Portfolio, do not respond to keyboard actions, such as the Tab key.
On the Web Portal, items on the data dashboard located atop the admin homepage are not accessible via keyboard navigation.
On the Web Portal, items in Learning Media cannot be selected cannot be selected through keyboard-based inputs. |
(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 | |
(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 with exceptions | On the Web Portal, focus is not visible when a classroom is selected on the homepage.
In the Educator App (Android), the “Add” button does not receive focus when adding a new teacher within the “Roster” tab.
In the Educator App (iPhone), input fields do not receive focus when filling out a survey.
In the Parent App (iPhone), the “like” button under engagement posts does not receive focus. |
(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 with exceptions | On the Web Portal, site and class select boxes on the weekly planner creation page do not have accessible names.
In the Educator App (Android), the back button at the top of the screen do not have an accessible name.
In the Parent App (iPhone), the bottom navigation tabs do not have accessible names. |
(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 | All iconography is rendered via the Element library. |
(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 | |
(g) Applications shall not override user selected contrast and color selections and other individual display attributes. | Supports | |
(h) When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user. | Supports with exceptions | On the Web Portal, there is no descriptive text to indicate the loading status of the “Assessment Progress” page.
In the Parent App (Android), there is no descriptive text to indicate the playing status of the DLL homework recording. |
(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 with exceptions | On the Web Portal, ratings on DRDP reports rely on color-coding to indicate levels without accompanying descriptive text. |
(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. | Not applicable | |
(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 | Applications have no flashing or blinking elements. |
(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 with exceptions | On the Web Portal, when adding an observation note, media attachment options are not keyboard navigable.
On the Web Portal, when adding an engagement post, the required fields lack clear indications of their mandatory status. |