Fillable The Social Security Administration Paper Prototype Accessibility Checklist

Fill Online, Printable, Fillable, Blank The Social Security Administration Paper Prototype Accessibility Checklist Form

Use Fill to complete blank online SOCIAL SECURITY ADMINISTRATION (MD) pdf forms for free. Once completed you can sign your fillable form or send for signing. All forms are printable and downloadable.

The Social Security Administration Paper Prototype Accessibility Checklist

On average this form takes 6 minutes to complete

The The Social Security Administration Paper Prototype Accessibility Checklist form is 3 pages long and contains:

  • 0 signatures
  • 50 check-boxes
  • 0 other fields

Country of origin: US
File type: PDF

U.S.A. forms for Social Security Administration

BROWSE SOCIAL SECURITY ADMINISTRATION (MD) FORMS

Related forms
Fill has a huge library of thousands of forms all set up to be filled in easily and signed.
Fill in your chosen form
Sign the form using our drawing tool
Send to someone else to fill in and sign.
find another form
 
Accessibility Checklist for Paper Prototypes
This checklist is used when walking through a paper prototype. Any issues identified
should be fixed at this point, if possible, or documented to be addressed later in the
UI specification or in development.
Input Controls
1. Are there calendar controls?
Yes
No
If yes, ask an accessibility specialist for example(s) of calendar controls
that have worked well for accessibility, and note this issue as something
to be monitored during online prototyping and development.
2. Are there text areas?
Yes
No
If yes, ensure that the design accommodates a character counter, or at
least a “count characters” push button.
3. Are any controls used inappropriately or in a non-standard way?
Yes
No
NA
Unknown
If yes, change the design to match the standard use of controls.
Navigation and Links
4. Will all links be clearly recognizable as links? (even when magnified so that the context is
not visible)
Yes
No
NA
Unknown
If no, consider modifying the design to make links look more like links. If
unsure, consult an Accessibility specialist to determine whether or not it is
an issue.
5. Do any links say “Click here”?
Yes
No
If yes, change the wording of the link to reflect the link’s destination.
6. Are there multiple links on the page with the same wording (e.g. multiple “example”
or “more info” links)?
Yes
No
If yes, consider whether more wording is needed to clarify the purpose of
the links.
If the purpose is clear without additional wording (due to the visual layout
or the context of the page), note the issue for later documentation (the
links will need title attributes).
7. Are any labels, links, or buttons unpronounceable?
Yes
No
If yes, consider whether it is possible to change the wording to a
pronounceable label if possible.
Graphics and Colors
8. Is information conveyed by color alone?
Yes
No
NA
Unknown
If yes, there is no need to remove the color distinction, but it is necessary
to add some other attribute to communicate the distinction.
9. In the application, is task-critical information conveyed through graphics?
Yes
No
NA
Unknown
If yes,
- Work closely with accessibility specialists to determine the best
approach to providing equivalent information in a non-graphical format.
Page Layout
10. Does the page appear that it would be cumbersome to navigate via keyboard?
Yes
No
NA
Unknown
If yes,
-Consider how to insert within-page navigation to allow users to go
directly to specific sections (whether or not this navigation is visible in the
UI).
-Discuss with an accessibility specialist
11. Do information or controls follow the expected end of page?
Yes
No
NA
Unknown
If yes, consider whether the information or controls are relevant to the
task or whether they are unnecessary, such as legal disclaimers that most
people don’t read anyway.
12. Are there any tables that have two or more rows of column headings (or two or more
columns of row headings)?
Yes
No
If yes, consider whether the multiple rows or columns of headings provide
value in understanding the meaning of the table, or whether the table
could be presented in a simpler format without loss of meaning.
13. Are there objects that may be too far apart to be seen at the same time when the
screen is magnified?
Yes
No
NA
Unknown
If yes, try to adjust the page layout to move the objects closer together,
without compromising the usability of the page.
System Feedback and Error Handling
14. Has the approach to error handling been considered?
Yes
No
If no, review the Internet Standards for guidance on the requirements for
error handling.
If yes, make sure it is consistent with the requirements in the Internet
Standards.
ACCESSIBILITY CHECKLIST FOR PAPER PROTOTYPES
Other
15. Does it appear that disabled fields will be used to communicate read-only
information to the user?
Yes
No
NA
Unknown
If yes, consider how the information might be presented simply as
display text, rather than in a disabled field.
16. Will non-HTML files or applications (such as PDF, fillable Word forms, Flash, ActiveX)
be used?
Yes
No
NA
Unknown
If yes, consider whether it is possible to provide the same functionality
using HTML, or to provide an alternative HTML version in addition to the
PDF. If no, it is necessary to test the files or applications to determine
how they work with assistive technologies.
Prepared by the SSA Section 508 Accessibility Resource Center and the Usability Center
Version 1.0 (last updated 6/13/06)
Download
Save PDF to desktop
Email
Email completed PDF
Send for Signing
Email for others to sign
Print
Print document
Choose a Field
Click on a field and
select the person that should complete it
Want to add a signature?
You can add a signature field
and assign it to someone else
to sign
Choose a Field
Click on a field and
select the person that should complete it

The Social Security Administration Paper Prototype Accessibility Checklist

This document is locked as it has been sent for signing.

You have successfully completed this document.

Other parties need to complete fields in the document. You will recieve an email notification when the document has been completed by all parties.

This document has been signed by all parties.

Completed 20 July 2020

Message

View Audit Log
Print With Audit Log
Duplicate Document