Frameworks can help avoid reinventing the wheel, provide consistent designs and ways to achieve rapid prototyping, and help promote cross browser functionality. This session will look at a common-sense approach to either developing an in-house framework or adopting an already existing framework with accessibility in mind.
Frameworks have grown in popularity in recent years. When it comes to user experience and interaction, they can help avoid reinventing the wheel, provide consistent designs and ways to achieve rapid prototyping, and help promote cross browser functionality. But there is a downside. Relying on frameworks can lead to a lack of understanding of basic semantics and valid HTML, which is vital to an accessible web. Add to that the fact that some assume frameworks are accessible “out of the box” with all screen reader/browser combinations and you can see where adopting frameworks can lead to problems. By working together during the development cycle, different “silos” within your organization can come together–those who define business needs, create the designs, code for front-end development, write the content, and ensure accessibility–and ensure everyone’s needs are met. The session will also look at some examples from existing frameworks and what to look for in them from an accessibility perspective.