Accessibility in a Web 2.0 World

Download Accessibility in a Web 2.0 World

Post on 22-Jan-2016

32 views

Category:

Documents

0 download

Embed Size (px)

DESCRIPTION

Accessibility in a Web 2.0 World. (get a straw). Shawn Henry, W3C WAI. Topics. Components ATAG WCAG 2.0 Dynamic applications Scripting, AJAX, RIA (rich Internet applications) Handouts: Expanded version Additional URIs. You ?. W3C WAI ? WCAG 1.0 ? WCAG 2.0 ? ATAG ? Screen readers ? - PowerPoint PPT Presentation

TRANSCRIPT

  • Accessibility in aWeb 2.0 WorldShawn Henry, W3C WAI(get a straw)

  • TopicsComponentsATAGWCAG 2.0Dynamic applicationsScripting, AJAX, RIA (rich Internet applications)Handouts:Expanded versionAdditional URIs

  • You ?W3C WAI ?WCAG 1.0 ?WCAG 2.0 ?ATAG ?Screen readers ?AJAX ?Heard ofKnowfairlywell

  • Want to know about:Whats accessibility all about ?WCAG 2.0 ?Scripting, AJAX ?

  • W3C WAIWorld Wide Web Consortium (W3C)InternationalDevelops Web standards (HTML, CSS, )Web Accessibility Initiative (WAI)Develops Web accessibility guidelines, international standardswww.w3.org/WAI/

  • Components of Web AccessibilityUser Agent (UAAG)Authoring Tool (ATAG)Web Content (WCAG)

  • www.w3.org/WAI/intro/componentsUser Agent (UAAG)Authoring Tool (ATAG)Web Content (WCAG)

  • Weak ComponentsCause Accessibility Barriers

  • The Powerful Impact ofHigh Quality Components

  • Authoring Tools Support

  • ACTION !Actively encourage improvements in authoring toolsWAI resources:Authoring Tool Accessibility Guidelines (ATAG)Selecting and Using Authoring Tools for Web Accessibility

  • ACTION !Actively encourage improvements in authoring toolsWAI resources:Authoring Tool Accessibility Guidelines (ATAG) www.w3.org/WAI/intro/atagSelecting and Using Authoring Tools for Web Accessibility www.w3.org/WAI/impl/software

  • Whats New with WCAG TwoApplies to more advanced Web technologiesMore precisely testable (still need human)Adaptable for situations (Baseline)Extensive supporting materials, practical implementation

  • WCAG 1.0

    GuidelinesCheckpoints Priority 1, 2, 3

    WCAG 2.0PrinciplesGuidelinesSuccess Criteria Level 1, 2, 3

  • PrinciplesPerceivableOperableUnderstandableRobust

  • Testable, Levels ExampleWCAG 1.0 Checkpoint 2.2 Ensure that foreground and background color combinations provide sufficient contrast when viewed by someone having color deficitsWCAG 2.0 Success Criteria1.4.1 Text or diagrams, and their background, have a luminosity contrast ratio of at least 5:1 [Level 2]1.4.3 Text or diagrams, and their background, have a luminosity contrast ratio of at least 10:1 [Level 3][Level 2]

  • WCAG 2.0 Supporting DocumentsOverview of WCAG 2.0 DocumentsTechniques for WCAG 2.0 WDWCAG 2.0 Quick Reference WD Understanding WCAG 2.0 WD ComingHow to make accessible tables, forms, Quick Tips UI

  • WCAG 2.0 Supporting DocumentsOverview of WCAG 2.0 Documents www.w3.org/WAI/intro/wcag20Read this firstProvides foundationUpdated with changesLinks to Frequently Asked Questions (FAQ), W3C ProcessTechniques for WCAG 2.0 WDWCAG 2.0 Quick Reference WDCustomizableSuccess CriteriaSufficient Techniques

  • WCAG 2.0 Supporting DocumentsUnderstanding WCAG 2.0 WD Intent of the success criterionKey termsTechniquesCommon failuresExamplesBenefits, how it helps people with disabilitiesComingHow to make accessible tables, forms, UI

  • When? Public Working DraftsLast Call Working Draft Candidate RecommendationImplementations Proposed Recommendation W3C Recommendation=Web Standard

  • TransitioningMost sites that conform to WCAG 1.0 should not require significant changes See WCAG 2 FAQSupport: "How WCAG 2.0 Drafts Differ from WCAG 1.0" sectionComparison of WCAG 1.0 Checkpoints to WCAG 2.0Transitioning Web SitesTransitioning Accessibility Policies

  • TransitioningMost sites that conform to WCAG 1.0 should not require significant changesAccessibility issues basically the sameDifferent approach takes some time to learnSupport: "How WCAG 2.0 Drafts Differ from WCAG 1.0" sectionComparison of WCAG 1.0 Checkpoints to WCAG 2.0Transitioning Web SitesTransitioning Accessibility Policies

  • Baseline in WCAG 2.0Heard ofTried to understand

  • Understanding BaselineFirst, WhyFlexibility for different situations todayFlexibility over timeFor example, SVG (Scalable Vector Graphics)

    WCAG Working Group is refining (expect some changes)

  • BaselineList of technologies For example: HTML, CSS, etc...That are accessible, that users have availableAn established list of Web technologies that an author can use to create accessible Web contentCan use technologies outside of baseline, if content is usable withoutThat is, used for enhancement

  • Questions ?ComponentsATAGWCAG 2.0BaselineDynamic applicationsScripting, AJAX, RIA(coming up: additional slides since handout)

  • TopicsComponentsATAGWCAG 2.0BaselineDynamic applicationsScripting, AJAX, RIA(coming up: additional slides since handout)

  • Scripting, AJAX, RIAGood news with WCAG 2 !Baseline

  • Scripting Tips for AccessibilityDo automatic redirects on server side, instead of client sideDevice independence, e.g., onmouseover & onfocusmousedown& keydownclick & keypressmouseover& focusmouseout& blurTechniques for WCAG 2.0 Client-side Scripting Techniques

  • AJAXAccessibilityUsability general, for allUser doesnt know updates will happen autoUser doesnt notice updatesUser cant find updated infoUnexpected change in focusBack button breaksCant bookmark

  • Demo: WCAG 2.0 Quick Reference

  • AJAX Temperature GaugeNot just cool, hot? Really useful to users?Approach DISCLAIMER: not endorse, others too, the hows and whys of degradable ajaxProgressive enhancement with Ajaxfirst build your app using old-fashioned server-side technology once youve got that built, you can then apply JavaScriptprogressive enhancement [is] how we should all be building our web apps Jeremy Keith

  • AJAXAccessibilityUsability general, for allUser doesnt know updates will happen autoUser doesnt notice updatesUser cant find updated infoUnexpected change in focusBack button breaksCant bookmark

  • Straw ActivitySome people have a very small field of vision -- called tunnel vision. Imagine using a complex Web page like this

  • Screen Magnification

  • AJAXAccessibilityUser doesnt know updates will happen autoUser doesnt notice updatesUser cant find updated infoUnexpected change in focus cant read pageBack button breaksCant bookmark

  • AJAXAccessibilityUser doesnt know updates will happen autoUser doesnt notice updatesUser cant find updated infoUnexpected change in focus cant read page

  • Whaddyado for NowExplain interactionProvide options (default least problematic!)Manual updateNotifications (e.g., dialog box)Draw attention (e.g., yellow fade technique)Set focusAvoid automatic focus change (usually)

  • More Whaddyado for Now and proper markupProvide navigation to changesExample: The DOM and Screen Readers (Juicystudio) Errors from Form Validation DISCLAIMER: not endorse, others too,

  • Whaddyado for LaterARIA Suite for Accessible Rich Internet Apps from W3C WAI Protocols & Formats WGSome implementations already

  • Accessibility for Dynamic ApplicationsCreate desktop-style widgets for Web e.g., tree controlKeyboard nav (w/o excessive Tab) (benefit keyboard power users)Notification of updates

  • Dynamic ApplicationsDISCLAIMER: not endorse, others too, AJAX Accessibility Overview, Becky Gibson, IBMW3C Announces Roadmap for Accessible Rich Internet Applications (WAI-ARIA) press releaseCall for Review: Accessible Rich Internet Applications (WAI-ARIA) Working Drafts e-mailARIA Overview (coming soon)www.w3.org/WAI/ Highlights

  • Dynamic ApplicationsW3C Announces Roadmap for Accessible Rich Internet Applications (WAI-ARIA) press releaseCall for Review: Accessible Rich Internet Applications (WAI-ARIA) Working Drafts e-mailARIA Overviewwww.w3.org/WAI/ Highlights

  • Example

  • And soWCAG 2.OBetter for developersBetter accessibilityDynamic ApplicationsBe a showcase: Get attention, get help

  • More:Tomorrow 2:00 Accessibility: Better, Faster, CheaperResponsibilitiesBusiness CaseBlack, White, GrayCollaborators with DisabilitiesDemosUnderstanding Web Accessibility book chapter www.uiaccess.com/understanding.html

    @@ save to USB & /or CD. AND Web :LATERPREP: read through NotesLOW: what more do people need to know here?PRINT: NOAsk: authoring tools, also CMS, blog, flickr, myspaceLater: crisper image (next slide too)PRINT: yesProject: hideSAY: bad: developers work harder, less accessible sites1,000 tool developers, billions of content producersSAY: Tools facilitate accessibilityLess knowledge requiredBetter accessibility for less effortLATER: add example(s)Note: Talk more about tomorrow

    PRINT: NO

    PRINT: yesProject: hideSAY: Applies to more advanced Web technologies current, future, and non-w3c@@ add notes & on printoutLATER: BuildsNote:Overview published July 2005Guidelines are technical standards

    @LOW: make the check mark a separate text box that disappears with next itemPRINT: NOPRINT: yesProject: hidePRINT: yesProject: hide

    LATER: builds Notes:"Last Call Working Draft is where the working group thinks that they have addressed all known issues and that the document is stable. - During LCWD, WAI pushes the document out very broadly for review (& I ad lib 'which by the way we did already for three or four previous working drafts'), from as many potential adopters, implementors, and interested parties as possible. - During WCAG 2.0 LCWD, we received broad comment & review, which is what we were hoping. - The working group then reviews and responds to each of the comments that it has received, and makes adjustments to the working draft where necessary. - If those adjustments result in substantial changes, then the working group may need to issue a second last call. - The next formal stage is Candidate Recommendation, where..." - JB email with extension: however it is followed by another stage, Candidate Recommendation, where reviewers can submit comments based on implementations of WCAG 2.0; then by Proposed Recommendation, when W3C Members review it for approval as a Recommendation. - e-mail original Call for Review: * Candidate Recommendation - when the WCAG WG will collect implementation experience on use of WCAG 2.0 to design and evaluate Web content for accessibility;* Proposed Recommendation - when W3C will seek endorsement of the specification from W3C Member organizations;* http://www.w3.org/2005/10/Process-20051014/tr.html#ReportsCandidate Recommendation (CR)A Candidate Recommendation is a document that W3C believes has been widely reviewed and satisfies the Working Group's technical requirements. W3C publishes a Candidate Recommendation to gather implementation experience.Proposed Recommendation (PR)A Proposed Recommendation is a mature technical report that, after wide review for technical soundness and implementability, W3C has sent to the W3C Advisory Committee for final endorsement.W3C Recommendation (REC)A W3C Recommendation is a specification or set of guidelines that, after extensive consensus-building, has received the endorsement of W3C Members and the Director. W3C recommends the wide deployment of its Recommendations. Note: W3C Recommendations are similar to the standards published by other organizations.SAY: FAQ whenPRINT: NOPRINT: yesProject: hideLATER: BuildsSay: remember until user agent clauses in WCAG 1.0 ?LATER: Buildswww.w3.org/wai/wcag20/baseline/LATER: delete the crossed out textNotes:dynamic, incremental updates are a paradigm shift of Web usagepeople are not always expecting this new behaviorpeople might not notice the actual change in data/content

    @LOW: image for shift gearsPREP: Queue up WCAG 2.0 Quick ReferenceNotes:show that was expecting [Submit] buttonmissing feedbacklooking at incorporating feedbackminor usability major accessibilityDELETE for PRINT versionLATER: update this example to modern page from UIAccess Just Ask!PREP: Queue up screen magnifier videoNotes:imagine reading first paragraph of page, then update moves focus elsewhere. disoriented & has to find way back to where was reading. then does it again, etc. and she cant even read the page :/problems can be exacerbated for people who use AT *and* people with cognitive disabilities(can also be beneficial for people with disabilities, including screen reader users and people with cognitive disabilities by providing progressive disclosure, limiting options to those needed, etc.)Print: NODisplay: yes

    Print: YESDisplay: HIDEPREP: Queue up pages in Opera & HPRSAY at WDW: will demo tomorrowNotes:W3C WAI PF, IBM, Mozilla FoundationFirefox 1.5Window Eyes 5.5Yahoo!, AOL(Becky Gibson, Rich Schwerdtfeger)PRINT: NONotes:role and state informationcreate alert notification & text descriptions (read by screen reader)

    PRINT: yesProject: hideLATER: for print page: add linksPRINT: yesProject: hideLATER: check flow with previous slides for project & printlater