Web Pages (HTML content) | Public websites, service portals, public-facing resources | Yes | HTML tags that explicitly describe the meaning and purpose, meaningful alt text, color contrast, keyboard only navigation, accurate captions (video content) | No exceptions except archived pages meeting specific conditions |
| Electronic Documents (PDFs, Word, Excel) | Forms, reports, informational docs online (public) | Yes, when newly created, updated, or actively used | Tagged PDFs (no image only PDFs), headings, meaningful alt text for images, proper reading order, color contrast, | 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 | Yes (due to ADA Title I, Section 504 compliance) | Tagged PDFs (no image only PDFs), headings, meaningful alt text for images, proper reading order, color contrast, | No exemption; employment, education, or essential service docs must be accessible even internally |
| Images and Non-text Media | Charts, infographics, diagrams on websites/apps | Yes | Provide meaningful alt text, decorative images hidden from screen readers | Pre-deadline or archived content exempt if not actively used |
| Audio/Video Media | Videos, podcasts, multimedia presentations | Yes | Accurate captions, transcripts, audio descriptions, keyboard accessible players | Pre-deadline, archived multimedia exempt if no active use; accommodation required if requested |
| Online Forms & Interactive Tools | Web applications, registration, interactive widgets | Yes | Accessible labels, error handling, keyboard only navigation, screen reader testing | No formal exceptions; third-party vendor integrations must comply |
| Mobile Application Content | Public-facing service apps | Yes | Use accessibility APIs, semantic labels, meaningful alt text, responsive design | No exceptions; same requirements as websites |
| Social Media Posts | Public social media posts by public entities | Yes (for new posts) | Use plain language, provide meaningful alt text, caption media content, clear hashtags that uses CamelCase, provide text alternatives, accessible design (adequate color contrast, readable fonts, etc.) | Pre deadline legacy posts exempt, but provide alternate accommodations if requested |
| Third-Party Embedded Widgets/Tools | Maps, embedded video players, payment gateways | 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 | No | Ensure submission interface is accessible | Not directly responsible for accessibility of user-submitted content but must accommodate requests |
| Archived Web Content | Historical, inactive content stored for records | 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 | No (if Pre deadline and not actively used or updated) | Provide accessibility remediation upon request; update proactively if possible | Loses exemption status if updated or still actively used |
| Pre deadline Social Media Content | Old social media posts before compliance date | No | Accommodate accessibility requests individually as needed | Legacy social media content exempt; current social media posts no exception |