A A A A A

(Inactive) Web Best Practices: Teleconference Details

Teleconference details

Agenda

1. Create new group called Open Accessibility Alliance
  • Require people to sign up again if they want to participate
  • Create new listserv

2. Comments or ideas for Triage summary report in OAA Accessibility Extension 2.0.20 alpha

3. Comments or ideas for HTML reports in OAA Accessibility Extension 2.0.20 alpha

4. Review Layout rules

5. Review Keyboard rules

6. Rules for the following WCAG Success Criteria

Minutes

1. Open Access Alliance
  • Require people to sign up again if they want to participate
  • Create new listserv
  • JG: Create new list and collaboration
  • MS: Will the monday group merge
  • HR: Will you be wipping out the current information

2. Comments or ideas for Triage summary report in OAA Accessibility Extension 2.0.20 alpha
  • JG: Any comments
  • MS: I have a concern about passing triage more of a hidden thing
  • MS: The rules you flag as a triage rules, we provide some additional feedback or instructions
  • MS: Some people may be mislead that it is good enough
  • MS: We don’t want manual testers to waste their time
  • JG: How do you do it?
  • MS: Should not be able to slect a “Triage” summary
  • MS: If any of the Triage rules are failed, basically you want the devleoper to address these rues first
  • MS: This is something that manual testers do it
  • MR: We want to hide complexity for people who are just learning about accessibility
  • NH: A group on Illinois use these rules as a test and feedback to developers
  • MS: What was there goal in aborting? To hide complexity?
  • NH: They are aborting there were so many problems, so rather than creating a detailed report, they would have a shorter report, they would be wasting their time with the detailed report
  • MS: Sheild users from priroties
  • JG: Is priroty a better term?
  • MS: Priority already means something in WCAG 2.0
  • MS: You should have an understanding of the basic accessibility
  • NH: I like term triage
  • MR: Quick check versus full check in Adobe PDF
  • JG: I am open to a user interface that communicates the concept that there is more than the triage rules
  • NH: Build in huestics that in an “all report:, if have failures in the triage rules are empheiszed in the view
  • NH: Dialof or message that that basic rules have been violated, you understand the basics of accessibility
  • MS: There needs to be a differientiation of action of you need to learn something
  • MS: Some way to present a message that you need to understand basical accessibility with the report
  • NH: Thee is the potential to do this within categories
  • JG: I am hearing:
    • Integrating the traige information in the other rules
    • Poor implementation of triage rules should get “special” feedback on learning the basics
  • MS: Do you want o include MAIN landmark as a triage rule?
  • NH: I tend to agree with that
  • MS: Traige rules should be required

3. Comments or ideas for HTML reports in OAA Accessibility Extension 2.0.20 alpha

4. Review Layout rules

5. Review Keyboard rules

6. Rules for the following WCAG Success Criteria 1.4.1 Use of Color (A) http://www.w3.org/TR/WCAG20/#visual-audio-contrast-without-color 1.4.2 Audio Control (A) http://www.w3.org/TR/WCAG20/#visual-audio-contrast-dis-audio 2.2.1 Timing Adjustable (A) http://www.w3.org/TR/WCAG20/#keyboard-operation-keyboard-operable 2.2.2 Pause, Stop, Hide (A) http://www.w3.org/TR/WCAG20/#time-limits-pause

Participants