For ARIA, and a look at how accessibility works with interactive content,
I'd recommend Artur Ortega's talk where he demo's VoiceOver on his iPhone,
and gives an overview of how he built accessibility into Yell's web site.
http://vimeo.com/51952723
The basic ideas haven't changed: Start with well-structured HTML, add ARIA
landmarks for page navigation, use ARIA roles and states to expose
javascript widgets to the accessibility API, use progressive enhancement so
the experience isn't totally broken if the CSS or JavaScript fails. Test
with a mix of users and assistive technologies if you can.
Cheers
Jim
On 30 January 2015 at 06:49, Dave Gerrard <[log in to unmask]> wrote:
> Hi Nick,
>
> I think the web has given us more accessibility with one hand: namely the
> things you refer to in your message, e.g. - "XHTML", properly-formed
> semantically well designed documents etc. But it has taken away
> accessibility with the other hand with the introduction of AJAX / REST and
> JavaScript frameworks such as JQuery etc, and the general rise of
> JavaScript as a programming language and browsers almost becoming de-facto
> Operating Systems (or in the case of Chromebook, not even de-facto). The
> ease at which apps / web pages can incorporate JQuery etc these days might
> tend to emphasise interactivity over content, and in so doing they run a
> definite risk of making content inaccessible.
>
> I must confess my accessibility knowledge is quite out of date, but this
> discussion prompted me to take a virtual stroll over to the W3C and take a
> look. Back in the days when I used to build websites for a living, the W3C
> used to have a partner set of standards to WCAG called WAAG (Web
> Application Accessibility Guidelines). By their very nature these were more
> complicated and deeper than the guidelines for making content accessible,
> but they were there and could be referred to. From the looks of things,
> these have been migrated to the WAI-ARIA (Accessible Rich Internet
> Application) guidelines now:
> http://www.w3.org/standards/techs/aria#w3c_all.
>
> My point being - the guidance for making rich interactive content is out
> there too. It's by definition denser and harder to get into than WCAG, but
> it is there, so people should refer to it (indeed, you could be
> contravening the DDA if you don't, though personally I think the moral
> responsibility to make more interactive apps accessible should be a more
> pressing concern than the legal one).
>
> Cheers,
>
> Dave
>
>
> ________________________________________
> From: Museums Computer Group [[log in to unmask]] on behalf of Nick Poole
> [[log in to unmask]]
> Sent: 29 January 2015 09:26
> To: [log in to unmask]
> Subject: Is Web Accessibility still a thing?
>
> Dear MCG'ers,
>
> The discussion over the past few days has prompted me to return to the
> question of where 'web accessibility' fits into peoples' priorities these
> days.
>
> Back in the day, when the Disability Discrimination Act was fresh and new
> and initiatives like Bobby and the W3C Web Content Accessibility Guidelines
> were in the ascendant, we spent lot of time beating ourselves up about
> 'AAA' or 'AA' compliance.
>
> Then, slightly inevitably, there was a bit of a backlash as people came to
> realise that machine-processed accessibility was not the same as human
> accessibility. At roughly the same time, the dominant narrative came to be
> about Universal Design and the idea that rather than designing specific
> experiences for specific audiences, we ought to be using web standards
> (HTML4 and CSS - remember them!?) to create universally accessible, liquid
> interfaces that played nice on screens and mobiles. I sat in a *lot* of
> meetings with web development companies who would eye roll when web
> accessibility came up and then dismiss it with 'our world-class coders make
> code that's so silky smooth, it laughs at your puny guidelines'.
>
> Now, with the power and flexibility of HTML5 and the rise of mobile-first,
> responsive design, we certainly have much nicer interfaces (generally
> speaking). Screen readers are smarter, their users more experienced and
> fiddly keys are gradually being replaced by the elegance of swipe and pinch.
>
> I worry, though, that accessibility in general, and more specifically
> taking positive and proactive steps to meet users halfway if they have
> specific needs, has taken something of a back seat. I heard yesterday that
> the number of museums with 'provisional' as opposed to full Accreditation
> status has increased significantly, and that many are being asked to
> improve both their access provision and the quality of information they
> provide about accessibility - which increasingly means online.
>
> I am hoping that people are going to tell me that web accessibility, both
> in a 'universal' and a specific sense, is still high on the list when you
> are specifying and developing web projects, but it has been a long time
> (until this thread) since I have seen anyone talk about it as a
> high-profile commitment - with the obvious exception of the excellent work
> of the Jodi Awards. Also, while I have seen people mention technical (ie.
> web standards) accessibility, I really haven't seen anything about
> intellectual accessibility since around 2004.
>
> So - my question to the list: is web accessibility still a thing? If not,
> why not? If so, has it simply gone to ground as an embedded part of the
> development process?
>
> All best,
>
> Nick
>
> Nick Poole
> Chief Executive
> Collections Trust
> Tel: +44 (0)20 7942 6080
> [log in to unmask]<[log in to unmask]>
>
> [cid:image001.gif@01CFF4F4.61308100]<
> http://www.collectionstrust.org.uk/copyright-seminar/copyright-seminar-2015
> >
>
> [ct-logo-cmyk]<http://www.collectionstrust.org.uk/>
>
> [http://www.beaconmm.com/wp-content/uploads/2013/06/linkedin1.png]<
> http://www.linkedin.com/groupItem?view=&gid=3280471&type=member&item=127734931&qid=f3e77705-7ec2-44c7-99db-7fe325bb16fc&trk=group_most_recent_rich-0-b-ttl&goback=%2Egmr_3280471>Join
> Collections Trust's Collections Management Group<
> http://www.linkedin.com/groupItem?view=&gid=3280471&type=member&item=127734931&qid=f3e77705-7ec2-44c7-99db-7fe325bb16fc&trk=group_most_recent_rich-0-b-ttl&goback=%2Egmr_3280471
> >
> [https://twitter.com/images/resources/twitter-bird-white-on-blue.png]<
> http://www.twitter.com/collectiontrust>Follow us on Twitter<
> http://www.twitter.com/collectiontrust>
> [cid:image005.jpg@01CF3DD3.15EED080]<
> https://www.facebook.com/hiddentreasuresuk?ref=hl>Like us on Facebook<
> https://www.facebook.com/hiddentreasuresuk?ref=hl>
>
> www.collectionstrust.org.uk. Company Registration No: 1300565 Registered
> Charity No: 273984
> Registered Office: Collections Trust, WC 209, Natural History Museum,
> Cromwell Road, London, SW7 5BD
>
>
> ****************************************************************
> 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/
> ****************************************************************
> ****************************************************************
> 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/
> ****************************************************************
>
****************************************************************
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/
****************************************************************
|