Test whether Views conforms to WCAG 2.0 and ATAG 2.0 [#1806278]

Part of meta issues #1805996: [META] Views in Drupal Core and #1802678: [META] Views: accessibility review.

The Views user interface introduces several new user interface patterns to core. We need to document these patterns and identify potential accessibility problems.

Steps

Test this issue using 8.x HEAD:
git clone --recursive --branch 8.x http://git.drupal.org/project/drupal.git
Enable Views and Views UI.
Test each screen of the Views UI, including: the administrative view listing, the view creation wizard, the advanced administrative interface, and modal dialogs.
Post screenshots of each screen and interaction in this issue. Crop screenshots to only the relevant portion of the screen (less than 900px wide).
Report any problems in this issue.

References

WCAG 2.0
ATAG 2.0
Drupal accessibility statement
Drupal UI standards (Human interface guidelines)
More on Drupal UI patterns

Reference: core accessibility gate.

Comments

Comment #0.0

xjm

she/her

English

CreditAttribution: xjm commented 8 October 2012 at 11:47

Issue summary:

View changes

Updated issue summary.

Comment #1

xjm

she/her

English

CreditAttribution: xjm commented 8 October 2012 at 18:08

Project:	Drupal core	» VDC
Version:	8.x-dev	»
Component:	other	» Code

Comment #2

Anonymous (not verified) CreditAttribution: Anonymous commented 20 October 2012 at 20:17

At present I don't have a a test environment in 8, but if anyone has a development box where I can login I'd be happy to check this against 8.

A better option may be to save the views section pages as html pages, so that we can run these through different automatic tools, and do some of the grunt work for final manual check. If we could post those html files, than people don't need to git 8. As well as solving the problem of accessing tools from the browser when logged in (if there is solution for that, feel free to let me know).

The latter option would allow more people to test it. We can update the HTML periodically, while track of progress in the cue.

Finally, point 3 is unclear to me. What is meant with this?

Comment #3

xjm

she/her

English

CreditAttribution: xjm commented 21 October 2012 at 17:46

@DesignDolphin, the overhead of manually saving HTML for every screen in Views and posting it is greater than the overhead of helping you get a development environment set up. If you're on a Mac, for example, installing MAMP and git from binaries will take maybe 5 minutes. Or, see these helpful videos, and ask in IRC if you run into any problems.

Regarding "point 3," could you be more clear about what's unclear? ;) I don't understand what it is that you don't understand.

Comment #4

Anonymous (not verified) CreditAttribution: Anonymous commented 21 October 2012 at 18:03

Post screenshots of each screen and interaction in this issue. Crop screenshots to only the relevant portion of the screen (less than 900px wide).

What is meant with 'interaction in this issue' ?

Do you mean of the test results, the screen, or something else?

What is meant with 'the relevant portion of the screen'?

Comment #5

xjm

she/her

English

CreditAttribution: xjm commented 21 October 2012 at 18:50

Parse error. :) The instructions are to post screenshots of each screen and interaction. That is, take screenshots of each screen and interaction (e.g. clicking on a dropbutton, or opening a modal), and attach them to a comment to post them on this issue.

The relevant portion of the screen == the part of the screen that has the relevant content, the stuff you're testing. The views UI, not your browser tabs or scrollbar or the site's footer or sidebar menus or whatever.

This is a screenshot of the relevant portion of the screen for a particular issue:
http://drupal.org/files/drag-area.jpg

This is not:
http://skitch.com/00sven/bekji/boot-camp-partition