Skip to content
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

Update accessibility-statement.md #2678

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update accessibility-statement.md #2678

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
12 changes: 4 additions & 8 deletions website/docs/about/accessibility-statement.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
title: Accessibility statement
navigation:
order: 105
order: 105
Copy link
Member

@alex-ju alex-ju Feb 6, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This needs to remain nested as it's a subitem of navigation (which can potentially contain other items, such as hidden or label)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
order: 105
order: 105

---

We believe accessibility is a core requirement and not an optional feature. Our approach to accessibility closely aligns with our [HashiCorp principles](https://www.hashicorp.com/our-principles), such as our core principle of integrity.
Expand All @@ -26,23 +26,19 @@ Because we’re firm in our commitment to accessibility, we take practical steps
We intend to be compatible with the following assistive technologies:

- Safari with VoiceOver on macOS
- Chrome with JAWS on Windows
- Firefox with JAWS and NVDA on Windows
- Chrome or Edge with JAWS on Windows
- Firefox with NVDA on Windows

## Conformance status

The Web Content Accessibility Guidelines (WCAG) define requirements for designers and engineers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA. Helios intends to be fully conformant with WCAG 2.2 Level AA requirements.

For clarity, fully conformant means that the content fully conforms to the accessibility standard.

### Limitations and alternatives

Despite our best efforts to ensure accessibility of Helios, there may be some limitations.
Despite our best efforts to ensure the accessibility of Helios, there may be some limitations of browser technology.

If we can’t provide conformance through the component, we’ll provide documentation for implementing an equivalent experience. We outline other accessibility-related exceptions and considerations and provide the relevant WCAG Success Criteria within each component’s documentation.

#### Known limitations

The known WCAG conformance issues are listed on the component’s page under the accessibility tab.

## Assessment approach
Expand Down