Accessibility Minutes 2015 11 20

From MemberWiki

Jump to: navigation, search


  • Jon Gunderson (University of Illinois) - Chair, Scribe
  • Mike Scott (State of Illinois)
  • Nicholas Hoyt (University of Illinois)


  • Jon: Have been busy working on getting FAE 2.0 re-factored.
  • Jon: Department of Homeland Security interested in bookmarklets & accessible name calculation.
  • Jon: Issue #69 "Is is ok to submit forms without a submit button as long as the page that returns maintains focus on the element that caused the submission?"
  • Jon: Focus 5 requires that form have a submit button. Based on WCAG 3.2.2 "On Input: Changing the setting of any user interface component does not automatically cause a[n unexpected] change of context" and H32 "Providing submit buttons."
  • All: Seems OK.
  • Jon: Will associate Focus 4 "select must not change context" to 3.2.2 instead of 3.2.1.
  • Nick: Suggested we may need a general manual check for 3.2.1 that "When any component receives focus, it does not initiate a change of context."
  • Jon: Issue #68 Control 9: Summary.
  • Jon: Control 9 Summary says "Verify title is label."
  • Nick: Wording is unclear; seems to indicate that title SHOULD be used as label.
  • Mike: Suggested "If title is used as label, verify that title is appropriate label."
  • Nick: Suggested "Verify title is intended label."
  • Mike: Suggested putting "if" condition in Definition instead of Summary, e.g. "If title is serving as label for form control, verify that title text is intended/appropriate label for the control."
  • Jon: Issue #63: Use sectioning elements to structure content.
  • Nick: Do we need to add a rule that recommends the use of HTML5 sectioning elements to structure content both at the top level (as with landmarks, i.e., main, nav, etc.) and at lower levels (e.g., within landmarks, e.g., section, article, etc.)?
  • Nick: With the deletion of the Reading Order rule that attempted to show a relationship between the use of sectioning elements and maintaining the correct reading order of text content, we may want to fill the gap with this type of rule, whose main purpose is reinforce structure through semantic use of HTML5 elements, but with the side effect that reading order may be more easily maintained.
  • Jon: Good idea for version 1.1.
  • Jon: Issue #62 Long description for images: how do 'alt' and 'title' affect each other?
  • Nick: Working on accessible name calculation in bookmarklets. Finding gaps/things that are unclear.
  • Jon: Longdesc and aria-describedat being removed. Alternatives such as dyanmically hidden descriptions or iframes being suggested.
  • Jon: May be a role="description". With flow-to, could cause the description to be read immediately after the image.
  • Nick: For now, alt provides accessible name, if both alt and title, title should be accessible description.
  • Jon: Leave it open and continue at next meeting.


Personal tools