测试
There are several points of review to conduct before declaring an application accessible. Over the course of development you may want to consider automated testing techniques. LDTP, for example, may complement your automated testing plan.
This section describes a number of tests you can perform manually on an application to test its accessibility. Passing all the tests does not necessarily imply that the application is fully accessible, but if the application fails any of these tests, then further work may need to be done to improve that aspect of its accessibility.

键盘导航
The following keyboard operations should be tested. Do not use the mouse in any part of this test.
Using only keyboard commands, move the focus through all menu bars in the application.
确认：
上下文敏感的菜单显示正确。
工具栏上列出的任何功能均能使用键盘执行。
你可以在应用程序和对话框中的客户区操作每一个控件。
文本和客户区内的对象可被选取。
Any keyboard enhancements or shortcuts are working as designed.

图形元素
测试并验证使用屏幕阅读器的应用程序：
标签与文本被正确读入，包括菜单与工具栏。
对象信息可正确读取。

视觉焦点指示器
Verify that when moving among objects that the visual focus indicator is easy to identify.
Keyboard navigation through the software and menus should be clearly visible when the focus moves.
Confirm that the screen reader is tracking the visual focus indicator as you navigate using a keyboard.
Run a screen magnification program (if available) and verify that the magnifier can track the visual focus indicator as you navigate using the keyboard and mouse.

字体与文本
Change the font in the application and confirm that the settings are maintained.
Test the application by changing colors and confirm that all settings are maintained.
If magnification is available, test the font, color, and size using the magnification option.

颜色与对比度
Print screenshots to a black and white printer and confirm that all information is visible.
Test applications using only black and white, high-contrast settings and confirm that all information is conveyed correctly.
Test that the application provides at least three combinations of color schemes and that high-contrast schemes are available (e.g. white on black or yellow on blue).
Turn on high-contrast settings in the GNOME Control Center and confirm that the application respects these settings.
Test various themes to ensure that the software is working for all the available settings.

音频
There should be an option in the application to show audio alerts visually.
Test that the audio is working correctly by enabling sound in the GNOME Control Center and then perform the following actions:
Perform an action that should generate an audio alert and confirm that the application is working as designed.
Verify that the application works correctly when increasing or decreasing the volume.
Confirm that warning messages and alerts can be heard correctly in a noisy work environment.

动画
Verify that an option is available to stop animation and that it is working as designed.
Turn the animation off. Confirm that all information is still conveyed correctly.

键盘焦点
Test all messages to confirm that the user is notified before a message times out and is given the option to indicate that more time is needed.
Make sure an option has been included to adjust the response time and confirm that it is working as designed.

文档
Test ASCII text documentation with a screen reader to confirm that it is clear and precise and can be read by assistive technologies.
Test HTML applications using a web browser and screen reader to confirm that the documentation is accessible to assistive technologies.
Note: There are web accessibility guidelines available at http://www.w3.org/TR/WAI-WEBCONTENT/.
Confirm the following information is included in the documentation:
State if the application does not support the standard keyboard access used by the OS.
Identify if there are unique keyboard commands.
Identify any unique accessibility features.
If an action is documented for the mouse, make sure there is an alternative for using the keyboard.

用户界面检查清单
This section summarizes the guidelines given in User Interface Guidelines for Supporting Accessibility. You should refer to that section of the guide for more detailed information on any of the checklist items given here.
When testing an application for accessibility, you should go through each of the items in the list. Note whether the application passes or fails each test, or does not apply to that application.

通用原则列表
GP	通用原则	通过/失败/NA
GP.1	每一个改变用户数据或程序设置的操作均可被撤消。
GP.2	所有应用程序设置均可被恢复默认值，而不需要用户记住默认值是什么。
GP.3	安装完成后，应用程序随时都可运行而不需用户插入磁盘/CD。
GP.4	最频繁的操作要放在菜单结构的最顶层。

键盘导航检查清单
KN	键盘导航	通过/失败/NA
KN.1	为所有应用程序特性提供高效地键盘访问。
KN.2	所有窗口拥有一个逻辑键盘导航顺序。
KN.3	The correct tab order is used for controls whose enabled state is dependent on checkboxes, radio buttons or toggle buttons.
KN.4	键盘访问的应用程序指定函数不能覆盖已存在的系统辅助功能特性。
KN.5	应用程序应尽可能提供一种以上的方法来执行键盘执行的任务。
KN.6	尽可能拥有可选组合键。
KN.7	频繁执行的键盘操作用起来应该顺手(译注：考虑键位)。
KN.8	应用程序不应使用重复、同时的按键。
KN.9	应用程序应赋予键盘所有的鼠标功能。
KN.10	任何文本或对象，可分别用鼠标或键盘选中。
KN.11	任何可调整大小或移动的对象可分别用鼠标或键盘单独控制。
KN.12	应用程序不应使用任何通用导航功能来触发操作。
KN.13	所有键盘绑定的菜单、窗口和提示信息均要出现在与之相关联的对象旁边。

鼠标交互检查清单
MI	鼠标交互	通过/失败/NA
MI.1	避免依靠来自鼠标 右键 或 中键 输入的操作。
MI.2	所有的鼠标操作在确定之前均可被取消。
MI.3	为拖放操作提供视觉反馈
MI.4	鼠标指针不能在程序控制下反常，或者它的移动不因程序而受限于屏幕某个区域。

图形元素检查清单
GE	图形元素	通过/失败/NA
GE.1	避免对图形属性，比如线、边框或阴影度进行硬编码。
GE.2	尽可能让多色图形元素也能显示在单色环境下。
GE.3	能非常容易区分可交互 GUI 元素与静态 GUI 元素。
GE.4	提供一个隐藏非必需图形的选项。

