• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
corePHP Usability Accessibility by Steven Pignataro
 

corePHP Usability Accessibility by Steven Pignataro

on

  • 2,186 views

corePHP Usability Accessibility by Steven Pignataro presentation given at CMS Expo in Denver, December 2008.

corePHP Usability Accessibility by Steven Pignataro presentation given at CMS Expo in Denver, December 2008.

Statistics

Views

Total Views
2,186
Views on SlideShare
2,186
Embed Views
0

Actions

Likes
1
Downloads
27
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Welcoming Let me first introduce myself. I am Steven Pignataro CEO and co-owner of ‘corePHP’. ‘corePHP’ has been in existence since 2001 and we pride ourselves in the quality development and services that we provide. I am one of the oldest members of the Joomla! Community - no not of my age but of the projects age. I was part of the original team for Mambo development. With this I have spent most of my time researching and developing concepts for the project, helping others through development, marketing of the project, and forum administration. In 2006 I stepped down from the project. Today ‘corePHP’ provides training, support, custom development for Joomla!, print design, high quality template designs, data recovery, and enterprise level digital signage software solutions. So with all the above things that we do - I hope that throughout this presentation you will learn what we have learned over the past 8-10 years - or more then 100+ combined years of experience within our company (it just sounds funny if you think about it).

