(Inactive) Web Best Practices: Teleconference Details

Teleconference details


1. Form control rule clarifications
  • http://html.cita.illinois.edu/nav/form/form-rules.php
  • Button element, is there a need to any rules for content, or TITLE * Priorities of TITLE in overriding VALUE, ALT and LABEL element content for labeling
  • Should there be rules for prohibiting TITLE and when other labeling techniques are being used? * Do we need a rule to prohibit FIELDSET/LEGEND nesting? * What happens when TITLE is empty and another labeling technique is used?

2. Section 508 Refresh

3. Other issues?


1. For input (class #1), select, and textarea elements, Rule #1 states that if label and @title both exist, the label element will take precedence. The 2nd sentence of Rule #4 (quoted above) seems to contradict this. Which is correct?
  • NH: There are different types of form control labeling
  • NH: I broke down the input elements into 3 types
  • NH: The first type is input[type=text], select and textarea
  • NH: Does label take present will title attribute be ignored?
  • MR: Yes
  • TO: Doesn’t jaws have to change modes to read titles
  • MR: The default setting is not to read title
  • JG: TITLE on just form controls or all elements?
  • TO: My question is for all elements

2. For input (class #2) elements, Rule #2 states that title takes precedence over alt. What if you have a non-empty alt with an *empty* title. Do you end up without any primary content (i.e., does title still override alt)?

3. Likewise for input (class #3) elements and Rule #3: Does an empty title take precedence over a non-empty value?

4. For button elements, does title play any part in what ends up being the effective label? * MR: A button element I think it just uses the content, you could use some hidden text * HR: The TITLE doesn’t probably play any part
  • MR: I think we need some test cases

5. Do we need additional rules for input (class #2 and #3) elements that say “if you use alt or value on an input element, you should not use @title” (to prevent cases of unintentional overrides)?
  • MR: We need more testing for class #2
  • MR: We testing with input button element and input[type=button|submit|reset]
  • MR: I will create the test and share with the group

2. Section 508 Refresh
  • MR: I looked at the WCAG 2.0 to section 508 draft and see where they were
  • MR: Most are in section 3, 4 5 and 6
  • MR: Some are not in, for example error processing
  • MR: It seems strange that color is in a different sections
  • MR: The divisions seem arbitrary
  • HR: They try to introduce the rules in chapter 4 and discuss the details in other sections, WCAG 2.0 is easier to read
  • MR: That makes sense to me
  • MR: The good news is that they seem to map, word for word in most cases
  • HR: Mostly seems more by the law, I am concerned about how developers can follow
  • MR: 3.3.3 and 3.3.4 are not part of the the Section 508 refresh
  • MR: The rest are scatter in chapters
  • JG: does the organization makes sense?
  • HR: Chapter 4 is the big application, you can have electronic documents and media content
  • JG: They should combine 4 chapters
  • HR: I am more used to WCAG 2.0
  • MR: Chapter 5 is more to authors ….
  • MR: You want developers to pay attention to
  • JG: We want to provide feedback that is useful, we cannot just say it is confusing
  • NH: Chapter 5 includes PDF, Simple Web Pages (no flash or javascript), and PPT
  • MR: It seems that complying with WCAG 2.0 will satisfy these requirements
  • RC: It seems there are some time out things that are not part of WCAG 2.0
  • MR: I have confusion about the levels
  • HR: They went the other direction

Our Purpose in reviewing the Refresh
  • Potentially provide feedback to Section 508
  • How this document would work for IITAA refresh
  • How are best practices relate to the Section 508 refresh