Accessibility Minutes 2014 01 06

From MemberWiki

Jump to: navigation, search

Contents

Present

  • Ann Abbott (IBM)
  • Marc Johlic (IBM)
  • Rich Schwerdtfeger (IBM)
  • Mike Scott (State of Illinois)
  • Jon Gunderson (University of Illinois)
  • Nicholas Hoyt (University of Illinois) - scribe

Minutes

Ruleset version 1.0 questions

JG: We want rules for problems we've seen, but not necessarily for problems that might occur

JG: What are the criteria we could develop for inclusion in 1.0

JG: Nesting and use of landmarks

AA: Have seen problems with nesting all other landmarks in a banner

MJ: Have also seen nesting problems

RS: ARIA does have structural guidelines

AA: Not seeing them for landmarks nesting

RS: We do have instructions in best practices (support documents) for nesting of landmarks

WCAG Success Criteria for which we do not have rules

JG: Would like to go through some of the SC we don't have rules for

JG: 1.3.3 Sensory Characteristics: Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound. (Level A)

JG: Can this only be a manual check?

JG: Would like to go with page-level manual check for this SC

Consensus: OK

AA: I find the things that fail this often are documentation

MS: Might help in the help text we provide if we say "If the page includes instructions..."

JG: Good suggestion

JG: 1.4.1 Use of Color: Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. (Level A)

JG: Is this also just a page-level manual check?

JG: 1.4.2 Audio Control: If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level. (Level A)

JG: Do you fail this if there is an "autoplay" attribute on an audio object?

MS: Problem is we don't have a way to tell if it plays for 3 seconds or longer

JG: 1.4.4 Resize text: Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality. (Level AA)

JG: Do we need a rule for this SC?

MS: With modern browsers, I don't think we do.

JG: What would the manual check be?

MS: Set browser zoom to 200% and see if there is any loss of content or functionality

AA: Not all browsers indicate percent zoom

JG: Maybe embed objects, frames and iframes would trigger this rule

AA: In Firefox, if you press Ctrl-+ 6 times you get to 200%

JG: 1.4.5 Images of Text: If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following: (Level AA)

AA: 1.4.4: refer to Firefox preference (http://kb.mozillazine.org/Toolkit.zoomManager.zoomValues ) that defines zoom steps for more details.

Customizable: The image of text can be visually customized to the user's requirements;

Essential: A particular presentation of text is essential to the information being conveyed

JG: Applies to IMG

MS: and to INPUT type=image

JG: 2.3.1 Three Flashes or Below Threshold: Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds. (Level A)

MS: page-level manual check

JG: All pages?

AA: It would seem so.

JG: If it didn't have any JavaScript or Flash

JG: We'll put it on all pages for now.

JG: 3.2.2 On Input: Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component. (Level A)

JG: Any element that has onchange or onfocus event would be element-level manual check

AA: What we see is combobox and you select an item and page changes

JG: select, input type=checkbox, input type=radio, and combobox widget

NH: Does this include change of focus? Such as phone number broken into multiple input boxes

MS: Any form control that has a value, this could apply

JG: 3.3.3 Error Suggestion: If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content. (Level AA)

JG: 3.3.4 Error Prevention (Legal, Financial, Data): For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true: (Level AA)

MS: 3.3.3 goes pretty closely with 3.3.1

JG: We do have rule for 3.3.1: invalid values detected

JG: 3.3.1 may need manual check rule

JG: 3.3.3 and 3.3.4 would be element-level manual checks

JG: Brings up another question about rules: We have SCs closely related, do we need separate rules, or just one if it could cover multiple SCs

MS: Just one if possible

JG: When rule applies to more than one SC, which is primary SC?

MS: If only one is single A, choose it.

MS: But AA is more stringent for some rules

JG: We'll think about this one (which SC is primary, not always clear)

JG: I like the idea about combining 3.3.1, 3.3.3 and 3.3.4

AA: 3.3.4 (cont) at least one of the following is true: Reversible: Submissions are reversible.

Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.

Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.

MS: In practice, this applies to legal or financial

MS: It's not clear whether this goes beyond typical form validation (the checked option)

JG: I think we've covered all of the SCs we do not have rules for.

JG: Next teleconference, go over landmark rules to make sure we've covered everything we want

JG: Will send out link to reports that show how links fared in the real world

JG: Have analyzed 230,000 pages

JG: With strict ruleset, on average less than 60% of the rules are passing, average: 55% and on average 14 rules require manual checks

JG: Have been going through rules looking at messaging, and how we can eliminate manual check rules that don't apply

Personal tools