# Someone Found an Accessibility Issue. Now What? If you've ever filed a web accessibility concern or are thinking about it, you might wonder: does anyone actually read these? Who gets involved? What does a "fix" even look like, and how long does it take? Your report does not disappear into a black hole. Here's what happens behind the scenes once you hit submit, and how a single report can lead to a lasting change. June 10, 2026 [ Kyle Shachmut ](/people/kyle-shachmut) ![Universal access symbol with a circle around the figure broken up into segments with arrows flowing in a circle.](/sites/g/files/omnuum12446/files/styles/hwp_16_9__480x270/public/2026-05/RWAC%20blog2%20concept_5a_multicolor_loop-16x9.png?itok=Q7WOCFRY) *Note: This post picks up where* [*No, It's Not Just You: Why Reporting Accessibility Issues Matters*](/news/2026/05/reporting-accessibility-issues "No, It's Not Just You: Why Reporting Accessibility Issues Matters") *leaves off.* ## Step 1: Triage - Verify and scope the issue All reports come to [Digital Accessibility Services](/about "About Digital Accessibility Services") (DAS), part of Harvard University Information Technology (HUIT), where they are reviewed and acted on promptly. First we briefly assess and triage the scope of the reported issue. Someone works to reproduce the problem using the details from your report, which is one reason specifics like your browser, device, and assistive technology really matter. Then, the team determines: - Can this be fixed quickly, or does it need more substantial development work? - Is there a workaround we can offer right away? - Is the issue with a specific piece of content (a video with no captions, an image without alt text) or caused by a platform or system issue? - What platform(s) caused the accessibility issue? - Does it involve a third-party vendor? ## Step 2: Assemble the right team After the reported issue is validated, it must be determined which part of the vast technology ecosystem at the university is responsible for the technology relevant to the issue. This spans a wide array of schools, departments, and seemingly countless platforms and tools, so figuring out what unit or who is responsible for a particular site isn't always straightforward. That is where our network of [Digital Accessibility Liaisons](/digital-accessibility-liaisons "Digital Accessibility Liaisons") (DALs) are ready to assist. DAL are staff appointed by Senior Leadership within Schools and units who help DAS connect each report to the right technical owner, whether that's a department web team, a vendor-hosted platform, or a central IT service. ## Step 3: Work toward a solution Fixes don't look the same in every case: - Quick fixes: some issues stem from a small content error or oversight and can be addressed right away. - Longer-term fixes: others need to be worked into a development cycle or platform update; we work with site owners to establish a realistic plan. - Third-party platforms: vendors add a layer of complexity, and fix timelines may not be entirely within the site owner's control. Our [procurement process](/procurement-process "Accessible Technology Procurement ") recommends vetting tools for accessibility before purchase, and accessibility provisions in vendor contracts can help move things along. Where a permanent fix takes time, we work to identify interim work arounds with the technology business owners. If appropriate, we refer members of the Harvard community to their [Student Local Disability Coordinator](https://accessibility.harvard.edu/student-coordinators) for academic accommodations or local human resources offices to discuss [workplace accommodation](https://accessibility.harvard.edu/workplace-accommodations) needs. And for guests or visitors, we may refer them to [University Disability Resources](https://accessibility.harvard.edu) as appropriate. ## Step 4: Follow up with you If you shared contact information, you should hear from DAS at each meaningful step along the way: - Confirmation that we received your report - Any follow-up to help confirm technology details to reproduce and validate the issue - A workaround, if one is available while a fix is underway - Confirmation when the issue is resolved or an honest update on the timeline if it will be longer than desired ## Step 5: Learn from the data Individual reports are valuable. Patterns across reports can be even more so. Over time, report data helps identify if there are recurring problems such as platforms that keep generating issues, teams that would benefit from training, or content practices worth reviewing more broadly. The goal is to use any such insights to get ahead of problems before they reach users in the first place. ## Reporting as a safety net, not a substitute As a reminder, Harvard’s [Digital Accessibility Policy](/digital-accessibility-policy "Harvard University Digital Accessibility Policy") sets the expectation that digital tools are built accessibly from the start following the Web Content Accessibility Guidelines (WCAG) 2.1 AA technical standard. They should be tested before launch, and monitored on an ongoing basis. Reports of digital accessibility issues are a critical feedback loop and safety net, not a replacement for that proactive work. When both are working well, they reinforce each other. We build access in from the start, and the reporting process catches what may slip through, helping us continuously improve. ## A note for content owners and site managers If you manage a university website or application, accessibility reports related to your work will be routed through DAS and your unit's DAL. Treating these the same way you would treat any quality or bug report–documented, prioritized, and tracked to resolution–is both good practice and consistent with our Digital Accessibility Policy. For further guidance and suggestions, visit our[ reporting guidance for accessibility issues](/template-reporting-accessibility-issues "Template for Reporting Accessibility Issues"). ## More Blog Posts [### No, It's Not Just You: Why Reporting Accessibility Issues Matters ](/news/2026/05/reporting-accessibility-issues) May 29, 2026 If you spend enough time on university websites, apps, or online tools, you'll eventually run into something that just does not work as expected for accessibility. Whatever the barrier, we want to know about it. Here's how to tell us and why it matters. ![Report a Web Accessibility Concern form. ](/sites/g/files/omnuum12446/files/styles/hwp_16_9__480x270/public/2026-05/RWAC-form-16x9_0.png?itok=m9PQsQzF) [### A Deep Dive into Contrast Themes ](/news/2026/05/deep-dive-contrast-themes) May 20, 2026 People use Contrast Themes to improve their experience of sites by radically changing their visual display to enhance perception and access. Site designs often don't need to account for them but it's worth checking whether there are barriers present or... ![Windows 11 Contrast themes settings, Dusk enabled.](/sites/g/files/omnuum12446/files/styles/hwp_16_9__480x270/public/2026-04/Windows%2011%20Contrast%20themes%2C%20Dusk%20enabled%2016x9.png?itok=mxuGudi3) [### In Digital Accessibility, We All Start Somewhere ](/news/2026/05/we-all-start-somewhere) May 14, 2026 A suggestion to help make accessibility something you can truly care about, and not just something you’ve been told you need to care about, is to discover your own, personal connection to it. ![illustration of a dotted line extending across a flat surface and up a mountain with a red flag on top, colored dots are at different points on the line.](/sites/g/files/omnuum12446/files/styles/hwp_16_9__480x270/public/2026-05/be1956f6-2315-4bf4-afd5-6e61903a47ab-image_gen_oai_img_magpovvc3lDR-T6iDn5HU_0.png?itok=SYETDLrd) [ View All Posts arrow\_circle\_right ](/das-blog-all-posts) See also:- [ Accessibility Basics ](/das-blog/accessibility-basics) - [ Strategy ](/das-blog/strategy) - [ Testing ](/das-blog-topics/testing)