I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin from the late 20th century.
These days I do more Javascript and CSS and whatnot, and promote UX and accessibility.
You're very right - people seem to think that a11y applies to only the customer-facing side of a project, and miss out on the documentation. I think the same about back-end interfaces, too - the CMS, the configuration panel, etc. So many blogging platforms etc. don't even let you use the menus unless you have a huge monitor. Colours in dashboards are used to represent state, and companies don't put the effort into making them accessible because they're interfaces for employees, and obviously they don't have any employees with accessibility needs...
I've made a post here before about how using services like Carbon to embed "code" in posts or documentation is actively harmful.
Side note: I read a toot this morning that described video documentation as "throwing unflavored popcorn into the wind". Thought it was a good expression!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
You're very right - people seem to think that a11y applies to only the customer-facing side of a project, and miss out on the documentation. I think the same about back-end interfaces, too - the CMS, the configuration panel, etc. So many blogging platforms etc. don't even let you use the menus unless you have a huge monitor. Colours in dashboards are used to represent state, and companies don't put the effort into making them accessible because they're interfaces for employees, and obviously they don't have any employees with accessibility needs...
I've made a post here before about how using services like Carbon to embed "code" in posts or documentation is actively harmful.
Side note: I read a toot this morning that described video documentation as "throwing unflavored popcorn into the wind". Thought it was a good expression!