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 Supported 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. For all Supported With Exceptions - In the calendar, VoiceOver 4.1.2 Name, Role, Value: user interface components announces the of the (including but not limited to: form days, instead of the full names. elements, links and components - VoiceOver doesn't read out the role generated by scripts), the name and of color on a shift. Managers who role can be programmatically create schedules pick Colors for shifts determined; states, properties, and and it's up to them to decide values that can be set by the user whether or not they add a 'Label' can be programmatically set; and along with the color or not. notification of changes to these - In messaging, VoiceOver doesn't items is available to user agents, announce the role of the 'Add including assistive technologies. 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.
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.
Microsoft%20StaffHub-%20iOS.iOS.WCAG_090517.DOCX