Existing issues still not addressed:
1. ARIA Attributes and roles have not been added to make the menus accessible for screen reading software.
2. The key binding has been removed from search box. Unfortunately, because the key bindings has not been modified for the other menu items which immediately precede the search box, there is a partial keyboard trap when using arrow navigation. When arrowing (left/right) between the first set of menu links, the focus should wrap between the first and last links.
3.When arrowing through the sub navigation links the focus should also wrap from bottom to top and vice versa.
The menu should conform to the navigation scheme lists in the WAI-ARIA Authoring practice (http://www.w3.org/TR/wai-aria-practices/#menu
Since the current Jira ticket description would not completely meet WCAG 2.0 Success Criterion 1.3.1 (http://www.w3.org/TR/WCAG20/#content-structure-separation-programmatic),
WCAG 2.0 Success Criterion 2.1 (http://www.w3.org/TR/WCAG20/#keyboard-operation
) and WCAG 2.0 Success Criterion 4.1.2 (http://www.w3.org/TR/WCAG20/#keyboard-operation):
1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A)
2.1.1 Keyboard: All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints. (Level A)
2.1.2 No Keyboard Trap: If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away. (Level A)
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. (Level A)
Should I create another Jira to address the outstanding issues or should I modify the current description?