Accessibility
Web accessibility is the practice of making websites and digital interfaces usable by as many people as possible, including people with disabilities.
Accessible work includes semantic structure, keyboard operation, readable contrast, text alternatives, clear labels and compatibility with assistive technologies.
Making interfaces perceivable and operable
Accessible work includes semantic structure, keyboard operation, readable contrast, text alternatives, clear labels and compatibility with assistive technologies. In practical terms, Accessibility belongs to the browser, server or document layer. Knowing that layer is important because it tells you what the term can change, what it cannot change, and where to look when something behaves unexpectedly.
A form that works with keyboard and assistive technology
A form label connected to its input, visible keyboard focus and sufficient contrast all help people use the interface in different ways.
Where accessibility becomes testable
You do not need to memorize the term in isolation. It becomes useful when you can recognize it in the tool, browser, file or conversation where the concept is doing real work.
Accessibility is not the same thing as usability
Web accessibility is the practice of making websites and digital interfaces usable by as many people as possible, including people with disabilities. By contrast, Usability describes how effectively, efficiently and satisfactorily people can use an interface to achieve intended goals. The two can appear in the same project, but they describe different parts of the work and should not be used as interchangeable labels.
The mistake: treating compliance as a visual checklist
The common mistake is to use Accessibility as if it also meant Usability. That blurs two separate decisions and usually sends troubleshooting in the wrong direction. A better test is practical: Navigate with a keyboard, zoom the page, check focus order and use an accessibility tree or audit tool as a starting point.
Why access belongs in the design itself
In day-to-day work, Accessibility matters when the concept needs to be identified precisely instead of being grouped with a nearby term. The practical value is not the vocabulary itself; it is being able to identify the right control, file, setting or decision when the concept becomes relevant.
A form label connected to its input, visible keyboard focus and sufficient contrast all help people use the interface in different ways. That example is useful because it turns the definition into something you can recognize, test and discuss with other people working on the same project.
Related terms worth learning next
Sources and further reading
Use these references when you need documentation-level detail, specifications or product-specific behavior beyond the plain-English explanation above.