thearchivist.funW3C WAI: make access part of the research workflow
W3C's Web Accessibility Initiative provides introductory material about accessibility, user needs and the components that make the web usable. It is useful before selecting a checklist because it connects technical requirements with people trying to read, navigate, contribute or complete a task. Start with the introductory material and the stories of how people use the web. Choose one flow in your own project, such as finding a record, reading an image caption or exporting notes. Identify potential barriers in that flow and connect each proposed improvement to a user need. Continue to the relevant standards and evaluation resources for more detailed guidance. Accessibility is not established by adding one feature or passing one automated scan. Different people use different combinations of devices, settings and assistive technologies. Keep testing with real tasks, including keyboard navigation, text enlargement and understandable feedback. Use these resources to make accessibility a routine editorial and product responsibility rather than an isolated cleanup step before release.
Context and provenance
Foundational explanations connecting accessibility requirements with people’s actual use of the web.
Sources and evidence
Editorial review: 2026-09-23. New evidence may change this account.