Print

Send

Share

Slideshow of this presentation on SlideShare

Assessment of accessibility 1.0

Illustration of Web 1.0 and accessibility 1.0

International: single source

• Definition: Web Accessibility 1.0 (HTML + CSS + CMS with Flash and PDF).
• International Rules: a body ( W3C / WAI ) and a standard ( WCAG 2.0 ).
• Symbolic rule: put an alt to images.

France: a legal and methodological

• French standards: RGAA .
• National laws: mandatory accessibility of public websites (France: Article 47 of Law No. 2005-102 (February 11, 2005) + implementing decree No. 2009-546 (May 14, 2009) + Order of October 21, 2009 on the RGAA ).
• Methodological environment:
  • Administrative Authority: the "Interdepartmental Committee Disability" should establish a website and tools / guides.
  • Providers, training over 200 internet agencies with at least one person trained in the evaluation of accessibility guidelines.
  • Label Web 1.0 sites: Label AccessiWeb (association, not state).

Conclusion: Accessibility 1.0 is possible

• The Web Accessibility 1.0 (many public sector sites) is now possible.
• Why?
  • The rules are standardized.
  • Web 1.0 sites are characterized mainly by a centralized structure (control of Web pages hosted on the same server) and by a single author (editorial control). It is therefore possible to control their accessibility relative to standardized rules.
• This is a technical accessibility (application of rules on the code of a Web site upstream on the Web server) that does not require to take into account downstream uses on the client.
• Accessibility 1.0 application providers trained to WCAG 2.0. These training providers and these exist.

(1/3) The Web in 2009: the diversity of users and uses

Illustration of the diversity of Internet users

Audiences and purposes

• Disability:
  • Blind: using a screen reader ( JAWS , NVDA ...) with braille output and speech synthesis linear reading or paragraph headings or list of links; need a structured and semantic content; need seamless navigation.
  • Visually impaired: Use a screen magnifier ( ZoomText ...) with speech, reading by zooming; need good color contrast, a homogeneous structure and navigation and classic.
  • Deaf and hearing impaired: use of popular entertainment / Flash videos especially for people who sign; need videos with synchronized captions and a translator RSA.
  • Persons with mobility impairments: use the Tab key on the keyboard and web browser adapted; need coding logic of information and links avoidance.
  • People with cognitive disabilities: difficulty to the disability to visit the websites; need content as well as simple and clear illustrations.
• Seniors: multiplicity of needs based on disability and ownership of computers (large print, color contrasts, Web links away because of tremor, simple ergonomics, not an overload of information ...), the " Seniors and the Web "are under consideration by the W3C / WAI group in the WAI-AGE which includes Pierre Guillou ( Ideose ).
• et Talks ). Mobile user: simple websites can be used on small screens of mobile phones (compliance with WCAG 2.0 and Mobile Web Best Practices 1.0 ), others must be adapted (iPhone apps), the phones themselves must be accessible ( iPhone accessibility , screen readers for mobile phones as Mobile Speak and Talks ).
• Digital television, multimedia terminals ...: the methods of consultation and customization of its consultation multiply.

Conclusion: the diversity of public consultation and uses a web application multiple

• Diversity of audiences who browse the Web ...
• Variety of consultation tools Web (hardware and software) ...
• Diversity of needs and uses Web Consulting ...
• Need to be able to customize the display of Web content to fit their needs consultation.
• In 2009, take into account the diversity of audiences and purposes. The technical accessibility is not enough.
• The issue of accessibility is moving users (the flow of electronic data must be convertible at the computer of the Web).

(2/3) The Web in 2009: specialized services

• Specific services for people with disabilities: AccessTextNetwork (service in the U.S. that allows disabled students to get courses and books in a format suitable).
• The specific services for the visually impaired: RoboBraille (automatic conversion of documents in an accessible format and emailing), Previsite Platform (Firefox plugin to solve CAPTCHA OCR).
• Web for the deaf: News in LSF , telephone relay center (United States), service eSourds (EDF) .
• ...

Conclusion: Web Accessibility is more than the accessibility of websites!

Web accessibility is also Web services tailored to the needs of people.

(3/3) The Web in 2009: Web 2.0

Illustration of Web 2.0

Understanding Web 2.0

