| Web Pages (HTML content) | Public websites, service portals, public-facing resources | Browser (desktop or mobile) | Yes | Semantic HTML, alt text, color contrast, keyboard nav, captions | No exceptions except archived pages meeting specific conditions |
| Electronic Documents (PDFs, Word, Excel) | Forms, reports, informational docs online (public) | Browser or plugin viewer | Yes (if newly created, updated, or actively used) | Tagged PDFs, semantic headings, alt text for images, proper reading order | Older, preexisting documents exempt unless updated or actively used |
| Electronic Documents (Intranet or Internal) | Employee manuals, training, policy docs behind login; critical for employment or education | Internal network, Single Sign-On (SSO) intranet portals | Yes (due to ADA Title I, Section 504 compliance) | Tagged PDFs, semantic structures, alt text, proper reading order | No exemption; employment, education, or essential service docs must be accessible even internally |
| Images and Non-text Media | Charts, infographics, diagrams on websites/apps | Embedded in websites/apps | Yes | Provide alt text descriptions, decorative images hidden from screen readers | Pre-rule or archived content exempt if not actively used |
| Audio/Video Media | Videos, podcasts, multimedia presentations | Embedded players, external video/audio platforms | Yes | Captions, transcripts, audio descriptions, keyboard accessible players | Pre-rule, archived multimedia exempt if no active use; accommodation required if requested |
| Online Forms & Interactive Tools | Web applications, registration, interactive widgets | Web browsers, mobile apps | Yes | Accessible labels, error handling, keyboard operability, screen reader testing | No formal exceptions; third-party vendor integrations must comply |
| Mobile Application Content | Public-facing government or service apps | Mobile (iOS/Android) | Yes | Use accessibility APIs, semantic labels, alt text, responsive design | No exceptions; same requirements as websites |
| Social Media Posts | Public social media posts by public entities | Third-party social media platforms | Yes (for new posts) | Provide alt text, caption media content, clear hashtags, provide text alternatives | Pre-rule legacy posts exempt, but provide alternate accommodations if requested |
| Third-Party Embedded Widgets/Tools | Maps, embedded video players, payment gateways | Web browser, mobile app via embed codes | Yes | Select compliant third-party tools, provide alternative accessible options, use semantic wrappers | No exemption if chosen by agency/entity |
| User-Generated Content | Comments, forum submissions, uploaded content from public users | Web browser, mobile apps via submission interfaces | No | Ensure submission interface is accessible; optionally provide guidance for accessible user submissions | Agencies not directly responsible for accessibility of user-submitted content but must accommodate requests |
| Archived Web Content | Historical, inactive content stored for records | Archive sections of websites | No | Clearly labeled archives; accommodate accessibility requests individually | Exempt only if meets archive conditions (old, inactive, segregated) |
| Preexisting Documents (Legacy Files) | Old PDFs/documents still hosted online | Browser or download via plugins | No (if pre-rule and not actively used or updated) | Provide accessibility remediation upon request; update proactively if possible | Loses exemption status if updated or still actively used |
| Password-Protected Individual Documents | Individualized secure files (e.g. bills, personal statements) | Secure SSO portals, internal secured accounts | No (general exemption from WCAG, but accessibility still required upon individual request) | Provide accessible alternative formats on request; portal itself must remain accessible | Exempt if individually generated, downloadable, and password protected; HTML versions not exempt |
| Pre-Rule Social Media Content | Old social media posts before compliance date | Social platforms (Facebook, Twitter, Instagram, YouTube) | No | Accommodate accessibility requests individually as needed | Legacy social content exempt from proactive remediation but still subject to ADA effective communication duty |
| Internal-Facing Digital Content | Intranets, internal training modules, essential employee/student resources behind login | Internal university portals, Single Sign-On protected intranets/apps | Yes (required by ADA Title I, Section 504 compliance) | Apply WCAG as a best practice; use semantic structure, proper PDF tagging, alt text, keyboard navigation | Not specifically covered by Title II, but mandatory under ADA Title I employment protections and Section 504 if federally funded |
