Accessibility

To make Forem the most inclusive community platform around, accessibility should be considered to enable people with disabilities to create and consume content.

Forem UI changes should consider accessibility wherever possible. Common issues to watch out for in frontend code:

• Adequate color contrast
• Semantic structure and headings
• Alternative text for images
• Unique button and link text
• Accessible forms with labels
• Visible keyboard focus styles

If you're working on something JavaScript-heavy or animated, there are a few additional considerations for accessibility:

• Forem Accessibility Tests
• Intro to ARIA
• Handle focus for client-side interactions
• Reducing motion with CSS media queries
• Linting with eslint-plugin-jsx-a11y
• Testing with Jest-axe

See a list of testing steps to follow during development or for a Pull Request review on the Forem Accessibility Testing Docs.

There's a wealth of information out there to learn about digital accessibility! Here are some resources:

• W3C's Web Accessibility Initiative
• Web Content Accessibility Guidelines
• ARIA Authoring Practices
• WebAIM
• A11y Project
• Deque University
• React Accessibility Docs (most will apply to Preact)
• The Importance of Manual Accessibility Testing
• Accessibility Insights extension