Criteria Supporting Feature 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. Supported 1.3.2 Meaningful Sequence: When the sequence in content is presented affects its meaning, a correct reading sequence can be programmatically determined. Supported 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. Supported Guideline 1.4 Distinguishable Make it easier for users to see and hear content including separating foreground from background. Criteria Supporting Feature Remarks and Explanations 1.4.1 Use of Color: Color is not used as the visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. Supported With Exceptions - Managers who create schedules pick Colors for shifts and it's up to them to decide whether or not they add a 'Label' along with the color or not. - Under Requests, on the top bar, color is used to show the status of a request. However, right below the bar, the status is written in text, so the user wouldn't miss anything. - Within the messaging tab, VoiceOver doesn't announce which messages are read/unread. As a work around, while navigating to the Messaging tab, the count of unread messages is read out and the unread messages always appear on top of the messaging list. 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 Not Applicable
available to control audio volume independently from the overall system volume level. 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: • 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. Supported With Exceptions - Select Team label has a contrast ratio less than 4.5:1. - A couple of areas in the Calendar and the Help & Feedback section have contrast ratio less that 4.5:1. E.g. selected date in calendar. 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. Supported 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: • 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. Supported 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 Feature Remarks and Explanations
and correcting information before finalizing the submission. Principle 4: Robust Content must be robust enough that it can be 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 Feature 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. Supported 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. Supported With Exceptions - In the calendar, VoiceOver announces the of the days, instead of the full names. - VoiceOver doesn't read out the role of color on a shift. Managers who create schedules pick Colors for shifts and it's up to them to decide whether or not they add a 'Label' along with the color or not. - In messaging, VoiceOver doesn't announce the role of the 'Add People' button. - In messaging, VoiceOver doesn't announce if a particular chat is muted. - VoiceOver announces the Menu button incorrectly as the Settings button. - In messaging, on selecting members to chat with, VoiceOver doesn't announce the selected state of members. However, as a work around, user can navigate to the top search bar "To" and find out who all have been selected.