Accessibility Minutes 2009 09 30

From MemberWiki

Jump to: navigation, search

Participants

  • Sandy Foltz (University of Illinois)
  • Jon Gunderson (University of Illinois)
  • Nathan Jacobiak (ParaSoft)
  • Michael Squillace (IBM - chair)
  • Ann Abbott (IBM)
  • David Todd (IBM)

Minutes

Mike: no updates to rules requirements page

Mike: discussing enable/disable rules.

Sandy: Concerned about being able to disable rules.

Nathan: WebKing is able to configure rules.

Nathan: i.e., enable/disable rules

Nathan: rules are duplicated when they are modified and called a different name

Nathan: can turn rules on/off in WebKing

Nathan: would like to see the ability to enable/disable rules

Mike: need a default setting -> true

Mike: lets talk about severity codes

{ severityCode : 'level.violation', messageCode:'WCAG20.msg.missingMustContain', criterionNumber : '1.1.1'}

Mike: can severity code be one we've defined or some custom code.

Sandy: Something that was a warning and progress to a warning.

Sandy: Rules can progress in severity for example.

Jon: developers tend to ignore manual checks. FAE sticks to errors and warnings.

Jon: FAE - some rules changed from failures to warnings because of Illinois accessibility guidelines.

Sandy: have a default value for severity code

Jon: nice if there were a data structure would support a rule associated with a specification.

Mike: we have this already

Mike/Jon: Internalization will also be supported

Mike: Does WCAG say what to report when a failure occurs?

David: No

Mike: Have default severity codes and let folks override them if desired.

Jon: Doesn't think we should enable overrides.

Nathan: WebKing provides overrides

Nathan: we don't need to specify anything else besides having keys into rule error codes

Mike: Leave rules as they are currently specified. We won't provide a means to override in the work that we're doing.

Mike: Lets talk about rule context

Mike: Does everyone agree that we need a rule context?

Nathan: Context and selectors in Mikes note are doing the same thing. Can we combine them?

Nathan: What suppose to be in a context and what suppose to be in a selector?

Mike: Want to keep rule logic simple. Context would be a single node but Mike didn't know if he should go that far.

- element with specific parent-child relationships ::= ???

Mike: Selector mechanism for specifying same set of rules to elements.

contexts should include functions for parent-child relationships

have an array of contexts each with ID reference the ID in the rule

rules contain context OR context contain rules or both BOTH

comparing: link text is the same yet diff URL, OR same URL diff link text. Rule only really possible at context level too expensive at rule level

Team: Collect everything on a particular element then run a rule on it.

Sandy: Array of context would handle this.

Mike: Pass each image for example to each rule.

Sandy: describes processing all links on a page.

Mike: that's a document context

Sandy: that makes sense

Nathan: If dynamic update on a page we don't need to process the whole page just the new nodes that appeared.

Mike: Rule determines the context.

Mike: context should be as simple as possible producing simple logic

Nathan: Still trying to understand difference between context and selector.

Sandy: Context at the document level is a problem because users are going to want to see which element error applies to.

Sandy: If on document level return an array of nodes.

aaronlev has left irc.mozilla.org (Ping timeout)

Nathan: still thinks selectors and context are confusing

Mike: refer to context note I sent out.

Team: looking at Mike's note.

aaronlev (chatzilla@moz-4522EEC4.c3-0.arl-ubr1.sbo-arl.ma.cable.rcn.com) has joined #oaa-accessibility

Mike: Talks about an image example. Processing an image, image is the context.

Mike: Headings example. Should be incremented by 1. Heading 1, 2, 3 etc. Context has to the entire document.

Jon: This might not be true with ARIA markup.

Jon: Mashups for example.

Jon: Standard Web page headings example would be at document level, but this will get more complex especially with ARIA regions.

Nathan: Does the context change for a given rule or is it static?

Mike: It's static

Mike: As the page changes re-execute certain rules, but the context stays the same.

Nathan: What's the purpose of the abstraction?

Nathan: For the headers example, would the document context be passed to the rule logic?

Mike: yes

Personal tools