To follow on from Perry's point... In the past I've found that some
agencies promise they'll create 'accessible' sites when they're pitching,
but somehow accessibility has dropped off the list by the time they deliver
the files. It'd be great if any external guidance or conditions took that
into consideration by outlining the best times and ways to incorporate
accessibility checking into general user acceptance testing. Realistically,
it can't require too much specialised knowledge, be too time-consuming, and
it must generate specific steps that an agency can take to meet the
standards required. (Also, I'd like the moon on a stick, please.)
Cheers, Mia
--------------------------------------------
http://openobjects.org.uk/
http://twitter.com/mia_out
Check out my book! http://bit.ly/CrowdsourcingCulturalHeritage
<http://bit.ly/CrowdsourcingCulturalHeritage>
I mostly use this address for list mail; my open.ac.uk address is checked
daily
On 5 February 2015 at 10:23, Bonewell, Perry <[log in to unmask]>
wrote:
> " So you could look at today's lack of focus on web accessibility by
> museums as resulting from the absence of a business argument as compelling
> as the ones sold by the native app marketeers."
>
> NOF made a decent fist of making accessibility a consideration by making
> it a condition for funding.
>
> It's a bit of an old saw for me on this list but I've witnessed scenarios
> where funders make no demands whatsoever.
>
> This is fine I guess if you have a team that values these requirements,
> but if you're a lone voice in an organisation and trying to make a case to
> "deaf ears" about how best to approach web projects and consider
> accessibility, usability and sustainability and so on, external guidance or
> conditions would be a tremendous help.
>
>
>
****************************************************************
website: http://museumscomputergroup.org.uk/
Twitter: http://www.twitter.com/ukmcg
Facebook: http://www.facebook.com/museumscomputergroup
[un]subscribe: http://museumscomputergroup.org.uk/email-list/
****************************************************************
|