Accessibility Minutes 2014 09 15

From MemberWiki

Jump to: navigation, search



  • Ann Abbott (IBM)
  • Jon Gunderson (University of Illinois)
  • Marc Johlic (IBM)
  • Mike Scott (State of Illinois)
  • Todd Weissenberger (University of Iowa)
  • Nicholas Hoyt (University of Illinois) - Scribe


AInspector Sidebar

NH: New version of AInspector Sidebar (from email):

AInspector Sidebar version 0.16.5, released on Sep 15th, is now available at:

Updates include:

  • Rules added or modified in Forms and Links categories
  • Added a user preference for the 'Rerun Evaluation' button that allows for delayed automatic evaluation (from 5 sec. to 1 min.).
  • This permits the user to manipulate dynamic features in a web page until a desired state is achieved, and the browser to maintain focus on the page while the reevaluation runs automatically (i.e., without the user having to physically interact with the 'Rerun Evaluation' button).
  • Removed the keyboard shortcut for toggling the sidebar, along with associated user preferences.
  • Reorganized the Preferences dialog panels.

NH: Still need to look into automatic updates from new versions on the Mozilla Add-ons site.

FAE 2.0

JG: Problems with FAE 2.0: People who were submitting comments from the feedback form were getting 500 errors; that may be related to security settings.

JG: If you have an account on the FAE 2.0 server, please try out the feedback form.


JG: The other issue with FAE 2.0 is that the ruleset is out of date.

JG: Will be updating ruleset within the next two weeks.

JG: Garrett Smith is working on updating the template system to use bootstrap.js, which will change the styling and make the UI responsive to small screens.

Tools User Group

JG: In the next month, we are going to be starting a new group that reviews the tools.

TW: Are you seeing that group to include actual hardcore testing?

JG: Yes, testing could be a significant part.

Rule re. fieldset element

JG: Do you see nested fieldset elements? The DRES website was failing a rule due to this.

TW, MS, AA: Have not seen this before.

TW: Editors draft for fieldset in HTML5 claims that nesting is legal.

JG: Looking into current spec for HTML5: they do show a nesting example, so apparently it is supported.


FAE Auditor

JG: Mike, would FAE Auditor be useful for testing Illinois websites?

MS: Yes, I've made some recommendations re. use of FAE Auditor for that purpose.

OAA Evaluation Library modifications and refactoring

JG: OpenAjax Evaluation Library: How do we deal with reporting hidden results?

JG: 1. We are removing the filtering functionality from the API to simplify it and since it is no longer used.

JG: 2. We have two levels of results when rules are evaluated: rule level and element level

JG: At the element level, one of the results is "Hidden", which means that the element was not evaluated.

JG: How does this relate to rule results? We used to have a result value at the rule level of "Hidden".

NH: At the rule level, the result values are graded. E.g., V overrides W, W -> MC, MC -> P, etc.

JG: What should happen if there are only hidden, or only P + H?

JG: The tools indicate that there are hidden elements, which means that they were not evaluated.

JG: We have refactored the eval. lib. so that element result values and rule result values are distinct. Element results include "hidden" but the rule result values do not.

AA: Should there be a warning that all content should be exposed?


JG: AInspector Sidebar does allow the user to expose certain hidden content and test it appropriately using the Rerun Evaluation delay feature.

JG: FAE 2.0 only indicates the presence of hidden elements related to a rule result. If you open the page in question in AInspector Sidebar and go to that rule, you can get a list of the hidden elements.

Changes to link rule

JG: Changes to the link rule rel. to link text having same accessible name for same URL.

JG: However, in actual use, there seem to be numerous cases where the rule was violated (links having different acc. names that go to same URL).

JG: As it existed previously, it seemed to be too restrictive. Have modified the rule to bring up manual checks instead of violations.

JG: We have a different rule for same acc. name with different URLs.

MS: Would prefer that we don't ask people to manually check all links, just have manual checks for links with same URLs.

NH: 2.4.4 Link Purpose (In Context): The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. (Level A)

JG: Can talk more about 2.4.4 and 2.4.9 next week.

JG: Problem with 2.4.4 is that there is no requirement for the developer to do anything.

JG: Now that we have aria-describedby, should that be used to indicated where the relevant context is?

JG: If you use aria-describedby, screen reader will read the link, then the description (but not in the list of links)

JG: Believe that 2.4.4 is flawed the way it is written now.

Personal tools