Throughout the environment tab controls are implemented to present content. However, these tabpanels are constructed by placing a <role> of "tabpanel" on the containing <ul>, as well as a <role> of "tab" on each inner anchor. Implementing roles of "tabpanel" and "tab" imply that standard keyboard interaction (left and right arrow keys) should navigate the tab elements. However, this function is not provided and instead a keyboard user is forced to tab through the tab elements with the tab key. This is nonstandard interaction and can be quite confusing for screen-reader users.
The role of "tabpanel" and "tab" indicates standard keyboard interaction that is not currently provided. The user should be able to tab to the first tab in the tabpanel, and then navigate through the tabs with the left and right arrow. Developers are urged to review the following links regarding tabpanel implementation and keyboard navigability.