Your operating system and keyboard are what you will primarily use to determine your site's accessibility.
Optional tools that you may find helpful include screen readers, like NVDA. These can be used to clarify confusion about elements like tab order. Use the instructions and questions to evaluate your site or content's accessibility.
Does the vendor offer a VPAT (Voluntary Product Accessibility Template)?
- If not, request a VPAT.
- Note that we only look at sections A and AA.
- Learn more about VPATs.
Is the solution fully keyboard accessible?
- If not, where are the exceptions?
- Do these exceptions impact the solution’s basic functionality for a keyboard-only user? To what features will a keyboard-only user lose access?
- Learn more about keyboard accessibility.
Do all images have alternate text?
- If not, where are the exceptions?
- Do these exceptions impact the solution’s basic functionality for a non-visual user? To what features will a non-visual user lose access?
- Learn more about alternate text.
Is the color contrast of text to backgrounds adequate (meeting a ratio of at least 4.5:1)?
- Check using the Color Contrast Analyser.
- If not, where are the exceptions?
- Do these exceptions impact the solution’s basic functionality for a colorblind or low vision user? To what features will a colorblind or low vision user lose access?
- Learn more about color contrast.
If operating system accessibility features are turned on, like screen magnification or sticky keys, does the solution interrupt them?
- If so, where?
- Do these exceptions impact the solution’s basic functionality for users with disabilities? To what features will a user with a disability lose access?
- Learn more about Windows accessibility features.
- Learn more about Mac accessibility features.
If the solution is not fully accessible, is there a plan for equally effective alternate access?
- If not, contact the requesting department and ask for a plan.
- Learn more about equally effective alternate access plans.
Last modified April 3, 2020