ENGAGE-392: Code entry areas not accessible to VoiceOver

Metadata

Source
ENGAGE-392
Type
Bug
Priority
Blocker
Status
Closed
Resolution
Won't Fix
Assignee
Svetoslav Nedkov
Reporter
Sambhavi Chandrashekar
Created
2010-02-16T15:50:07.000-0500
Updated
2017-12-22T09:44:19.320-0500
Versions
  1. 0.3b
Fixed Versions
  1. 0.3
Component
  1. Object Code Entry

Description

VoiceOver user does not know that a two-digit number has to be entered for code. The two code entry boxes that afford a visual clue for this are not announced by VO.
Likewise, when entering a number, invoking a button press (by double-tapping a selected button) does not provide a message to VoiceOver that the selected digit has been entered.

Environments

iPhone OS 3.0 with VoiceOver

Comments

  • Sambhavi Chandrashekar commented 2010-02-17T15:27:28.000-0500

    Bug Parade Engage 0.3

  • Sambhavi Chandrashekar commented 2010-02-24T12:46:34.000-0500

    a11y issue

  • y z commented 2010-03-02T13:54:21.000-0500

    By adding tabindex to the message and the digit fields we should be able to access those fields with VO. However, dynamically updated values are not updated via VO unless focused.

  • Svetoslav Nedkov commented 2010-03-12T11:48:30.000-0500

    ENGAGE-392.patch replaces the two code digit fields with images, that are recognized by VoiceOver. The images themselves are not included in the patch and should be added manually. The images are attached as codeEntryImages.zip.

  • Justin Obara commented 2017-12-22T09:44:19.318-0500

    The repository has been archived.