How we make our files accessible
The AHRC website has a range of content types. Below are the steps we are taking for each of these content types.
We aim to develop the AHRC website to meet World Wide Web Consortium (WC3) Web Content Accessibility Guidelines (WCAG) 2.0 Priorities 1 and 2, and the Web Accessibility Initiative (WAI) AA rating.
The steps we have taken in the development of our website include:
- Using cascading style sheets to control page layout and design
- Ensuring contrast between colours is at least 4.5:1
- Avoiding tables where possible
As well as working with our developers to ensure ongoing development is made accessible we also take steps to ensure page content is accessible. This includes:
- Using simple page layouts
- Using appropriate heading structures
- Using alt text on images
- Marking up tables
- State when a weblink opens in a new window
- Stating file size and format when linking to a document
Microsoft office documents
We will aim to make common Microsoft Office files such as Word, Excel and PowerPoint more accessible by:
- Structuring documents using styles to define headings and text
- Using alternative (alt) text on images
All pdfs published after the 1st August 2013 have been made accessible. In addition to this the most frequently downloaded pdfs have also been made accessible. All pdf’s published after the 1st August 2013 have:
- Heading structure
- Alt text for images
- Been checked by the Adobe accessibility checker
- Pdfs of publications are all required to pass the Adobe accessibility checker before being signed off with the designers
- Large text or braille versions of publications are available on request
All AHRC multimedia content has either subtitles or transcripts available.
We use social media sites including Twitter, Facebook, Google+ and LinkedIn. As we have no control over the accessibility of these sites, we ensure that we don’t publish information purely through social media but that it is also published on the AHRC website.
Writing for the web
In addition to the actions outlined above, we have also run training sessions for staff in writing for the web and all staff have been provided with good practice guidelines.
To monitor the accessibility of our website we
- Use an accessibility checker
- Undertake manual checking by the web team
If you have any questions or would like further information please contact:
Philip Pothen, Head of Communications email@example.com
Tricia Brabham, Publications and Web Communications Officer firstname.lastname@example.org