|
|
Created:
6 years, 2 months ago by shreeramk Modified:
6 years, 1 month ago CC:
chromium-reviews, plundblad+watch_chromium.org, aboxhall+watch_chromium.org, jam, yuzo+watch_chromium.org, darin-cc_chromium.org, dmazzoni+watch_chromium.org, dtseng+watch_chromium.org Base URL:
https://chromium.googlesource.com/chromium/src.git@master Project:
chromium Visibility:
Public. |
Description<address> elements should have AXRoleDescription of 'address'
According to latest editor spec http://rawgit.com/w3c/html-api-map/master/index.html
Recommended AXRoleDescription of "address" to disambiguate
from "contentinfo" landmark role for address element.
BUG=169577
Committed: https://crrev.com/b6894d59ad9f364d44b0609d0dda67a3f9d673ef
Cr-Commit-Position: refs/heads/master@{#301671}
Patch Set 1 #
Total comments: 1
Patch Set 2 : updating name and desc #Patch Set 3 : Rebasing changes #
Messages
Total messages: 19 (4 generated)
shreeram.k@samsung.com changed reviewers: + aboxhall@chromium.org, dmazzoni@chromium.org
Please review. Thanks!
https://codereview.chromium.org/670493002/diff/1/content/app/strings/content_... File content/app/strings/content_strings.grd (right): https://codereview.chromium.org/670493002/diff/1/content/app/strings/content_... content/app/strings/content_strings.grd:364: <message name="IDS_AX_ROLE_CONTENT_INFO" desc="accessibility role description for contentinfo"> As before, the name and description of the message should match the text to be translated. The translators are not going to understand what "contentinfo" is, or its relationship to "address".
On 2014/10/20 16:31:55, dmazzoni wrote: > https://codereview.chromium.org/670493002/diff/1/content/app/strings/content_... > File content/app/strings/content_strings.grd (right): > > https://codereview.chromium.org/670493002/diff/1/content/app/strings/content_... > content/app/strings/content_strings.grd:364: <message > name="IDS_AX_ROLE_CONTENT_INFO" desc="accessibility role description for > contentinfo"> > As before, the name and description of the message should match the text to be > translated. The translators are not going to understand what "contentinfo" is, > or its relationship to "address". Then to match and make the translator understand. Following can be used: name="IDS_AX_ROLE_ADDRESS" and desc="accessibility role description for address" Is this correct/fine?
On 2014/10/20 17:16:29, shreeramk wrote: > On 2014/10/20 16:31:55, dmazzoni wrote: > > > https://codereview.chromium.org/670493002/diff/1/content/app/strings/content_... > > File content/app/strings/content_strings.grd (right): > > > > > https://codereview.chromium.org/670493002/diff/1/content/app/strings/content_... > > content/app/strings/content_strings.grd:364: <message > > name="IDS_AX_ROLE_CONTENT_INFO" desc="accessibility role description for > > contentinfo"> > > As before, the name and description of the message should match the text to be > > translated. The translators are not going to understand what "contentinfo" is, > > or its relationship to "address". > > Then to match and make the translator understand. Following can be used: > > name="IDS_AX_ROLE_ADDRESS" and desc="accessibility role description for address" > > Is this correct/fine? Yes. This is fine - but it's often better to add more information for translators if the word is ambiguous. Here "address" does not mean "web address (url)", but "a section of the page containing contact information in the form of a postal address".
On 2014/10/20 17:21:37, dmazzoni wrote: > On 2014/10/20 17:16:29, shreeramk wrote: > > On 2014/10/20 16:31:55, dmazzoni wrote: > > > > > > https://codereview.chromium.org/670493002/diff/1/content/app/strings/content_... > > > File content/app/strings/content_strings.grd (right): > > > > > > > > > https://codereview.chromium.org/670493002/diff/1/content/app/strings/content_... > > > content/app/strings/content_strings.grd:364: <message > > > name="IDS_AX_ROLE_CONTENT_INFO" desc="accessibility role description for > > > contentinfo"> > > > As before, the name and description of the message should match the text to > be > > > translated. The translators are not going to understand what "contentinfo" > is, > > > or its relationship to "address". > > > > Then to match and make the translator understand. Following can be used: > > > > name="IDS_AX_ROLE_ADDRESS" and desc="accessibility role description for > address" > > > > Is this correct/fine? > > Yes. > > This is fine - but it's often better to add more information for translators if > the word is ambiguous. Here "address" does not mean "web address (url)", but "a > section of the page containing contact information in the form of a postal > address". Ok. Now I think I am getting this translator related fixes properly. I was not completely clear on it. I think this would be more clear/unambiguous. name="IDS_AX_ROLE_CONTACT_INFORMATION" and desc="accessibility role description for contact information"
On 2014/10/20 17:30:27, shreeramk wrote: > On 2014/10/20 17:21:37, dmazzoni wrote: > > On 2014/10/20 17:16:29, shreeramk wrote: > > > On 2014/10/20 16:31:55, dmazzoni wrote: > > > > > > > > > > https://codereview.chromium.org/670493002/diff/1/content/app/strings/content_... > > > > File content/app/strings/content_strings.grd (right): > > > > > > > > > > > > > > https://codereview.chromium.org/670493002/diff/1/content/app/strings/content_... > > > > content/app/strings/content_strings.grd:364: <message > > > > name="IDS_AX_ROLE_CONTENT_INFO" desc="accessibility role description for > > > > contentinfo"> > > > > As before, the name and description of the message should match the text > to > > be > > > > translated. The translators are not going to understand what "contentinfo" > > is, > > > > or its relationship to "address". > > > > > > Then to match and make the translator understand. Following can be used: > > > > > > name="IDS_AX_ROLE_ADDRESS" and desc="accessibility role description for > > address" > > > > > > Is this correct/fine? > > > > Yes. > > > > This is fine - but it's often better to add more information for translators > if > > the word is ambiguous. Here "address" does not mean "web address (url)", but > "a > > section of the page containing contact information in the form of a postal > > address". > > Ok. Now I think I am getting this translator related fixes properly. I was not > completely clear on it. > > I think this would be more clear/unambiguous. > > name="IDS_AX_ROLE_CONTACT_INFORMATION" and desc="accessibility role description > for contact information" That implies that someone should translate the phrase "contact information" into their language. We want them to translate the word "address" - but if there are multiple meaning of "address", they should pick the one that they'd use when talking about a person's contact information, as opposed to a web address. How about: name="IDS_AX_ROLE_ADDRESS" and desc="accessibility role description for an address (as in a person's contact information)"
On 2014/10/20 17:36:34, dmazzoni wrote: > On 2014/10/20 17:30:27, shreeramk wrote: > > On 2014/10/20 17:21:37, dmazzoni wrote: > > > On 2014/10/20 17:16:29, shreeramk wrote: > > > > On 2014/10/20 16:31:55, dmazzoni wrote: > > > > > > > > > > > > > > > https://codereview.chromium.org/670493002/diff/1/content/app/strings/content_... > > > > > File content/app/strings/content_strings.grd (right): > > > > > > > > > > > > > > > > > > > > https://codereview.chromium.org/670493002/diff/1/content/app/strings/content_... > > > > > content/app/strings/content_strings.grd:364: <message > > > > > name="IDS_AX_ROLE_CONTENT_INFO" desc="accessibility role description for > > > > > contentinfo"> > > > > > As before, the name and description of the message should match the text > > to > > > be > > > > > translated. The translators are not going to understand what > "contentinfo" > > > is, > > > > > or its relationship to "address". > > > > > > > > Then to match and make the translator understand. Following can be used: > > > > > > > > name="IDS_AX_ROLE_ADDRESS" and desc="accessibility role description for > > > address" > > > > > > > > Is this correct/fine? > > > > > > Yes. > > > > > > This is fine - but it's often better to add more information for translators > > if > > > the word is ambiguous. Here "address" does not mean "web address (url)", but > > "a > > > section of the page containing contact information in the form of a postal > > > address". > > > > Ok. Now I think I am getting this translator related fixes properly. I was not > > completely clear on it. > > > > I think this would be more clear/unambiguous. > > > > name="IDS_AX_ROLE_CONTACT_INFORMATION" and desc="accessibility role > description > > for contact information" > > That implies that someone should translate the phrase "contact information" into > their language. We want them to translate the word "address" - but if there are > multiple meaning of "address", they should pick the one that they'd use when > talking about a person's contact information, as opposed to a web address. Ok...:) > How about: > > name="IDS_AX_ROLE_ADDRESS" and desc="accessibility role description for an > address (as in a person's contact information)" Yes. This looks fine. I ll update the CL with mentioned changes. Thanks a lot for the guidance. :)
@Dominic: PTAL! Thanks :)
shreeram.k@samsung.com changed reviewers: + jam@chromium.org
shreeram.k@samsung.com changed required reviewers: + dmazzoni@chromium.org, jam@chromium.org
lgtm
@Dominic: I think all required changes has been done in last Patchset. PTAL. Thanks :)
On 2014/10/21 18:50:37, shreeramk_OOO_2nd_Nov wrote: > @Dominic: I think all required changes has been done in last Patchset. > PTAL. > > Thanks :) @Dominic: Could you please review this CL as well? Thanks
The CQ bit was checked by dmazzoni@chromium.org
lgtm
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/670493002/40001
Message was sent while issue was closed.
Committed patchset #3 (id:40001)
Message was sent while issue was closed.
Patchset 3 (id:??) landed as https://crrev.com/b6894d59ad9f364d44b0609d0dda67a3f9d673ef Cr-Commit-Position: refs/heads/master@{#301671} |