[TIMOB-14735] iOS: Accessibility: ButtonBar: Accessibility does not work on Button Bar
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Medium |
Status | Closed |
Resolution | Invalid |
Resolution Date | 2014-09-16T21:27:58.000+0000 |
Affected Version/s | n/a |
Fix Version/s | n/a |
Components | iOS |
Labels | qe-3.1.2 |
Reporter | Paras Mishra |
Assignee | Muhammad Dadu |
Created | 2013-08-01T09:54:42.000+0000 |
Updated | 2017-03-24T17:10:00.000+0000 |
Description
iOS: Accessibility: ButtonBar: Accessibility does not work on Button Bar. The Label, Value or Hint are not voiced over.
This is not a regression. It occurs since sdk 3.0.0.GA.
Steps to reproduce:
1. Run the app as Accessibility Acceptance Access_1102 iOS Only under Accessibility module.
2. Touch the first Buttonbar (with LVH defined in sequence)
Actual:
if 'red' is touched then 'red button 2 of 3" is spoken.
The Label, Value or Hint are not voiced over.
Expected:
2. The device reads aloud:
buttontext, tab, (button number) of (total number of buttonson buttonbar)
[eg. 2 of 3]
followed by ""Buttonbar1"", ""Value1"", ""Hint1""
Fails with: Appcelerator Studio, build: 3.2.3.201403271839 Titanium SDK, build:3.2.3.v20140401134117 Node.JS Version: v0.10.13 NPM Version: 1.3.2 ├── acs@1.0.14 ├── alloy@1.3.1 ├── node-appc@0.2.0 ├── npm@1.3.2 ├── titanium@3.2.3-alpha2 └── titanium-code-processor@1.1.1-alpha Xcode 5.1 Devices: IPhone5S iOS 7.1 iPad Air iOS 7.1
This issue was previously scheduled to be worked on in more than one sprint: * 'Release 3.1.2' (on board '3.1.X Triage') * 'Release 3.0.1/TS 3.0.2' (on board '3.1.0 Triage') Starting from JIRA Agile 6.3, an issue can only belong to a single future sprint. Read more about this change: http://docs.atlassian.com/agile/docs-0630/Sprint+Marker+Migration This issue is now scheduled for future sprint 'Release 3.1.2' (on board '3.1.X Triage'). If this is incorrect, please update the issue accordingly. This comment was automatically generated by JIRA. If it is no longer relevant, please feel free to delete it.
Titanium behavior is consistent with native applications.
Closing ticket as invalid with reference to the above comments.