字体与文本检查清单
FT	字体与文本	通过/失败/NA
FT.1	避免字体风格或大小是硬编码的。
FT.2	提供一个关闭文本图形背景的选项。
FT.3	所有标签的名字在失去上下文后仍有意义。
FT.4	同一个窗口不应重复使用同一个标签名。
FT.5	标签的位置在整个程序中应始终如一。
FT.6	All static text labels that identify other controls end in a colon (:).
FT.7	Static text labels that identify other controls immediately precede those controls in the tab order.
FT.8	An alternative to WYSIWYG is provided. For example, the ability to specify different screen and printer fonts in a text editor.

颜色与对比度检查清单
CC	颜色与对比度	通过/失败/NA
CC.1	应用程序的颜色避免硬编码，而应根据当前桌面主题或程序设置来确定并绘制。
CC.2	颜色仅用于增强说明，而不能用于传达信息或活动。
CC.3	应用程序应支持所有可用的高对比度主题和设置。
CC.4	软件不应依赖任何特殊的高对比度主题或设置。

放大功能检查清单
MG	放大镜	通过/失败/NA
MG.1	应用程序应提供放大工作区域的能力。
MG.2	应用程序应提供缩放工作区域的选项。
MG.3	应用程序的功能不受放大或缩小改变的影响。

音频检查清单
AU	音频	通过/失败/NA
AU.1	声音不能是传达任何物体信息的唯一方法。
AU.2	用户可以配置所有声音和警告音的频率与音量。

动画检查清单
AN	动画	通过/失败/NA
AN.1	避免使用频率范围在 2Hz—55Hz 间的闪烁元素。
AN.2	任何闪烁应限制在屏幕的某个小区域里。
AN.3	如果动画已被启用，至少应提供一个可以在它第一次展示前关闭的选项。

键盘焦点检查清单
KF	键盘焦点	通过/失败/NA
KF.1	当窗口打开后，焦点应位于最常用的控件上。
KF.2	当前输入焦点位置总是清晰可见的。
KF.3	输入焦点总是明确显示在某个窗口上。
KF.4	Appropriate audio or visual feedback is provided when the user attempts to navigate past either end of a group of related objects.
KF.5	The default audio or visual warning signal is played when the user presses an inappropriate key.
KF.6	There is sufficient audio information for the visual focus that the user can figure out what to do next.
KF.7	When using assistive technologies, such as a screen reader or braille device, the current program indicates the position and content of the visual focus indicator.

Timing checklist
TM	计时器	通过/失败/NA
TM.1	There are no hard-coded time-outs or time-based features in the application.
TM.2	The display or hiding of important information is not triggered solely by movement of the mouse pointer.

Documentation checklist
DC	文档	通过/失败/NA
DC.1	All documentation is in an accessible format, with textual alternate descriptions provided for all figures and diagrams.
DC.2	The documentation includes a section that covers all the application's accessibility features.

GOK (GNOME Onscreen Keyboard)
The information on this page is partially outdated: GNOME 3's Caribou has effectively replaced GNOME 2's gok.
Your application should be usable via gok; key input should be generated entirely by gok, not the keyboard. The aim here would be to work with your application and the desktop in general, ensuring any type of character input can be performed with the on-screen keyboard.
The gok application ships with the GNOME Desktop so should already be present. For full documentation, refer to the official gok site.
Follow these steps to verify the correct operation of gok with your application:
Login into the GNOME desktop
Run gok
启动你的应用程序
Provide input to your application with a pointing device (e.g., mouse or head-tracker) and gok.
Work using the auto-completion and word prediction features of gok.
Verify that gok enables and disables the Menus and Toolbars buttons based on the kind of application invoked; for example, the Menus and Toolbars buttons are disabled for the 'Font properties' capplet, but the same buttons are enabled for the Gedit application.
Verify that the gok on-screen keyboard provided by the Compose button can be used to type in any text for the selected application; run Gedit, click on the text area, and then click on the Compose button in gok. Select the required keys from the on-screen keyboard. The characters should appear in the Gedit text area.
Verify that the Launcher button allows the user to launch any of the Terminal, Web Browser or Text Editor applications.
Verify that the Activate button allows the user to activate any of the currently running application windows on the user's desktop, including GNOME panels and the GNOME desktop.
Verify that the Menus button lists all the available menus in the current application. Verify that clicking on a menu button displays the sub-menu and menu items contained within the sub-menu. Finally, verify that clicking on a menu item activates the menu item. For example, click on the Help Browser application and click on the Menus button. The GOK window now displays the File, Go and Help buttons (the Help Browser menus). Click on the File button and it displays the New Window and Close Window buttons (menu items).
Verify that the Toolbars button lists all the available buttons in the application toolbar. For example, click on the Help Browser application and then click on the Toolbars button. The GOK window now displays the Back, Forward and Home buttons.
Verify that the UI Grab button displays all the button objects for the selected application window. For example, open the 'Font Properties' capplet and click on the UI Grab button in the GOK window. The GOK window should now display the names of the buttons in the capplet - Sans, Sans-serif, Close and Help.

Accerciser
Accerciser and the GNOME Accessibility Architecture
Accerciser is an interactive Python accessibility explorer for the GNOME Desktop. It uses AT-SPI to inspect and control widgets, allowing you to check if an application is providing correct information to assistive technologies and automated test frameworks. Accerciser has a simple plugin framework which you can use to create custom views of accessibility information. Full documentation can be found in the Official Accerciser Manual. For a demonstration of Accerciser and PyATSPI (Python-wrappered access and usage of AT-SPI), see this article. For an excellent walkthrough from the author, see the article titled Make Your Application Accessible with Accerciser.
Accerciser 事实上已经取代了 at-poke 工具。