github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-31 14:00:34 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #21608] feat: Accessibility Reports #58201

New Issue
Closed
opened 2026-05-05 22:31:53 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-05-05 22:31:53 -05:00
Owner
Copy Link

Originally created by @ncecere on GitHub (Feb 19, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/21608

Check Existing Issues

  • I have searched for all existing open AND closed issues and discussions for similar requests. I have found none that is comparable to my request.

Verify Feature Scope

  • I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.

Problem Description

Request: Publish Accessibility Conformance Report (WCAG 2.2 Level AA)

To support adoption by federally funded educational institutions and other public sector organizations, we request the publication of formal accessibility conformance documentation demonstrating compliance with Web Content Accessibility Guidelines (WCAG) 2.2 Level AA.

Desired Solution you'd like

Conformance with WCAG 2.2 AA is increasingly required under U.S. federal and state accessibility regulations, including standards aligned with Section 508 of the Rehabilitation Act and updated ADA Title II requirements applicable to public education institutions.

Without documented accessibility conformance (such as an Accessibility Conformance Report (ACR) or VPAT), many K–12 schools, colleges, universities, and other federally funded entities may be unable to:

  • Approve the product for institutional use
  • Complete procurement and compliance reviews
  • Demonstrate accessibility compliance during audits
  • Mitigate regulatory or legal risk

Requested Deliverables

  1. A current Accessibility Conformance Report (ACR), preferably in VPAT 2.4 (or latest) format
  2. Explicit mapping of product functionality to WCAG 2.2 Level AA success criteria
  3. Documentation of:
  • Known accessibility limitations
  • Planned remediation timelines (if applicable)
  • Testing methodology (manual testing, assistive technology validation, automated testing, etc.)

Rationale

Educational institutions are increasingly required to verify digital accessibility prior to software approval and deployment. Providing formal WCAG 2.2 AA documentation:

  • Enables eligibility for public sector procurement
  • Reduces review and approval delays
  • Demonstrates commitment to inclusive and equitable access
  • Reduces institutional compliance risk

We respectfully request that accessibility conformance reporting for WCAG 2.2 Level AA be prioritized to support responsible adoption within regulated educational environments.

Alternatives Considered

No response

Additional Context

https://www.w3.org/TR/WCAG22/

Originally created by @ncecere on GitHub (Feb 19, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/21608 ### Check Existing Issues - [x] I have searched for all existing **open AND closed** issues and discussions for similar requests. I have found none that is comparable to my request. ### Verify Feature Scope - [x] I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions. ### Problem Description # Request: Publish Accessibility Conformance Report (WCAG 2.2 Level AA) To support adoption by federally funded educational institutions and other public sector organizations, we request the publication of formal accessibility conformance documentation demonstrating compliance with Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. ### Desired Solution you'd like Conformance with WCAG 2.2 AA is increasingly required under U.S. federal and state accessibility regulations, including standards aligned with Section 508 of the Rehabilitation Act and updated ADA Title II requirements applicable to public education institutions. Without documented accessibility conformance (such as an Accessibility Conformance Report (ACR) or VPAT), many K–12 schools, colleges, universities, and other federally funded entities may be unable to: - Approve the product for institutional use - Complete procurement and compliance reviews - Demonstrate accessibility compliance during audits - Mitigate regulatory or legal risk ## Requested Deliverables 1. A current Accessibility Conformance Report (ACR), preferably in VPAT 2.4 (or latest) format 2. Explicit mapping of product functionality to WCAG 2.2 Level AA success criteria 3. Documentation of: - Known accessibility limitations - Planned remediation timelines (if applicable) - Testing methodology (manual testing, assistive technology validation, automated testing, etc.) ## Rationale Educational institutions are increasingly required to verify digital accessibility prior to software approval and deployment. Providing formal WCAG 2.2 AA documentation: - Enables eligibility for public sector procurement - Reduces review and approval delays - Demonstrates commitment to inclusive and equitable access - Reduces institutional compliance risk We respectfully request that accessibility conformance reporting for WCAG 2.2 Level AA be prioritized to support responsible adoption within regulated educational environments. ### Alternatives Considered _No response_ ### Additional Context https://www.w3.org/TR/WCAG22/
GiteaMirror commented 2026-05-05 22:31:58 -05:00
Author
Owner
Copy Link

@Classic298 commented on GitHub (Feb 19, 2026):

If you plan to purchase the enterprise version, please contact the team via the official channels (see more here: https://docs.openwebui.com/enterprise/) to request reports.

For everything else: https://github.com/open-webui/open-webui/issues/2790 and https://github.com/open-webui/open-webui/issues?q=sort%3Aupdated-desc%20is%3Aissue%20is%3Aopen%20accessibility and https://github.com/open-webui/open-webui/issues?q=sort%3Aupdated-desc%20is%3Aissue%20state%3Aclosed%20accessibility

Issues are not the correct area for requesting reports.
GitHub Issues are meant to be used for issues not for requesting reports.

I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.

<!-- gh-comment-id:3927997409 --> @Classic298 commented on GitHub (Feb 19, 2026): If you plan to purchase the enterprise version, please contact the team via the official channels (see more here: https://docs.openwebui.com/enterprise/) to request reports. For everything else: https://github.com/open-webui/open-webui/issues/2790 and https://github.com/open-webui/open-webui/issues?q=sort%3Aupdated-desc%20is%3Aissue%20is%3Aopen%20accessibility and https://github.com/open-webui/open-webui/issues?q=sort%3Aupdated-desc%20is%3Aissue%20state%3Aclosed%20accessibility Issues are not the correct area for requesting reports. GitHub Issues are meant to be used for issues not for requesting reports. > I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.
GiteaMirror commented 2026-05-05 22:32:03 -05:00
Author
Owner
Copy Link

@ncecere commented on GitHub (Feb 20, 2026):

Sorry, issue was the only way I could think of posting this information. The reason I ask is because public institution's running Open WebUI could face fines if it doesn't. I'm not sure if any of the enterprise customers have brought this but it will be required by April 24th for a lot of organizations. A lot of other projects and software I have been working with have just been publishing there WCVAG 2.2 report card on there documentation site so that we can reference that. That is all I was trying to bring up is that if the Open WebUI had any accessibility reports , it would be nice if they were available on the documentation site.

Thank you for the work you do on this project it is amazing

<!-- gh-comment-id:3935765181 --> @ncecere commented on GitHub (Feb 20, 2026): Sorry, issue was the only way I could think of posting this information. The reason I ask is because public institution's running Open WebUI could face fines if it doesn't. I'm not sure if any of the enterprise customers have brought this but it will be required by April 24th for a lot of organizations. A lot of other projects and software I have been working with have just been publishing there WCVAG 2.2 report card on there documentation site so that we can reference that. That is all I was trying to bring up is that if the Open WebUI had any accessibility reports , it would be nice if they were available on the documentation site. Thank you for the work you do on this project it is amazing
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#58201
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?