A A A A A

(Inactive) Web Best Practices: Teleconference Details

Teleconference details

Agenda

  1. New Best Practices Website
    1. http://webacc-dev.cita.illinois.edu
  2. Review of IITAA requirements that we don’t have rules for
    1. http://webacc-dev.cita.illinois.edu/specs/wcag10/
  3. Adobe PDF resources
  4. Hadi Questions
    1. http://tinyurl.com/ygl988z

Minutes

1. New Best Practices Website 1. http://webacc-dev.cita.illinois.edu

2. Review of IITAA requirements that we don’t have rules for 1. http://webacc-dev.cita.illinois.edu/specs/wcag10/

MR: Here are some mapping
MR: Sub-Heading content cannot come only form image alt text
MR: Text content of an H1 element should not only come from ALT text
MS: ASCII Art is tougher, might be testable, there are some common ones, or a link with >> for paging, there might be a few common test patterns
JG: Do we need to go through the requirements and add rules
MS: Color is tough
MS: Sound will be mostly manual checks
MS: May want to trigger tests based on Flash object or other multimedia pattern to highlight changes
JG: What about manual checks if we detect
JS: We at Human Kenetics would be useful for manual checks
MS: It is moderate priority, this would be useful to have manual checks
MS: We have had some confusion with FAE and it is an entire Flash, warning here would help
TO: If we are going to suggest manual test, link text and color contrast
JG: Maybe there would be priorities on the manual tests?
JS: Would option to filter manual tests
TB: Not all users are the same
TO: People may not know what is important or not
HR: Alerting people to manual testing they can at least know about manual testing
TO: Is there going to be a resource about manual
TB: Do we need to support people in performing manual checks
HN: FAE is a higher level view of accessibility, other tools like Firefox extensions and IE extensions can provide more specific information
JG: Nick lets put manual tests on the to do list for FAE
NH: The mapping do we have mappings, we may want to differentiate between test that cover the rule, and there are rules that cover only part of the rule. We need to have caution that we are missing important manual.
MS: Animations are manual checks, MO-1 and MO-3
JG: Are 13.3 and 13.4 trigger if we see scripting
MS: Yes
JG: 14. Embedded Objects
MS: These are embedded object, object, embed or applet element a manual check is triggered
JG: 15. Embedded Documents
MS: Would be triggered on link extensions, PDF, DOC, etc…
JG: 16.1 trigger on forms and form contols+scripting?
NH: I am not sure, university library uses session variables, even when there are not forms
MS: Might be too much on every forms page
JS: We delivered time tests
MS: This rule may apply if the person has an accommodation
JG: 16.2 META Refresh? But probably become less used as javascript libraries become available.
MS: 18.1 Use separate accessible versions only as a last resort could look for text only link text that
JS: Could look at CSS properties fixed sizes for horizontal scrolling
MS: This does not have a Section 508, so it may go away
NH: It seems to me that we want content to flow, is there another guideline about flow of content
MS: We have layout and reading order, but not flow, this one is about 800×600

3. Adobe PDF resources
  • No time to discuss

4. Hadi Questions (http://tinyurl.com/ygl988z)
  • HR: Were trying to use the best practices and then there did not seem to be some for these situation
  • JG: ISSUE 1: TITLE on links
  • TO: Jaws requires extra commands to read title text
  • HR: Yes, I don’t know when there is something to read
  • MS: Discuss JAWS configuration
  • TO: Some people using TITLE for differentiating links
  • HR: That is a problem
  • HR: Main issue is to discourage people using TITLE attribute
  • JG: ISSUE 2: Landmark is before after a heading for the navigation
  • HR: Yes, need coding practices for removing heading at some point
  • JG: ISSUE 3: Sorting information

Participants