When people talk about Section 508 compliance, they often focus on technical standards. But there is another layer that deserves equal attention. Functional Performance Criteria under Section 508 fills the gaps that technical requirements alone cannot cover. They ensure that information and communication technology (ICT) is actually usable by people with a wide range of disabilities.
Understanding these criteria is essential for anyone building, procuring, or evaluating federal technology.
What Are Functional Performance Criteria (FPC)?
Technical accessibility standards are specific. They address things like color contrast, keyboard navigation, and alt text. But not every accessibility need perfectly fits into a technical checklist.
FPC takes a broader view. They focus on outcomes. It focuses on whether a person with a disability can actually use technology.
The FPC also supports alignment with EN 301 549, the European accessibility standard. This creates consistency between U.S. and European ICT accessibility requirements. That consistency matters most for software, web content, and electronic documents used across both regions.
The underlying goal is that ICT must be usable by as many people as possible.
The Nine Functional Performance Criteria
The Revised Section 508 Standards include nine FPC categories. Each one addresses a specific disability condition. Together, they cover the full range of users that accessible technology must serve.
1. Without Vision
Some users are blind and rely entirely on non-visual access. ICT must provide at least one way to access information without sight. It must also support assistive technologies such as screen readers. If a user cannot see the screen at all, the content must still be fully reachable.
2. Limited Vision
All vision disabilities does not cause total blindness. Many users have reduced vision and need visual enhancements. ICT must support magnification options and accommodate different viewing distances. Text must remain readable when enlarged. Layouts must hold together at higher zoom levels.
3. Without Color Recognition
Color alone cannot be the only way information is communicated. Some users cannot distinguish between colors at all. ICT must ensure that content remains fully understandable without identifying colors. Labels, patterns, or text must reinforce what color alone might otherwise signal.
4. Without Hearing
Users who are deaf need a non-audio path to all content. ICT must offer at least one mode that does not require hearing. This includes support for captions on video content and compatibility with hearing-related assistive technologies where applicable.
5. Limited Hearing
Hearing loss exists on a spectrum. Some users can hear but need audio to be clearer or louder. ICT should provide audio enhancement features. It should also be compatible with hearing devices such as hearing aids and cochlear implant processors.
6. Without Speech
Some users cannot speak at all. So, voice input cannot be the only way to operate technology. ICT must allow users to complete all tasks through alternative methods. Text input is one example. The technology must not assume the user can speak.
7. Limited Manipulation
Fine motor control varies widely among users. Some users cannot grip, pinch, or perform precise hand movements. ICT must not require complex physical actions to operate. It should support alternative input methods. This allows users to interact in a way that works for them.
8. Limited Reach and Strength
Physical reach and strength are not the same for every user. Controls and interfaces must be usable with minimal physical effort. They must not require users to stretch, hold awkward positions, or apply significant force.
9. Limited Language, Cognitive, and Learning Abilities
Cognitive accessibility often does not get the attention it deserves most discussions about digital accessibility. But it is just as important. ICT should simplify tasks wherever possible and reduce unnecessary distractions. It should support users who process information differently or who have learning disabilities.
All Nine Criteria at a Glance
| Disability Area | Condition | What ICT Must Do |
|---|---|---|
| Vision | Without vision | Provide non-visual access; support screen readers. |
| Vision | Limited vision | Support magnification and visual enhancements. |
| Color perception | Without color recognition | Ensure content works without color identification. |
| Hearing | Without hearing | Offer a non-audio mode; support captions. |
| Hearing | Limited hearing | Provide audio enhancement; support hearing devices. |
| Speech | Without speech | Allow full operation without voice input. |
| Physical | Limited manipulation | Avoid complex physical actions; support alternate input. |
| Physical | Limited reach and strength | Require minimal effort, reach, and force. |
| Cognitive and learning | Limited language, cognitive, and learning abilities | Simplify tasks; reduce distractions; support cognitive needs. |
Why FPC Matter Beyond Technical Compliance
Meeting a technical requirement does not always mean the technology works for real users. A website can pass an automated accessibility scan and still be unusable for someone with low vision or limited hand strength.
Functional Performance Criteria under Section 508 exists to close that gap. They shift the focus from input to outcomes. They ask whether a person can actually get the job done using technology in front of them.
For federal agencies and their vendors, this is not optional. FPC is part of the Revised Section 508 Standards. They apply when technical requirements do not fully address a user's needs.
Building to these criteria from the start is far more efficient than remediating after the fact. It leads to better products and reduces legal and procurement risk. More importantly, it serves people who depend on accessible technology every day.
Functional Performance Criteria is not a secondary concern. They are a core part of what it means to build truly accessible ICT under Section 508.