github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Placeholder for Outcome of Accessibility Audit #7675

New Issue
Closed
opened 2025-11-02 07:33:08 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-02 07:33:08 -06:00
Owner
Copy Link

Originally created by @techknowlogick on GitHub (Aug 9, 2021).

The Gitea project is currently reaching out to professionals who would be able to perform an accessibility audit (and be paid of course).

This issue is currently a placeholder for when we receive the report so we can coordinate remediation of issues identified.

If you are, or know, someone who can perform a professional accessibility audit of Gitea please reach out to the project team at maintainers@gitea.io (or any of the project owners per their email in CONTRIBUTING.md).

I'm going to lock this issue now as we don't yet have a report, and will reopen it once we have something to act upon.

I want to say a general thanks to everyone who has helped us so far in this matter.

Related issue:

Originally created by @techknowlogick on GitHub (Aug 9, 2021). The Gitea project is currently reaching out to professionals who would be able to perform an accessibility audit (and be paid of course). This issue is currently a placeholder for when we receive the report so we can coordinate remediation of issues identified. If you are, or know, someone who can perform a professional accessibility audit of Gitea please reach out to the project team at maintainers@gitea.io (or any of the project owners per their email in CONTRIBUTING.md). I'm going to lock this issue now as we don't yet have a report, and will reopen it once we have something to act upon. I want to say a general thanks to everyone who has helped us so far in this matter. Related issue: * #7057 * #8638 * #10672 * #16581
GiteaMirror commented 2025-11-02 07:33:09 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Jan 17, 2022):

Some very good news, as part of our NLnet funding they provide us with access to accessibility experts, and while the amount of time we receive is likely not to be enough for a full audit there would still be that relationship established and we could ask if we could pay them directly for additional work.

@techknowlogick commented on GitHub (Jan 17, 2022): Some very good news, as part of our NLnet funding they provide us with access to accessibility experts, and while the amount of time we receive is likely not to be enough for a full audit there would still be that relationship established and we could ask if we could pay them directly for additional work.
GiteaMirror commented 2025-11-02 07:33:09 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Jun 4, 2022):

Looks like all these issues are resolved.

@lunny commented on GitHub (Jun 4, 2022): Looks like all these issues are resolved.
GiteaMirror commented 2025-11-02 07:33:10 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Oct 27, 2024):

Inactive for long time and these issues have been resolved.

@wxiaoguang commented on GitHub (Oct 27, 2024): Inactive for long time and these issues have been resolved.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
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/gitea#7675
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?