• Voluntary Product Accessibility Template® (VPAT®) 1
• About This Document 1
• Essential Requirements and Best Practices for Information & Communications Technology (ICT) Vendors 2
• Getting Started 3
• Essential Requirements for Authors 3
• Best Practices for Authors 7
• Posting the Final Document 9
• Table Information for VPAT® Readers 10
• [Company] Accessibility Conformance Report 11
• Applicable Standards/Guidelines 11
• Terms 12
• WCAG 2.x Report 12
• Revised Section 508 Report 37
• EN 301 549 Report 42
• Legal Disclaimer (Company) 50

Voluntary Product Accessibility Template® (VPAT®)

International Edition

Version 2.5Rev

• Voluntary Product Accessibility Template® (VPAT®) 1
• About This Document 1
• Essential Requirements and Best Practices for Information & Communications Technology (ICT) Vendors 2
• Getting Started 3
• Essential Requirements for Authors 3
• Best Practices for Authors 7
• Posting the Final Document 9
• Table Information for VPAT® Readers 10
• [Company] Accessibility Conformance Report 11
• Applicable Standards/Guidelines 11
• Terms 12
• WCAG 2.x Report 12
• Revised Section 508 Report 37
• EN 301 549 Report 42
• Legal Disclaimer (Company) 50

About This Document

The VPAT is provided in four editions based on the standards/guidelines being evaluated. The editions are WCAG, Revised 508, EN 301 549 and International, which includes all of the standards.

This is the International edition of the VPAT. It includes the following standards/guidelines:

• Web Content Accessibility Guidelines 2.0
• Web Content Accessibility Guidelines 2.1
• Web Content Accessibility Guidelines 2.2
• Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018
• EN 301 549 Accessibility requirements for ICT products and services - V3.1.1 (2019-11)
• EN 301 549 Accessibility requirements for ICT products and services - V3.2.1 (2021-03)

Note that both EN 301 549 V3.1.1 and V3.2.1 are listed in this section because the criteria are identical and the VPAT covers both standards. If you need a different combination of standards/guidelines, use the appropriate alternate edition of the VPAT found on ITI Accessibility web page.

If you do not need to report on all these standards/guidelines, use the appropriate standard-specific VPAT edition found on the ITI Accessibility web page.

This document is broken into two main sections:

• Essential Requirements and Best Practices for using the VPAT® to complete an Accessibility Conformance Report (the instructions)
• The VPAT

Please carefully review the Essential Requirements and Best Practices sections before using the VPAT to create an Accessibility Conformance Report.

The purpose of these instructions is to promote accurate and consistent reporting of product accessibility information.

The VPAT is a template used to document a product’s conformance with accessibility standards and guidelines. The purpose of the Accessibility Conformance Report is to assist customers and buyers in making preliminary assessments regarding the availability of commercial “Electronic and Information Technology,” also referred to as “Information and Communication Technology” (ICT) products and services with features that support accessibility.

The Information Technology Industry Council (ITI) provides the VPAT. Use of the template and service mark does not require membership in ITI.

Essential Requirements and Best Practices for Information & Communications Technology (ICT) Vendors

This section** provides guidance for reporting product conformance for major accessibility standards and guidelines using the VPAT**®** to produce an Accessibility Conformance Report. Deviating from these guidelines precludes vendors from referencing the template by name and/or the VPAT acronym.

Getting Started

1. Before creating a report, read all of the materials provided in this document.
2. Determine which accessibility standards/guidelines will be included in the product conformance report and use the appropriate VPAT file.
3. It is the vendor’s responsibility to maintain the integrity of the data in the report.

Essential Requirements for Authors

The following are the minimum requirements to produce an Accessibility Conformance Report based on the VPAT**®**.

