accessibility:testing
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| accessibility:testing [2024/04/15 10:08] – [Automated Testing] lhernandez | accessibility:testing [2024/04/22 14:46] (current) – Added UI Accessibility Checklist created for EG Conference 2024 Tip of the Iceburg presentation lhernandez | ||
|---|---|---|---|
| Line 83: | Line 83: | ||
| * [[https:// | * [[https:// | ||
| * [[https:// | * [[https:// | ||
| + | |||
| + | ===== UI Checklist for Accessibility ===== | ||
| + | |||
| + | ==== Context ==== | ||
| + | |||
| + | Accessibility problems can often be spotted by just looking for things that seem glitchy or odd to you. If you have a few minutes, a keyboard, or an accessibility testing browser extension, you could help spot even more! Tips and details on some optional tools are available on the Evergreen wiki under Accessibility Testing. The details in the other sections of this page can be used in conjunction with this list. | ||
| + | |||
| + | Regardless of what tools you use to spot the bugs, once a bug is spotted you should submit a Launchpad (LP) bug report about it! Anyone can create an account and report bugs. You do not need to be an expert or know the cause of the bug you found; someone else can come and add more information to your report as comments. Make sure you include your version number for Evergreen when reporting. More information on LP tags and submission can be found on the wiki page [[dev: | ||
| + | |||
| + | Community test servers are available if you want to test on a system without any customizations or confirm that a suspected bug is not just a glitch specific to your computer. Details about the test systems can be found on the [[: | ||
| + | |||
| + | ==== Using the Checklist ==== | ||
| + | |||
| + | This checklist is intended to help you spot signs of common accessibility problems. The list has been broken out into some broad categories, however there is overlap between the categories. If your answer is no to any of these questions, that is an indication there may be an accessibility issue on that interface. Follow up with a bug report! | ||
| + | |||
| + | === General === | ||
| + | |||
| + | * Does the layout of the page make sense for how you use it? | ||
| + | * Are the layout pieces in proportion to each other? | ||
| + | * Does the page work how you expect it to? | ||
| + | * Are colors used only where necessary and do the colors used match their purposes? | ||
| + | * Do the words on the page make sense in context? | ||
| + | |||
| + | === Words === | ||
| + | |||
| + | * Does the specific part of the title on the browser tab match the page name? | ||
| + | * Does the title in the browser tab go from most specific information to least specific? | ||
| + | * Does the page have a single blue title area, and does it make sense for the page? | ||
| + | * Do the words match between the page title and any menu links that bring you to the page? | ||
| + | * Do any error messages make sense and give you enough information to resolve the issue? | ||
| + | * If there is an error, confirmation, | ||
| + | * Do you receive a message when there is an empty state such as “nothing to display?” | ||
| + | * If your system uses translations, | ||
| + | |||
| + | === Buttons === | ||
| + | |||
| + | * Are the buttons the correct size for their location and purpose? | ||
| + | * Are the buttons placed in the expected location? | ||
| + | * Where appropriate, | ||
| + | * Do the words and/or icons on the button make sense? | ||
| + | * If the button only has an icon, is there a tooltip to indicate the purpose of the button? | ||
| + | * Is the color of the button consistent with the color of similar buttons elsewhere? | ||
| + | * If the button is red or yellow, is this an appropriate use of these colors? | ||
| + | * When you use your keyboard, can you tab to the button? | ||
| + | * When you tab to a button does it get a focus outline? | ||
| + | * Once you have tabbed to a button, does pressing Enter activate it? | ||
| + | * If the button changes state based on actions or changes on screen, does this work as you expect? | ||
| + | |||
| + | === Grids === | ||
| + | |||
| + | * Where appropriate, | ||
| + | * Do the column values display? | ||
| + | * Do the column values appear as you expected them to? | ||
| + | * Do any column values that are links open into new tabs? | ||
| + | * Are the options available on the function bar (grid actions) the ones you would expect? | ||
| + | * Do the grid settings work as expected? | ||
| + | |||
| + | === Forms === | ||
| + | |||
| + | * Do the labels on the form fields make sense? | ||
| + | * Does clicking on the form field label place the cursor in the input field or check the box? | ||
| + | * Is there help or descriptive text where appropriate? | ||
| + | * Does the text or label match the context without the need for insider jokes/ | ||
| + | * Can the form be completed and submitted without the use of a mouse? | ||
| + | * If pressing Enter in the input should submit the form, does it? | ||
accessibility/testing.txt · Last modified: 2024/04/22 14:46 by lhernandez