Accessibility Minutes 2010 07 28

From MemberWiki

Jump to: navigation, search

Present

  • Mike Squillace (IBM - Co-Chair)
  • Rich Schwerdtfeger (IBM - Co-Chair)
  • Ann Abbott (IBM)
  • David Todd (IBM)
  • Ken Jacobi (IBM)
  • Nathan Jukubiak (Parasoft)
  • David Bolter (Mozilla)
  • Jon Gunderson (Illinois)

Discussion

MS: Let's get started

MS: OK thats everyone but dylan and shaun

MS: The first thing is the charter, it is ready

MS: We went through a few iterations, in June we migrated to a task force to have deliverables, the deliverables are in the charter

MS: We must have a creation review, it is scheduled for 11 August our next meeting time

MS: JF already set out an invitation

MS: Once the creation review is finished, then there will be a vote by all the OAA member on the creation of the group

MS: We ill then need to use actual HTML to publish the deliverables

AA: What will need to be in HTML

MS: The wiki versions will need to be converted to static HTML documents

MS: The minutes can just be on the wiki like now

MS: Just the deliverables need to be in HTML for final form

MS: Please attend on 11 August

RS: JF will post to the list?

MS: Yes

MS: Agenda Item # 3

MS: Rules review process

MS: Reviewing the procedures

MS: Members can submit a rule

MS: If you are not a member you need to go through a member

MS: Open source has contributors and committers

AA: Accessibility Validation Rules Review Process can be found at http://www.openajax.org/member/wiki/Accessibility_Validation_Rules_Review_Process

MS: The chairs would appoint people to review the rule

MS: RS and I looked at the rules pretty extensively on how people might use the rules or want to modify them

MS: The idea is that each rule in the documentation, would have a state (submitted, reviewing, editing, approved)

MS: The only distinction is the "approved" state is in the official release for WCAG 2.0

MS: There is probably a better way to do this on the wiki

Nathan: If a rule is not accepted where is it put?

MS: We have not decided it

Nathan: People may want to have access to all the proposed rules

MS: Nathan can you add that to the wiki page

DB: The edit state is when the rule for revision

MS: It can be that or it could be taken out of the approved state if a problem has been found

MS: If you have an approved rule you want to take out it may cause a versioning issue

MS: Sub version will generate version information

MS: I also added information on the page about admin procedures

MS: One question I have for the creation review, is this process be considered a deliverable

JG: Maybe we want to leave it in wiki form until we have some experience with the process and more people start submitting bugs or contributing rules

MS: Anything else about this process?

JG: Looks good to me

MS: I will add the editing state and nathan has an action

MS: The four different stat of a rule

MS: Next item is test suites and test data

MS: I have not done a lot of work on this, it includes JSON META data

AA: Rule Test Cases can be found at http://www.openajax.org/member/wiki/Accessibility_Validation_Rule_Codification_Requirements#Rule_Test_Cases

JG: Do we need to have XPath's

MS: Any thoughts about XPaths versus IDs?

MS: We would need to change the requirements for people to put in IDs ont he passing and failing nodes

JG: JG: We need to have a way to validate correct label generation

MS: Would the rule be able to calculate from the rule what the label

MS: I just trying to understand

MS: There is know what to do that in the current test

JG: Let me think and build an example

MS: It is just a javascript object so we can put anything we want in it

JG: I will make an example

MS: Do we want just IDs or XPaths as an option

Nathan: I do not have an opinion

MS: Let's wait for Dylan to come back to see if he has to say

MS: Topic Rule IDs

MS: We should probably narrow the ranges for the 4 organizations

MS: When you contribute a rule you can change the number

JG: My concern is we are setting up static system that will be difficult to maintain

JG: I think that we need a database system

RS: Why don't JG and I get to JF to see if this could work on the openajax website

JG: Dlyan has already worked with Django and python

JG: I would be willing to move the system to openajax

DB: The database driven approach makes sense to me

Nathan: I am open to using it as long as it is eay to get things in and out

MS: JG and RS have there action to talk to JF

MS: I have not heard much about test suites and I put a sample set of test cases in the repository, all the test equivalent rules with the test cases

Proposed test case folder structure/file naming convention can be found at http://openajax.org/pipermail/accessibility/2010-July/000344.html

DT: It looks good to me

MS: There is a top level folder, and support folder, run folder and bootstrapping an automated test ...

MS: There is a test cases folder for the different categories rules

MS: There are 6 folders

Nathan: You could have under test cases folder and than that thing would have test cases, then there would be supporting files, everything would be a test case

MS: You would have a lot of directories

JG: Again I advocate the use of a database for the tests

MS: I think this is dependent on the use of the database

MS: JG: I think we will still need static versions

MS: That's all I have for today

MS: There will be a different call in number

RS: Right now OpenAjax server runs python 2.3 and we need something more than that for Django

RS: JF will check if we can upgrade

Retrieved from "http://www.openajax.org/member/wiki/Accessibility_Minutes_2010_07_28"
Personal tools