VPAT/ACR Evaluator Help Center – Evaluation Rubric

VPAT/ACR Evaluator Help Center

Evaluation Rubric

Understand scoring logic, KPIs, and how evaluations are determined.

What are ICT Type and ICT Subcategory, and how do they work together?

  • ICT Type defines the broad category of your product (e.g., Software, Web Content, Hardware) and is required.
  • ICT Subcategory provides a more detailed description of features or functions and is optional.

Together, they determine the scope and precision of the evaluation criteria applied in the VPAT/ACR.

How do I choose the correct ICT Type(s) and Subcategory(ies)?

Select based on:

  • What your product is (Type)
  • How users interact with it (Subcategory)

✔ You can select multiple options
✔ Choose all that apply
✖ Avoid selecting irrelevant categories

What happens if I select multiple ICT Types or Subcategories?

Selecting multiple options expands the evaluation:

  • Applies more standards and criteria
  • Produces a more comprehensive VPAT/ACR

This is recommended for products with multiple components or capabilities.

What happens if I do not select an ICT Subcategory?

If left blank, the system will:
Automatically include all subcategories associated with the selected ICT Type(s)

This results in a broader (less targeted) evaluation scope.

What if my selection is not supported by the evaluator?

If the selected ICT Type or Subcategory is not yet supported, you will see:

Notice: Evaluation Not Yet Available for Selected ICT
The ICT Type or Subcategory you selected is not currently supported by this VPAT/ACR Evaluator...

This means the evaluation criteria for that category are still being developed and will be included in future releases.

Can I change ICT Type or Subcategory after starting an evaluation?

Yes, but changes may:

  • Add or remove criteria
  • Affect progress or results

It is best to confirm selections before starting the evaluation.

Why do these selections matter for my VPAT/ACR?

ICT Type and Subcategory directly control:

  • Which standards are evaluated (e.g., WCAG, Section 508, EN 301 549)
  • Which criteria appear
  • The accuracy and completeness of your compliance results

What is the best practice for accurate evaluation?

✔ Select all relevant ICT Types
✔ Choose precise Subcategories when possible
✔ Avoid over- or under-selection
✔ Review selections before proceeding

How does the evaluator determine which accessibility criteria to apply?

The evaluator maps your selected ICT Type and ICT Subcategory to a predefined rubric that aligns with applicable standards such as:

  • Section 508 (Ch. 3–6, E205, §402–§407, §502, §603)
  • EN 301 549 (Clauses 4–13)
  • WCAG 2.x (for web and content)
  • Section 255 (for telecommunications)

These mappings are defined in the system taxonomy and drive which requirements appear in your evaluation.

What types of standards are included in the evaluation rubrics?

Depending on your selection, the evaluator may apply:

  • Technical standards (e.g., WCAG success criteria, hardware/software requirements)
  • Functional performance criteria (e.g., without vision, limited hearing)
  • Interoperability requirements (e.g., assistive technology compatibility)
  • Support and documentation requirements

The combination ensures both technical compliance and real-world usability.

How do ICT Type and Subcategory affect which standards are applied?

  • ICT Type determines the primary regulatory framework
    • Example:
      • Web Content → WCAG + Section 508 E205
      • Hardware → Section 508 Chapter 4 + EN 301 549 Clause 5/8
  • ICT Subcategory refines specific clauses and testable requirements
    • Example:
      • Closed Function Systems → §402 + EN 301 549 Clause 5.1–5.5
      • Multimedia Content → WCAG 1.2.x + EN 301 549 Clause 7

What types of ICT can the Evaluator be used for?

The Evaluator is designed to support a broad range of Information and Communication Technology (ICT), including:

  • Software and applications
  • Web content and web applications
  • Electronic documents and multimedia
  • Hardware and telecommunications (as standards coverage expands)

What is the role of Functional Performance Criteria in the rubric?

Functional Performance (Section 508 Chapter 3 / EN 301 549 Clause 4.2) ensures accessibility when:

  • Technical requirements are insufficient, or
  • Multiple disabilities must be considered

These criteria evaluate outcomes, such as:

  • Use without vision
  • Use with limited manipulation
  • Use without hearing

They act as a cross-cutting validation layer across all ICT types.

How granular are the evaluation criteria?

The rubric is fully decomposed and testable, including:

  • Specific clause references (e.g., §407.3 Key Repeat, WCAG 1.2.2 Captions)
  • Test methods (manual, automated, assistive tech testing)
  • Acceptance criteria
  • Evidence requirements

This enables consistent, auditable VPAT/ACR reporting.

What happens if I select multiple ICT Types or Subcategories?

The evaluator aggregates all applicable criteria across selections.

This results in:

  • A combined compliance matrix
  • Broader coverage across standards
  • More comprehensive, but potentially more complex, evaluation

How are regulatory overlaps handled (e.g., WCAG vs. Section 508 vs. EN 301 549)?

The evaluator uses a harmonized mapping approach, where:

  • WCAG criteria are incorporated by reference into Section 508 and EN 301 549
  • Duplicate requirements are aligned, not repeated
  • Crosswalks ensure consistency across standards

This prevents redundancy while maintaining full regulatory coverage.

Does the rubric differ by ICT domain (hardware vs. software vs. telecom)?

Yes. Each domain has distinct evaluation logic:

  • Hardware → Physical controls, operability, closed functionality
  • Software → UI accessibility, keyboard access, AT interoperability
  • Web Content → WCAG POUR principles
  • Telecommunications → Real-time communication, RTT, captions (Section 255)
  • Support Services → Documentation and communication accessibility

How does this impact my VPAT/ACR output?

The selected rubric directly determines:

  • Which criteria are included
  • How results are structured and reported
  • The scope of compliance claims

Accurate ICT selection ensures your VPAT/ACR is:
✔ Complete
✔ Defensible
✔ Aligned with regulatory expectations

VPAT/ACR Evaluator SaaS

iAccessible - Full Lifecycle Website & PDF Testing and Reporting for Digital Accessibility and Optimal User Experience

Discovery District at the University of Maryland

5825 University Research Court, Ste 1100 | College Park, MD 20740

Our experts are available to assist you from 9:00 AM to  4:00 PM EST

Visit our main website: iAccessible

Email: info@iAccessible.com | Phone: 833-922-2377 or (833) 9 - Access