(l) When utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology. l.1 Can the functionality of scripted elements or tagged PDF - - - - elements (including in documents) be used with only a keyboard? (i.e., no mouse installed) l.1.a Can menus and sub-menu items be opened from the - - - - keyboard? l.1.b Can sortable table columns be sorted with the - - - - keyboard? l.1.c - - - - Are selectable rows selectable from the keyboard? l.1.d Are calendar components accessible from the - - - - keyboard? l.1.e Are tree and outline node components accessible - - - - from the keyboard? l.1.f Can embedded elements be navigated through or - - - - past with the keyboard? l.1.g Does the tab order of elements make sense, such as - - - - providing a logical tab order? l.2 Is keyboard focus visually and programmatically - - - - discernable? l.2.a If there are forced focus changes, are they clearly - - - - indicated to users of assistive technology? l.2.b Are event handlers that trigger focus changes - - - - avoided? l.2.c When simulated dialogs and calendars are activated - - - - within the same window, does focus move to the new information? l.2.d When the simulated dialog or calendar is closed, does - - - - focus return to an appropriate position? l.2.e Is sufficient information about a user interface element - - - - including the identification, operation and state of the element available to assistive technology? l.3 Is all content information of the scripted element - - - - available to of assistive technology?
(l) When utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology. l.1 Can the functionality of scripted elements or tagged PDF elements (including in documents) be used with only a keyboard? (i.e., no mouse installed) - - - - l.1.a Can menus and sub-menu items be opened from the keyboard? - - - - l.1.b Can sortable table columns be sorted with the keyboard? - - - - l.1.c Are selectable rows selectable from the keyboard? - - - - l.1.d Are calendar components accessible from the keyboard? - - - - l.1.e Are tree and outline node components accessible from the keyboard? - - - - l.1.f Can embedded elements be navigated through or past with the keyboard? - - - - l.1.g Does the tab order of elements make sense, such as providing a logical tab order? - - - - l.2 Is keyboard focus visually and programmatically discernable? - - - - l.2.a If there are forced focus changes, are they clearly indicated to users of assistive technology? - - - - l.2.b Are event handlers that trigger focus changes avoided? - - - - l.2.c When simulated dialogs and calendars are activated within the same window, does focus move to the new information? - - - - l.2.d When the simulated dialog or calendar is closed, does focus return to an appropriate position? - - - - l.2.e Is sufficient information about a user interface element including the identification, operation and state of the element available to assistive technology? - - - - l.3 Is all content information of the scripted element available to of assistive technology? - - - -
crc_mg.docx