On 21-22 June 2011 UKOLN’s DevCSI project is organised the #a11y hackspace event, which is described as “A two day workshop bringing developers, accessibility (a11y) users and experts together to hack on ideas, prototypes and mashups, while exploring the challenges in providing usable accessibility“.
It seems to be that this event could provide an ideal opportunity for developers with an interest in accessibility to explore solutions and approaches which could be used in the context of the BS 8878 Code of Practice on Web accessibility (which is summarised on the AbilityNet Web site).
In a post on Web Accessibility, Institutional Repositories and BS 8878 I have previously described how the 16 steps defined in BS 8878 could be applied in the context of defining the accessibility policies and processes for enhancing the accessibility of institutional buy topamax uk repositories. One of the steps is to “Assure the Web products accessibility through production (i.e. at all stages)“. I suggested that this could be addressed by use of tools to monitor the extent to which PDFs hosted in institutional repositories are conforming with accessibility guidelines for PDFs. This suggestion was based on a paper on “Supporting PDF accessibility evaluation: Early results from the FixRep project” which I described in a blog post last year. Might there be an opportunity for developers to build on this initial work, I wonder?