For the seventh consecutive year, Crawford Technologies has been ranked as one of Canada’s top Information and Communication companies in the Branham300 listing. This list is published once a year by the Branham Group, a highly respected analyst and advisory firm. For 23 years, the Branhan300 has highlighted the top Canadian and Multinational ICT companies operating in Canada, as ranked by revenue.
For most organizations, creating and delivering accessible documents to meet the needs of their blind, partially-sighted, and cognitively disabled customers is a constantly evolving process. We all know that it’s important to be in compliance with global regulations, but the regulations themselves and their enforcement have changed over the past few years. Our blog post on the recently announced Section 508 Refresh provides a good overview of this critical piece of legislation.
May 18th, 2017 marks the 6th Global Accessibility Awareness Day, or GAAD. This event started in 2012 when a single blog post posted by Joe Devon, a Los Angeles based web developer, was stumbled upon by Jennison Asuncion, a Toronto accessibility professional. Together they came up with the idea to call attention to the importance of making websites, mobile devices, documents and other technologies accessible to people with varying types of disabilities.
Over the last few months, through a series of blogs and short technical demonstrations, we have been looking in detail at Advanced Function Presentation (AFP), the technology that underpins an enterprise archive.
Web and document accessibility has changed dramatically over the last several years. The traditional formats (such as hard copy braille and large print) are still regularly requested, but electronic formats are becoming ever more prevalent. Accessible HTML5 is a good example of this. Although HTML is generally associated with web pages, it can also be used to produce accessible documents of any length and complexity level. HTML is certainly not a new format, and even Accessible HTML5 has been around for a number of years. So what is it about Accessible HTML5 that makes it different from HTML and why is it such a great option for transactional document accessibility?