Comments on Insisting on Core Development Principles

9 Reader Comments

Back to the Article
  1. Thank you.

    Over the years I have learned and observed all of the points you raise, more recently preached them too.

    With that said though, I haven’t seen the contents of my mind so well put as with your article.

    There is much wisdom to be found here, for the humble worker bee closing tickets to the best closing salesperson, as well as their manager and our clients.

    Great stuff!

    Copy & paste the code below to embed this comment.
  2. Don’t get me wrong, it’s fantastic that you’re championing the best practices we should all aspire to.

    But the commercial reality is often somewhat different. If the client doesn’t understand what is really meant by accessibility for example, and hasn’t asked for it, then increasing our costs because of it (because time = money) could mean we don’t even get the work to begin with.

    The only real way we have to deal with this is to leave it out to start with to get the work, and if the client decides or can be convinced that they want it later (for a workable price) then we can include it as a chargeable extra. That won’t always (or often) happen though.

    Copy & paste the code below to embed this comment.
  3. About: ‘..are not part of any development project unless the client specifically asks for them’
    - it depends on the project type.
    If the client is another software development company, and they are just renting developers for a specific project, in addition to their internal team, very often you have no say in what you do daily and how you do it..

    Copy & paste the code below to embed this comment.
  4. I just wondered if it is All of our Responsibility to improve accessibility as a whole, by contributing to any open-source apps/plugins/themes we use so that we don’t make the changes ourselves?

    Kendra, this is a unique eye-opener for me.

    Also as Dave Wallace put it, that it really does gather up all the running thoughts about this, even more that it’s into just One Article!

    Thank you for the post.

    This is the reason why I keep note of these, because they live on for a long time.

    Kind regards,


    Copy & paste the code below to embed this comment.
  5. In general I agree with most points, save one of the accessibility points. Getting subtitles, captions, and audio descriptions (which are often overlooked) done on video is not something that is easy, nor cheap. It’s simple to include those assets once they are created, but not creating them itself tends to be a business in itself. If a client does not understand the need for accessibility, and your competitor does not care about it and will just put up a video without them, then you’re likely going to have issues with justifying those costs to the client.

    @Kendra what contributions have you made with Drupal and how did you achieve success in this? I have posted a bug on the Devel module saying that it was not appropriate for them to switch from a table-based output to divs for the semantic table that is output once “Display query log” is checked. The claim was that it was better for rendering/performance, but it greatly reduced the accessibility of the output.

    Copy & paste the code below to embed this comment.