[*] Accessibility is often abbreviated as the numeronym a11y, where the number 11 refers to the number of letters omitted.
I am going to talk about Accessibility for the Web by offering a software engineer perspective (my area of knowledge) of it. However, it is important to highlight that each member of the team could approach this topic from their own discipline.
For instance, product designers could ensure that colours have an adequate contrast ratio. QA engineers could use end to end tools to test whether pages can be used with assistive technologies (AT), and so on.
To continue with this exercise, I will use the Five Ws
The best inclusive tool of all!
Accessibility is the practice of making websites usable by as many people as possible. It is treating everyone equally and giving them the same opportunities, regardless of ability or circumstances. 
You and your team!
By using modern software delivery techniques (Agile, Scrum, Kanban, etc.), developers can work together (and not exclusively) with product designers, user experience designers, QA engineers, product managers, among others. All of us should raise and maintain the conversation on how to develop accessible products and services at all times.
From the beginning and forever!
Accessibility should not be just one more layer of development to be added later. Not only is this approach more expensive, but it is more complex.
Accessibility must be the core of all development because in the end, what we are doing is solving human problems with the use of technologies. Therefore, our focus must be anthropocentric.
For starters, in all HTML development!
When the native semantic information provided by the HTML elements of web applications fails, it can be supplemented by features of the WAI-ARIA specification.
Because it is the law! It helps people and SEO.
Some countries have specific legislation that regulates the need of accessibility for websites. For example, EN 301 549 in the EU, Section 508 of the Rehabilitation Act in the USA, Accessibility Regulation 2018 in the UK are some examples.
Even though accessibility for the web is included in some laws, unfortunately, there is still no authority to issue fines to those who break the law (more on this at the end of this article).
But if following the law is not enough stimulus, I am going to name another one: SEO! Search engine indexers (Yahoo !, Google, Bing, DuckDuckGo) use semantic HTML to extract information about a web page. It means that to have accessibility as a core leads to better chances that the content we are serving will be best ranked in search engines.
Easier than you think!
I am going to mention some tools that have helped me when I develop.
- Semantic HTML: Use HTML tags to give semantic meaning to the content. For example, it is very common to see developers who, when viewing the content directly from design, get confused if the content is a paragraph (<p>) or a heading (<h1>-<h6>) when the font size is big. So you should always ask the following question: what is the semantic intention of this content?
- Command-line browsers: Before styling the component with CSS, add it to the pages where it will be used and then navigate to them using a command-line browser like Lynx. If you can navigate and use the component with a command-line browser, it means that that component is accessible.
- Linters: ESLint has accessibility plugins that together with Git Hooks can generate the first barrier for non-accessible components in the source code.
- CI accessibility tests: Run accessibility tests against multiple URLs and reports on any issues using Pa11y-CI or Puppeteer with Axe.
Domino's v. Robles. On October 7th of 2018, the U.S. Supreme Court allowed a blind man’s accessibility lawsuit against Domino’s Pizza to proceed, paving the way to enforce more companies to provide accessible digital services.
- ^” So What is accessibility”. Mozilla Developer Network