It is now a given - or at least, it should be - that our work should be accessible to as wide an audience as possible. Too often, though, this isn't the case; either because developers don't know how to make our work accessible or because we don't know how to make a business case for investing time in accessibility.
A large percentage of the population will have a disability at some point in their lives. For some, this will be a permanent disability, such as someone losing his sight. For others, it will be temporary, such as someone unable to make finely controlled mouse movements due to an injured wrist. It may even be very temporary - the person who can't read an important document because it doesn't display correctly on her smartphone. By following best practices for accessibility, we can allow people who would otherwise be locked out of our websites to use them effectively, while also improving usability for the majority of the audience who do not actually identify as disabled.
This talk covers both general design principles to follow and some specific technical changes to make when coding.