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 • The descriptions in advance interface components (including but table of content dialog may not be not limited to: form elements, links clear using a screen reader. Instead, and components generated by automatic table of contents may be scripts), the name and role can be used. programmatically determined; states, • The AutoCorrect Options dialog properties, and values that can be set may not immediately announce by the user can be programmatically “Replace” and “With” pairs while set; and notification of changes to navigating through the list using these items is available to user agents, assistive technologies. You may including assistive technologies. work around the issue by searching for an existing "Replace" & "With" pairs by typing out the "replace" word, arrowing through the results, and tabbing between the "Results" and "With" fields. You can use this method to create new "Replace" and "With" pairs or replace existing ones. • Information about the advanced color picker found in the “More Colors” dialog is not exposed programmatically but screen-reader users can read or edit the values direct in the UI provided. • Screen Reader cannot read the values under 'Foreground color' and 'Background color' dropdown as they don't have Names. Chapter 3 Functional Performance Criteria 301 General 301.1 Scope 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. 302 Functional Performance Criteria
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 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 • The descriptions in advance table of content dialog may not be clear using a screen reader. Instead, automatic table of contents may be used. • The AutoCorrect Options dialog may not immediately announce “Replace” and “With” pairs while navigating through the list using assistive technologies. You may work around the issue by searching for an existing "Replace" & "With" pairs by typing out the "replace" word, arrowing through the results, and tabbing between the "Results" and "With" fields. You can use this method to create new "Replace" and "With" pairs or replace existing ones. • Information about the advanced color picker found in the “More Colors” dialog is not exposed programmatically but screen-reader users can read or edit the values direct in the UI provided. • Screen Reader cannot read the values under 'Foreground color' and 'Background color' dropdown as they don't have Names. Chapter 3 Functional Performance Criteria 301 General 301.1 Scope 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. 302 Functional Performance Criteria
Word%202016%20for%20Windows%20for%20Office%20365.Win32.RevisedSection508_121817.docx