search

USDepartmentofLabor / Local-Labor-Market-Data-IOS

0 stars 1 forks source link

Accessibility - City Screen - Confusing Text between Heading and Button #14

Closed jfc3-dol closed 5 years ago

jfc3-dol commented 5 years ago

Why when reading the "Industry Employment" does VoiceOver read "Industry Employment heading" for the text but then reads "Industry Hierarchy button heading tap to view Industry Hierarchy". Is there a reason the first item is "Industry Employment" and the second uses the term "Industry Hierarchy"?

I would expect them both the heading and the button to start with "Industry Employment" and the button to have additional information about the button but first say "Industry Employment more details" or "More details about Industry Employment". Both followed by the word button and any instructions about how to activate it.

chawlani commented 5 years ago

Had changed the button to say "detail" but will change it to "Industry Employment more details" and for Occupations button to say "Occupations more details"

jfc3-dol commented 5 years ago

Thanks, I think using whatever the heading text is along with the words "more details" for all the buttons makes sense.

jfc3-dol commented 5 years ago

I like that the buttons to the other screens with more details now have the text "more details" after the name and code. Is the word "heading" being added at the end because the non-button text is a heading or the whole row is wrapped in a heading?

chawlani commented 5 years ago

the whole title row is a header hence button is being read as heading also. I have tried to remove "heading" but iOS is adding it.

jfc3-dol commented 5 years ago

It the issue with reading the word "heading" after the button because it's on the same row or the whole row is wrapped in code denoting it's a heading? I'm not as familiar with iOS coding as I am with HTML/web pages.

chawlani commented 5 years ago

I had informed you about this issues if we keep the title and button read separately on 04/15 and 4/16 and that why I had suggested to keep them together and read as heading and button. Let me know if I should change it back to that.

jfc3-dol commented 5 years ago

Let me think about it.

jfc3-dol commented 5 years ago

Each piece of text should be its own link to a person can skip back a few levels instead of only being able to go back one level at a time. To me, these remind me of bread crumbs which you can click or tap on any of the links/items listed.

jfc3-dol commented 5 years ago

I can tap on the individual links when VoiceOver is off and it takes me to the correct screen but when VoiceOver is on it only goes back one screen because it's acting as one link.

jfc3-dol commented 5 years ago

Sorry, about putting the wrong notes in this issue.

I'm going to close this issue now even though VoiceOver reads "heading" at the end of the button because it's part of a heading row.