References
http://demo.phpmyadmin.net/
RELEASE_4_4_1-1208-g286b31c
You can quickly test a piece of software by looking at it against the WCAG checklist. http://webaim.org/standards/wcag/checklist
Just a quick test using the demo I would fail it at WCAG2.0 LevelA. Below are a couple reasons I feel it fails after about a 15 minute review. It looks like there are enough issues with phpmyadmin that I wouldn't tackle trying to make it complaint. You would be better off replacing it with some home grown tool that provides the users just enough to get done what they need to get done that is WCAG compliant or simply train your your folks how to use mysql CLI.
2.1.1 (Level A) - All page functionality is available using the keyboard, unless the functionality cannot be accomplished in any known way using a keyboard (e.g., free hand drawing).
- Really doesn't seem to function too well or at all with keyboard. I'm not great with keyboard only controls but I don't seems to be able to get anywhere.
2.1.2 No Keyboard Trap (Level A) - Keyboard focus is never locked or trapped at one particular page element. The user can navigate to and from all navigable page elements using only a keyboard.
- Seems like keyboard is trapped in select a database/table frame on the left.
2.4.4 Link Purpose (In Context) (Level A) - The purpose of each link (or form image button or image map hotspot) can be determined from the link text alone, or from the link text and its context (e.g., surrounding paragraph, list item, table cell, or table headers).
Links (or form image buttons) with the same text that go to different locations are readily distinguishable.
Table links in the left frame are all title are "Structure" so these links won't be readily distinguishable.
Further the EDIT, COPY, DELETE links on table row data doesn't distinguish which row it will impact. This alone would fail the whole app at Level A.
.
4. 3.3.1 (Level A) Error Identification - errors are presented in an efficient, intuitive, and accessible manner. The error is clearly identified, quick access to the problematic element is provided, and user is allowed to easily fix the error and resubmit the form.
- Go to Database and create a new table without providing a name. The error is a tool tip popup which you loose by changing focus. This will make it very difficult for a visually impaired user to detect the validation error.