A A A A A

(Inactive) Web Best Practices: Teleconference Details

Teleconference details

Agenda

1. No meeting next week (10 October)

2. Changing the Group Name
  • Suggestion: Open Accessibility Alliance
  • Purpose: Open source evaluation tools and resources to support accessible design

3. Rule Documentation

4. Rule Categories

Minutes

1. No meeting next week (10 October)

2. Changing the Group Name
  • Suggestion: Open Web Accessibility Alliance
  • Purpose: Open source evaluation tools and resources to support accessible design
  • JG: Taking about changing the name of the group
  • JG: There would be three groups:
    • Coding practices group
    • Rules group
    • Tools group
  • NH: Might be a good idea
  • HR: Why “Open”??
  • JG: My idea
  • HR: I like web best practices more than open
  • HR: “Web Accessibility Alliance” might be better

3. Rule Documentation

4. Rule Categories

Links/Navigation NH: Links are the primary thing you navigate with NH: Include the requirements for site/page navigation MS: Ball park is good, we can make changes as we find a need to JG: 2.4.5 and 3.2.3 MS: I think it works

Form Controls
  • Labeling and grouping
  • Required and invalid
  • Instructions
  • Error feedback
  • Form submission
HR: Form submission and verification of form submission NH: I will make the change HR: Separate “Required” and “Invalid” MS: Invalid is the same as error feedback MS: Error feedback and verification is closely KG: Required formatting? NH: Related to instructions JG: Include formatting as a sub item under instruction MS: Error Identification/Error Prevention/Error Suggestion is in WCAG 2.0 HR: What is error suggestion? MS: Feedback on how to fix an error HR: If there are submit and cancel buttons, the cancel is a link NH: They are trying to make the cancel button look different, and maybe positioned away MS: You think the cancel should be a button, we have brought this up in IITAA work MS: If it looks like a button make it a button, if it looks like a link make it a link

Scripts/Widgets
  • Content being added and deleted (both based on user action and asynchronous events)
  • Naming
  • Keyboard support
  • Properties and states
  • Instructions
  • Error feedback
  • Embedded objects that are not video
  • Types of widgets
    • Captcha (documentation)

h4.

Participants