A A A A A

(Inactive) Web Best Practices: Teleconference Details

Teleconference details

Agenda

1. No call next week, unless someone wants to chair

2. Updates on conceptual model for coding practices:

3. Rule Categories

Minutes

1. Meeting Next Week
  • no meeting next week

Updates to Conceptual Model

Discussion of Rule Categories
  • NH: I took a snap shot of the implementation of the OAA rules
  • NH: Not all of the rules implemented in the code have defined rule categories in the OAA ruleset, mostly organized on rule id labels
  • Discussion of rule caterogies
  • Coding is basically about using standards and being well formed
  • Frames are still used in may websites, not sure what the rule would be
  • Frame rule may be part of structure
  • KG: Are there differences between iframes and frames?
  • KG: There a lot of iframes
  • MS: Are you using title element in the html document or title attribute on the iframe element
  • KG: I am not sure, but they are now “passing” the rule
  • MS: I think it is less important to have a title attribute than a title element
  • MR: Title attribute and then title element
  • JG: Do we want to use frames for supporting navigation??
  • MR: Some learning management systems using frames
  • MS: If there are frames who to we management
  • KG: iframes do not effect navigation
  • MS: Do screen readers know if there are iframes are there?
  • HR: Yes they do
  • MS: We need to write the rules first to see what rules we need
  • JG: What is navigation?
  • MS: These are for the three WCAG 2.0 requirements related to web site accessibility
  • HR: We should change the name to “Site Navigation”
  • JG: Timing
  • MS: These are for the WCAG 2.0 time outs and …
  • JG: There are 5 success criteria for the Guideline 2.2 Enough Time: Provide users enough time to read and use content.
  • HR: Table should be data table and lout should be layout and linearization
  • MS: Layout and order, for tab order
  • HR: Content should be content/structure
  • NH: headings, landmarks, list of navigational links
  • HR: Content and structure are two different things to me
  • NH: Content implies low level
  • MS: Documents, doesn’t even fit anymore
  • JG: We can have rules for manual checks for downloadable documents, I would put them in the links rules
  • MS: Downloadable documents and embeded applications, these have accessibility issues and are beyond the scope of these documents
  • JG: WCAG 2.0 does have techniques for PDF, Silver light and Flash ….
  • JG: We can have rules to ask manual checks
  • HR: I am bothered by content and headings are together
  • NH: I sent a message to the group on a revised list
  • Sent by NH:
    • WIDGETS: SCRIPTS/WIDGETS
    • HEADINGS: CONTENT/STRUCTURE
    • LANDMARKS: CONTENT/STRUCTURE
    • TITLE_MAIN: CONTENT/STRUCTURE
    • LISTS: CONTENT/STRUCTURE
    • IMAGES: IMAGES
    • LINKS: LINKS
    • MEDIA: AUDIO/VIDEO/MULTIMEDIA
    • TABLES: TABLES
    • LAYOUT: LAYOUT
    • Other suggestions:
      • DATA TABLES, LAYOUT AND ORDER
    • Not addressed:
      • CODING: example rules: lang, others? (could go under CONTENT/STRUCTURE)
      • FRAMES: Do we need this?
      • NAVIGATION: three WCAG SC about multiple ways, consistent nav, consistent ident. Hadi recommends changing to SITE NAVIGATION
      • TIMING: requirement re. timeouts, giving users change to respond before content changes, timing adjustable, et al. (5 SCs in WCAG)
      • DOCUMENTS: may not fit anymore: downloadable documents: manual checks for PDF, Word, Excel

Draft Rule Categories
  • Form Controls
    • Labeling
    • Required and invalid
    • Instructions
    • Error feedback
    • Form submission
  • Scripts/Widgets/Objects
    • Content being added and deleted (both based on user action and asynchromous events)
    • Naming
    • Properties and states
    • Instructions
    • Error feedback
    • Embeded object that are not video
  • Data Tables
    • naming of table
    • table headers
  • Links
    • Links meaningful
    • Links unique or similar
    • Links to downloadable documents
  • Structure
    • Headers
    • Landmarks
    • List of links
    • Use of lists
    • Frames
    • Title
  • Content
    • Abbreviations
    • Langauge
    • Doctype
  • Layout and Order
    • Tab order
    • Linearization
      • Tables used for layout
  • Timing
    • Auto fresh of pages
    • Scripting that might limit response time
  • Images
    • Captcha
    • alt text
    • long descriptions
  • Audio/Video/Multimedia
    • embeded objects
    • HTML 5 video and audio tags

Participants