A A A A A

(Inactive) Web Best Practices: Teleconference Details

Teleconference details

Agenda

1. IITAA Update and Certification
  • Scheduling a one day conference
  • Tentative date is 17 December 2010
  • Location: University of Illinois, Champaign, IL

2. Public Commenting on Web Accessibility Rules for ADA

3. Browser Testing for Accessibility
  • A question came up recently about what web browser(s) to use when accessibility testing. The IITAA talks about web sites being compatible with “the two most recent production versions of the two most popular products,” however this is in the definition of “Leading Assistive Technology,” so it wouldn’t seem to apply to browsers.
  • We normally only test with Internet Explorer, but recently ran into a situation where a Flash-based site worked with JAWS in IE but not Firefox.
  • So the question is, should “the two most recent production versions of the two most popular products” apply to browsers, too? How about plug-ins like the Flash player? Operating systems?

4. Web Services Calendar
  1. Default calendar view. Search is disabled, mini calendar is disablled, and only one event list is shown: http://test.webservices.illinois.edu/calendar/list/220?skinId=4581
  2. View with everything turned on. We will use this for large master calendars: http://test.webservices.illinois.edu/calendar/list/598?skinId=2155

Minutes

1. IITAA Update and Certification
  • Scheduling a one day conference
  • Tentative date is 17 December 2010
  • Location: University of Illinois, Champaign, IL
  • MS: That time is good
  • JG: Interested in tour
  • MS: We don’t care
  • MS: Jamie McCoy is interested
  • JG: Is it ok to announce widely, but as a technical session
  • MS: Start at 9:30am and go to 3:30pm
  • JG: Organize box lunches
  • MS: Review current requirements and then review new requirements related to WCAG 2.0 (errors, scripting, PDF, Flash)
  • JG: Setup some type of registration page

2. Public Commenting on Web Accessibility Rules for ADA
  • http://www.ada.gov/anprm2010.htm
  • Do we want to comment as a group?
  • JG: Is this something the group wants to do?
  • MS: I would like to do it, this is big
  • MS: This is the moment of truth for web accessibility
  • MS: What ever we can do?
  • TO: I think it is important to provide feedback
  • MS: We have taken a first pass
  • MS: I would value some back and forth discussion
  • MS: Questions 1 and 2 should be compatible with Section 508 refresh
  • NH: On going question related to timing
  • MS: There is a question further down that relates to the timing issue
  • MS: They appear to be suggesting that the comment will be retroactive, let me pull it up
  • JG: I read it as should it apply legacy websites
  • MS: They are saying after 2 years it would be retroactive, this is not what we say in IITAA
  • MS: This does not seem feasible, we would suggest that it could not be retroactive
  • TO: I don’t think it would be enforcable
  • TO: I like the way IITAA handles implementation
  • NH: I think there should be a provision about legacy websites, that there is a review process to get something updated
  • MS: I think we should look at buildings
  • TO: Older websites will probably be static and easier to update
  • JG: It will probably will depend on the type of website
  • MS: Cost seems, I don’t think we know a cost
  • HR: Educause teleconference
  • MS: We will put up a moderated wiki
  • JG: We will make this the agenda for next week
  • CD: HTML5 will take a long to implement
  • JG: HTML5 is a large specification and will take a long time to implement
  • NH: There will be a working draft from the W3C

3. Browser Testing for Accessibility
  • A question came up recently about what web browser(s) to use when accessibility testing. The IITAA talks about web sites being compatible with “the two most recent production versions of the two most popular products,” however this is in the definition of “Leading Assistive Technology,” so it wouldn’t seem to apply to browsers.
  • We normally only test with Internet Explorer, but recently ran into a situation where a Flash-based site worked with JAWS in IE but not Firefox.
  • So the question is, should “the two most recent production versions of the two most popular products” apply to browsers, too? How about plug-ins like the Flash player? Operating systems?
  • MS: A university wanted to do a flash based holiday card, it worked with IE 7 and 8 with jaws 11+12, but the tester tested with JAWS 10 and FF
  • MS: The question, what do we need to support, unless otherwise specified, we should support the latest two version of assistive technology, we don’t talk about browsers, but what browsers as well
  • MS: Does is have to work with JAWS in FF, IE or ….
  • MS: What is the groups feeling about what we define as accessible?
  • NH: I would not limit it to IE
  • MS: It is a combination of assistive technologies
  • NH: OS X has FF, Safari, Opera, Chrome
  • MS: We assume Windows, anything in Flash was only supported in IE, but if we include OS X and linux nothing would be accessible
  • NH: Flash is supported on those OS
  • MS: But not accessible Flash
  • MS: Flash player 10 now supports accessibility through FF
  • MS: Accessibility is first supported in Windows OS and IE, then it trickles out
  • MS: We should probably talk about on the 17th
  • JG: We may want to talk about technology specific information in IITAA that helps guide accessibility to more accessible technologies

4. Web Services Calendar
  1. Default calendar view. Search is disabled, mini calendar is disabled, and only one event list is shown: http://test.webservices.illinois.edu/calendar/list/220?skinId=4581
  2. View with everything turned on. We will use this for large master calendars: http://test.webservices.illinois.edu/calendar/list/598?skinId=2155
    • JW: I am using radio buttons
    • MS: We use structure, hide visibility, but not from the screen reader
    • HR: I am against the approach since it is more clutter for me to have to wade through, sighted people have the option and I need one two
    • HR: It is also confusing when working with a sited partner
    • MS: On this page is it going to be functionally different
    • HR: Some times I need to narrow down options like at Amazon
    • MS: If it was a filter I would agree with you, this seems to be choosing between two different views, this is picking
    • CD: What happens when you go to the week view
    • JW: Jon suggested “Go to”
    • MS: What does not work in IE 7
    • JW: The code did not work, there was documented that it would not work in IE 7
    • MS: The code could probably be twiked
    • JW: I could try to do that
    • HR: It seems to be working correctly
    • JW: So maybe I have resolved that
    • JW: The only time this will be used on master calendars
    • NH: The label events and repeating events, I find the confusing
    • JW: I did not get a lot of field back, part of it is a logic issue
    • JW: The drop down calendars, on focus for the text field
    • JW: What about took the javascript pop out, what if we launched a new browser, some one would have to click ont he icon, they could just enter the date
    • JW: The pop up calendar would be in the new browser, when you close the browser the date would be entered
    • MS: We have done that with some dialog boxes, most people just fill in the date, it seems to be good for me
    • MS: The text box does not trigger the popup, but the next button does trigger the popup
    • MS: There is a show modal feature in IE that some other browsers
    • JG: The calendar be just links?
    • JW: We are using a third party calendar function
    • HR: I can’t find the window with the calendar
    • JW: Everytime I know you get lost
    • MS: The content is the DIV is at the bottom of the page
    • MS: Dojo library
    • JG: We need to make a collection of accessible widgets

Participants