Accessibility doesn’t have to cost a lot, but here are some sure-fire methods to ensure that you pay more than you need to.

Here are our top 9 tips that help you ensure that you pay much more for web accessibility than you should. Because who doesn’t want that, right?

  1. Be sure to save on hourly rate for your design and development work by choosing the lowest cost per hour. After that doesn’t work (you get what you pay for) you’ll have the opportunity to do all that work again and pay for it twice!
  2. Make sure that everything that you do with respect to accessibility isn’t documented and cannot be repeated.
  3. Tell designers that accessibility is the responsibility of the developers and tell the developers that accessibility is the responsibility of the designers. Likewise, tell managers that it’s the responsibility of the CIO or CTO and tell the CIO or CTO that it’s all on the managers.
  4. Ensure you provide absolutely no training to your teams.
  5. Wait until just before launch to seek accessibility help.
  6. Don’t get your developers or Quality Assurance team to test anything with the keyboard.
  7. Ensure that ALL your solutions rely on proprietary materials or software.
  8. Be sure that you don’t put any accessibility requirements in your procurement documents/requirements/rating criteria.
  9. Rely entirely on automated tools for testing.

What do you have?

Okay, that’s 9 quick ones off the top of my head. Please, add your own in the comments. This could be fun! 🙂

13 thoughts on “How to ensure you pay more for web accessibility than you should”

Read comments

  1. Pratik Patel says:

    10. Make sure that your content creators are exempt from any responsibility.

  2. Monica Ackermann says:

    Create accessibility requirements that only say “Must be compatible with JAWS”.

  3. Henny Swan says:

    Only test for screen reader support.
    User test on inaccessible prototypes.

  4. Gonz Blinko says:

    Permit your developers to make the accessibility user interface design decisions – especially if said dev has a relative with a disability.

  5. Never choose development tools, COTS/middleware products or javascript libraries that create accessible, valid or semantic code, or make it easy to customize code and the user interface layer.

  6. Mia L says:

    Base accessibility design decisions on the imagined needs of a hypothetical person with a disability created from stereotypes.

    Or extrapolate the needs of all users with disabilities from that one person you met that one time.

    Don’t consult actual users or research..

  7. Richard says:

    Use the international definition of accessibility: “appears on the first page of Google”

    Don’t worry about dropdown menus. Nothing important goes below the top level.

    Focus indicators only apply in the case of Attention Deficit Disorder

  8. Kevin Potts says:

    10. Assume “disability” = “blind person”.
    11. Make sure everyone everywhere knows what an “alt tag” is so it can be keyword bombed for SEO.
    12. Rely on the W3C for guidance.

  9. Nice take on the subject, although, the search engines being what they are, I fear this list might be extracted out of its context… and be mistaken for a list of good practices!
    My own: Choose a team that has next to no experience in dealing with accessibility. And ensure they are new to the CMS/framework they plan to implement.

  10. Kim Dirks says:

    Can I say this? Use lots and lots and lots of Flash.

    Don’t include any preferences for customization. (Font size & color, whether to underline links, whether to show the “skip nav” links…)

    Make sure to use a flat (low contrast) color palatte becuase it’s restful and pretty.

  11. tanguy loheac says:

    Just trust your agency who pretends to be expert in accessibility, without even having a look on its website and without making some search on what it has already delivered.

  12. tedd says:

    Yes, look to Local, State, and Federal Government Websites as the way to do things.

Hi there! We've closed the comments after a week of spirited discussion on this post. If there's something we've missed, please reach out and let us know.