1. The VPAT name and template are registered service marks of ITI. Use of the VPAT template and name requires the inclusion of the registered service mark (i.e., “VPAT®").
2. Users of the VPAT agree not to deviate from the Essential Requirements for Authors.
3. The template file can be used as is or replicated in a different delivery format, for example as HTML or PDF. The final conformance report must be accessible.
4. A report must contain the following content at a minimum:

• Report Title – In the heading format of “[Company Name] Accessibility Conformance Report”
• VPAT Heading Information – Template version
• Name of Product/Version – Name of Product being reported, including product version identifier if available
• Report Date – Date of report publication. At a minimum, provide the month and year of the report publication. For example, “May 2025”. If a date is included, ensure it is clear “4 May 2025” or “May 4, 2025”.
• Product Description – A brief description of the product
• Contact Information – Contact Information for follow-up questions. Listing an email is sufficient.
• Notes – Any details or further explanation about the product or the report. This section may be left blank.
• Evaluation Methods Used – Include a description of evaluation methods used to complete the VPAT for the product under test.
• Applicable Standards/Guidelines – A clear indication of which Standards/Guidelines this Conformance Report covers.
  • The list must include only the Standards/Guidelines used to evaluate the product.
  • A report must contain a minimum of one Standard/Guideline or any combination of the Standards.
  • The applicable Standards/Guidelines that may be included are:
    • Web Content Accessibility Guidelines 2.0 or WCAG 2.0 (ISO/IEC 40500)
    • Web Content Accessibility Guidelines 2.1 or WCAG 2.1
    • Web Content Accessibility Guidelines 2.2 or WCAG 2.2
    • Revised Section 508 standards – the U.S. Federal accessibility standard for ICT Products, published by the U.S. Access Board in the Federal Register on January 18, 2017 and corrected on January 22, 2018
    • EN 301 549 Accessibility requirements for ICT products and services - V3.1.1 (2019-11)
    • EN 301 549 Accessibility requirements for ICT products and services - V3.2.1 (2021-03)
  • Note that both EN 301 549 V3.1.1 and V3.2.1 are listed in this section because the criteria are identical and the VPAT covers both standards. If you need a different combination of standards/guidelines, use the appropriate alternate edition of the VPAT found on ITI Accessibility web page.
  • If other Standards/Guidelines are reported, use the appropriate VPAT edition.
  • This information can be in a table format at the top of the report with the table heading ‘Standards/Guidelines’ and the reported Standards/Guidelines identified. This information can alternatively be supplied in the introductory text of the report. In the VPAT we have used a table as an example and listed “(yes / no)” for each standard/guideline. To indicate what the report covers, leave the appropriate yes or no on each standard/guideline.
  • If multiple Standards or Guideline tables are included, each table must identify the Standard or Guideline that the criteria in that table represent.
• Terms – The report must list the definition of the terms used in the Conformance Level column. ITI recommends the following terms. If a vendor deviates from the ITI definitions, the vendor shall reference this change in the heading Notes section. If a term is not used it can be removed from the list. The ITI definitions are:
  • Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
  • Partially Supports: Some functionality of the product does not meet the criterion.
  • Does Not Support: The majority of product functionality does not meet the criterion.
  • Not Applicable: The criterion is not relevant to the product.

Note: When filling in the WCAG tables, a response may use ‘Supports’ where one might otherwise be inclined to use ‘Not Applicable’. This is in keeping with WCAG 2.0 Understanding Conformance: This means that if there is no content to which a success criterion applies, the success criterion is satisfied.

* <strong>Not Evaluated</strong>: The product has not been evaluated against the criterion. This can only be used in WCAG Level AAA criteria.

• Tables for Each Standard or Guideline – Tables showing the responses to the criteria.

5. WCAG Conformance Information – The answers in the WCAG success criteria are based on the level of conformance being reported (Level A, AA or AAA).

• These tables are used to answer:
  • Revised Section 508:
    • Chapter 5 Software
    • Chapter 6 Support Documentation
  • EN 301 549 Standard:
    • Clause 9 Web
    • Clause 10 Non-Web Documents
    • Clause 11 Software
    • Clause 12 Documentation and Support Services
  • The selected levels of WCAG 2.x Guidelines.
• The WCAG conformance information can either be included in the provided WCAG section of the report which is cross-referenced from the EN 301 549 responses, or the WCAG information can be incorporated within the EN 301 549 section of the report. The information does not need to be duplicated.
• If using a summary table, due to answers applying to multiple criteria, when answering for the Revised Section 508 or EN 301 549, the answers need to be clear about which individual criteria the answer applies to. It is possible to either use a summary, selecting the worst case for the criteria, or to have separate answers or even tables for software, support documentation, authoring tools, etc., so long as the methodology used is made clear.
• If not reporting on Section 508 or EN 301 549, then the mapping breakdown to provisions in those standards can be removed.
• If not reporting on WCAG 2.1, it is acceptable to remove the WCAG 2.1 from the tables as long as the EN 301 549 is not being reported on. These are marked ‘2.1 and 2.2’ within the row. Likewise, if not reporting on WCAG 2.2, it is acceptable to remove the rows with criteria marked ‘2.2 only’ from the table.

6. Remarks and Explanations – Detailed remarks should be provided in the Remarks and Explanations column to justify your answer in the Conformance Level column.
   • When the conformance level is ‘Partially Supports’ or ‘Does Not Support’, the remarks should identify: 5. The functions or features with issues 5. How they do not fully support
   • If the criterion does not apply, explain why.
   • If an accessible alternative is used, describe it.
7. In the Section 508 tables, when subsections of criteria do not apply to the product, the section may be summarized or removed as long as an explanation is provided explaining why a criterion does not apply. Another alternative is to leave the table and add a summary why the section does not apply. For example, in Chapter 5 the criteria in 502 and 503 will not apply to a web only application, thus those sections can be removed with a summary in the notes for the chapter, or a row in the table.

Best Practices for Authors

ITI suggests that authors adopt the following best practices when using the VPAT**®** to create an Accessibility Conformance Report.

• Branding Header: Company logo or branding information

• Report Date Changes: If a report is revised, change the report date and explain the revision in the Notes section. Alternately, create a new report and explain in the Notes section that it supersedes an earlier version of the report.

• Notes: Add any notes applicable to product or the report

  • Additional information about the product version that the document references
  • Any revisions to the document
  • Links to any related documents
  • Additional information describing the product
  • Additional information about what the document does or does not cover
  • Information suggested by the WCAG 2.0 Conformance Claim
  • Information needed to satisfy ISO/IEC 17050-1:2004, Supplier’s Declaration of Conformity

• Evaluation Methods Used – Describe the testing performed. Information to enter may include details on some combination of the following:

  • Indicate whether testing is performed by testers with knowledge of general product functionality. (Instructional note: This would mean the tester knows the common uses and flows of the product in addition to accessibility.)
  • If the product is similar to another evaluated product, provide a link to the report of the other product that contains the description of the evaluation methods used.
  • Describe testing conducted with assistive technologies (Optional: Include the assistive technologies that were used in testing.)
  • Describe testing conducted with manual and automated testing tools. (Optional: Provide a list of the tools used for testing the product.)
  • If a published test method was used, provide name, publisher, URL link of the test method.
  • If a vendor proprietary test method was used, provide the vendor’s name and any non-proprietary details of the testing performed.
  • If another test method was used, provide a description of the test method.

• Remarks and Explanations: This section may include:

  • Information regarding the testing of a given criteria.
  • Information on application dependencies to support accessibility (e.g. OS, app frameworks, browsers recommended).
  • How the customer can find more information about accessibility issues. One method can be to include the bug ID where customers can call the company’s customer support to get additional information.
  • Known workarounds for accessibility issues.

• Legal Disclaimer: Area for any legal disclaimer text required by your organization.

• Report Size: To reduce the size of the report it is acceptable to remove sections. Individual criteria cannot be removed, only sections at a time. Section removal is acceptable in the following situations:

  • When an entire standard is not being reported on, for example EN 301 549, there should be no references of it in the report. We recommend using the appropriate template for the standards you are reporting conformance on, so using the WCAG, EU, or 508 version may be more appropriate than removing a standard from the template.
  • When an entire section is not being reported on because it does not apply to the product, for example:
    • Chapter 4: Hardware. Information should be included in the notes for that section why it has been removed.
    • A card reader that does not have sound could remove the criteria in section 413 Closed Caption Processing Technologies and just note why the criteria does not apply.
  • If not reporting on WCAG 2.1, it is acceptable to remove the WCAG 2.1 from the tables as long as the EN 301 549 is not being reported on. These are marked ‘2.1 and 2.2’ within the row. Likewise, if not reporting on WCAG 2.2, it is acceptable to remove the rows with criteria marked ‘2.2 only’ from the table.
  • If the product is not being evaluated for a level of the criteria (for example Level AAA) then that table may be deleted.
  • If a requesting customer has identified that a section of the standard does not apply, information should be included in the notes that the section has been removed.

• WCAG 2.x Tables: The WCAG 2.x criteria are shown in three tables, Level A, Level AA, and Level AAA.

  • If desired, these tables can be combined into one table.
  • When reporting on a level (A, AA, or AAA) all criteria for that level must be answered for the particular version of WCAG that the report includes.

• Language: Translation to other languages is permitted.

• Multiple Reports: When using the VPAT to create an Accessibility Conformance Report for complex products it may be helpful to separate answers into multiple reports. For example, when a product is an Authoring Tool that also has web content and documentation. When multiple reports are used for a complex product, it is required to explain this and how to reach the other reports in the Notes section of each report.

• Criteria Text: To help conserve space in the ITI template only the criteria ID number and a short title have been included. Where possible, links have been included to the standard/guideline.

  • It is acceptable to add the full text of the criteria into the cell if desired to help with understanding.
  • The links to the standards/guidelines can be removed.

• Ordering of Tables: The order that the standards/guideline tables appear may be changed to facilitate reading. The current order is WCAG, Section 508 and EN 301 549. You can change this order if desired or incorporate the WCAG criteria into the Section 508 and EN 301 549 tables.

• Guideline Section Heading Rows in Tables: The tables include heading rows to facilitate understanding the context of the criteria.

  • The cells in these rows do not require answers as indicated by “Heading cell – no response required.”
  • It is optional to add a response if desired.
  • The shading of the row is also optional.
  • If removing the heading rows, edit the criteria titles so it’s clear where they apply.

Posting the Final Document

• When publishing your Accessibility Conformance Report, be sure to remove the entire first 10 pages of this document, including the table of contents, introductory information and instructions.
• Check for each required item in the VPAT® document:
  • [Company Name] Accessibility Conformance Report (report title)
  • (Based on VPAT® Version 2.5Rev)
  • Name of Product/Version
  • Report Date
  • Product Description
  • Contact Information
  • Notes
  • Evaluation Methods Used
  • Applicable Standards/Guidelines
  • Terms
  • Tables for Each Standard or Guideline
    • Check that there is a response for each criterion for ‘Conformance Level’ and ‘Remarks and Explanations.’
• Verify that the final document is accessible.
• Post your final document on your company’s web site, or make the document available to customers upon request.

Table Information for VPAT® Readers

For each of the standards, the criteria are listed by chapter in a table. The structures of the tables are:

• The first column contains the criteria being evaluated, the second column describes the level of conformance of the product regarding the criteria and the third column contains any additional remarks and explanations regarding the product.
• When sections of criteria do not apply, or are deemed by the customer as not applicable, the section is noted as such and the rest of that table may be removed for that section.
• When multiple standards are being recorded in this document, the duplicative sections are noted and responded to only one time. The duplicate entry will note the cross reference to the data.

Medical Informatics Engineering

Accessibility Conformance Report

International Edition

(Based on VPAT®** Version 2.5Rev)**

Name of Product/Version: WebChart EHR / Enterprise Health EHR

Report Date: July 6th, 2025

Product Description:

WebChart EHR and Enterprise Health EHR are integrated, browser-based electronic health record (EHR) systems developed by Medical Informatics Engineering. These platforms support clinical documentation, patient charting, scheduling, medical billing, secure messaging, and data exchange in compliance with healthcare industry standards. WebChart EHR is primarily used by ambulatory care providers, while Enterprise Health EHR is designed for employee health and occupational medicine programs within large organizations, including government and corporate entities. Both systems are accessed via modern web browsers and offer customizable workflows to support patient-centric and data-driven healthcare delivery.

Contact Information:

Phone: +1 (260) 459-6270

Email: support@mieweb.com

Website: https://www.mieweb.com

Address:

Medical Informatics Engineering, Inc.

1690 Broadway, STE 550

Fort Wayne, IN 46802

USA

Notes:

This Accessibility Conformance Report reflects the current status of conformance for WebChart EHR / Enterprise Health EHR as evaluated against the applicable accessibility standards, including WCAG 2.1 and EN 301 549. The evaluation covers core functionality available through supported web browsers.

Custom configurations, third-party integrations, and user-generated content may impact accessibility and are not fully addressed in this report. Medical Informatics Engineering is committed to continuous improvement of product accessibility and will provide updated conformance reports upon significant changes or new releases.

For additional information or accessibility support, please contact us using the details provided above.

Evaluation Methods Used:

Medical Informatics Engineering conducted this accessibility evaluation using a combination of automated testing, manual inspection, and assistive technology testing. The evaluation was performed against the Web Content Accessibility Guidelines (WCAG) 2.1 Level A and AA success criteria, as well as applicable clauses of EN 301 549.

The assessment included:

*Automated testing using Axe to identify common accessibility issues *Manual keyboard-only navigation testing *Screen reader compatibility testing using NVDA and JAWS *Visual inspection to verify semantic HTML, ARIA attributes, color contrast, and content structure *Functional testing in supported web browsers, including Chrome, Firefox, and Edge

This evaluation reflects the accessibility of the default configuration of WebChart EHR / Enterprise Health EHR in a representative usage environment.

Applicable Standards/Guidelines

This report covers the degree of conformance for the following accessibility standard/guidelines:

Terms

The terms used in the Conformance Level information are defined as follows:

• Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
• Partially Supports: Some functionality of the product does not meet the criterion.
• Does Not Support: The majority of product functionality does not meet the criterion.
• Not Applicable: The criterion is not relevant to the product.
• Not Evaluated: The product has not been evaluated against the criterion. This can only be used in WCAG Level AAA criteria.

WCAG 2.x Report

Tables 1 and 2 also document conformance with:

• EN 301 549:
  • Clause 9 - Web
  • Clauses 10.1-10.4 of Clause 10 - Non-Web documents
  • Clauses 11.1-11.4 and 11.8.2 of Clause 11 - Software
  • Clauses 12.1.2 and 12.2.4 of Clause 12 - Documentation and support services
• Revised Section 508:
  • Chapter 5 - 501.1 Scope and 504.2 Content Creation or Editing
  • Chapter 6 - 602.3 Electronic Support Documentation

Note: When reporting on conformance with the WCAG 2.x Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.1 Conformance Requirements.

Table 1: Success Criteria, Level A

Notes:

Table 2: Success Criteria, Level AA

Notes:

Table 3: Success Criteria, Level AAA

Notes:

Revised Section 508 Report

Notes:

Chapter 3: Functional Performance Criteria (FPC)

Notes:

Chapter 4: Hardware

Notes:

Chapter 5: Software

Notes:

Chapter 6: Support Documentation and Services

Notes:

EN 301 549 Report

Notes:

Clause 4: Functional Performance Statements (FPS)

Notes:

Clause 5: Generic Requirements

Notes:

Clause 6: ICT with Two-Way Voice Communication

Notes:

Clause 7: ICT with Video Capabilities**

Notes:

Clause 8: Hardware

Notes:

Clause 9: Web (see WCAG 2.x section)

Notes:

Clause 10: Non-Web Documents

Notes:

Clause 11: Software

Notes:

Clause 12: Documentation and Support Services

Notes:

Clause 13: ICT Providing Relay or Emergency Service Access

Notes:

Legal Disclaimer (Company)

Include your company legal disclaimer here, if needed.