ARIA and Assistive Technologies Community Group Weekly Teleconference
  • Past
  • Confirmed

Meeting

Event details

Date:
– Pacific Standard Time
Status:
Confirmed
Repeats:
Every other week on Thursday, starting from 14 November 2024, until 31 December 2026
Overview of the recurring event
Groups:
ARIA and Assistive Technologies Community Group ( View calendar)

Weekly meeting focused primarily on generating ARIA-AT reports via manual testing. Alternates between an earlier Wednesday time one week and later Thursday time the next.

Agenda

 View agenda

Review agenda and next meeting dates

  • Requests for changes to agenda?
  • Next Community Group Meeting: Wednesday November 20
  • No meeting Thursday November 28
  • Next AT Driver Subgroup meeting: Monday December 9

Current status

Goals:

  • 6 recommended plans by September 30.
  • Total of 10 Recommended + 10 in Candidate Review by December 31.

Status: Behind schedule

8 refactored plans in candidate review

Plan Vispero Apple
Alert Approved In Review
Action Menu Button Example Using aria-activedescendant In Review In Review
Color Viewer Slider in review Not started
Command Button Approved In review
Link Example 1 (span element with text content) Approved In review
Modal Dialog Approved Not started
Radio Group Example Using aria-activedescendant in Review Not started
Toggle Button approved In review

Three refactored plans in draft review

  1. Disclosure Navigation Menu Example
  2. Navigation Menu Button
  3. Action Menu Button Example Using element.focus

Refactor in progress

  1. Radio Group Example Using Roving tabindex

Issue 365: Impact of hints on testing

Impact of hint text/help messages on test results · Issue #365 · w3c/aria-at

Proposal for discussion (included as comment in issue):

Define hint in the glossary

Hint: Supplemental output provided by a screen reader that is intended to help users understand an element or how to use it. Hints are distinct from base output that includes required information, such as name, role, value, state, and properties. Hints may repeat information that is included in base output. hints that are conveyed with speech are spoken after base output.

Update Testing guidance

Why AARIA-AT does not test hints, i.e., test assertions do not apply to hints?

  1. Hints are supplemental output. While it is very important that hints do not interfere with interoperability, hints are not essential functionality. The scope of ARIA-AT is limited to fostering interoperability of essential functionality.
  2. Because users of certain screen readers commonly disable hints, base output must satisfy interoperability requirements. If a hint could satisfy an interoperability requirement, hints would have to be consider essential instead of supplemental.

why leave hints on during testing?

  1. Testing with default settings is an important principle.
  2. It is important to capture negative side effects caused by hints, e.g., a hint conflicts with base output.

testing requirements:

  1. Because hints are sometimes part of an AT response, they are included in the AT response recorded for a command. The goal is for response collection to be comprehensive; it must include both positive and negative side effects of the command. Good hints an be considered a positive side effect while inaccurate hints can be considered a negative side effect.
  2. Hint output is not analyzed to determine an assertion verdict. Thus, testers must have the skills and knowledge necessary to distinguish hints from base output.

Testing Action menu button with element.focus

Test plan for Action Menu Button Example Using element.focus

Testing Disclosure Navigation Menu

Test plan for Disclosure Navigation Menu Example

Issues to resolve:

Testing navigation menu button

Test Plan for Navigation Menu Button

Issues to resolve:

Minutes

 Read minutes

Export options

Personal Links

Please log in to export this event with all the information you have access to.

Public Links

The following links do not contain any sensitive information and can be shared publicly.

Feedback

Report feedback and issues on GitHub.