Perceivable
Use alternatives, adaptable structure, readable content, and sufficient contrast.
Web Accessibility
Designing and building websites that people with disabilities can perceive, operate, understand, and use with assistive technologies.
In plain language
Web accessibility removes barriers for people with different abilities and ways of interacting, including keyboards, screen readers, zoom, and voice control.
Accessibility needs ongoing attention. Combine automated checks with human testing across inputs and assistive technologies.
The foundation
What matters in Accessibility
Operable and understandable
Support different inputs, visible focus, clear controls, and understandable errors.
Robust
Use semantic markup and standard behaviour that work with assistive technologies.
Applied by The Forge
How we put it into practice
We consider accessibility in the design, content, and controls from the start.
Start with semantic structure
Use native HTML, logical headings, labels, and reading order.
Support different interactions
Plan for keyboards, zoom, visible focus, adequate targets, contrast, and reduced motion.
Make content understandable
Use clear language, helpful instructions, and predictable controls.
Combine automated and human testing
Combine audits with keyboard, zoom, and assistive-technology checks.
A useful boundary
Limits to keep in mind
- It is not only for blind people or screen-reader users.
- A Lighthouse or automated audit score cannot prove that a website is accessible.
- Accessibility is not optional polish: barriers can prevent people from completing essential tasks.
A concrete example
An appointment form
An appointment form has clear labels, helpful errors, keyboard controls, announced status changes, and readable text when enlarged.
Further reading
Primary sources
Check the sources behind these explanations.
Related concept
Core Web Vitals: Core Web Vitals
Google's real-world page-experience metrics for loading speed, interaction responsiveness, and visual stability.