QR Code Campus Accessibility Services Checklist
Accessibility services codes may open appointments, request forms, document uploads, account pages, feedback, or assistive technology. Give every code a documented owner, limited purpose, exact destination, accessible fallback, inspection routine, and removal date.
Record the service before publishing
- Name the office owner, reviewer, sign locations, publication date, next review, and planned removal date.
- Record one exact task for the code and identify the form or service owner.
- Reach the service from the school's official site. Record the final domain, redirects, and any approved outside provider.
- List every requested field, file, recipient, account action, download, and expected confirmation.
- Print a readable official route and known office contact that provides the same service without scanning.
The campus accessibility services QR guide explains common student-facing scenarios. Use the scanner workflow comparison to define each tool's role.
Review the destination and request
- Confirm that the displayed office, task, form owner, fields, recipient, and deadline match the approved record.
- Keep school sign-in actions inside the known account route and never ask students to report passwords or one-time codes.
- Verify the exact product, publisher, platform, source, and permissions for any assistive technology download.
- Test the fallback with the same care as the QR path; it should not lead to a shortened or unrelated destination.
- Send documentation, accommodation, eligibility, rights, and medical questions to the responsible campus office.
For submitted files, use the document upload response guide. The academic advising checklist offers a related office model.
Inspect and retire printed codes
- Test the final printed code on more than one phone without using live credentials or sensitive records.
- Compare every redirect with the approved record and inspect signs for overlays, damage, or old copies.
- Recheck after any form, provider, domain, requested field, software, or process change.
- Remove every copy when the task ends and retain a location list for follow-up.
- For a mismatch, preserve the URL and location, cover the sign, and report it through the office and campus IT.
Use the QR sticker inspection checklist for a detailed physical inspection routine.
Frequently asked questions
Who should own an accessibility services QR code?
A named office owner should confirm the task, destination, form owner, requested fields, fallback, review date, and removal date.
Should every QR code have a non-QR option?
Yes. Publish a readable official route and known office contact that reaches the same verified service without requiring a scan.
How often should printed codes be inspected?
Inspect them on a documented schedule and after any form, provider, domain, field, sign, or office-process change.
Can QRsafer approve an accessibility services form?
No. QRsafer helps preview a destination. The campus office must confirm the service, form, request, and recipient.
Preview before opening
QRsafer helps preview destinations; the campus office still verifies every form and request. Download for iOS or Android.