Skip to content

docs(governance): add accessibility statement #1787

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
RUKAYAT-CODER merged 1 commit into from
Oct 16, 2026
Merged

docs(governance): add accessibility statement #1787

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
38 changes: 38 additions & 0 deletions Governance/compliance/ACCESSIBILITY_STATEMENT.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,38 @@
# Accessibility statement

TeachLink Web aims to make its web experience usable by people with disabilities.
This statement records the project's current accessibility commitment and how
people can report barriers.

## Conformance level and current status

The project targets **WCAG 2.1 Level AA**. This is a target, not a claim that the
entire website currently conforms. The application includes accessibility
patterns and automated checks, but automated checks do not establish full
conformance. Page-by-page review, keyboard-only use, and screen-reader testing
are still required. See the [accessibility guide](../../docs/ACCESSIBILITY.md)
for the implemented toolkit, known limits, and manual checks.

## Feedback and accessibility requests

Report an accessibility barrier or request an accessible alternative through
the repository's [GitHub issue tracker](https://github.com/rinafcode/teachLink_web/issues).
Include the affected page or workflow, what you were trying to do, the assistive
technology or browser involved when relevant, and a way for maintainers to
follow up. Do not include passwords, private account information, or other
sensitive personal data in a public issue. Describe the barrier and affected
workflow without including private account details.

## Review cadence and ownership

The maintainers review this statement at least once every **12 months** and
after a material change to the accessibility toolkit, supported user flows, or
conformance target. A report that identifies a barrier should trigger an earlier
review of the affected section. The maintainers own updates to this statement
and should record material changes in the pull request that updates it.

## Related guidance

- [Accessibility implementation and testing guide](../../docs/ACCESSIBILITY.md)
- [Component contribution accessibility requirements](../domains/COMPONENT_CONTRIBUTION.md)
- [Project scope](../SCOPE.md)
Loading