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. 4.1.2 Name, Role, Value: For all Supported With Exceptions Information or help icons are user interface components incorrectly marked up as links but (including but not limited to: form doesn’t prevent users from getting elements, links and components the information. generated by scripts), the name and Theme name links in Change the role can be programmatically Look could provide more descriptive determined; states, properties, and text. values that can be set by the user In wiki editing “Text Layout” is can be programmatically set; and marked up as a button, while actually notification of changes to these a menu. items is available to user agents, In web part page editing, edit web including assistive technologies. part operation is marked up as a link, Note: This success criterion is while actually a menu. primarily for Web authors who In the site homepage, document develop or script their own user library settings page and user interface components. For example, permissions page, there are several standard HTML controls already controls not being read in a proper meet this success criterion when used way by screen readers. according to specification.
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. Note: This success criterion is primarily for Web authors who develop or script their own user interface components. For example, standard HTML controls already meet this success criterion when used according to specification. Supported With Exceptions Information or help icons are incorrectly marked up as links but doesn’t prevent users from getting the information. Theme name links in Change the Look could provide more descriptive text. In wiki editing “Text Layout” is marked up as a button, while actually a menu. In web part page editing, edit web part operation is marked up as a link, while actually a menu. In the site homepage, document library settings page and user permissions page, there are several controls not being read in a proper way by screen readers.
SharePoint_Server_2016_Web_WCAG_081116.DOCX