A A A A A

(Inactive) Web Best Practices: Teleconference Details

Teleconference details

Agenda

1. Discussion of IITAA Update

2. Javascript Links
  • Use of javascript in “onclick” or “href” of a links

3. Table Rules

4. PDF Accessibility Best Practices

Minutes

Universal Design
  • CD: Working with a select number of faculty on creating accessible course materials
  • CD: Will share with best practices group
  • CD: Connecticut has add 2 principles to the original 7
  • CD: I am promoting ATHEN and IBHE Group

IITAA Update
  • MS: No new news on this front
  • MS: We were hoping to leverage SS admin group
  • MS: We should talk about it at a future meeting

Javascript Links
  • HR: Using javascript in the HREF
  • JG: Any accessibility issue?
  • HR: It shows up as a link, I do not see any recommendation
  • HR: Could it be a button, different keyboard interaction
  • NH: Questions
  • NH: Separate styling, simiply using javascript as an HREF, using window.location.href is the then same as using a URL
  • NH: Function is import
  • MS: We see that in .NET use a link to submit a form
  • MS: We call this out as improper use of a link as a button
  • HR: In the past Section 508 required that pages function with out javascript, but many pages require javascript
  • MS: Section 508 has a small door for using scripting
  • MS: Not everything with javascript is bad, some types of javascript are bad for everybody (security)
  • MS: We recommended developers not use javascript unless they understood the accessibility issues
  • HR: Where should javascript
  • JG: BP javascript for form submission should not use links, if it loks like a button and acts like a button use button
  • MS: Submitting a form should use button
  • NH: AJAX is an example of getting a form
  • NH: HR has said that the form should only have one submit button
  • NH: There are different ways a form is submitted
  • NH: You can use javascript on a link to update content on the page
  • NH: It is not a form submission
  • HR: How do you define the difference between a link and button
  • HN: FAE has a link to display results of an analysis
  • NH: It is hard to pin down the actions of a button
  • NH: Links take us to a different page
  • MS: The get and post seem straight forward
  • MS: Certainly a post is a button
  • HR: They are used in a consistent way, the submit is a button and the cancel is a link
  • NH: That is probably done for visual users want something to link
  • JS: Cancel also has a navigational component to take you back
  • JG: Links are used to move to a new resource, everything else is a button?
  • MS: That might be a place to start
  • NH: I would like some clarification, a button posts some data and takes you somewhere else
  • HR: They could also use onClick event
  • JG: Does the presence or absence of other form controls on the page make a difference
  • HR: We need to have some senarios
  • MS: When the user is interacting with form controls, if links are used they may miss it
  • MS: Maybe button is required to submit a form
  • JG: Would this also require reseting and cancel?
  • HR: Yes
  • NH: Cancel is vague and it is not form specific
  • HR: They fall into the same categories
  • MS: The user would expect a button
  • MS: I can see it your way Nick
  • NH: This is contextual
  • MS: I looked up get and post, get should not do anything but retrieval, POST sending data
  • MS: Links use GET, POST should always be a form
  • JG: So if you use GET instead of POST it is OK to use a link
  • MS: It breaks down there
  • NH: Describing how GET and POST work
  • MS: A user interface definition, if the action initiates a form submission should be a button
  • NH: How does a screen reader get to a submit button
  • HR: A airline reservation has many links for choosing the flights
  • HR: It is hard to find the continue button
  • NH: I agree best practice
  • JG: Warning if javascript found in links with form control?
  • JG: Describing a rule for a warning, if forms, no submit button and link with javascript as the HREF would trigger a warning
  • NH: Some type button on the page
  • NH: We have button, input[submit], input[reset], input[image]
  • JG: How many pages don’t use form elements?
  • MS: We see that in .NET, we would need to check for visible form elements, certain control elements
  • NH: There are some pages that do not use Forms

Tab Panels
  • MS: I sent out an e-mail with some examples
  • MS: We were testing a flash based application, they have tabbed interface, the panel area shows content
  • MS: How should a screen reader user
  • MS: We looked at ARIA examples and the design patterns should be a single tab stop,... see AOL style guide
  • MS: It describes what you see in a dialog box in windows, like the print dialog box
  • MS: In the panel is static content there are some form controls
  • MS: The screen reader users miss the cotent if they tab, JAWS auto forms mode fixed that
  • MS: When I am in the tab bar,, there is no way to get out of the tab bar using the arrow keys
  • HR: I was part of the style guide group, something seems to have gotten lost
  • MS: Those are not in the design patterns
  • MS: The examples all have a form control
  • MS: We sent an example
  • JG: I would like to bring this to the ARIA group
  • NH: Can return be used take you to the content
  • MS: Good point Nick, this applies to other compound controls

Participants