| 2013-12-10 03:27:15 |
Jono M |
description |
Mahara (latest master) uses the tabindex attribute on various forms and buttons, overriding the standard tab order. For screen reader users this is a dealbreaker in many areas, since the elements appear out-of-order when tabbing through the page.
Tab indexing is used in the following areas (and potentially others)
- The site search box
- Individual search forms (eg. in Find Groups)
- Key buttons such as "Create Page", "Edit" (in Resume -> Cover Letter), etc
- Key forms such as "Edit Title and Description" for pages
As an example, in "Contact Information" (Content -> Resume) the input fields are given a tab index but the email address radio buttons + links are not. This means that to a screen reader user, most of the form including its submit button appear to be situated above the site logo (since they're first in the tab order) while the options for email address are in their correct position much further down the page.
Since Mahara's pages are generally structured quite logically, getting rid of all tabindex attributes would vastly improve accessibility. Perhaps a key element (like the first form field) could still be focused by default for people who don't use a screen reader but want to use the keyboard?
(WCAG Level A) |
Mahara (latest master) uses the tabindex attribute on various forms and buttons, overriding the standard tab order. For screen reader users this is a dealbreaker in many areas, since the elements appear out-of-order when tabbing through the page.
Tab indexing is used in the following areas (and potentially others)
- The site search box
- Individual search forms (eg. in Find Groups)
- Key buttons such as "Create Page", "Edit" (in Resume -> Cover Letter), etc
- Key forms such as "Edit Title and Description" for pages
As an example, in "Contact Information" (Content -> Resume) the input fields are given a tab index but the email address radio buttons + links are not. This means that to a screen reader user, most of the form including its submit button appear to be situated above the site logo (since they're first in the tab order) while the options for email address are in their correct position much further down the page.
Since Mahara's pages are generally structured quite logically, getting rid of all tabindex attributes would vastly improve accessibility. Perhaps a key element (like the first form field) could still be focused by default for people who don't use a screen reader but want to use the keyboard?
Affects latest master (using Orca 3.4.2)
(WCAG Level A) |
|
