4.1.1 Parsing: In content Supported implemented 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. 4.1.2 Name, Role, Value: For all user Supported With Exceptions Areas that are not fully supported interface components (including but today: not limited to: form elements, links * Voting results and components generated by * Search and addressing scripts), the name and role can be suggestions programmatically determined; states, * Source in list of most recently used properties, and values that can be set attachments by the user can be programmatically * Reminders' extra information and set; and notification of changes to title of drop down these items is available to user agents, * Mail inspector 'from' or 'sent' titles including assistive technologies. of fields * Calendar under My Calendar email address source * Meeting invite 'when' and 'location' fields * Meeting inspector 'location' field cannot be proofed * Scheduling Assistant does not provide free/busy information * Date picker in the meeting form does not read out * Rules & Alerts menu does not read out * Signature compose experience does not read out * Groups, Modern Conversation View, Calendar View, To-Do Bar, and Task List do not contain full and programmatic access, but alternative views or modes exist and provide equivalent functionality. Chapter 3 Functional Performance Criteria 301 General 301.1 The requirements of Chapter 3 shall apply to ICT where required by , 255 Chapter 2 (Scoping Requirements), and where otherwise referenced in any other chapter of the Revised 508 Standards or Revised 255 Guidelines.
4.1.1 Parsing: In content implemented 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 Areas that are not fully supported today: * Voting results * Search and addressing suggestions * Source in list of most recently used attachments * Reminders' extra information and title of drop down * Mail inspector 'from' or 'sent' titles of fields * Calendar under My Calendar email address source * Meeting invite 'when' and 'location' fields * Meeting inspector 'location' field cannot be proofed * Scheduling Assistant does not provide free/busy information * Date picker in the meeting form does not read out * Rules & Alerts menu does not read out * Signature compose experience does not read out * Groups, Modern Conversation View, Calendar View, To-Do Bar, and Task List do not contain full and programmatic access, but alternative views or modes exist and provide equivalent functionality. Chapter 3 Functional Performance Criteria 301 General 301.1 The requirements of Chapter 3 shall apply to ICT where required by , 255 Chapter 2 (Scoping Requirements), and where otherwise referenced in any other chapter of the Revised 508 Standards or Revised 255 Guidelines.
Outlook%202016%20for%20Windows.Win32.RevisedSection508_091217.docx