• Definition: "Web 2.0 is the set of technologies and uses the World Wide Web that followed the initial shape of the web, especially interfaces that allow users with little technical knowledge to interact with both simple the content and structure of pages but between them, including creating the social Web. "[ Web 2.0 on Wikipedia ]
• « ), blog (l'incrémental Web), wiki et non CMS, divers lecteurs Web et pas seulement les navigateurs Web, coopération et pas contrôle, API , widgets, mashups, AJAX . Keywords of Web 2.0 and an attitude not a technology, internet contributor, rich user experience, and participation not publishing, syndication and RSS feeds, interaction, Web platform, sharing, permanent beta, SEO and not domain name , data flows, data management, decentralization, tags and not categories (unlike folksonomy taxonomy), multiple Web sources ("long tail") and not just a few reference sites, a system without an owner, standard open, collective intelligence and wisdom of crowds ("wisdom of crowds"), blog (the incremental web), and not wiki CMS, various readers, not just Web browsers, not cooperation and control, APIs, widgets, mashups, AJAX.
• Web 2.0 tools: blogs, wikis, social bookmarking, social networks ...
• Emblematic examples: Wikipedia , Google Reader , Google Maps , Netvibes , Flickr , Delicious , Facebook .
• Web 2.0 is evolving towards the "Real Time Web": Twitter , Google Wave ...

Conclusion: Web 2.0 decentralizes Web site owners Web (Web 1.0) to users

Web services are becoming more and more Web 2.0 services. In 2012, the information "Real Time Web" will occupy 25% of the Web. These services and information are they and are they accessible?

Problems and solutions to accessibility of Web 2.0

Illustrations of accessibility solutions Web 2.0

Problems for Web accessibility 2.0

• Dynamic content: modification of traffic patterns that may lead to destabilization.
• The Internet user technical support is not warned: update of data fields without reloading the page,
• No editorial control: updated content by Internet users and not by the site owner (compared to 1.0 websites).
• The entire web interface is interactive (web) while technical aids only recognize the buttons and links as object interaction (very low accessibility to the keyboard).
• Change interaction mechanisms (examples: data is saved as and when they are typed and not after submitting a form, you can rearrange the positioning information from the mouse).
• Deconstruction of the notion of "website": each user can create the website using the same data flow thanks to the widgets and mashups.
• Many ways to use a Web 2.0 service: unlike the Web 1.0 sites, the user must define its own use of a Web 2.0 service.
• CAPTCHA: all characters in the form of an image without alternative.
• Language not clear and explicit: the @ replies, and DM on Twitter hastag eg texting or unexplained acronyms.

Solutions for Web Accessibility 2.0: no single solution

• Usability: If accessibility problems exist for Web 2.0, it should also be noted that many Web 2.0 services are simpler and more intuitive to use for many users (best design, which is very important for the use ).
• Make available the code: the information must have a valid code and comply with accessibility rules of W3C / WAI ( WCAG 2.0 ) for Web applications, you must apply the rules WAI-ARIA (accessibility guidelines defined by W3C / WAI to make accessible Web Services using AJAX), and there is AxsJAX (ARIA script library defined by Google and to make available at the server level or on a Web service client using AJAX).
• Rely on a community: Social Accessibility Project (social network allowing real-time correction of any web page accessibility by authorized users), Scripting Enabled (community of developers creating alternatives available to existing Web 2.0 services like YouTube, Flickr or SlideShare).
• Develop alternative Web services: Web 2.0 services give control of its flow of information to the user (eg RSS feeds from blogs that allow the user to read blog entries not on the website issuer but in the reader's choice), it is then possible to as many suitable reader developer of these information flows that are required consultation ( Accessible Twitter , Accessible Interface to YouTube , Easy YouTube , Flickr Easy , Easy SlideShare ).
• Deploy automation solutions on the accessibility of existing services: Automatic captions in YouTube .
• Personalization and error compensation Accessibility Web services existing at the client: GreaseMonkey .

Conclusion: Web 2.0 is a chance for accessibility ... but requires a new industry structure (methods, training, customized services, social networks to access, etc..)

• The accessibility of Web 2.0 requires increased technical competence and consideration of uses.
• The only knowledge of HTML and WCAG 2.0 is not sufficient (necessary but not sufficient).
• You have to study and focus its development on Web 2.0 and user interactions.
• It should (sometimes) develop alternatives or give the user the tools to change the behavior of a Web service directly into its client.
• It is therefore an Accessibility 2.0 compared with 1.0 website accessibility.

Summary: accessibility includes accessibility 2.0 1.0

• Accessibility 1.0 is necessary because there are still many websites 1.0. It is becoming well known and training courses and providers exist.
• But the Web today is also:
  • a wide variety of audiences with special needs,
  • specialized Web services, not just sites,
  • information flows and Web 2.0 rather than static sites.
• New methods of access and approach both more technical and taking into account the uses are required: this is the accessibility 2.0!
• The training program methodologies and providers accessibility 2.0 yet developed.