corePHP Usability Accessibility by Steven Pignataro corePHP Usability Accessibility by Steven Pignataro Presentation Transcript

  • Usability and Accessibility Steven Pignataro CEO
  • CONTENTS
    • Fill in with all the content that will be discuss throughout - just a brief overview - last thing to do.
  • Defining Usability How usable is this presentation?
  • What is Usability?
    • Designers and Developers ensure that websites work well and a person of average (or lower) ability and experience can properly use it.
    • Provide to the end user a easy navigation system that allows for many different ways of getting to content.
  • Examples of Bad Usability
    • http://www.havenworks.com/
    • http://www.5safepoints.com/
    • http://www.lbl.org/Home.html
  • Good Examples of Usability
    • http://www.apple.com
    • http://www.google.com
    • http://www.theonion.com
    • http://www.amazon.com
  • So why care about Usability?
    • Increased productivity (for the user)
    • Decreased training and support costs
    • Increased enrollment (sales and revenues)
    • Reduced development time and costs
    • Reduced maintenance costs
    • Increased customer satisfaction
  • The usable way
    • Don’t make the end user think!
    • As much as possible, when you look at a website, It should be self-evident. Obvious. Self Explanatory. To the point. Pop-out. (you get the picture)
    • If the user has to extend or exert extra effort to complete a task, then you can still refine your efforts to make the task easier.
  • Which is a button?
    • The example to the right shows 3 different buttons. As an end user which looks like a button to you?
    • We have the underline for text hyperlinks.
  • How do you view a site?
    • Raise you hand if you read a web site? If anyone in this room raises there hand - Steven (the presenter) has full right to grab you by your undies and pitch you outside in the snow.
  • We do not read sites!
    • Yep you read the title right - we do not read sites. We scan them. 9 out of 10 users will scan a site to find the information they are looking for.
  • How you (designer) reads a site!
  • How user (not you) reads the site!
  • How the Zen Penguin reads the site!
  • The users point of view
    • A user will look for anything that is off there interest and move on.
    • Pretty much find something that vaguely resembles what they are searching for.
  • What will help?
    • Site identification (site logo and tagline)
    • Page name
    • Sections and sub-sections (global navigation)
    • Local navigation
    • “You are here” indicators (breadcrumbs)
    • Search
  • Visual See It!
  • Get feedback
    • If you do not get user feedback on the work you do then the work done is not 100% usable. As developers we sometimes get lost into code / design / etc that we forget the basics and need to be slapped a bit in order to make things easier for people. JUST TEST IT!!!
  • Test Drive that new Porsche
    • You test a car before you drive it? So test your site before you deploy it!
  • Accessibility What am I see?
  • What is web accessibility
    • It’s about making websites accessible to all people with disabilities as well as to people using different operating systems, web browsers and devices.
    • More specifically, web accessibility means that people with disabilities can perceive, understand, navigate, and interact with the web. Web accessibility also benefits others, including older people with changing abilities due to aging.
  • Starting with Accessibility
    • Practice of making web pages on the Internet accessible to all users, especially those with disabilities.
    • You cannot use something if you do not have access to it.
    • Make your site accessible by following the web standard by w3c - http://www.w3.org/pany.
  • Rafael - The Penguin: Hard at work! Rafael waking Kobby up to Learn Accessibility
  • Totally not accessibly to users! Why make your site that way?
  • Why is Web Accessibility Important?
    • Firstly, it is now a law. June 21st 2001 new rules where mandated and applied to websites operated by the federal government agencies. Higher education is also moving towards accessible designs for there web sites.
    • Secondly, it is the right thing to do. By providing access to web-based information to others with disabilities you provide a better site over all.
    • Lastly, it is great strategy. This allows you to provide your site in a very mobile format.
  • Why Cont.
    • Accessible design improves maintainability and efficiency of sites. By separating structure and presentation and style sheets you can easily change the look of a site by modifying one file. It is just forward thinking.
    • Techniques like using style sheets, color independence, and avoiding deprecated elements makes web content more readily available to the changing which is nice considering the constant change in technology.
  • What type of users?
    • Blind users: web users who have no sight may utilize a screen reader. This type of software reads the content of the web page, or rather the HTML, back to them. This sites between the user and the browser, sifts through the HTML markup and deciphers the technology to what should be read aloud and what should be ignored.
    • Partial or poor sight users: Users that enlarge text within there browsers. Users may also us the built in screen magnifiers.
  • Users Cont.
    • Deaf Users: These users are able to access the internet in much the same way as non-deaf people with one key exception - AUDIO content. Be sure to provide written transcripts for some of your content if video recorded.
    • Keyboard/voice only users: some users may not have the ability to use a mouse.
  • Making the Web Accessible:
    • Making a site accessible generally means using HTML to structure data properly and make sure you add accessibility features where relevant.
  • Three Key Steps:
    • Step One:
      • Learn and follow established accessibility guidelines and standards.
      • Section 508 Guidelines (1194.22 Standards)
  • Three Key Steps: Cont.
    • Step Two:
      • Validate your HTML and CSS code to be sure that it is error-free and complies with the federal standards. A key to accessibility is to design for device independence, so that your pages work on any device, that supports the openly published standards. The existence of standards such as HTML 4, XHTML and CSS makes this a possibility. Error-free, well-formed, standards-compliant HTML is the foundation of an accessible web site. The more a page is edited and re-edited in a WYSIWYG program, the more syntax errors will creep in. Many WYSIWYG programs generate tag soup. This is particularly true if the author is an HTML novice or is paying more attention to the page's visual presentation than to its underlying structure.
  • Three Key Steps: Cont.
    • Step Three:
      • Evaluate the pages in your site with accessibility tools. Here are some tools that can help:
        • ATRC Web Accessiblity Checker: http://checker.atrc.utoronto.ca
        • WAVE - This tool helps people perform design tasks that require human judgment. The Wave displays the ALT text of images and areas on the page for comparison with the images, provides numbered arrows to show the linearized reading order, and shows the HTML equivalent provided for applets.
  • Here are some tools that can help:
    • W3C HTML Validator - Checks HTML documents for conformance to W3C HTML and XHTML recommendations and other HTML standards. It is important to use the HTML validator to create documents that validate to publish formal grammars.
      • W3C CSS Validation Service - Checks Cascading Style Sheets for conformance to standards.
      • HTML TIDY - Tidy is a free lint utility to check and clean up badly formed HTML. It is useful as a first-pass for helping to fix bad HTML.
  • How to be the user
    • A graphical user interface (GUI) browser. These can be helpful for accessibility evaluation also. Examine your pages while adjusting the browser settings.
      • Turn off images
      • Turn off the sound
      • Turn off scripting
      • Change the font size (larger and smaller)
      • Change the display color to black and white and observe whether color contrast is adequate.
      • Put away the mouse and tab through the links and form controls on a page.
  • Priority list - Priority 1
    • Provide a text equivalent for every non-text element This includes: images, graphical representations of text image map regions, animations, applets and programmatic objects, ascii art, frames, scripts, images used as list bullets, spacers, graphical buttons, sounds, stand-alone audio files, audio tracks of video, and video.
    • Ensure that all information conveyed with color is also available without color, for example from context or markup.
    • Clearly identify changes in the natural language of a document's text and any text equivalents.
  • Priority list - Priority 1 - Cont.
    • Organize documents so they may be read without style sheets. For example, when an HTML document is rendered without associated style sheets, it must still be possible to read the document.
    • Ensure that equivalents for dynamic content are updated when the dynamic content changes.
    • Until user agents allow users to control flickering, avoid causing the screen to flicker.
    • Use the clearest and simplest language appropriate for a site's content.
  • Priority list - Priority 1 - Cont.
    • And if you use tables (Priority 1)
      • For data tables, identify row and column headers.
      • For data tables that have two or more logical levels of row or column headers, use markup to associate data cells and header cells.
  • Priority list - Priority 1 - Cont.
    • And if you use frames (Priority 1)
      • Title each frame to facilitate frame identification and navigation.
    • And if you use applets and scripts (Priority 1)
      • Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported. If this is not possible, provide equivalent information on an alternative accessible page.
  • Priority list - Priority 1 - Cont.
    • And if you use multimedia (Priority 1)
      • Until user agents can automatically read aloud the text equivalent of a visual track, provide an auditory description of the important information of the visual track of a multimedia presentation.
      • For any time-based multimedia presentation synchronize equivalent alternatives with the presentation.
  • Priority list - Priority 1 - Cont.
    • And if all else fails (Priority 1)
      • If, after best efforts, you cannot create an accessible page, provide a link to an alternative page that uses W3C technologies, is accessible, has equivalent information, and is updated as often as the inaccessible page.
  • Priority list - Priority 2
    • Ensure that foreground and background color combinations provide sufficient contrast when viewed by someone having color deficits or when viewed on a black and white screen.
    • When an appropriate markup language exists, use markup rather than images to convey information.
    • Create documents that validate to published formal grammars.
    • Use style sheets to control layout and presentation.
    • Use relative rather than absolute units in markup language attribute values and style sheet property values.
  • Priority list - Priority 2 - Cont.
    • Use header elements to convey document structure and use them according to specification.
    • Mark up lists and list items properly.
    • Mark up quotations. Do not use quotation markup for formatting effects such as indentation.
    • Ensure that dynamic content is accessible or provide an alternative presentation or page.
    • Until user agents allow users to control blinking, avoid causing content to blink.
  • Priority list - Priority 2 - Cont.
    • Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages.
    • Until user agents provide the ability to stop auto-redirect, do not use markup to redirect pages automatically. Instead, configure the server to perform redirects.
    • Until user agents allow users to turn off spawned windows, do not cause pop-ups or other windows to appear and do not change the current window without informing the user.
    • Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported.
  • Priority list - Priority 2 - Cont.
    • Avoid deprecated features of W3C technologies.
    • Divide large blocks of information into more manageable groups where natural and appropriate.
    • Clearly identify the target of each link.
    • Provide metadata to add semantic information to pages and sites.
    • Provide information about the general layout of a site.
    • Use navigation mechanisms in a consistent manner.
  • Priority list - Priority 2 - Cont.
    • And if you use tables (Priority 2)
      • Do not use tables for layout unless the table makes sense when linearized.
      • If a table is used for layout, do not use any structural markup for the purpose of visual formatting.
    • And if you use frames (Priority 2)
      • Describe the purpose of frames and how frames relate to each other if it is not obvious by frame titles alone.
  • Priority list - Priority 2 - Cont.
    • And if you use forms (Priority 2)
      • Until user agents support explicit associations between labels and form controls.
        • Associate labels explicitly with their controls.
    • And if you use applets and scripts (Priority 2)
      • For scripts and applets, ensure that event handlers are input device-independent.
      • Until user agents allow users to freeze moving content, avoid movement in pages.
  • Priority list - Priority 2 - Cont.
      • Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies.
    • Ensure that any element that has its own interface can be operated in a device-independent manner.
    • For scripts, specify logical event handlers rather than device-dependent event handlers.
  • Priority list - Priority 3
    • Specify the expansion of each abbreviation or acronym in a document where it first occurs.
    • Identify the primary natural language of a document.
    • Create a logical tab order through links, form controls, and objects.
    • Provide keyboard shortcuts to important links.
    • Until user agents render adjacent links distinctly, include non-link, printable characters between adjacent links.
  • Priority list - Priority 3 - Cont.
    • Provide information so that users may receive documents according to their preferences.
    • Provide navigation bars to highlight and give access to the navigation mechanism.
    • Group related links, identify the group (for user agents), and, until user agents do so, provide a way to bypass the group.
    • If search functions are provided, enable different types of searches for different skill levels and preferences.
  • Priority list - Priority 3 - Cont.
    • Place distinguishing information at the beginning of headings, paragraphs, lists, etc.
    • Provide information about document collections.
    • Provide a means to skip over multi-line ASCII art.
    • Supplement text with graphic or auditory presentations where they will facilitate comprehension of the page.
    • Create a style of presentation that is consistent across pages.
  • Priority list - Priority 3 - Cont.
    • And if you use tables (Priority 3)
      • Provide summaries for tables.
      • Provide abbreviations for header labels.
      • Until user agents render side-by-side text correctly, provide a linear text alternative for all tables that lay out text in parallel, word-wrapped columns.
    • And if you use forms (Priority 3)
      • Until user agents handle empty controls correctly, include default, place-holding characters in edit boxes and text areas.
  • What Accessibility is not?
    • Creation of separate versions of a page
      • You will not need to create one page for your disabled users and another for your regular users. Everyone will utilize the same page.
  • What Accessibility is not?
    • Text-only pages
      • Text only pages can be helpful for a particular user group but may actually hinder another. People with a learning disability may actually get over loaded with the mass of continuous text. Creation of text-only pages never carries the same information as the regular page. Graphics, typography, color scheme, and page design are also information.
  • What Accessibility is not?
    • Accessibility is Boring
      • all too often, people assume that accessible means boring, quite to the contrary. This is usually due to the misconception that accessible websites have to be mostly text. Graphic elements are perfectly acceptable in accessible web design; in fact they are actually encouraged. Graphics actually enhance accessibility by providing visual; cues as to the meaning and organization of the content. These cues help people to understand the content better, thus increasing the accessibility of the content.
  • Accessibility goals
    • List goals
  • The process of how to make web pages accessible
    • Think through the process
    • Understanding the process
    • Simplifying the process
    • Design
    • Develop
    • Deploy
  • Current state of web standards
    • What are the current state of web standards for your site.
  • And finally …
    • Any web developer with basic HTML and CSS design knowledge, and a bit of time on their hands, can easily learn and implement web accessibility — it’s not brain science after all. Web accessibility is all about following design standards and then adding in a few simple accessibility features. It’s not just about disabled users being able to access your website — it’s about everyone being able to access your website.
  • Questions?
  • THE END There is no end when the beginning is so near!