Skip to content

Commit d63bb02

Browse files
authored
Update accessibility-statement.md (#2678)
1 parent 8d4e47a commit d63bb02

File tree

1 file changed

+3
-7
lines changed

1 file changed

+3
-7
lines changed

website/docs/about/accessibility-statement.md

+3-7
Original file line numberDiff line numberDiff line change
@@ -26,23 +26,19 @@ Because we’re firm in our commitment to accessibility, we take practical steps
2626
We intend to be compatible with the following assistive technologies:
2727

2828
- Safari with VoiceOver on macOS
29-
- Chrome with JAWS on Windows
30-
- Firefox with JAWS and NVDA on Windows
29+
- Chrome or Edge with JAWS on Windows
30+
- Firefox with NVDA on Windows
3131

3232
## Conformance status
3333

3434
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.
3535

36-
For clarity, fully conformant means that the content fully conforms to the accessibility standard.
37-
3836
### Limitations and alternatives
3937

40-
Despite our best efforts to ensure accessibility of Helios, there may be some limitations.
38+
Despite our best efforts to ensure the accessibility of Helios, there may be some limitations of browser technology.
4139

4240
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.
4341

44-
#### Known limitations
45-
4642
The known WCAG conformance issues are listed on the component’s page under the accessibility tab.
4743

4844
## Assessment approach

0 commit comments

Comments
 (0)