Good question, there's definitely a lot that back end devs can do, too! (For reference, here's a talk I gave about exactly this idea, that back end devs also need to care about it!)
Accessibility is everyone's job. Sure, some folks like front end devs might write more code to support accessibility, but it's everyone's job to advocate for it and ensure that the team is remembering the end user. Anyone can play a valuable role in implementing accessibility improvements, regardless of role and experience. Here's a great article about an 8-step model for accessibility implementation that outlines how anyone can help.
If you're working with a content management system, back end devs need to structure the CMS such that content managers can easily make the site accessible. This includes things like making sure that images can have alternative text, that form fields have autocomplete attributes, and that content creators can add the appropriate tags to their content, like language.
Even without a content management system, back end devs need to ensure that content is stored in a way that preserves its accessibility attributes. Images, for example, might need to have different alternative text based on context, and your database schema needs to account for this.
Back end developers who integrate front end code into a back end also generally need to be well-informed about semantic structure of accessible HTML, so they can ensure that they preserve important structure when they integrate a front end.
Good question, there's definitely a lot that back end devs can do, too! (For reference, here's a talk I gave about exactly this idea, that back end devs also need to care about it!)
Accessibility is everyone's job. Sure, some folks like front end devs might write more code to support accessibility, but it's everyone's job to advocate for it and ensure that the team is remembering the end user. Anyone can play a valuable role in implementing accessibility improvements, regardless of role and experience. Here's a great article about an 8-step model for accessibility implementation that outlines how anyone can help.
If you're working with a content management system, back end devs need to structure the CMS such that content managers can easily make the site accessible. This includes things like making sure that images can have alternative text, that form fields have autocomplete attributes, and that content creators can add the appropriate tags to their content, like language.
Even without a content management system, back end devs need to ensure that content is stored in a way that preserves its accessibility attributes. Images, for example, might need to have different alternative text based on context, and your database schema needs to account for this.
Back end developers who integrate front end code into a back end also generally need to be well-informed about semantic structure of accessible HTML, so they can ensure that they preserve important structure when they integrate a front end.
This is gold, thanks!