Greater Lowell Technical High School Accessibility Quick Guides

Accessibility Quick Guides

Quick Start Accessibility by Content Type

Procurement

Procurement means buying products and services. Accessibility procurement is a planning task, not a cleanup task. When the school buys software, devices, websites, learning platforms, or digital content, accessibility requirements need to be included before vendors are reviewed or contracts are signed.

Open Print Version (8.5 x 11)

Quick Focus

  • Ask vendors to explain how their product supports WCAG 2.1 AA and other accessibility duties.
  • Ask for current accessibility documents, product demos, and a plan to fix barriers before purchase.
  • Do not accept broad claims such as 'accessible' without proof and test criteria.

Core Guidance

Do This First

  1. Put accessibility in the request. State accessibility requirements in the scope, bid language, and contract terms for any product or service with digital access needs.
  2. Review vendor evidence. Request a current VPAT or similar report, ask follow-up questions, and watch a demo of key user tasks.
  3. Define acceptance criteria. Tie approval, launch, and ownership for fixes to measurable checks so accessibility issues are not pushed off with no end date.

Essential Checks

What to Cover

  • Include accessibility for software, websites, learning platforms, documents, hardware interfaces, and digital curriculum.
  • Match the procurement scope to real student, staff, and family tasks such as forms, alerts, navigation, media, and account access.
  • Identify assistive technology compatibility questions early, not after purchase.

Vendor Review

  • Ask vendors which WCAG 2.1 AA criteria their product meets and where known gaps remain.
  • Request timelines and ownership for fixing barriers that affect launch or renewal decisions.
  • Make sure the demo covers keyboard use, visible focus, captions, alt text, and screen reader basics when relevant.

Decision Controls

  • Keep written records of accessibility questions, vendor responses, and promises to fix barriers.
  • Coordinate unresolved issues with procurement leadership and accessibility support contacts before approval.
  • Treat accessibility findings as part of product fit, not as an optional extra.

Procurement Reminder

If accessibility is not written into the scope, evaluation, and acceptance criteria, it usually costs more and takes more work to fix later.

Common Problems to Catch

  • Buying a product before anyone asks for accessibility evidence.
  • Accepting an old or incomplete conformance report without review.
  • Letting procurement language say accessibility will be handled after implementation.
  • Skipping real-task demos for login, navigation, forms, alerts, media, or mobile workflows.

Key WCAG 2.1 AA Checkpoints

High-value checkpoints for procurement work
Success Criterion What to confirm
SC 1.1.1 Non-text ContentProducts still need text alternatives for images, icons, and media.
SC 1.3.1 Info and RelationshipsForms, layouts, and content structure must be clear to assistive technology.
SC 2.1.1 KeyboardCritical tasks should be usable without a mouse.
SC 2.4.7 Focus VisibleKeyboard users need a visible focus indicator while navigating the product.
SC 4.1.2 Name, Role, ValueControls need accessible names and roles that assistive technology can announce.