Documentation
HECVAT Lite v3.0.6
IT Accessibility
ITAC-06

Question ITAC-06

Do you have a documented and implemented process for reporting and tracking accessibility issues?

Weight20
High RiskNo
RequiredYes
Compliant AnswerYes

Standard Guidance

EDUCAUSE provides no guidance here

Answering "NO"

State how users should report accessibility issues. Describe any expected related process updates.

Answering "YES"

Describe the process and any recent examples of fixes as a result of the process.

Reason for Question

Tracking and addressing technical issues is a natural part of any web or software product. Critical accessibility issues can cause a product to become unusable. Vendors should have a process to intake, triage, and address accessibility issue reports. Vendors that treat accessibility as "feature requests" for future versions of a product or as nontracked bug reports (i.e., bug reports lacking accessibility tags) should score lower.

Follow-Up Inquiries

Follow-up inquiries for IT Accessibility content will be institution/implementation specific.

HECVAT Pro Advice

[Add expert insights and best practices]

Implementation Tips

[Add practical steps for SME SaaS vendors]

FAQ

[Add common questions related to this HECVAT item]

Resources

[Add links to relevant articles or tools]