A A A A A

(Inactive) Web Best Practices: Teleconference Details

Teleconference details

Agenda

1. Review navigation bar rule resolutions from last week for JG benefit
  1. Require the use of role=“navigation” on the list element and an aria-labelledby attribute that points to the heading that precedes the list
  2. Require at least one element having the role=“main”

2. Review unique form control labeling rules review from last week for JG benefit
  • [Legend] + [(Associated Label Text) | Title Attribute | Alt Attribute | Button Element Text Content | Value Attribute]

3. New Best Practices Website
  • "http://webacc-dev.cita.illinois.edu":http://webacc-dev.cita.illinois.edu

4. Adobe PDF resources

Minutes

1. Review navigation bar rule resolutions from last week for JG benefit

Require the use of role=“navigation” on the list element and an aria-labelledby attribute that points to the heading that precedes the list
  • JG: What about people just using role=navigation?
  • MS: Do we need the aria-labelledby?
  • HR: The information is redundant
  • MS: aria-labelledby will help make navigation bar unique
  • MS: Typically we have a div that contains h2 and the list
  • MS: Do we need the role=navigation on the list?
  • JG: no
  • HR: We only have one implementation
  • MS: Last week, we talked about the role main, but we are not sure how it will play out
  • MS: Maybe we just want the role navigation, no aria-labelledby?
  • NH: I like your suggestion
  • HR: MM what do you think?
  • MS: Simpler is better, this is an unusual situation, this is looking to the future
  • MS: We are using the XHTML and cannot use role
  • MM: I am not sure, it seems so new to me
  • MS: A small step in the right direction
  • JG: If you have more than one navigation bar, then use aria-labelledby
  • TO: I think we need to go slowly, developers will need to try to understand these new concepts
  • HR: Option in FAE to test for ARIA?
  • MS: Is that to much for implementation?
  • NH: The downside to that is people turn off
  • MS: The first step is just putting in NAVIGATION and MAIN
  • HR: Sometimes people abuse headings, making to many
  • NH: I think that is a good question
  • MS: We need to have some information in the best practices
  • JG: I think it is going be easy to get into the best practices
  • MS: We probably need to wait until we have a doctype people can validate to
  • MM: I agree, when it be comes available add a set of FAE rules
  • JG: We can get some of these rules on the test server, until some of these things happen
  • MS: that sounds like a good strategy

Require at least one element having the role=“main”
  • JG: Only one main in the page?
  • MS: At least one role=main
  • RS: The spec says that you can have more than one
  • JG: Mashups may have more than one main
  • RS: The home page is much different than the destination pages, home pages are typically primarily navigation
  • RS: If you are designing something to be plugged in it should not be main

2. Review unique form control labeling rules review from last week for JG benefit
  • [Legend] + [(Associated Label Text) | Title Attribute | Alt Attribute | Button Element Text Content | Value Attribute]
  • NH: What most needed was testing JAWS with button element and input[type=button]
  • MS: JAWS doesn’t use LABEL element content for button element and input[type=button]
  • MS: value attribute can be in the button element
  • MS: With the newest version of JAWS (11) the value attribute will be spoken in preference over title, this is a big change, it can be configured by the user
  • MS: WindowEyes gives preference to title attribute
  • MS: This can be a probem for redundent buttons, like deleting elements from a shopping cart, this will not work with JAWS 11
  • MS: The developers have fewer choices
  • NH: I have been looking into mobile web markup and doing testing on the iPhone/iTouch. The input[type=image] the ALT worked on desktop, but not on iPhone, but title works the same on both, title also is considered a help tag in OS X accessibility
  • MS: In the state we will configure JAWS to read title first, I am hoping Jaws will switch back
  • MS: I the default settings there is screen text and this caused a change in behavior
  • MS: Input[type=button] in older versions of JAWS 10 and earlier does read a label, but this is not used in practice

4. Adobe PDF resources
  • MS: Someone was asking about PDF accessibility
  • MS: Someone sent some links to the federal department of HHS
  • MS: It is a good starting point
  • MS: Maybe we want to have a spin off group
  • JG: I think it would be good
  • MS: We could maybe work on the reviewing the current resources

3. New Best Practices Website

Evaluation Resources

Participants